johnm Posted December 5, 2012 Report post Posted December 5, 2012 Hello all, looking for assistance with an issue we have after installing R2 onto a SCCM 2007 SP2 installation. (running on Windows 2008 + SQL 2008). new machines succesfully install the clients, but when looking at the "components" tab, all of them are in status "installed" and under actions tab only "computer policy" and "user policy" exist. checking the logfiles on the clients brings up this ccmexec.log Raising event: instance of CCM_CcmHttp_Status { DateTime = "20121205094822.825000+000"; HostName = "servername.domain.local"; HRESULT = "0x00000000"; ProcessID = 1724; StatusCode = 0; ThreadID = 3744; }; CCMEXEC 5/12/2012 10:48:22 3744 (0x0EA0) HandleRemoteSyncSend failed (0x8007000e). CCMEXEC 5/12/2012 10:48:22 3744 (0x0EA0) CForwarder_Sync::Send failed (0x8007000e). CCMEXEC 5/12/2012 10:48:22 3744 (0x0EA0) CForwarder_Base::Send failed (0x8007000e). CCMEXEC 5/12/2012 10:48:22 3744 (0x0EA0) ClientIDManagerStartup.log RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 5/12/2012 11:28:22 3744 (0x0EA0) RegTask: Failed to send registration request message. Error: 0x8007000e ClientIDManagerStartup 5/12/2012 11:28:22 3744 (0x0EA0) RegTask: Failed to send registration request. Error: 0x8007000e ClientIDManagerStartup 5/12/2012 11:28:22 3744 (0x0EA0) clients are assigned to the correct SITE, I can also correctly re-discover them. (ClientLocation.log) It can find the MP site (LocationServices.log) but gives an error regarding reset of certificate Failed to reset certificate request times. (0x80041002) LocationServices 5/12/2012 9:54:36 6772 (0x1A74) any help is much appreciated! Quote Share this post Link to post Share on other sites More sharing options...
johnm Posted December 5, 2012 Report post Posted December 5, 2012 clients and servers are in the same forest and domain, site is running in mixed mode since install (2010), to only thing that changed was installation of R2 last week.Install R2, reboot server; since then we get these errors on our newly deployed clients.... Quote Share this post Link to post Share on other sites More sharing options...
johnm Posted December 6, 2012 Report post Posted December 6, 2012 got this reply at MyITForum which resolves the issue You could spend time reading logs: iis logs, and any of the mp_ logs.But sometimes it's simply easier to 1) remove the management point (and watch mpsetup.log until it says it's uninstalled. 2) add the management point right back. and watch mpsetup.log. If there's something missing that the MP needed--during reinstall the mpsetup.log will tell you what. Or... the simple act of uninstall/reinstall will fix it. Basically "can't hurt to try" and uninstall/reinstall of the MP. Site Settings\Site Systems. Find the server that has the MP installed; click on it. In the right-hand pane, right click on "ConfigMgr management point" and select delete. watch the server-side log file of "mpsetup.log". It'll take 2-3 minutes to uninstall the Management Point. As soon as MP was reinstalled, I rebooted problem clients and they are now reporting to the SCCM server correctly Quote Share this post Link to post Share on other sites More sharing options...
edgekrusher Posted February 6, 2013 Report post Posted February 6, 2013 got this reply at MyITForum which resolves the issue As soon as MP was reinstalled, I rebooted problem clients and they are now reporting to the SCCM server correctly This solved my issue as well, it appears that something happened to the MP during the SP1 upgrade. I can only assume this as it was the only thing that changed in the environment before clients stopped reporting. Quote Share this post Link to post Share on other sites More sharing options...