SCCM 2012 / Forefront Updating

Soldato
Joined
10 Mar 2003
Posts
6,790
Hi,

Just wondered if we have any SCCM gurus around?

Essentially I have SCCM 2012 R2 up and running and I've created ADR's to deploy the FEP definitions.

However FEP on the clients doesn't seem to want to update. On the Endpoint Policy I've told clients that 'Updates distributed from Configuration Manager' as the only update source yet it still looks like it's trying to go out to the internet.

Any ideas? There is the Windows Update log below where I can see it trying to go out - we have a proxy in place but it doesn't look like it's configured (any ideas where I can configure this??)

From WindowsUpdate.log:
2014-07-10 10:11:54:272 1072 115c Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2014-07-10 10:11:54:272 1072 115c Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://www.update.microsoft.com/v9/1/windowsupdate/redir/muv4wuredir.cab. error 0x80072ee2
2014-07-10 10:11:54:272 1072 115c Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2014-07-10 10:11:54:272 1072 115c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2014-07-10 10:11:54:272 1072 115c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2014-07-10 10:11:54:272 1072 115c Misc WARNING: DownloadFileInternal failed for <same path as above> error 0x80072ee2
2014-07-10 10:11:54:272 1072 115c Agent WARNING: Failed to obtain the authorization cab URLs, hr=0x80072ee22014-07-10 10:11:54:272 1072 115c Agent * WARNING: Online service registration/service ID resolution failed, hr=0x80072EE2
2014-07-10 10:11:54:288 1072 115c Agent * WARNING: Exit code = 0x80072EE2


Thanks!
 
Might be an idea to review the WUAHandler.log on the client to see why. This should hopefully give you an idea as to why it isn't working.

Have you set up the SUP to get the definition updates?
 
Yep - the definitions work on some clients!

Below is the WUA log:

Enabling WUA Managed server policy to use server: http://CORRECT:8530 WUAHandler 08/07/2014 15:50:42 5888 (0x1700)
Waiting for 2 mins for Group Policy to notify of WUA policy change... WUAHandler 08/07/2014 15:50:42 5888 (0x1700)
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://WRONG and Policy ENABLED WUAHandler 08/07/2014 15:50:44 5888 (0x1700)
Failed to Add Update Source for WUAgent of type (2) and id ({AD619C8B-F697-406D-91A0-D295C655E64F}). Error = 0x87d00692. WUAHandler 08/07/2014 15:50:44 5888 (0x1700)
CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles WUAHandler 08/07/2014 15:51:53 5180 (0x143C)
Its a WSUS Update Source type ({AD619C8B-F697-406D-91A0-D295C655E64F}), adding it. WUAHandler 08/07/2014 17:40:04 180 (0x00B4)
Enabling WUA Managed server policy to use server: http://CORRECT:8530 WUAHandler 08/07/2014 17:40:04 180 (0x00B4)
Waiting for 2 mins for Group Policy to notify of WUA policy change... WUAHandler 08/07/2014 17:40:04 180 (0x00B4)
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://WRONG and Policy ENABLED WUAHandler 08/07/2014 17:40:05 180 (0x00B4)
Failed to Add Update Source for WUAgent of type (2) and id ({AD619C8B-F697-406D-91A0-D295C655E64F}). Error = 0x87d00692. WUAHandler 08/07/2014 17:40:05 180 (0x00B4)
 
Back
Top Bottom