WSUS
.. WSUS FAQ
.. WSUS on SBS
.. WSUS Troubleshooting
.. WSUS News Groups
.. Known WSUS Issues
.. WSUS Links
.. WSUS Wish List
WSUS Documents
.. WSUS Deployment Guide
.. WSUS Installation Guide
.. WSUS Release Notes
.. WSUS Best Practice
SUS
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. Wiki Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page
Miscellaneous Stuff
.. Other Resources
.. Do You Know?
Terms of Use
Trademarks
Privacy Statement
Troubleshooting Client Targeting |
If you are having troubles with targeting updates, check the following:
1. How did you do the Targetting?
Make sure the target group names on the client match target group names on the WSUS server.
2. Are the target groups created?
Make sure you have followed the advice on the Creating Target Groups page to create the groups on both the Server and at the Client.
3. Ensure that the AU updates have been applied applied to the client. One way to do this is to check the registry entries on the client by running the following from command prompt:
Reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /s
4. Is WUS installed on Default Website??
If your client policies are setup to point to the default web site for updating, check that WSUS is also installed in Default Website. If not, you can change this by running the script %Program Files%\MicrosoftWindowsUpdate\Services\"SetupInstallSelfupdateOnPort80.vbs.
Comments:
From chmeehan - 1/29/07 11:55 AM
From Siminole1 - 5/29/06 4:04 AM
Having problems with the SusClientid being the same on several servers or computers? I did and I found the fix. What was happening was clients were updating to the WSUS fine but overwriting each other due to having the same SusClientid. To check to see if you have duplicate ID's go to:
HKLM\Software\Microsoft\Windows\CurrentVersion\Windowsupdate
Check the SusClientID and see if it matches the others. If so, to fix this problem, delete the SusClientID and also the AccountDomainSID. This will require a reboot after the change. After boot go to the same registry (HKLM\Software\Microsoft\Windows\CurrentVersion\Windowsupdate) and check to see if a new SusClientID and AccountDomainSID are there. If not, goto command line and run
wuauclt /resetauthorization /detectnow
Perform a refresh on the registry and you should see the new ID's and it should now report to the WSUS fine. Hope this helps anyone who is having issues with this.
From spaceboy - 3/31/05 3:50 AM
How does it currently work wiht the Client-side targeting via registry keys? What should I do to target a client via reg keys?
spacenoynr1@web.de
From wab2000 - 3/11/05 9:32 AM
Help
Last Modified 3/22/05 2:59 PM
FYI.... An alternate to reboot the server / workstation if it can not be done in the middle of the day is to perform the following
steps.
The new IDs & SIDs should appear and the system should show up in the correct target group.