Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
That's not really how Windows servers work. Most large enterprises are likely going to be using WSUS or other patch management for updates where you can choose exactly which patches you want and when to do them. Those updates do almost always require reboots, but again you can schedule those reboots at a time of your choosing.
Even without WSUS, you can disable automatic updates and reboots. Plenty of Windows servers sitting there unpatched with uptime in years.
For sure, I honestly just added that bit so it would sound like i knew what i was talking about at least a little bit.
Also the idea of a windows server having an uptime in years gives me chills in a bad way.
They hopefully mostly sit inside an unexposed subnet and aren't reachable from the internet, but I've seen several companies running their public facing production applications on an unpatched EOLed Windows that hasn't been rebooted in years because the person who set it up no longer works there and they're afraid to find out what one time scripts he ran to get the system running without setting up any persistence.