WSUS - Computer status listed as "Not Yet Reported"

[Ladybug]

We have been using WSUS for approximately 3 months.....with many problems,
all of which I have been able to resolve until now. In addition we upgraded
to XP\SP2 within the last 3 months. Currently I am showing about 40 machines
in the Computer Console with a status of "Not Yet Reported". We have tried
several fixes, but without success, to include:

- running the fix for AU and BITS because the services kept stopping
- stopping the AU and WMI services and deleting the contents of the Software
Distribution folder and the WBEM\Repository folder.....deleting the following
registry keys under WindowsUpdate: SUSClientID, AccountDomainSid, restarting
AU and WMI.
- removing a few of the computers from the Computer Console and then running
the following command on the client computer: wuauclt.exe
/resetauthorization /detectnow

Note: We do clone our drives, but did use a SID changing tool when we
deployed the drives. However, there still is a possibility that some of the
drives didn't have the utility run on them. With that said, it is my
understanding that if the SIDs are the same, the machines would just appear
and disappear on the WSUS Computer Console (we've experienced this problem
also).

Any suggestions would be greatly appreciated. One this is corrected, I
think we will finally be running smoothly.

[mskaren911]

Give this a try:

Go to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate and
delete:

PingID
AccountDomainSid
SusClientId
And then restart the WSUS client-side service. Then run wuauclt.exe
/resetauthorization /detectnow

Post by Ladybug
We have been using WSUS for approximately 3 months.....with many problems,
all of which I have been able to resolve until now. In addition we upgraded
to XP\SP2 within the last 3 months. Currently I am showing about 40 machines
in the Computer Console with a status of "Not Yet Reported". We have tried
- running the fix for AU and BITS because the services kept stopping
- stopping the AU and WMI services and deleting the contents of the Software
Distribution folder and the WBEM\Repository folder.....deleting the following
registry keys under WindowsUpdate: SUSClientID, AccountDomainSid, restarting
AU and WMI.
- removing a few of the computers from the Computer Console and then running
the following command on the client computer: wuauclt.exe
/resetauthorization /detectnow
Note: We do clone our drives, but did use a SID changing tool when we
deployed the drives. However, there still is a possibility that some of the
drives didn't have the utility run on them. With that said, it is my
understanding that if the SIDs are the same, the machines would just appear
and disappear on the WSUS Computer Console (we've experienced this problem
also).
Any suggestions would be greatly appreciated. One this is corrected, I
think we will finally be running smoothly.

[mskaren911]

Give this a try:

Go to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate and
delete:

PingID
AccountDomainSid
SusClientId
And then restart the WSUS client-side service. Then run wuauclt.exe
/resetauthorization /detectnow

Post by Ladybug
We have been using WSUS for approximately 3 months.....with many problems,
all of which I have been able to resolve until now. In addition we upgraded
to XP\SP2 within the last 3 months. Currently I am showing about 40 machines
in the Computer Console with a status of "Not Yet Reported". We have tried
- running the fix for AU and BITS because the services kept stopping
- stopping the AU and WMI services and deleting the contents of the Software
Distribution folder and the WBEM\Repository folder.....deleting the following
registry keys under WindowsUpdate: SUSClientID, AccountDomainSid, restarting
AU and WMI.
- removing a few of the computers from the Computer Console and then running
the following command on the client computer: wuauclt.exe
/resetauthorization /detectnow
Note: We do clone our drives, but did use a SID changing tool when we
deployed the drives. However, there still is a possibility that some of the
drives didn't have the utility run on them. With that said, it is my
understanding that if the SIDs are the same, the machines would just appear
and disappear on the WSUS Computer Console (we've experienced this problem
also).
Any suggestions would be greatly appreciated. One this is corrected, I
think we will finally be running smoothly.