We're getting the following errors in the WUAHandler.log on about 3/70K machines:
-------------------------------------------------------------
- Its a WSUS Update Source type ({F5DD8FAF-442E-4309-A536-190FF99E644A}), adding it. WUAHandler 5/17/2013 1:03:56 PM 9832 (0x2668)
- Unable to read existing resultant WUA policy. Error = 0x800703fa. WUAHandler 5/17/2013 1:03:56 PM 9832 (0x2668)
- Enabling WUA Managed server policy to use server:
http://USFLTPA-WAP01.ADS.AEXP.COM:8530 WUAHandler 5/17/2013 1:03:56 PM 9832 (0x2668)
- Waiting for 2 mins for Group Policy to notify of WUA policy change... WUAHandler 5/17/2013 1:03:56 PM 9832 (0x2668)
- Unable to read existing WUA resultant policy. Error = 0x800703fa. WUAHandler 5/17/2013 1:04:30 PM 9832 (0x2668)
- Group policy settings were overwritten by a higher authority (Domain Controller) to: Server and Policy NOT CONFIGURED WUAHandler 5/17/2013 1:04:30 PM 9832 (0x2668)
- Failed to Add Update Source for WUAgent of type (2) and id ({F5DD8FAF-442E-4309-A536-190FF99E644A}). Error = 0x80040692. WUAHandler 5/17/2013 1:04:30 PM 9832 (0x2668)
-------------------------------------------------------------
From what I've found this generally refers to a GPO that's pointing the machines to an invalid server...............but in my case we do not have any GPOs in place that's changing WUA settings. I've been tracking the machines that this affects and have seen a machine successfully scan at 7:50am and then start to fail at 11:50am the same day.
Since I don't believe we have a GPO corrupting these settings I'm focusing on "Unable to read existing WUA resultant policy" and what would cause that.
Please advise.......
Jason Steeves
Jason