locked
No computers are showing up in WSUS console RRS feed

  • Question

  • Hey all, I have WSUS installed on Server 2012R2. I have some test Windows 7 computers in an OU I created and my GPO is linked to that OU (double-checked) but none of my computers are showing up in the WSUS console. I double-checked under Options > Computers and Use the Update Services console is checked. When I Google this issue I keep getting pointed to sites that pertain to Server 2003. I've never set up WSUS before so I'm starting to think that there are some hidden "Gotchas" that got me. Any ideas? Suggestions? Recommendations?

    Thanks,

    Joe B

    Monday, August 3, 2015 1:39 PM

Answers

  • If Burak's suggestions didn't work if you can post the values in the  Group Policy you set. It could be as simple as missing the port number :8530 on the tail end of your intranet site. or using https:// instead of http://

    Each time you change your Group Policy run gpupdate/force on Domain controller and the client computer, also restart windows update after each apply.

    If GP is working you should see the settings in the registry and windows update will also report that your system administrator controls some of the updates.

    • Marked as answer by JBruyet Thursday, August 6, 2015 9:33 PM
    Monday, August 3, 2015 2:41 PM
  • Hi

     You need to check the gpo's still apply the old wsus,and then remove old wsus from gpo.(Specially check default domain policy)

    • Marked as answer by JBruyet Thursday, August 6, 2015 9:30 PM
    Thursday, August 6, 2015 4:20 PM

