gordonf Posted February 5, 2013 Report post Posted February 5, 2013 When I deployed SCCM 2012 SP1, I tore down my previous SCCM installation and rebuilt it on a Windows Server 2012 server with SQL Standard 2012. I managed to update the majority of my clients running XP and Windows 7. Today I tried installing the client on my first 2012 server, with the error code 80004005 in the subject. The following ccmsetup.log entries appear. What makes me scratch my head is that the client installed on the new SCCM server, which is also Server 2012. It does install by hand though; it says it couldn't install the Microsoft Policy Platform component. However, if I install this component separately (a simple "next next finish" install) I can do the rest of the setup. Is this a matter of Server 2012 being a little more paranoid about what's auto-installing? Do I have this to look forward to when I start rolling out Windows 8? <![LOG[Couldn't verify 'C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi' authenticode signature. Return code 0x800b0101]LOG]!><time="10:21:36.257+360" date="02-05-2013" component="ccmsetup" context="" type="3" thread="636" file="util.cpp:1236"><![LOG[Sending Fallback Status Point message to '[censored].[censored]', STATEID='316'.]LOG]!><time="10:21:36.257+360" date="02-05-2013" component="ccmsetup" context="" type="1" thread="636" file="ccmsetup.cpp:9421"><![LOG[Failed to get client version for sending messages to FSP. Error 0x8004100e]LOG]!><time="10:21:36.257+360" date="02-05-2013" component="ccmsetup" context="" type="2" thread="636" file="ccmsetup.cpp:9503"><![LOG[Params to send FSP message '5.0.7804.1000 Deployment Error 0x80004005. Pre-req file name: C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi']LOG]!><time="10:21:36.257+360" date="02-05-2013" component="ccmsetup" context="" type="0" thread="636" file="ccmsetup.cpp:9552"><![LOG[State message with TopicType 800 and TopicId {8018722F-2C22-4912-8906-49C35B0FA4C2} has been sent to the FSP]LOG]!><time="10:21:36.272+360" date="02-05-2013" component="FSPStateMessage" context="" type="1" thread="636" file="fsputillib.cpp:752"><![LOG[InstallFromManifest failed 0x80004005]LOG]!><time="10:21:36.272+360" date="02-05-2013" component="ccmsetup" context="" type="3" thread="636" file="ccmsetup.cpp:7086"><![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.xml]LOG]!><time="10:21:36.272+360" date="02-05-2013" component="ccmsetup" context="" type="1" thread="636" file="ccmsetup.cpp:9156"><![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="10:21:36.272+360" date="02-05-2013" component="ccmsetup" context="" type="1" thread="636" file="ccmsetup.cpp:10544"> Quote Share this post Link to post Share on other sites More sharing options...
jkabaseball Posted February 5, 2013 Report post Posted February 5, 2013 Looks like you are missing an update. There is a fix for the cert being bad. It's CU0. 1 Quote Share this post Link to post Share on other sites More sharing options...
Oneone Posted February 7, 2013 Report post Posted February 7, 2013 You need this hotfix http://support.microsoft.com/kb/2801987/en 1 Quote Share this post Link to post Share on other sites More sharing options...
gordonf Posted March 10, 2013 Report post Posted March 10, 2013 It's ben a while since I poked back to this thread. Applying the missing hotfix, or just applying the latest updates from WU, was enough. Thanks for the hints. Quote Share this post Link to post Share on other sites More sharing options...
AmrelMahdy Posted March 10, 2013 Report post Posted March 10, 2013 Attach the ccmsetup.log Quote Share this post Link to post Share on other sites More sharing options...