• 0 Posts
  • 18 Comments
Joined 7 months ago
cake
Cake day: March 3rd, 2024

help-circle


  • LetsEncrypt is legit. A downside is that the certs expire after 90 days. However, that also carries an upside in that it limits the damage in case a certificate is compromised. There are procedures by which you can automatically renew/request (I forget whether they allow renewing an existing cert or require a brand new one) LE certs and apply them to your application, but that can be fiddly to configure.

    If you’re not comfortable with configuring automatic certificate cycling, a long-term paid cert would be more appropriate.



  • Desktop background (or other theme stuff) - easiest way is to just reset that to what you want.

    The arrow overlay on .lnk files, you could check regedit HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer for a “Shell Icons” key (“subfolder”), which should only be there if it was added manually, but I’d be interested in what it was if it was there.

    You could also try rebuilding the icon cache.

    I have to think that both of these have something to do with the system looking in the “old” place for the desktop background image and the icon cache, and not finding them there.


  • I am aware that on a Windows machine, turning on a OneDrive subscription (or at least an E5 license, is where I’m very specifically talking about), certain folders get moved from c:\users\[username] into c:\users\[username]\OneDrive. Then OneDrive syncs those locations up to 365.

    If you just open cmd (not as admin), it will put you at c:\users\[username] and then if you just cd desktop … yeah, that’s empy now. dir in c:\users\[username] and I bet you’ll find a OneDrive folder.

    Of note, the default user folder paths that get changed are \Attachments \Desktop \Documents \Pictures. \Downloads stays at c:\users\[username]\downloads




  • Nougat@fedia.iotoLinux@lemmy.mlWhy do you still hate Windows?
    link
    fedilink
    arrow-up
    3
    arrow-down
    3
    ·
    3 months ago

    The PIN is stored locally on the machine only. It doesn’t get synced with anything anywhere. It’s actually much safer to use a PIN for authentication because it’s four digits that you (well, maybe not you) don’t have to write down, and the only time it works is on the physical machine. The user account password can be long and/or complex, but if you’re only ever authenticating at the keyboard, all you have to remember is the PIN.



  • No.

    If you’re talking about desktops, there is a huge cost involved in switching to an entirely new operating system. I’m not just talking about “How do you get it installed and configured on n laptops for users to then use?” Those users will require training in order to use it - and allllll of the new and different applications that run on that new operating system. (Users are mainly just button pressers, and when you change the buttons …) The alternative to the above would simply be to disable Recall via group policy. Done and done.

    If you’re talking about migrating Active Directory to some Linux LDAP centralized authentication, that’s going to introduce a whole lot of other complications. Not impossible, no, but it would be a very long, time-consuming, and costly process.

    If you’re talking about servers, you surely know that lots of companies run Linux servers on the back end. When you’re using Windows servers, there’s a reason. You want/need to use MS SQL, or Exchange on premise, or SharePoint on premise, for example. Are there other mail servers, database servers, collaboration servers? Sure - but again, switching from an existing platform to a different platform is costly.

    These transition costs get exponentially higher when you consider whether companies actually have the in-house expertise to be able to pull off such a thing (Narrator: They don’t.)