All replies

  • Hi

     First make sure the wsus gpo is applied OU where the computers in.Then check on a client "gpresult /h" the gpo succesfully applied.

    Also run "wuauclt.exe /detectnow /reportnow" on client,then check on wsus console,have to be report.

    - net stop wuauserv

    - rmdir /S /Q /C:\winnt\softwaredistribution

    - net start wuauserv

    - wuauclt.exe /resetauthorization /detectnow

    ALso download this WSUS Client Diagnostic tool on client and check for the errors,

    https://www.microsoft.com/en-us/download/details.aspx?id=30827

    Monday, August 3, 2015 2:23 PM
  • If Burak's suggestions didn't work if you can post the values in the  Group Policy you set. It could be as simple as missing the port number :8530 on the tail end of your intranet site. or using https:// instead of http://

    Each time you change your Group Policy run gpupdate/force on Domain controller and the client computer, also restart windows update after each apply.

    If GP is working you should see the settings in the registry and windows update will also report that your system administrator controls some of the updates.

    • Marked as answer by JBruyet Thursday, August 6, 2015 9:33 PM
    Monday, August 3, 2015 2:41 PM
  • Hi

     First make sure the wsus gpo is applied OU where the computers in.Then check on a client "gpresult /h" the gpo succesfully applied.

    ########################## I checked the resulting page and I don't see where the WSUS policy has been applied. I can see the default domain policy but that's it.

    Also run "wuauclt.exe /detectnow /reportnow" on client,then check on wsus console,have to be report.

    ##########################  I did that and there were no errors but WSUS still shows 0 computers.

    - net stop wuauserv

    - rmdir /S /Q /C:\winnt\softwaredistribution

    - net start wuauserv

    - wuauclt.exe /resetauthorization /detectnow

    ##########################  I ran these commands (with a few tweaks for Windows 7) and they all ran without any errors but again, WSUS shows 0 computers.

    ALso download this WSUS Client Diagnostic tool on client and check for the errors,

    https://www.microsoft.com/en-us/download/details.aspx?id=30827

     Ok, regarding the diagnostic tool here's what I'm getting:

    WSUS Client Diagnostics Tool

    Checking Machine State
        Checking for admin rights to run tool................ PASS
        Automatic Updates Service is running................. PASS
        Background Intelligent Transfer Service is Running... PASS
        
    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    The System cannot find the file specified.

    Press Enter to Complete

    I Googled this error and I'm finding issues related to computers not being able to download updates. I'm still trying to get computers into the WSUS server. Does this speak to anyone?

    Thanks,

    Joe B

    Tuesday, August 4, 2015 10:25 PM
  • Hi Darren, is there a report I can run so I can post the values? I'm not sure what values you need or where to find them.

    Thanks,

    Joe B

    Tuesday, August 4, 2015 10:52 PM
  • Hmmm... One of the computers I'm testing, and it's the one I was just using to get the errors, won't allow me to do a manual update. It says:

    You receive updates:       Managed by your system Administrator

    Ok, there must be some configuration tweak that I've missed somewhere. Here are the policies that I've configured for WSUS:

    Windows Components/Windows Update
    Policy
    Configure Automatic Updates                 Enabled
        Configure automatic updating:            4 - Auto download and schedule the install
        The following settings are only required and applicable if 4 is selected.
        Install during automatic maintenance   Enabled
        Scheduled install day:                       0 - Every day
        Scheduled install time:                      02:00

    Policy
    No auto-restart with logged on users for scheduled automatic updates installations       Enabled
    Re-prompt for restart with scheduled installations                                                    Enabled
        Wait the following period before prompting again with a scheduled restart (minutes):  120
        
    Policy
    Specify intranet Microsoft update service location               Enabled
        Set the intranet update service for detecting updates:     http://srv-appy:8530
        Set the intranet statistics server:                                 http://srv-appy
        example: http://IntranetUpd01)

    Tuesday, August 4, 2015 11:30 PM
  • Hi

     Just for test : Set the intranet statistics server : http://srv-appy:8530(Add the port)

    Also please check the article and configure client side targeting,

    http://prajwaldesai.com/how-to-configure-client-side-targeting-in-wsus/

    Wednesday, August 5, 2015 1:03 PM
  • Ok, I added the :8530 port to the Statistics Server address and configured Client-Side Targeting. I did a gpupdate /force on the server and then on the client. Then I checked my WSUS console but it remains uncluttered by computers. How long after doing a gpupdate should I have to wait before WSUS starts getting populated by computers? Oh, I also did another ClientDiag and I'm still getting three passes and this error: 

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    Thanks,

    Joe B 

    Wednesday, August 5, 2015 6:19 PM
  • Hi

     For error please check this ms article and follow the steps

    https://support.microsoft.com/en-us/kb/910336

    After then run command wuauclt /resetauthorization /detectnow

    check WindowsUpdate.log 30 minutes later..

    Wednesday, August 5, 2015 6:41 PM
  • Ok, here are the last several lines from the log: 

    <<PROCESS>>: DllHost.exe	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x8024402c.
    2015-08-05	12:50:30:302	 384	bb4	Report	CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2015-08-05	12:50:30:302	 384	bb4	Report	WER Report sent: 7.6.7601.18917 0x8024402c(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 <<PROCESS>>: DllHost.exe {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2015-08-05	12:55:06:751	 384	bb4	Misc	WARNING: Send failed with hr = 80072ee7.
    2015-08-05	12:55:06:751	 384	bb4	Misc	WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2015-08-05	12:55:06:751	 384	bb4	Misc	FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x8024402c
    2015-08-05	12:55:06:751	 384	bb4	PT	  + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
    2015-08-05	12:55:06:751	 384	bb4	PT	  + Caller provided credentials = No
    2015-08-05	12:55:06:751	 384	bb4	PT	  + Impersonate flags = 0
    2015-08-05	12:55:06:751	 384	bb4	PT	  + Possible authorization schemes used = 
    2015-08-05	12:55:06:751	 384	bb4	PT	WARNING: GetConfig failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
    2015-08-05	12:55:06:751	 384	bb4	PT	WARNING: PTError: 0x8024402c
    2015-08-05	12:55:06:751	 384	bb4	PT	WARNING: GetConfig_WithRecovery failed: 0x8024402c
    2015-08-05	12:55:06:751	 384	bb4	PT	WARNING: RefreshConfig failed: 0x8024402c
    2015-08-05	12:55:06:751	 384	bb4	PT	WARNING: RefreshPTState failed: 0x8024402c
    2015-08-05	12:55:06:751	 384	bb4	PT	WARNING: PTError: 0x8024402c
    2015-08-05	12:55:06:751	 384	bb4	Report	WARNING: Reporter failed to upload events with hr = 8024402c.
    2015-08-05	13:05:47:315	 384	bb4	Misc	WARNING: Send failed with hr = 80072ee7.
    2015-08-05	13:05:47:315	 384	bb4	Misc	WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2015-08-05	13:05:47:315	 384	bb4	Misc	FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x8024402c
    2015-08-05	13:05:47:315	 384	bb4	PT	  + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
    2015-08-05	13:05:47:315	 384	bb4	PT	  + Caller provided credentials = No
    2015-08-05	13:05:47:315	 384	bb4	PT	  + Impersonate flags = 0
    2015-08-05	13:05:47:315	 384	bb4	PT	  + Possible authorization schemes used = 
    2015-08-05	13:05:47:315	 384	bb4	PT	WARNING: GetConfig failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
    2015-08-05	13:05:47:315	 384	bb4	PT	WARNING: PTError: 0x8024402c
    2015-08-05	13:05:47:315	 384	bb4	PT	WARNING: GetConfig_WithRecovery failed: 0x8024402c
    2015-08-05	13:05:47:315	 384	bb4	PT	WARNING: RefreshConfig failed: 0x8024402c
    2015-08-05	13:05:47:315	 384	bb4	PT	WARNING: RefreshPTState failed: 0x8024402c
    2015-08-05	13:05:47:315	 384	bb4	PT	WARNING: PTError: 0x8024402c
    2015-08-05	13:05:47:315	 384	bb4	Report	WARNING: Reporter failed to upload events with hr = 8024402c.
    2015-08-05	13:32:03:308	 384	10fc	Misc	WARNING: Send failed with hr = 80072ee7.
    2015-08-05	13:32:03:308	 384	10fc	Misc	WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2015-08-05	13:32:03:308	 384	10fc	Misc	FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x8024402c
    2015-08-05	13:32:03:308	 384	10fc	PT	  + Last proxy send request failed with hr = 0x80072EE7, HTTP status code = 0
    2015-08-05	13:32:03:308	 384	10fc	PT	  + Caller provided credentials = No
    2015-08-05	13:32:03:308	 384	10fc	PT	  + Impersonate flags = 0
    2015-08-05	13:32:03:308	 384	10fc	PT	  + Possible authorization schemes used = 
    2015-08-05	13:32:03:308	 384	10fc	PT	WARNING: GetConfig failure, error = 0x8024402C, soap client error = 5, soap error code = 0, HTTP status code = 200
    2015-08-05	13:32:03:308	 384	10fc	PT	WARNING: PTError: 0x8024402c
    2015-08-05	13:32:03:308	 384	10fc	PT	WARNING: GetConfig_WithRecovery failed: 0x8024402c
    2015-08-05	13:32:03:308	 384	10fc	PT	WARNING: RefreshConfig failed: 0x8024402c
    2015-08-05	13:32:03:308	 384	10fc	PT	WARNING: RefreshPTState failed: 0x8024402c
    2015-08-05	13:32:03:308	 384	10fc	PT	WARNING: PTError: 0x8024402c
    2015-08-05	13:32:03:308	 384	10fc	Report	WARNING: Reporter failed to upload events with hr = 8024402c.
    2015-08-05	13:34:58:013	 384	638	AU	AU setting next sqm report timeout to 2015-08-06 20:34:58

    There are a lot of 0x8024402c error codes so I Googled that code and found that it's because the clients can't see the WSUS server. Duh. BUT, I also found a recommendation to use the FQDN for the WSUS server. I just changed my URL to the FQDN. I guess we wait again. 

    Thanks,

    Joe B 


    Wednesday, August 5, 2015 8:59 PM
  • OK !!!!!!! I just checked my log and I'm getting the same errors BUT... I went spelunking and found this line: 

    2015-08-06	04:13:17:158	1216	16f8	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://srv-appserv:8530/ClientWebService/client.asmx

    Notice the part about srv-appserv. That is the server that ran our previous version of WSUS which was set up by someone who no longer works here (thus my indoctrination into WSUS). Apparently there are remnants of this server in a configuration file somewhere. I have no idea where to look for this file (or these files?). I'm going to head to Google again and see what I can do, but if any ideas pop up here that would be great. 

    Thanks,

    Joe B 


    • Edited by JBruyet Thursday, August 6, 2015 2:50 PM Clarify device
    Thursday, August 6, 2015 2:49 PM
  • I believe I finally found my problem. Following some advice I found on a Technet site I checked these two registry settings: 

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\WUServer
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\WUStatusServer

    Sure enough, I found the settings for the previous dead server. I just looked up above and I see that I missed letting you know that there was a previous, crashed WSUS server. So sorry about that. So, is there a way to force new WSUS server settings into the registry or am I going to have to go on a tour of our facilities and change it on every computer? 

    Thanks,

    Joe B 

    Thursday, August 6, 2015 3:16 PM
  • Hi

     You need to check the gpo's still apply the old wsus,and then remove old wsus from gpo.(Specially check default domain policy)

    • Marked as answer by JBruyet Thursday, August 6, 2015 9:30 PM
    Thursday, August 6, 2015 4:20 PM
  • Ok, I didn't find any policies for WSUS but I did find one for Windows AU. While digging through the WindowsUpdate.log file I remembered finding some AU notations so I dug down into it and sure enough it was pointing WSUS to the old server. I deleted that GPO and ran gpupdate /force on my workstation (I make a good guinea pig) and now I'll wait 30 minutes and check the WindowsUpdate.log file to see how it's working. 

    Thanks,

    Joe B 

    Thursday, August 6, 2015 6:01 PM
  • Hi Burak, I couldn't find any WSUS policies but I did find an AU policy. I remembered seeing some AU entries in the WindowsUpdate logs so I looked at its configuration and it was pointing to that old server. I removed it, did another gpupdate /force and when I checked back later all four of my test computers were listed in the WSUS console. Thanks a lot for hanging in there with me. 

    And Darren, I should have paid more attention to your comment about the registry.

    Thank you both,

    Joe B 

    Thursday, August 6, 2015 9:35 PM