none
Server 2012 WSUS server - 2012 client not connecting to server

    Frage

  • I setup a 2012 WSUS server and client, but the client is not appearing in the WSUS admin console on the WSUS server. 

    • Client name : HyperV-02
    • WSUS server name: SRV01

    I setup the WSUS setting via GPO (intranet server: http://srv02:8530)

    Here's a screenshot of the RSOP output on the client:

    Here is the last few lines of C:\Windows\WindowsUpdate.log:

    PS C:\Users\Administrator.LAB> cat C:\Windows\WindowsUpdate.log -Last 20
    2013-09-05      17:32:56:031     864    ebc     WuTask  WuTaskManager delay initialize completed successfully..
    2013-09-05      17:32:56:105     864    ebc     Report  CWERReporter::Init succeeded
    2013-09-05      17:32:56:105     864    ebc     Agent   ***********  Agent: Initializing Windows Update Agent  ***********
    2013-09-05      17:32:56:105     864    ebc     DnldMgr Download manager restoring 0 downloads
    2013-09-05      17:32:56:106     864    ebc     AU      ###########  AU: Initializing Automatic Updates  ###########
    2013-09-05      17:32:56:107     864    ebc     AU      AIR Mode is disabled
    2013-09-05      17:32:56:107     864    ebc     AU        # Policy Driven Provider: http://srv02:8530
    2013-09-05      17:32:56:107     864    ebc     AU        # Detection frequency: 1
    2013-09-05      17:32:56:107     864    ebc     AU        # Target group: prod
    2013-09-05      17:32:56:107     864    ebc     AU        # Approval type: Scheduled (Policy)
    2013-09-05      17:32:56:107     864    ebc     AU        # Auto-install minor updates: Yes (User preference)
    2013-09-05      17:32:56:107     864    ebc     AU        # Will interact with non-admins (Non-admins are elevated (User preference))
    2013-09-05      17:32:56:108     864    ebc     AU      WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2013-09-05      17:32:56:108     864    ebc     AU      AU finished delayed initialization
    2013-09-05      17:33:04:378     864    ebc     AU      AU received policy change subscription event
    2013-09-05      17:42:57:116     864    ebc     AU      ###########  AU: Uninitializing Automatic Updates  ###########
    2013-09-05      17:42:57:284     864    ebc     WuTask  Uninit WU Task Manager
    2013-09-05      17:42:57:554     864    ebc     Service *********
    2013-09-05      17:42:57:554     864    ebc     Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2013-09-05      17:42:57:554     864    ebc     Service *************

    Via a suggestion on the web I checked to confirmed the selfupdate virtual directory existed on the WSUS server:

    I also ran gpupdate /force on the client and server.

    What else should I check? Thanks for any assistance.


    • Bearbeitet red888 Donnerstag, 5. September 2013 21:44
    Donnerstag, 5. September 2013 21:41

Antworten

  • Overnight though it looks like SRV02 and Hyperv-02 appeared in the WSUS console, but they appeared in the "All Computers" group not the "prod" group which they were assigned to via group policy.

    Please confirm that you have set Options | Computers to "Use Group Policy...". Also the group must exist on the WSUS server, it will not be auto-created. Make sure that the spelling of the group names is identical on the WSUS server and GPO.

    Also, your one hour detection interval may be interfering with the WUAgent's ability to actually report with the assigned group name(s). Target Group assignments are cached in a local targeting cookie. That cookie has a ~60 minute timeout. With a 1 hour detection interval, the cookie never gets expired, and functionally it continues to use stale targeting information.

    To be true... there's no significant value in having detection frequencies of an hour anyway. I would recommend a minimum value of 6-8 hours if you need multiple scans per day.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Freitag, 6. September 2013 17:19

Alle Antworten

  • 2013-09-05      17:42:57:554     864    ebc     Service *********
    2013-09-05      17:42:57:554     864    ebc     Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2013-09-05      17:42:57:554     864    ebc     Service *************

    My first question would be why is the SERVICE shutting down here, and what happened after 5:42pm local time?

    Other than that, to properly diagnose this we'll need a complete detection event log trace.

    Please do the following on your client system.

    1. Restart the system.
    2. From a command prompt run wuauclt /resetauthorization /detectnow.
    3. Wait 30 minutes.
    4. Post all of the log entries starting with the SERVICE START entry created from the reboot, and to the end of the logfile. (This should be between 100-200 lines.)

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Donnerstag, 5. September 2013 22:03
  • Thanks for the reply.

    Just to give you a clearer picture I actually have 3 servers, 2 of which are VMs, this is what my little lab setup looks like:

    SRV01: 2012 DC
    SRV02: 2012 WSUS server
    Hyperv-02: 2012 hyperv server with SRV01 and SRV02 running as guests

    To answer you questions after 5:45 I believe I rebooted SRV02 (not sure if the service the log was referring to is a local service or a service on the WSUS box). I also ran gpupdate /force on all the machines.

    Overnight though it looks like SRV02 and Hyperv-02 appeared in the WSUS console, but they appeared in the "All Computers" group not the "prod" group which they were assigned to via group policy.

    I restarted both VMs and hypver-02.
    ran wuauclt /resetauthorization /detectnow on SVR01 and Hyperv-02
    I will post the log entries on hypverv-02
    Freitag, 6. September 2013 14:04
  • Log entries on hypverv-02:

    2013-09-06	09:26:47:347	 812	fb8	Service	** START **  Service: Service startup
    2013-09-06	09:26:47:348	 812	fb8	Service	*********
    2013-09-06	09:26:47:354	 812	fb8	Agent	  * WU client version 7.8.9200.16384
    2013-09-06	09:26:47:354	 812	fb8	Agent	  * Base directory: C:\Windows\SoftwareDistribution
    2013-09-06	09:26:47:355	 812	fb8	Agent	  * Access type: No proxy
    2013-09-06	09:26:47:355	 812	fb8	Service	UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2013-09-06	09:26:47:355	 812	fb8	Service	UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2013-09-06	09:26:47:355	 812	fb8	Agent	  * Network state: Connected
    2013-09-06	09:26:47:427	 812	fb8	Service	UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2013-09-06	09:26:47:427	 812	fb8	Service	UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2013-09-06	09:26:47:661	 812	fb8	Agent	***********  Agent: Initializing global settings cache  ***********
    2013-09-06	09:26:47:661	 812	fb8	Agent	  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2013-09-06	09:26:47:661	 812	fb8	Agent	  * WSUS server: http://srv02:8530
    2013-09-06	09:26:47:661	 812	fb8	Agent	  * WSUS status server: http://srv02:8530
    2013-09-06	09:26:47:662	 812	fb8	Agent	  * Target group: prod
    2013-09-06	09:26:47:662	 812	fb8	Agent	  * Windows Update access disabled: No
    2013-09-06	09:26:47:667	 812	fb8	Misc	WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2013-09-06	09:26:47:680	 812	fb8	WuTask	WuTaskManager delay initialize completed successfully..
    2013-09-06	09:26:47:797	 812	fb8	Report	CWERReporter::Init succeeded
    2013-09-06	09:26:47:797	 812	fb8	Agent	***********  Agent: Initializing Windows Update Agent  ***********
    2013-09-06	09:26:47:805	 812	fb8	DnldMgr	Download manager restoring 0 downloads
    2013-09-06	09:26:47:807	 812	fb8	AU	###########  AU: Initializing Automatic Updates  ###########
    2013-09-06	09:26:47:917	 812	fb8	AU	AIR Mode is disabled
    2013-09-06	09:26:47:935	 812	fb8	AU	  # Policy Driven Provider: http://srv02:8530
    2013-09-06	09:26:47:935	 812	fb8	AU	  # Detection frequency: 1
    2013-09-06	09:26:47:935	 812	fb8	AU	  # Target group: prod
    2013-09-06	09:26:47:935	 812	fb8	AU	  # Approval type: Scheduled (Policy)
    2013-09-06	09:26:47:935	 812	fb8	AU	  # Auto-install minor updates: Yes (User preference)
    2013-09-06	09:26:47:935	 812	fb8	AU	  # Will interact with non-admins (Non-admins are elevated (User preference))
    2013-09-06	09:26:47:947	 812	fb8	AU	WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2013-09-06	09:26:47:947	 812	fb8	AU	AU finished delayed initialization
    2013-09-06	09:26:47:949	 812	348	AU	Triggering AU detection through DetectNow API
    2013-09-06	09:26:47:949	 812	348	AU	Triggering Online detection (non-interactive)
    2013-09-06	09:26:50:949	 812	fb8	AU	#############
    2013-09-06	09:26:50:949	 812	fb8	AU	## START ##  AU: Search for updates
    2013-09-06	09:26:50:949	 812	fb8	AU	#########
    2013-09-06	09:26:51:220	 812	fb8	Report	***********  Report: Initializing static reporting data  ***********
    2013-09-06	09:26:51:220	 812	fb8	Report	  * OS Version = 6.2.9200.0.0.197008
    2013-09-06	09:26:51:220	 812	fb8	Report	  * OS Product Type = 0x00000050
    2013-09-06	09:26:51:231	 812	fb8	Report	  * Computer Brand = Dell Inc.
    2013-09-06	09:26:51:231	 812	fb8	Report	  * Computer Model = OptiPlex XE                  
    2013-09-06	09:26:51:231	 812	fb8	Report	  * Platform Role = 5
    2013-09-06	09:26:51:232	 812	fb8	Report	  * AlwaysOn/AlwaysConnected (AOAC) = 0
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Revision = A03
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A03
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Release Date = 2011-01-21T00:00:00
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Sku Number unavailable.
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Vendor = Dell Inc.
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Family unavailable.
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Major Release = 2
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Bios Minor Release = 0
    2013-09-06	09:26:51:235	 812	fb8	Report	  * Locale ID = 1033
    2013-09-06	09:26:51:304	 812	fb8	AU	<<## SUBMITTED ## AU: Search for updates  [CallId = {825E91F0-1EE3-44B8-AF3A-E2D884E61E1E} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2013-09-06	09:26:51:304	 812	ea4	Agent	*************
    2013-09-06	09:26:51:304	 812	ea4	Agent	** START **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2013-09-06	09:26:51:304	 812	ea4	Agent	*********
    2013-09-06	09:26:51:305	 812	ea4	Agent	  * Online = Yes; Ignore download priority = No
    2013-09-06	09:26:51:305	 812	ea4	Agent	  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2013-09-06	09:26:51:305	 812	ea4	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-09-06	09:26:51:316	 812	ea4	Agent	  * Search Scope = {Machine & All Users}
    2013-09-06	09:26:51:316	 812	ea4	Agent	  * Caller SID for Applicability: S-1-5-18
    2013-09-06	09:26:51:340	 812	ea4	EP	Got WSUS Client/Server URL: "http://srv02:8530/ClientWebService/client.asmx"
    2013-09-06	09:26:52:925	 812	ea4	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-09-06	09:26:52:927	 812	ea4	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://srv02:8530/ClientWebService/client.asmx
    2013-09-06	09:26:52:938	 812	ea4	EP	Got WSUS SimpleTargeting URL: "http://srv02:8530"
    2013-09-06	09:26:52:958	 812	ea4	PT	Initializing simple targeting cookie, clientId = 2924f7a9-d405-4a69-97b3-222e37558828, target group = prod, DNS name = hyperv-02.lab.local
    2013-09-06	09:26:52:959	 812	ea4	PT	  Server URL = http://srv02:8530/SimpleAuthWebService/SimpleAuth.asmx
    2013-09-06	09:27:24:822	 812	ea4	Agent	  * Found 0 updates and 62 categories in search; evaluated appl. rules of 391 out of 549 deployed entities
    2013-09-06	09:27:24:875	 812	ea4	Agent	Reporting status event with 54 installable, 0 installed,  0 installed pending, 0 failed and 0 downloaded updates
    2013-09-06	09:27:24:875	 812	ea4	Agent	*********
    2013-09-06	09:27:24:876	 812	ea4	Agent	**  END  **  Agent: Finding updates [CallerId = Windows Update Command Line]
    2013-09-06	09:27:24:876	 812	ea4	Agent	*************
    2013-09-06	09:27:25:400	 812	f48	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {825E91F0-1EE3-44B8-AF3A-E2D884E61E1E} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2013-09-06	09:27:25:921	 812	f48	AU	  # 0 updates detected
    2013-09-06	09:27:27:481	 812	f48	AU	#########
    2013-09-06	09:27:27:482	 812	f48	AU	##  END  ##  AU: Search for updates  [CallId = {825E91F0-1EE3-44B8-AF3A-E2D884E61E1E} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2013-09-06	09:27:27:482	 812	f48	AU	#############
    2013-09-06	09:27:27:482	 812	f48	AU	All AU searches complete.
    2013-09-06	09:27:28:513	 812	f48	AU	AU setting next detection timeout to 2013-09-06 17:15:35
    2013-09-06	09:27:32:702	 812	f10	Report	REPORT EVENT: {A22F43EA-FEC2-4125-BA16-BDB1A73342AF}	2013-09-06 09:27:24:865-0700	1	147 [AGENT_DETECTION_FINISHED]	101	{00000000-0000-0000-0000-000000000000}	0	0	Windows Update Command Line	Success	Software Synchronization	Windows Update Client successfully detected 0 updates.
    2013-09-06	09:27:32:702	 812	f10	Report	REPORT EVENT: {D8FE19DC-5FBD-479B-9B91-4D7ADCFDA63C}	2013-09-06 09:27:24:875-0700	1	156 [AGENT_STATUS_30]	101	{00000000-0000-0000-0000-000000000000}	0	0	Windows Update Command Line	Success	Pre-Deployment Check	Reporting client status.
    2013-09-06	09:27:37:395	 812	f10	Report	CWERReporter finishing event handling. (00000000)
    2013-09-06	09:35:36:693	 812	f10	EP	Got WSUS Client/Server URL: "http://srv02:8530/ClientWebService/client.asmx"
    2013-09-06	09:35:36:693	 812	f10	PT	WARNING: Cached cookie has expired or new PID is available
    2013-09-06	09:35:36:693	 812	f10	EP	Got WSUS SimpleTargeting URL: "http://srv02:8530"
    2013-09-06	09:35:36:693	 812	f10	PT	Initializing simple targeting cookie, clientId = 2924f7a9-d405-4a69-97b3-222e37558828, target group = prod, DNS name = hyperv-02.lab.local
    2013-09-06	09:35:36:693	 812	f10	PT	  Server URL = http://srv02:8530/SimpleAuthWebService/SimpleAuth.asmx
    2013-09-06	09:35:37:206	 812	f10	EP	Got WSUS Reporting URL: "http://srv02:8530/ReportingWebService/ReportingWebService.asmx"
    2013-09-06	09:35:37:206	 812	f10	Report	Uploading 2 events using cached cookie, reporting URL = http://srv02:8530/ReportingWebService/ReportingWebService.asmx
    2013-09-06	09:35:37:819	 812	f10	Report	Reporter successfully uploaded 2 events.
    2013-09-06	09:37:37:511	 812	fb8	AU	###########  AU: Uninitializing Automatic Updates  ###########
    2013-09-06	09:37:37:642	 812	fb8	WuTask	Uninit WU Task Manager
    2013-09-06	09:37:38:185	 812	fb8	Service	*********
    2013-09-06	09:37:38:185	 812	fb8	Service	**  END  **  Service: Service exit [Exit code = 0x240001]
    2013-09-06	09:37:38:185	 812	fb8	Service	*************
    
    

    Freitag, 6. September 2013 14:05
  • Overnight though it looks like SRV02 and Hyperv-02 appeared in the WSUS console, but they appeared in the "All Computers" group not the "prod" group which they were assigned to via group policy.

    Please confirm that you have set Options | Computers to "Use Group Policy...". Also the group must exist on the WSUS server, it will not be auto-created. Make sure that the spelling of the group names is identical on the WSUS server and GPO.

    Also, your one hour detection interval may be interfering with the WUAgent's ability to actually report with the assigned group name(s). Target Group assignments are cached in a local targeting cookie. That cookie has a ~60 minute timeout. With a 1 hour detection interval, the cookie never gets expired, and functionally it continues to use stale targeting information.

    To be true... there's no significant value in having detection frequencies of an hour anyway. I would recommend a minimum value of 6-8 hours if you need multiple scans per day.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Freitag, 6. September 2013 17:19
  • Well I feel foolish, the default "Use the Update Services console" setting for computers in options was set. After changing it to use group policy it looks like its working now.

    Also thanks for the info regarding the detection interval. I had it set that low for this lab because I wanted to see a lot of activity.

    Thanks for the help.

    Freitag, 6. September 2013 18:53