WinPE Restarting

[Riz]

Hi

 

I have been successfully deploying OS images using SCCM 2007 Native for the past 18 months but last week they all stopped working. My initial suspicion was that the certificate has expired which was correct. I have now updated the certificate following MS guidelines but the OSD components are still not working.

I have enabled command support to get to the local SMSTS.log and when opened with Trace32 noticed a lot of 80004005 errors, excerpt as follows:

 

 

<![LOG[in SSL, but with no client cert]LOG]!><time="10:19:09.736+000" date="08-16-2011" component="TSPxe" context="" type="1" thread="1284" file="libsmsmessaging.cpp:7596">

<![LOG[The request has succeeded. 200 OK]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="libsmsmessaging.cpp:7734">

<![LOG[pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2072)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="libsmsmessaging.cpp:2072">

<![LOG[reply has no message header marker]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="3" thread="1284" file="libsmsmessaging.cpp:2072">

<![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,5010)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="libsmsmessaging.cpp:5010">

<![LOG[Failed to get client identity (80004005)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="3" thread="1284" file="libsmsmessaging.cpp:5269">

<![LOG[ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,815)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="tsmediawizardcontrol.cpp:815">

<![LOG[failed to request for client]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="3" thread="1284" file="tsmediawizardcontrol.cpp:815">

<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="tsmediawizardcontrol.cpp:1108">

<![LOG[GetPolicy(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2072)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="tsmediawizardcontrol.cpp:2072">

<![LOG[RunWizardForPXE(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2402)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="tsmediawizardcontrol.cpp:2402">

<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="tsmbootstrap.cpp:937">

<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106)]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="0" thread="1284" file="tsmbootstrap.cpp:1106">

<![LOG[Exiting with return code 0x80004005]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSPxe" context="" type="1" thread="1284" file="tsmbootstrap.cpp:1118">

<![LOG[Execution complete.]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSBootShell" context="" type="1" thread="864" file="bootshell.cpp:624">

<![LOG[Finalizing logging from process 816]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSBootShell" context="" type="1" thread="864" file="tslogging.cpp:1736">

<![LOG[Finalizing logs to root of first available drive]LOG]!><time="10:19:10.344+000" date="08-16-2011" component="TSBootShell" context="" type="1" thread="864" file="tslogging.cpp:1578">

<![LOG[successfully finalized logs to C:\SMSTSLog]LOG]!><time="10:19:10.375+000" date="08-16-2011" component="TSBootShell" context="" type="1" thread="864" file="tslogging.cpp:1635">

<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="10:19:10.375+000" date="08-16-2011" component="TSBootShell" context="" type="0" thread="864" file="tslogging.cpp:578">

 

Full attachment: smsts1.log

 

I have tried creating new boot media containing specific NIC drivers and also reduced the TS to its bare minimum to ensure that these are not affecting the deployment all to no avail

 

Any assistance greatly appreciated

 

Riz

[Peter van der Woude]

Which certificate was expired and which steps did you perform to renew it?

[Riz]

We had to replace the site server signing certificate.

 

I followed these instructions http://blogs.technet.com/b/configmgrteam/archive/2009/02/11/how-to-renew-the-site-server-signing-certificate-microsoft-certificate-services.aspx However, instead of creating the request and running the command line we used requested the certificate via the certificate MMC.

 

We have also since replaced the PXE Certificate.

[Riz]

Problem Solved.

 

The SMS_SITE_COMPONENT_MANAGER was not able to restart correctly due to connectivity issues with the WSUS server. This meant that the service was unable to update the certificate information on the SCCM Server. Once connectivity was re-established the SMS_SITE_COMPONENT_MANAGER successfully completed all of its tasks and OSD is now working.

[Peter van der Woude]

Nice and thanks for posting the solution!

[ajbar]

I had the same problem with error 5436 appearing on the site system status for my MP. it drove me crazy because a lot of people were experiencing this error and a lot of solutions were to uninstall the MP and ISS and that sort of things.

Works great in a lab environment but not in a production environment.

 

What solved it for me was a SITE RESET. described here http://technet.micro...y/bb694286.aspx followed by a reboot.

 

Hope this will help others with this problem

[Mikey C]

It is incredibly annoying that every here have suggested very drastic fixes, such as site resets, create new certs etc.

 

We are experiencing this problem ONLY on XenCenter. The boot images work fine on everything else. PXE works fine on everything else. Works fine on VSphere, works fine on VirtualBox, works fine on hype-v, works fine on physical machines.

 

I have confirmed the time in the Xencenter VM is correct, the date is correct so doesnt seem to be cert related (no error message indicating cert issue).

 

The error message we receive is identical to this one http://777notes.wordpress.com/2012/10/09/sccm-2012-failed-to-get-client-identity-80004005/ - but the time and date are correct (its NOT A PHYSICAL MACHINE!!! Cant change the BIOS time/date). This is soo frustrating!!!!

 

Also, when pressing F8 to open a dos window, we cannot map drives "system error 64 has occurred The specified network name is no longer available". I have recreated the boot images using the very latest (different) NIC drivers, so i am convinced its nothing to do with that.

 

What a major PITA.