Computers missing from WSUS Jen 7/2/2007 9:10:01 AM HELP! I accedentally deleted a computer group last week but thought that the computers would soon report back as unassigned computers... At least they have done so in the past... The thing is, I deleted the computers but then I reinstalled all of the computers with a new image (yes, I used sysprep before deploying the image ;o)). But now the computers aren't reporting as they should o WSUS. I only get ONE computer in the unassigned computes group and that one computer changes it's name back and forth... this is difficult to explain... There are a total of 22 computers in the classroom and one moment I can see computer x1 and the second time its computer x13! I am at a complete loss! I even tried to run sysprep again but it didn't help. I've changed the computers from one OU to another, still no help. What on earth can be causing this? Do I have a bug in my image? Do I have to start all over? The computers in question are installed with Windows 2000 and WSUS is running on our DC on Windows 2003 Server SP2. Please help me! Thank you!

Re: Computers missing from WSUS "Winfried Sonntag [MVP]" <Winfried.Sonntag[ at ]gmx.de> 7/2/2007 9:53:45 AM Jen schrieb: [Quoted Text] > The thing is, I deleted the computers but then I reinstalled all of the > computers with a new image (yes, I used sysprep before deploying the image > ;o)). But now the computers aren't reporting as they should o WSUS. I only > get ONE computer in the unassigned computes group and that one computer > changes it's name back and forth... this is difficult to explain... Delete the SUSID in the Registry by each Client: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate Winfried -- http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx http://www.wsuswiki.com/Home

Re: Computers missing from WSUS Jen 7/2/2007 10:56:03 AM "Winfried Sonntag [MVP]" wrote: [Quoted Text] > Jen schrieb: > > > The thing is, I deleted the computers but then I reinstalled all of the > > computers with a new image (yes, I used sysprep before deploying the image > > ;o)). But now the computers aren't reporting as they should o WSUS. I only > > get ONE computer in the unassigned computes group and that one computer > > changes it's name back and forth... this is difficult to explain... > > Delete the SUSID in the Registry by each Client: > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate > > Winfried > -- > http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx > http://www.wsuswiki.com/Home > No change... :'(

Re: Computers missing from WSUS "Winfried Sonntag [MVP]" <Winfried.Sonntag[ at ]gmx.de> 7/2/2007 11:21:36 AM Jen schrieb: [Quoted Text] >>> The thing is, I deleted the computers but then I reinstalled all of the >>> computers with a new image (yes, I used sysprep before deploying the image >>> ;o)). But now the computers aren't reporting as they should o WSUS. I only >>> get ONE computer in the unassigned computes group and that one computer >>> changes it's name back and forth... this is difficult to explain... >> >> Delete the SUSID in the Registry by each Client: >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate > > No change... :'( What you mean with: No Change? Delete the Client in the WSUS-Console and use this Script: http://msmvps.com/blogs/athif/pages/66376.aspx Winfried -- http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx http://www.wsuswiki.com/Home

Re: Computers missing from WSUS "gil.qi.zhang[ at ]gmail.com" <gil.qi.zhang[ at ]gmail.com> 7/2/2007 2:59:29 PM On Jul 2, 7:21 pm, "Winfried Sonntag [MVP]" <Winfried.Sonn...[ at ]gmx.de> wrote: [Quoted Text] > Jen schrieb: > > >>> The thing is, I deleted the computers but then I reinstalled all of the > >>> computers with a new image (yes, I used sysprep before deploying the image > >>> ;o)). But now the computers aren't reporting as they should o WSUS. I only > >>> get ONE computer in the unassigned computes group and that one computer > >>> changes it's name back and forth... this is difficult to explain... > > >> Delete the SUSID in the Registry by each Client: > >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate > > > No change... :'( > > What you mean with: No Change? Delete the Client in the WSUS-Console and > use this Script:http://msmvps.com/blogs/athif/pages/66376.aspx > > Winfried > --http://www.microsoft.com/germany/windowsserver2003/technologien/updat...http://www.wsuswiki.com/Home Using NewSID to change SID for each client. NewSID can be download from Microsoft, including in SysInternal Suite.

