Only half true. The best way to do is it to assign the SUS klient software to the computers you are going to manage, trough the same AD policy as you configure SUS. (The MSI files are preconfigured and ready for AD deployment. This way a pre-sp3 computer starts up, gets the client and the configuration, and the first download would be the latest servicepack. By doing it like this, you eliminate the need for SP1(XP) and SP3(2000). Mvh Svein Arild -----Opprinnelig melding----- Fra: Phil Smith [mailto:psmith@xxxxxxxxxxxxxx] Sendt: 4. juni 2004 14:14 Til: 'windows2000@xxxxxxxxxxxxx' Emne: [windows2000] Re: SUS Has the policy taken effect on the workstation? You can check by going to the control panel and opening Automatic Updates and seeing if it is grayed out or if you can make modifications to it. If you can modify it then the client has not gotten the policy yet. Win2k clients must have at least SP3 XP clients must have at least SP1 Check this community web page http://www.susserver.com lots of good info for SUS there. -----Original Message----- From: Mark Cook [mailto:mc@xxxxxxxxxx] Sent: Friday, June 04, 2004 7:02 AM To: 'windows2000@xxxxxxxxxxxxx' Subject: [windows2000] SUS Stumbling from bloody RIS to SUS now I'm afraid, life's one big acronym :-) Our SUS seems to have stopped working, or at least part of it. The main SUS server sync's with MS each day no problem, we approve what we want/need to and the Domain Policy is set to apply this to all PC's at 7am. Now here's the strange thing - only some PC's get the updates / others show absolutely no sign of activity in that area - yet all PC's are SP4 Win2K PRO ! The policy is set to tell the clients to locate the SUS server by it's IP address so no resolution issues ? Anyone got any suggestions or seen this before ? Cheers Mark