The time you assign is only the time to install updates. A computer who are by a policy configured to use SUS check for updates every 24 hours. It does not check for updates at 7am, this wopuld cause a massive traffic increase at 7am. This means if you authorize a update in SUS Admin, some computers might not download this package for 23 hours. Thus not install anything the next 7am Mvh Svein Arild -----Opprinnelig melding----- Fra: Mark Cook [mailto:mc@xxxxxxxxxx] Sendt: 4. juni 2004 13:02 Til: 'windows2000@xxxxxxxxxxxxx' Emne: [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