asked on

Computers not reporting to WSUS server

Dear experts,

I'm building a SCCM12 Lab to toy with. Infrastructure is:

- 1 CAS
- 1 Primary
- 1 DC

Both the CAS and Primary servers are WSUS/SUP enabled, with the CAS synchronizing with Microsoft while the Primary is synchronizing with the CAS (upstream synch). Databases are SQL Server 2008 R2 Standard.

WSUS settings are deployed through GPO, assigned to all 3 computers, specifying the Primary server as source.

After some initial problems and research I installed http://support.microsoft.com/kb/2720211 on both servers.

I successfully deployed the SCCM 12 Client as an Update on all machines. But that was my only success:

- All computers, when I manually check for updates, will tell me that I am up to date
- All computers still appear as "not yet reported" in the WSUS console on the Primary server.

I've checked the %windir%\WindowsUpdate.log on all machines, and they show this error:checkupdates.txt

I tried to run a wuauclt /resetauthorization /detectnow on all machines, it looks like it works fine, as shown in the log: resetauth.txt

..but the machines will stay as "not yet reported", and the GetCookie error shown in the first log will eventually appear again after some time.

Most of the similar issues I find on the web talk about an Office 2003 update...this doesn't apply in my case.

Any idea what else I could try to troubleshoot the issue?

Thank you in advance.

Don

Are your client pc's imaged/cloned ??

http://blogs.technet.com/b/sus/archive/2009/05/05/resolving-the-duplicate-susclientid-issue-or-why-don-t-all-my-clients-show-up-in-the-wsus-console.aspx

uescomp

Are the clients able to resolve to the WSUS http? Like http://wsusserver:port#

If you can make it to the site it should ask or prompt you to download/save a file.

abissa

ASKER

-> dstewartjr

Thanks for the suggestion. Actually the 3 machines were cloned and sysprepped. Anyway I checked, and:

- The DC doesn't have any reg key under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

- Both the CAS and Primary have 2 keys there: SusClientId and SusClientIdValidation - both different on both machines...but no PingId nor AccountDomainSid as specified in your link. I guess the DC not having any key at all is not normal...

To clarify my OP, all 3 machines are showing up in WSUS on the Primary, under "Unassigned computers" with the "Not yet reported" status.

-> uescomp

You may have found an interesting lead there...the AD and the CAS, when trying to open the webpage, show a Server Error - 403 Forbidden: Access is denied.

On the server itself (the Primary), I got a Server Error

HTTP Error 403.14 - Forbidden
The Web Server is configured to not list the contents of this directory.

Is there an auto-repair or something I could run to have default document and/or rights restored, or should I manually toy with the IIS settings?

Don

Go over the WSUS survival guide here

http://social.technet.microsoft.com/wiki/contents/articles/2491.wsus-troubleshooting-survival-guide.aspx

uescomp

I would check your windows firewall, updates can sometimes turn the firewall back on so clients might reject GPO or the server is not allowing the connection etc. Just a peek

Don

0x8024400D Is not indication of a firewall issue

@abissa

Did you delete those reg keys anyway and run wuauclt /resetauthorization /detectnow ??
(Or run the .BAT from the Blog)

abissa

ASKER

So first of all after some research, it's normal I get this 403 errors when trying to browse to http://server.
But individual files can be targeted, and then it works fine and gives me a save/open prompt, for example: http://server:port/iuident.cab

This works on all 3 machines.

@dstewartjr

Yes I did check the reg keys mentioned in the document and run a crazy amount of run wuauclt /resetauthorization /detectnow already :)

As said, the DC didn't have any of the 3 mentioned keys (PingID, AccountDomainSid, SusClientId) while the CAS and the Primary only had the SusClientId, and another one called SusClientIdValidation. (please see attached).
Both keys are different on both computers. I still ran the .BAT to re-randomize SusClientId key and run a wuaucult /resetauthorization /detectnow for the sake of it, but obviously it didn't help.

Thanks for the WSUS survival kit, I'm reading it now but unfortunately it is not really narrowed down to my particular issue and doesn't help much to this point...

Could removing the WSUS roles on the CAS and Primary and reset them help? Is there anything I should clean after removing the role to make sure I start fresh?

Any other idea?

Thank you.
clientid.png

Don

Do you have your WSUS fully updated including this update??

http://support.microsoft.com/kb/2720211

^^If you dont have that update installed, there will be a mismatch between client and WSUS with the wuauclt.exe.

abissa

ASKER

As specified in my original post, yes I did.

ASKER CERTIFIED SOLUTION

abissa

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

abissa

ASKER

It seems that is the case. Machines showing as "not yet reported" under WSUS console is apparently normal, when the computer is configured as a SUP for SCCM it takes over the role.

The whole process of approving and deploying updates is different with SCCM and even if the WSUS console is installed (pretty confusing to be honest) it shouldn't be used.

Please close.