Hello,
I am experiencing a frustrating issue when attempting to push out windows updates via SCCM in either a manual fashion or with an automatic deployment rule. About 50% of the computers in our test area are attempting to get their updates from the primary site server (which they cannot access because of network configurations) instead of the secondary site servers they are able to connect to. The other 50% of the area all contact the secondary site server and apply their updates as expected.
The "LocationServices.log" from both the working and non working computers look the same and properly identify the secondary site server a valid WSUS Path, the only difference is in the "WUAHandler.log" which will show the Primary site server as the WUA Manager server instead of the secondary site server.
All the machines are in the same boundary, have the same client version installed on them, and they all preform other SCCM operations as expected, Application distribution, Software/hardware inventory, Endpoint protection, etc.
Any assistance with this would be greatly appreciated.
Chris
LocationServices.log
Current AD site of machine is Staff-Academic-Public LocationServices 5/20/2015 8:23:50 PM 2176 (0x0880)
Created and Sent Location Request '{32CEE48D-074F-42A6-ADED-8A5BAE30C272}' for package {3B1C6533-2073-4D89-97E2-241013CC360D} LocationServices 5/20/2015 8:23:50 PM 2176 (0x0880)
Calling back with the following WSUS locations LocationServices 5/20/2015 8:23:50 PM 4128 (0x1020)
WSUS Path='http://vapp1660.DOMAIN:8530', Server='VAPP1660.DOMAIN', Version='2093' LocationServices 5/20/2015 8:23:50 PM 4128 (0x1020)
WSUS Path='http://VAPP1663.DOMAIN:8530', Server='VAPP1663.DOMAIN', Version='2093' LocationServices 5/20/2015 8:23:50 PM 4128 (0x1020)
WSUS Path='http://vapp1660.DOMAIN:8530', Server='VAPP1660.DOMAIN', Version='2093' LocationServices 5/20/2015 8:23:50 PM 4128 (0x1020)
Calling back with locations for WSUS request {32CEE48D-074F-42A6-ADED-8A5BAE30C272} LocationServices 5/20/2015 8:23:50 PM 4128 (0x1020)
Executing Task LSSiteRoleCycleTask LocationServices 5/20/2015 8:28:59 PM 2664 (0x0A68)
The MP name retrieved is 'vapp1660.DOMAIN' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices
5/21/2015 7:21:40 AM 4736 (0x1280)
MP 'vapp1660.DOMAIN' is compatible LocationServices 5/21/2015 7:21:40 AM 4736 (0x1280)
WUAHandler.log
Its a WSUS Update Source type ({3B1C6533-2073-4D89-97E2-241013CC360D}), adding it. WUAHandler 5/18/2015 9:03:50 PM 5116 (0x13FC)
Existing WUA Managed server was already set (http://vapp1660.DOMAIN:8530), skipping Group Policy registration. WUAHandler 5/18/2015 9:03:50 PM 5116 (0x13FC)
Added Update Source ({3B1C6533-2073-4D89-97E2-241013CC360D}) of content type: 2 WUAHandler 5/18/2015 9:03:50 PM 5116 (0x13FC)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 5/18/2015 9:03:50 PM 5116 (0x13FC)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 5/18/2015 9:03:50 PM 5116 (0x13FC)
Async searching of updates using WUAgent started. WUAHandler 5/18/2015 9:03:50 PM 5116 (0x13FC)
Async searching completed. WUAHandler 5/18/2015 9:04:15 PM 2408 (0x0968)
OnSearchComplete - Failed to end search job. Error = 0x80072ee2. WUAHandler 5/18/2015 9:04:15 PM 4312 (0x10D8)
Scan failed with error = 0x80072ee2. WUAHandler 5/18/2015 9:04:15 PM 4312 (0x10D8)
Other recent topics
