Just a lvl 29 guy from Finland. Full-stack web developer and Scrum Master by trade, but actually more into server-side programming, networking, and sysadmin stuff.
During the summer, I love trekking, camping, open water swimming and going on long hiking adventures. Also somewhat of an avgeek and a huge Lego fanatic.
A furry or something. Why be yourself when you can be a fluffy raccoon on the internet?
It works great when you log in as a user like you normally would on a Windows pc. But on a server you want it to run as a service, starting automatically in the background and/or being managed by the failover cluster without requiring a user to log in.
The solution back then was to use netplwiz autologon. Obviously a hack and bad for security, but fine for a homelab. After googling it now, it looks like some other “solutions” are documented in the GitHub issue about this.
Asking out of curiosity: is there a specific reason you’re running Windows on your server? I used to do the same on my home servers because that’s what we used to have at work, and I wanted to learn and test some stuff. But it was a difficult road, to put it mildly. Simple things, like getting Docker autostart on boot seemed almost impossible. At some point I just gave up and switched to Linux.
I run Debian on my homelab and manage Ubuntu Servers at work. I haven’t seen any practical differences between the two. Sometimes you might get a bit newer version of something from the Ubuntu repositories than from the Debian ones but not even once has that been an issue and most of stuff I use come from 3rd party repositories anyway.