Search the Community

Hello everyone! I cannot find an answer to technical question. When I add or move device to some collection, does it makes the SCCM client to run Policy Retrieval and Evaluation Cycle? Or the time interval is strictly configured in Client settings? In other words, if I want to immediately apply collection's deployments to a new computer do I have to run for it "Download computer Policy" from SCCM console?

SCCM 2012 R2 installed on Windows Server 2012 R2 WSUS and SUP installed on the same server. No proxy / no firewall between client and server Ports are open on server, firewall not active on server and not on clients. SCCM SUP is configured with default port 8530 / 8530 Software deployment (application / package deployment) on clients is working fine. Microsoft Patch installation was working too some days ago Accidently Component Direct Access on Server was installed, misconfigured and re-moved from server, dont know if this is really the starting point where my issue began. Problem: Updates can not be deployed on clients (Win7, Win Server 2008, ....) Here are the client log file information WUAHandler.log: Its a WSUS Update Source type ({4A7213ED-B15E-456C-813A-177073B905A3}), adding it. WUAHandler 28.03.2014 14:25:59 3348 (0x0D14) Existing WUA Managed server was already set (http://XXXXXXXX.xxxxxx.com:8530), skipping Group Policy registration. WUAHandler 28.03.2014 14:25:59 3348 (0x0D14) Added Update Source ({4A7213ED-B15E-456C-813A-177073B905A3}) of content type: 2 WUAHandler 28.03.2014 14:25:59 3348 (0x0D14) Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 28.03.2014 14:25:59 3348 (0x0D14) Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 28.03.2014 14:25:59 3348 (0x0D14) Async searching of updates using WUAgent started. WUAHandler 28.03.2014 14:25:59 3348 (0x0D14) Async searching completed. WUAHandler 28.03.2014 14:26:20 4248 (0x1098) OnSearchComplete - Failed to end search job. Error = 0x80072ee2. WUAHandler 28.03.2014 14:26:20 3348 (0x0D14) Scan failed with error = 0x80072ee2. WUAHandler 28.03.2014 14:26:20 3348 (0x0D14) UpdateDeployment.log Detection job ({A426DC07-8934-4646-93DF-6B8021B117DC}) started for assignment ({97225002-7716-494D-B131-CE8DA8844BE5}) UpdatesDeploymentAgent 28.03.2014 14:25:17 2704 (0x0A90) Started evaluation for assignment ({97225002-7716-494D-B131-CE8DA8844BE5}) UpdatesDeploymentAgent 28.03.2014 14:25:17 2704 (0x0A90) Evaluation initiated for (3) assignments. UpdatesDeploymentAgent 28.03.2014 14:25:17 2704 (0x0A90) Job error (0x80072ee2) received for assignment ({0C305096-E2F7-4711-B4F3-54E50DD4D96C}) action UpdatesDeploymentAgent 28.03.2014 14:25:38 4536 (0x11B8) Updates will not be made available UpdatesDeploymentAgent 28.03.2014 14:25:38 4536 (0x11B8) Job error (0x80072ee2) received for assignment ({97225002-7716-494D-B131-CE8DA8844BE5}) action UpdatesDeploymentAgent 28.03.2014 14:25:59 4352 (0x1100) Updates will not be made available UpdatesDeploymentAgent 28.03.2014 14:25:59 4352 (0x1100) Job error (0x80072ee2) received for assignment ({AB0A307B-130F-492B-A200-128DD1CBB7B4}) action UpdatesDeploymentAgent 28.03.2014 14:26:20 3348 (0x0D14) Updates will not be made available UpdatesDeploymentAgent 28.03.2014 14:26:20 3348 (0x0D14) error number indicates a Time-out "The operation timed out" "Source: Winhttp" Telenet session on client is showing this: telnet XXXXXXX 8530 Connecting To XXXXXXX...Could not open connection to the host, on port 8530: Connect failed open ports on server (netstat -ano) ..... TCP 0.0.0.0:8530 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:8531 0.0.0.0:0 LISTENING 4 ..... TCP [::]:8530 [::]:0 LISTENING 4 TCP [::]:8531 [::]:0 LISTENING 4 Checked a lot things, but I am still stuck Don't know how to fix this, searching the web for days without luck. Any Help is appreciated ------------------------------------------------------------------------------------------------------------------ Update April 04 2012 even Microsoft Support was not able after hours of investigation and tests to fix the problem. At the end a Server reinstallation with OS and SCCM 2012 R2 was the way to go.