January 8th, 2004, 05:47 PM
After you deploy the SUS server, you need to make sure all of your clients have at least Windows 2000 service pack 3, which is required for the automatic update client to point to a corporate SUS server. Also, eash of the clients needs to be configured to point to your corporate SUS server. The easiest way to do this is through Active Directory group policy, though the settings can be applied manually. For more information, see Microsoft's SUS Deployment White Paper, available here:
While SUS does a good job of determining what patches particular clients may need, it is not very controllable in how it reboots your client workstations. My recommendation is a system like SMS for the majority of the patch installations, with SUS being used to cover any clients missed by SMS.
January 8th, 2004, 10:23 PM
If you check my tutorial that I post in my last post, you'll see a Batch File Wake on Lan Utilites. At work, I use this utilites to open all my computer at 4:30am the Tuesday. I force the update to be apply at 5am so no user are bug!
While SUS does a good job of determining what patches particular clients may need, it is not very controllable in how it reboots your client workstations.