I'm looking for advice on how to handle updates for critical Windows servers and workstations that absolutely cannot reboot on their own. We're in an environment using SCCM, but no matter what I try, some machines still update and reboot unexpectedly. I need to ensure these machines are locked down to prevent any automatic booting. Any tips on how to manage this effectively?
3 Answers
It's worth focusing on making your services fault-tolerant across multiple servers. This way, you can schedule reboots without affecting availability. If the app is running on multiple servers, you can bring them down one at a time for maintenance.
Honestly, if these servers are critical, you need to set up redundancy. Ideally, have at least three servers running the same services. That way, even if one goes down, your system keeps running smoothly. Plus, make sure they're in different groups to avoid simultaneous updates.
If your servers are that vital, have you considered redundancy? This way, while one is being updated, the service remains available to users. Might save you from unexpected outages!
Great point! Multiple servers with load balancing can ensure uptime even during updates.