• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 493
  • Last Modified:

Some clients not showing up in the WSUS console.

Not sure whats going on but I just started deploying WSUS and about 4 of the 15 workstations that I applied the policy to are not showing up in the WSUS console. I know the workstation is getting the policy because I run gpresult and sure enough, the WSUS policy is applied. Also, the Updates applet in control panel has all grayed out settings so it looks like its being applied. I just don't see the workstations in the console. Anyone else experience this?
0
mikedotm
Asked:
mikedotm
  • 4
  • 3
  • 2
1 Solution
 
Netman66Commented:
Were these workstations imaged?   Did you use Sysprep if they are?

If the client SIDs are the same they will simply overwrite each other as they report.

0
 
mikedotmAuthor Commented:
The clients were imaged but we use Sysprep to create the image. I know this because the ones that are showing up were imaged also the same way the ones that are not showing up. Its something I never thought of however.
0
 
Netman66Commented:
Ok then, let's try something on one of the workstations that isn't reporting properly:

Copy this to a CMD file:

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f
cls
@echo Triggering detection after resetting WSUS client identity
net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow

Run it on from one of the misbehaving PCs.  Let ne know if it shows up.

Reference: http://www.wsuswiki.com/ClientFAQ
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
mikedotmAuthor Commented:
These commands did not work, but I just found out that the workstations I am having problems with were built with an image and sysprep was not run on them. Apparently there is some issue with sysprep and SP2 of XP that has something to do with profile moving or creation. Anyway, we are going to test this out by running a utility called
New SID on one of the problem workstations. If it shows up in WSUS after this, then we know for sure that is the issue.
I found out from my Help Desk that over 500 of these laptops were given out like this (no sysprep) so I have a lot of work to do.
0
 
oBdACommented:
Just for the record: you not only have a lot of work to do, you also have lost any chance of getting support from Microsoft for those machines, should you ever require it: "Microsoft does not provide support for computers that are set up by use of SID-duplicating tools other than the System Preparation tool. If an image was created without the use of sysprep, Microsoft does not support the running of Sysprep after the image is deployed as a way to bring the computer back into compliance."
The Microsoft Policy Concerning Disk Duplication of Windows XP Installations
http://support.microsoft.com/?kbid=314828

With more than 500 users, the Help Desk should know better ...
0
 
Netman66Commented:
I'd say so.

All those machines not only don't report to WSUS, but also share the same SID in the domain...

You can run Sysprep on all of them now, it'll just go through the mini-setup wizard when you reboot.  You'll have to put the workstations into Workgroup first and delete the computer account then rejoin them.

Lots of work for sure.

0
 
mikedotmAuthor Commented:
Yes indeed. I may have over estimated a bit on the amount. I went back and asked again. Its not 500 but its a lot. Thanks for your help in this.
0
 
Netman66Commented:
My solution - get the staff that made the mistake to fix it.  They won't learn anything unless they have to fix their own work.  Given the scope of this issue, they'll never again forget or ignore the correct procedure for imaging!

I know, I'm a bit of a PR#*@!  :o)





0
 
oBdACommented:
Running sysprep now won't help with the support, though; note the comment from above: " If an image was created without the use of sysprep, Microsoft does not support the running of Sysprep after the image is deployed as a way to bring the computer back into compliance."
The image that is deployed has to be prepared with Sysprep, so basically the helpdesk should re-rollout the machines with a properly created image ...
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now