Nice, I did the same for my blog. Didn't want to build a whole comment system when Lemmy fits the bill quite nicely :)
Yes, and that is where we enter the complicated territories..
I'm sorry, but have you ever needed to manage some certificates for a legacy system or something that isn't just a simple public facing webserver?
Automation becomes complicated very quickly. And you don't want to give DNS mutation access to all those systems to renew with DNS-01.
We call that percussive maintenance.. the brick is optional.
That's good advice, we will. Thank you.
Thankfully Microsoft is a thrustworthy partner with the users best interests in mind. /s
At home Proxmox works reall well. When our VMWare licenses expire we'll certainly evaluate that as option.
Wasn't really aimed at you but from the things I've seen I am afraid not all Windows administrators might realize that.
And probably as a security update as well.
Installing Word, on a server, running as administrator, forecefully linked to some MS account for activation... Is that really a reasonable solution in a Microsoft world? Smh.
If documentation comes as Word document there is no documentation and a huge red flag for the software.
This is the best answer. I've been doing it for years at work. Dual-booting is just very inconvenient and WSL(2) is the worst of both worlds.
Install Linux on the machine and keep windows in a nice secure kvm-based cage where it can do less damage.
I'm sorry, you're arguing in bad faith or have a huge case of Stockholm Syndrome.
But, just look at their Troubleshooting documentation where they tell you to drop to the terminal.
My point is that Microsoft has stopped making new buttons and dropdowns and refer you to new Powershell incantations for most new settings. Just look at how many options the new "Settings" app offers compared to the deprecated Control Panel.
Ha sure, although since it is not well traveled there aren't any Lemmy comments yet. But you're very welcome to visit..
See: Gele Sneeuw