Windows Forum

Ask something
Discussion Locked

SUS updates to NT4/2K Servers?

0 helpful
3 replies

by Member 32019386

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Hi All -- We currently push SUS updates to all XP clients and force them to reboot -- this works fine. I'd like to push SUS updates to my 20+ NT4/2K SERVERS and NOT have them reboot. This way the servers are always updated automagically (atleast a week or two behind the desktops). I'd like to schedule a server reboot after the SUS pushes to make sure the OS is always stable. I would like to get some ideas/comments/best practice scenarios...I've searched but haven't seen anything like this. This would save me much mundane NT admin time. Any help/tips would be great. Thanks in advance. Pete.

3 replies

by ewgny

You can make a new SUS group policy and apply it to your server OU and Domain Controller OU. Set that policy not reboot the Servers. Then you can reboot them yourself if needed and when it is best.
I personally do not use SUS for my servers, since I only have 8. I like to update emergency repair disks, and test the updates one server at a time.
If you want to have the Servers update a week after the workstations, you can just remove the Group policy from the Server & DC OU and reapply it when you are ready to deploy the updates.
(You actually may have to apply an SUS "not configured" GP after you remove the SUS policy to ensure that they won't update)
Group policy will work for your 2k Servers. How many NT servers do you have and how are you currently updating them ??

This discussion is closed to new replies.