Re: Computers missing from WSUS "gil.qi.zhang[ at ]gmail.com" <gil.qi.zhang[ at ]gmail.com> 7/2/2007 3:14:03 PM On Jul 2, 10:59 pm, "gil.qi.zh...[ at ]gmail.com" <gil.qi.zh...[ at ]gmail.com> wrote: [Quoted Text] > On Jul 2, 7:21 pm, "Winfried Sonntag [MVP]" <Winfried.Sonn...[ at ]gmx.de> > wrote: > > > > > Jen schrieb: > > > >>> The thing is, I deleted the computers but then I reinstalled all of the > > >>> computers with a new image (yes, I used sysprep before deploying the image > > >>> ;o)). But now the computers aren't reporting as they should o WSUS. I only > > >>> get ONE computer in the unassigned computes group and that one computer > > >>> changes it's name back and forth... this is difficult to explain... > > > >> Delete the SUSID in the Registry by each Client: > > >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate > > > > No change... :'( > > > What you mean with: No Change? Delete the Client in the WSUS-Console and > > use this Script:http://msmvps.com/blogs/athif/pages/66376.aspx > > > Winfried > > --http://www.microsoft.com/germany/windowsserver2003/technologien/updat... > > Using NewSID to change SID for each client. NewSID can be download > from Microsoft, including in SysInternal Suite. BTW, check your sysprep. Ensure do not use -nosidgen switch.

Re: Computers missing from WSUS "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/2/2007 4:32:41 PM "Jen" <Jen[ at ]discussions.microsoft.com> wrote in message news:6C531C4D-53FB-4591-99A0-24F8FE49AFB8[ at ]microsoft.com... [Quoted Text] > HELP! > I accedentally deleted a computer group last week but thought that the > computers would soon report back as unassigned computers... At least they > have done so in the past... Not if you're using client-side targeting and the target group is set by policy. In this case, all that you need to do is recreate the deleted group name. > The thing is, I deleted the computers Oh... that's kind of totally different from "accidentally deleted the computer group". In fact, pretty much makes the lead point irrelevant! :-) > but then I reinstalled all of the > computers with a new image (yes, I used sysprep before deploying the image > ;o)). > But now the computers aren't reporting as they should o WSUS. I only > get ONE computer in the unassigned computes group and that one computer > changes it's name back and forth... CLASSIC symptom of not properly prepping the image. > this is difficult to explain... Not all all.... you explained it perfectly, and we've seen it a gazillion times. It's directly a function of improperly using sysprep. Did you use the *RESEAL* parameter with sysprep? That's a required parameter in this scenario == particularly if you used WSUS or WU/MU to update your image prior to the sysprep! As partially explained by Winfried -- this is the remediation required: [1] Delete the SusID value in the registry key HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate BUT, (the steps he didn't include) you also need to: [2] Delete the AccountDomainSID value in the same registry key [3] Restart the Automatic Updates service -or- Reboot the system. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Computers missing from WSUS Jen 7/3/2007 7:18:01 AM THANK YOU THANK YOU THANK YOU!!! Now the computers are reporting to WSUS! I think the problem was with how I ran sysprep... I just double-clicked the application and that was it... guess I have to familiarise myself with the different parameters ;o). The problem was solved by doing as Lawrence Garvin, Winfrien Sonntag and Gil Qi Zhang said: net stop wuauserv Deleted the SusID value in the registry key from HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate (the other registry keys weren't found on the computers) net start wuauserv and finally I ran wuauclt /resetauthorization /detectnow and now everything seems to be working and reporting as it should be! Thanks guys for saving my holiday :D! This thing was driving me crazy and I'm such a BIG WSUS-fan! "Lawrence Garvin (MVP)" wrote: [Quoted Text] > > "Jen" <Jen[ at ]discussions.microsoft.com> wrote in message > news:6C531C4D-53FB-4591-99A0-24F8FE49AFB8[ at ]microsoft.com... > > HELP! > > I accedentally deleted a computer group last week but thought that the > > computers would soon report back as unassigned computers... At least they > > have done so in the past... > > Not if you're using client-side targeting and the target group is set by > policy. > > In this case, all that you need to do is recreate the deleted group name. > > > > The thing is, I deleted the computers > > Oh... that's kind of totally different from "accidentally deleted the > computer group". In fact, pretty much makes the lead point irrelevant! :-) > > > but then I reinstalled all of the > > computers with a new image (yes, I used sysprep before deploying the image > > ;o)). > > > But now the computers aren't reporting as they should o WSUS. I only > > get ONE computer in the unassigned computes group and that one computer > > changes it's name back and forth... > > CLASSIC symptom of not properly prepping the image. > > > > this is difficult to explain... > > Not all all.... you explained it perfectly, and we've seen it a gazillion > times. > > It's directly a function of improperly using sysprep. Did you use the > *RESEAL* parameter with sysprep? That's a required parameter in this > scenario == particularly if you used WSUS or WU/MU to update your image > prior to the sysprep! > > > As partially explained by Winfried -- this is the remediation required: > > [1] Delete the SusID value in the registry key > HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate > > BUT, (the steps he didn't include) you also need to: > > [2] Delete the AccountDomainSID value in the same registry key > [3] Restart the Automatic Updates service -or- Reboot the system. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > > >