Solved

Computers not reporting to WSUS server

Posted on 2013-01-07
11
3,544 Views
Last Modified: 2013-01-13
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.
0
Comment
Question by:abissa
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 2
11 Comments
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 38751128
0
 
LVL 16

Expert Comment

by:uescomp
ID: 38751146
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.
0
 
LVL 2

Author Comment

by:abissa
ID: 38751238
-> 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?
0
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 47

Expert Comment

by:Donald Stewart
ID: 38751323
0
 
LVL 16

Expert Comment

by:uescomp
ID: 38752055
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
0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 38752331
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)
0
 
LVL 2

Author Comment

by:abissa
ID: 38754195
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
0
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 38755014
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.
0
 
LVL 2

Author Comment

by:abissa
ID: 38755077
As specified in my original post, yes I did.
0
 
LVL 2

Accepted Solution

by:
abissa earned 0 total points
ID: 38755254
Maybe this is a question more for a SCCM expert than a WSUS expert, but could it simply be that once WSUS and SSCM are integrated, the WSUS console shouldn't be considered as a reliable source of information about clients and therefore not be used anymore?

I'm still in the process of understanding how updates deployment with SSCM works and I thought that I should use the WSUS console to troubleshoot issues first, but maybe I'm entirely wrong?
0
 
LVL 2

Author Closing Comment

by:abissa
ID: 38771675
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.
0

Featured Post

Independent Software Vendors: 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!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to leverage one TLS certificate to encrypt Microsoft SQL traffic and Remote Desktop Services, versus creating multiple tickets for the same server.
A procedure for exporting installed hotfix details of remote computers using powershell
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question