Jump to content


Riz

Established Members
  • Posts

    6
  • Joined

  • Last visited

Riz's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. 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.
  2. 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.
  3. 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
  4. Riz

    Build & Capture OSD Error

    The bindings on IIS look ok however I have found that I get a 403 Forbidden error from a domain workstation when attempting to access https://<MP Name?/sms_mp/.sms_aut?mplist This is the first attempt at deploying an OS
  5. Hi I have been struggling with the following problem for the last couple of days. We are attempting to deploy a Windows 7 image using SCCM in native mode. I have go most of the connectivity running but in the SMSTS.log on the client I get the following error: I have also noticed that I get the following on the Management Point IIS Logs 2009-12-01 12:13:49 172.18.2.36 GET /SMS_MP/.sms_pol PHX20012-PHX0001B-DBBBC9D6.1_00 443 - 172.18.108.8 OSD+Client 403 16 2148204809 15 I suspect a cert issue but now cannot see the wood for the trees, any assistance appreciated. Riz
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.