Managing Active Directory can get complicated. Often, the native tools for managing AD are just not up to the task. The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.
Solved
Computers not reporting to WSUS server
Posted on 2013-01-07
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
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.
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
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.
[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
Active today
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
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
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.
If you can make it to the site it should ask or prompt you to download/save a file.
Active today
-> 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\Wi
- 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?
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\Wi
- 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?
Active today
Go over the WSUS survival guide here
http://social.technet.microsoft.com/wiki/contents/articles/2491.wsus-troubleshooting-survival-guide.aspx
http://social.technet.microsoft.com/wiki/contents/articles/2491.wsus-troubleshooting-survival-guide.aspx
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
Active today
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
Did you delete those reg keys anyway and run wuauclt /resetauthorization /detectnow ??
(Or run the .BAT from the Blog)
Active today
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
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
Active today
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.
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.
Active today
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?
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?
Active today
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.
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.
Featured Post
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Background Information
Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders.
Click on Start and then select Computer to view the available drives on the se…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller.
Log onto the new domain controller with a user account t…
Suggested Courses
Course of the Month9 days, 18 hours left to enroll
722 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.