Microsoft KB Archive/903262

= A Windows 2000-based or Windows XP-based computer that was set up by using a Windows 2000 or Windows XP image does not appear in the Windows Server Update Services (WSUS) console =

Article ID: 903262

Article Last Modified on 1/29/2007

-

APPLIES TO

 Microsoft Windows XP Service Pack 2, when used with:  Microsoft Windows XP Professional

 Microsoft Windows XP Tablet PC Edition

 Microsoft Windows XP Home Edition

 Microsoft Windows XP Media Center Edition 2002</li></ul> </li> Microsoft Windows 2000 Server</li> Microsoft Windows 2000 Professional Edition</li> Microsoft Windows 2000 Advanced Server</li></ul>

-

<div class="notice_section">

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

<div class="symptoms_section">

SYMPTOMS
A Microsoft Windows 2000-based or Microsoft Windows XP-based computer does not appear in the Windows Server Update Services (WSUS) console. This symptom occurs if the Windows 2000-based or Windows XP-based computer was set up by using a Windows 2000 or Windows XP image. This symptom only occurs if the image was not created by Sysprep or other unique SID-generating technology.

<div class="cause_section">

CAUSE
This behavior occurs because the imaged clients may have a duplicate SusClientID value in the registry.

<div class="resolution_section">

RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, follow these steps on the Windows 2000-based or Windows XP-based computer was set up by using a Windows 2000 or Windows XP image: <ol> Click Start, click Run, type cmd in the Open box, and then click OK.</li> At the command prompt, type net stop wuauserv, and then press ENTER.</li> Click Start, click Run, type regedit in the Open box, and then click OK.</li> Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

</li> In the right pane of Registry Editor, delete the following registry entries:  PingID</li> AccountDomainSid</li> SusClientId</li></ul> </li> Quit Registry Editor.</li> At the command prompt, type net start wuauserv, and then press ENTER.</li> At the command prompt, type wuauclt.exe /resetauthorization /detectnow, and then press ENTER.</li> Wait 10 minutes for a detection cycle to finish.</li> <li>Start the WSUS console to make sure that the clients appear in the WSUS console.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
The first Windows 2000-based or Windows XP-based computer that was set up by using a Windows 2000 or Windows XP image appears in the WSUS console. However, subsequent Windows 2000-based or Windows XP-based computers that were set up by using the same Windows 2000 or Windows XP image do not appear. This symptom occurs because the first Windows 2000-based or Windows XP-based computer that was set up by using a Windows 2000 or Windows XP image is using the same SusClientID value. After you follow the steps that are described in the &quot;Resolution&quot; section, a new SusClientID value is created.Additionally, subsequent Windows 2000-based or Windows XP-based computers that were set up by using the same Windows 2000 or Windows XP image appear in the WSUS console.

Keywords: kbdeployment kbtshoot kbprb KB903262

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.