Search the Community

Hello Everyone I am new to SCCM and recently dove into OSD to self train. On my initial install everything went smooth until an error came up. It may have just been a time sync issue however while troubleshooting I made the situation worse. Now I can not even pxe boot using System center. I receive several errors while trying to re-install pxe and whenever I try to load boot images it errors indicating failed to load binaries. I did read on some blogs that it could be an issue with a cert however I've tried unsuccessfully to install and nogo. Below are some of the errors from SMSpxe and Distmgr. I'm running Server 2012 R2 and SCCM R2. [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] : dwStatusInformationLength is 4 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] : *lpvStatusInformation is 0x10 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] : WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID is set SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) sending with winhttp failed; 80072f8f SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) Failed to get information for MP: https://DC.AD.CourtesyItsolutions.com. 80072f8f. SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) In SSL, but with no client cert SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] : dwStatusInformationLength is 4 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] : *lpvStatusInformation is 0x10 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] : WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID is set SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) [TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) sending with winhttp failed; 80072f8f SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) Failed to get information for MP: https://DC.AD.CourtesyItsolutions.com. 80072f8f. SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) 00:15:5D:00:05:02, B0305986-3893-4600-9D54-BF00B509A11B: Not serviced. SMSPXE 5/21/2016 1:59:11 PM 1860 (0x0744) In SSL, but with no client cert SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] : dwStatusInformationLength is 4 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] : *lpvStatusInformation is 0x10 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] : WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID is set SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) sending with winhttp failed; 80072f8f SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) Failed to get information for MP: https://DC.AD.CourtesyItsolutions.com. 80072f8f. SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) In SSL, but with no client cert SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] : dwStatusInformationLength is 4 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] : *lpvStatusInformation is 0x10 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] : WINHTTP_CALLBACK_STATUS_FLAG_CERT_CN_INVALID is set SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) [TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) sending with winhttp failed; 80072f8f SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) Failed to get information for MP: https://DC.AD.CourtesyItsolutions.com. 80072f8f. SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 5/21/2016 1:59:27 PM 1860 (0x0744) cannot connect with winhttp; 80072ee5 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) Failed to get information for MP: . 80072ee5. SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) cannot connect with winhttp; 80072ee5 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) Failed to get information for MP: . 80072ee5. SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) cannot connect with winhttp; 80072ee5 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) Failed to get information for MP: . 80072ee5. SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) cannot connect with winhttp; 80072ee5 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) Failed to get information for MP: . 80072ee5. SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 5/21/2016 2:03:37 PM 1860 (0x0744)

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">

I have a Domain Controller with Server 2008R2 and 2 Member Servers with Windows Server 2012 SQL Server 2008R2sp1 is Isnatalled on 1 and I wanna Install SCCM on another Member Server But it Shows an Error that IIS 7 is Not Integrated with BITS Any Solution to install IIS 7 or Connect BITS with IIS 8 Thanks in Advance