That’s the problem, the local policy isn’t getting to the client, e.g. wsus entries in gpedit are undefined.
This also happens on a previous Win7/CM07 client. Basically all clients behave the same, it has to be the servers. Now I’ve tried with a 2nd primary and SUP, the same. So something is consistent wrong. Can someone confirm that this is supposed to work? Jason? I’ve read a few posting from you J · All server WS2012 R2 · CM12 SP1 R2 · SQL 2012 SP1, CU6 · CAS: WSUS, SUP · Primary: o Site server: WSUS console, CM, FSP, nothing else o Remote SQL: CM DB, WSUS DB, Reporting o 2 MPs: Using replica o 1 SUP: WSUS full, SUP role, nothing else Any pointers on where to look on the servers? Like where the WSUS server are stored in, used to create the policy or the policy? The MP replicas must have that somewhere. I assume the clients get that configuration also from the MPs. -R From: [email protected] [mailto:[email protected]] On Behalf Of Matthias Berroth Sent: Mittwoch, 20. November 2013 14:16 To: [email protected] Subject: RE: [mssms] SUP issue on clients E_FAIL_POLICY_NOT_FOUND Please check the following: In the windowsupdate.log search for your configmgr site, which should be connected. Is it successful? Check if you’re ports are opened from the client to the server, for example with telnet. Or check this http://blogs.technet.com/b/michaelgriswold/archive/2010/04/15/auto-fix-wmi.aspx From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Mittwoch, 20. November 2013 11:10 To: [email protected] Subject: RE: [mssms] SUP issue on clients E_FAIL_POLICY_NOT_FOUND Also throwing errors, but I think they are normal as there isn’t a proper server specified, due the policy not providing them: 2013-11-20 10:59:28:013 776 2718 Agent * FATAL: Service CheckAccessByPolicy rejected call, hr=0x8024002E 2013-11-20 10:59:28:013 776 2718 Agent * WARNING: Exit code = 0x8024002E 2013-11-20 10:59:28:013 776 2718 Agent ********* 2013-11-20 10:59:28:013 776 2718 Agent ** END ** Agent: Finding updates [CallerId = Device Driver Retrieval Client Id = 3] 2013-11-20 10:59:28:013 776 2718 Agent ************* 2013-11-20 10:59:28:013 776 2718 Agent WARNING: WU client failed Searching for update with error 0x8024002e 2013-11-20 10:59:28:013 776 2718 IdleTmr WU operation (CSearchCall::Init ID 3, operation # 79) stopped; does use network; is not at background priority 2013-11-20 10:59:28:013 776 2718 IdleTmr Decremented PDC RefCount for Network to 0 2013-11-20 10:59:28:013 776 2718 IdleTmr Decremented idle timer priority operation counter to 1 2013-11-20 10:59:28:013 776 1134 COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = Device Driver Retrieval Client] 2013-11-20 10:59:28:013 776 1134 COMAPI - Updates found = 0 2013-11-20 10:59:28:013 776 1134 COMAPI - WARNING: Exit code = 0x00000000, Result code = 0x8024002E 2013-11-20 10:59:28:013 776 1134 COMAPI --------- 2013-11-20 10:59:28:013 776 1134 COMAPI -- END -- COMAPI: Search [ClientId = Device Driver Retrieval Client] 2013-11-20 10:59:28:013 776 1134 COMAPI ------------- 2013-11-20 10:59:28:013 776 8f4 COMAPI WARNING: Operation failed due to earlier error, hr=8024002E 2013-11-20 10:59:28:013 776 8f4 COMAPI FATAL: Unable to complete asynchronous search. (hr=8024002E) GPOs: I know, there aren’t any. DisableWindowsUpdateAccess (that has to be from the MP) and UseWUServer are the only registry values set for the agent. Since the port is part of the server name in the registry, and there isn’t one, it must got lost somehow. I probably could set it manually and see. Can I check on the server what’s policy created? Validate there is a server entry there? -R From: [email protected] [mailto:[email protected]] On Behalf Of Matthias Berroth Sent: Mittwoch, 20. November 2013 10:19 To: [email protected]; Roland Janus Subject: RE: [mssms] SUP issue on clients E_FAIL_POLICY_NOT_FOUND Check the windowsupdate.log on the client. It’s located on %Windir%. Check which port is used from the client. If it’s different to the port you using for sup, check you’re gpos. FYI you don’t need gpos for the sup. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Mittwoch, 20. November 2013 09:39 To: [email protected]; Roland Janus Subject: RE: [mssms] SUP issue on clients E_FAIL_POLICY_NOT_FOUND mp working? do you have group policy defining wsus settings? /Robert Roland Janus <[email protected]> wrote: I did that of course and it happens on two SUP/primaries, makes it more likely something is done wrong From: [email protected] [mailto:[email protected]] On Behalf Of Mark Mears Sent: Dienstag, 19. November 2013 17:08 To: [email protected] Subject: RE: [mssms] SUP issue on clients E_FAIL_POLICY_NOT_FOUND First thing I would do is remove then reinstall the SUP role with a 30 minute intermission. Thanks, _____ Mark Mears [email protected] <mailto:[email protected]%0d> Phone: (757) 945-2651 <http://www.cireson.com/> Image removed by sender. cid:[email protected] <http://twitter.com/teamcireson> Image removed by sender. cid:[email protected] Check out our System Center App Store: www.cireson.com/app-store _____ From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Tuesday, November 19, 2013 11:05 AM To: [email protected] Subject: [mssms] SUP issue on clients E_FAIL_POLICY_NOT_FOUND This is driving me nuts: · All server WS2012 R2 · CM12 R2 · SQL 2012 SP1, CU6 · CAS: WSUS, SUP · Primary: o Site server: WSUS console, CM, FSP, nothing else o Remote SQL: CM DB, WSUS DB, Reporting o 2 MPs: Using replica o 1 SUP: WSUS full, SUP role, nothing else SUP on the servers are all working, synching fine on both, everything green. Clients pick up policy for everything but not the WSUS server they are supposed to use. The WSUS agent is partially configured, as “managed by your administrator” in “windows update”, but it is not picking up the server. There is nothing in: root\ccm\softwareupdates\wuahandler, therefor not in the wsus registry hence the agent doesn’t know where to scan against. Scanagent.log: Failed to get instance of CCM_UpdateSource for ToolUniqueID {9C5A03EB-2ABE-4CB5-900D-058E9B2108C7} ScanAgent 19.11.2013 13:43:55 2028 (0x07EC) -ScanUpdateSource policy not found no scan will be performed, returning E_FAIL_POLICY_NOT_FOUND ScanAgent 19.11.2013 13:43:55 2028 (0x07EC) CScanAgent::HandleMessage - ScanByUpdateSource failed. Error = 0x87d00600 ScanAgent 19.11.2013 13:43:55 2028 (0x07EC) All clients do that for both primaries, so I assume it must be something I did wrong or I missed. I Any pointers please? -R
<<image001.jpg>>
<<image002.jpg>>
