U.S. seeing only18 at a time "John G Howard" <mailto[ at ]NOSPAM.ncmb.uscourts.gov> 10/31/2008 7:10:40 PM I have a new installation of WSUS 3.0 on a 2003 server. In the Update Services console, I never see more than 18 computers reporting, and it's evident that when a new one is detected, one is dropped. Is this by design? I can't see any reference to suggest that. Also, the clients are being directed via Group Policy. It seems that running gpupdate /force isn't enough to a client to appear in U.S., but a reboot is required. That's a lot of manual messing around! Is something wrong in what I'm doing?

Re: U.S. seeing only18 at a time "Lawrence Garvin \(MVP\)" <lawrence[ at ]nospam> 10/31/2008 7:52:02 PM "John G Howard" <mailto[ at ]NOSPAM.ncmb.uscourts.gov> wrote in message news:gefl7i$j31$1[ at ]coronis.nyed.circ2.dcn... [Quoted Text] >I have a new installation of WSUS 3.0 on a 2003 server. In the Update >Services console, I never see more than 18 computers reporting, and it's >evident that when a new one is detected, one is dropped. Is this by >design? Well sorta.... <VBG>... it's "by the design" you used to clone your systems. :-) It's caused by duplicated SusClientID values in the registry. 1. Shutdown the Automatic Updates service (net stop wuauserv). 2. Delete the values i HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate (but not from any of the subkeys!) 3. Restart the Automatic Updates service (net start wuauserv). > Also, the clients are being directed via Group Policy. It seems that > running gpupdate /force isn't enough to a client to appear in U.S., but a > reboot is required. That's a lot of manual messing around! Is something > wrong in what I'm doing? Yes. No reboot is required. 'gupdate /force /target:computer' will update the computer policies, which will trigger a reload of the WUA configuration data, which *may* trigger an immediate detection event, depending on what, if any, configuration values were changed. This all will be logged in %windir%\WindowsUpdate.log. Now, what you could be observing happening is that the policy refresh doesn't contain a value that would trigger a detection, thus the client doesn't appear, but a restart does (possibly because the previous detection failed -- or doesn't exist). This can also be determined by reviewing %windir%\WindowsUpdate.log at the time of the policy refresh. -- Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009) MS WSUS Website: http://www.microsoft.com/wsus My Websites: http://www.onsitechsolutions.com; http://wsusinfo.onsitechsolutions.com My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Re: U.S. seeing only18 at a time "John G Howard" <mailto[ at ]NOSPAM.ncmb.uscourts.gov> 10/31/2008 8:28:28 PM What an informed, thorough reply. Thanks, Lawrence, I appreciate it. J "Lawrence Garvin (MVP)" <lawrence[ at ]nospam> wrote in message news:eFV4lI5OJHA.2292[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > "John G Howard" <mailto[ at ]NOSPAM.ncmb.uscourts.gov> wrote in message > news:gefl7i$j31$1[ at ]coronis.nyed.circ2.dcn... >>I have a new installation of WSUS 3.0 on a 2003 server. In the Update >>Services console, I never see more than 18 computers reporting, and it's >>evident that when a new one is detected, one is dropped. Is this by >>design? > > Well sorta.... <VBG>... it's "by the design" you used to clone your > systems. :-) > > It's caused by duplicated SusClientID values in the registry. > > 1. Shutdown the Automatic Updates service (net stop wuauserv). > 2. Delete the values i > HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate (but not from > any of the subkeys!) > 3. Restart the Automatic Updates service (net start wuauserv). > >> Also, the clients are being directed via Group Policy. It seems that >> running gpupdate /force isn't enough to a client to appear in U.S., but a >> reboot is required. That's a lot of manual messing around! Is something >> wrong in what I'm doing? > > Yes. > > No reboot is required. 'gupdate /force /target:computer' will update the > computer policies, which will trigger a reload of the WUA configuration > data, which *may* trigger an immediate detection event, depending on what, > if any, configuration values were changed. This all will be logged in > %windir%\WindowsUpdate.log. > > Now, what you could be observing happening is that the policy refresh > doesn't contain a value that would trigger a detection, thus the client > doesn't appear, but a restart does (possibly because the previous > detection failed -- or doesn't exist). This can also be determined by > reviewing %windir%\WindowsUpdate.log at the time of the policy refresh. > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus > My Websites: http://www.onsitechsolutions.com; > http://wsusinfo.onsitechsolutions.com > My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin >