none
Failed to get client Identity

    Question

  • Hi,

     

    Winpe reboots after initializing the network card.

    Other people have had this issue but their problems seemed to be cert. related - I'm not running in native mode.

     

     

    I'm trying to Capture an XP SP2 reference image and get the following error in my smsts.log:

     

    Requesting client identity

    pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,1825)

    reply has no message header marker

    DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,4674)

    Failed to get client identity (80004005)

    ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,793)

    failed to request for client

     

     

    Thanks

    Deon

    Thursday, November 01, 2007 2:52 PM

Answers

  • This is way past the PXE boot process (which works and the client is found)- the smsts.log file exists on the client machine already and this extract is from there.

     

    Anyway - I rebuilt my SCCM server myself with the pre-requisites and this portion is working now.

     

    I'm guessing some kind of config never happened on IIS on the original install.

     

    Thanks anyway

     

    Deon

     

    Wednesday, November 07, 2007 1:07 PM

All replies

  • This is most likely because you did not import the machine information for this client.

    Friday, November 02, 2007 6:01 PM
  • This is way past the PXE boot process (which works and the client is found)- the smsts.log file exists on the client machine already and this extract is from there.

     

    Anyway - I rebuilt my SCCM server myself with the pre-requisites and this portion is working now.

     

    I'm guessing some kind of config never happened on IIS on the original install.

     

    Thanks anyway

     

    Deon

     

    Wednesday, November 07, 2007 1:07 PM
  • While I am happy your up and running, rebuilding servers is not an acceptable answer.  What happens when you are in production and can no longer rebuild on a whim.  Microsoft experts reading these thread(s) about PXE imaging need to step up.  There are dozens of PXE imaging issues on this forum, MyITForum, etc.  There is not good troubleshooting documentation.

     

    In every case, the solutions are vague.  There is no systematic troubleshooting list from Microsoft.  Everyone is groping and guessing.  They are getting tidbits in logs that are not convenient (e.g. SMSTS.log on "command-line enabled" WinPE booted clients) to troubleshoot.

     

    We cannot keep doing what everyone seems to do...  "I uninstalled..."  "I rebuilt..."  "I rebooted..."   etc.  Restarting services and rebooting may be possible/practical, but rebuilding and unspecified uninstall/install sequences are not acceptable.

     

    These systems are supposed to be up and reliable.  Yesterday, I had three consecutive PXE boot installations.  Things were working perfectly.  I then decided to add a custom wallpaper to the boot image and AntiVirus to the task sequence.  There were no indications of problems with either step.  Now PXE installation have broken.

    I found the PXE Cert not set error in the SMSPXE.log.  Why?  What would cause the certificate to go bad? 

    I reset the expiration date on the PXE server role and that error went away.  Yesterday, that was the second to last step to getting things running.  When I did that and then reset my Network Access Account, everything worked perfectly.  Now the SMSTS.log from the client includes an
    80004005 error.  That usually means "permissions" are not right.  Here is the extract:

    reply has no message header marker TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    DoRequest (sReply, true), HRESULT=80004005
    (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,4674) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    Failed to get client identity (80004005) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    ClientIdentity.RequestClientIdentity (), HRESULT=80004005
    (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,793) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    failed to request for client TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    Exiting TSMediaWizardControl::GetPolicy. TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    GetPolicy(), HRESULT=80004005

     






    Today, the full PXE client SMSTS.log shows:




    ...
    we are booted using PXE TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    we are booted using PXE and we use a generated password TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,185) TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    SMS::Crypto:Big SmileES:Big SmileecryptBuffer( (BYTE*)pszPassword, wcslen(pszPassword)*sizeof(WCHAR), encryptedBuffer.getBuffer(), encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,386) TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Verifying media password. TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Found network adapter "Intel(R) PRO/1000 MT Network Connection" with IP Address 192.168.1.105. TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,185) TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    SMS::Crypto:Big SmileES:Big SmileecryptBuffer( (BYTE*)pszPassword, wcslen(pszPassword)*sizeof(WCHAR), encryptedBuffer.getBuffer(), encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sms_fre\sms\framework\tscore\tsremovablemedia.cpp,386) TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Entering TSMediaWizardControl::GetPolicy. TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting LogMaxSize to 1000000 TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting LogMaxHistory to 1 TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting LogLevel to 0 TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting LogEnabled to 1 TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting LogDebug to 1 TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Loading variables from the Task Sequencing Removable Media. TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSMediaGuid TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSBootMediaPackageID TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSHTTPPort TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSHTTPSPort TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSIISSSLState TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSLaunchMode TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSMP TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSMPCerts TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSMPPort TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSMediaPFX TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSPublicRootKey TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSSiteCode TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Setting _SMSTSUseFirstCert TS environment variable TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    MP Ports: http=80, https=443, default=80 TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Missing root CA environment variable from variables file TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Custom hook from X:\\TSConfig.INI is  TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    No custom hook found TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    No Need to create Authenticator Info TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Getting MP time information TSPxe 4/3/2008 12:06:41 PM 1372 (0x055C)
    Requesting client identity TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    CLibSMSMessageWinHttpTransport:Tongue Tiedend: URL: LBI-SCCM-01-1-S.LBI.NET:80  CCM_POST /ccm_system/request TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,1825) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    reply has no message header marker TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    DoRequest (sReply, true), HRESULT=80004005
    (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,4674) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    Failed to get client identity (80004005) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    ClientIdentity.RequestClientIdentity (), HRESULT=80004005
    (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,793) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    failed to request for client TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    Exiting TSMediaWizardControl::GetPolicy. TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    GetPolicy(), HRESULT=80004005
    (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2007) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    RunWizardForPXE(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2308) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,936) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1045) TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    Exiting with return code 0x80004005 TSPxe 4/3/2008 12:06:42 PM 1372 (0x055C)
    Execution complete. TSBootShell 4/3/2008 12:06:42 PM 860 (0x035C)

     

    Thursday, April 03, 2008 6:18 PM
  • Did you get a resolution? I'm getting the PXE errors at more and more clients. I'm writing PXE off as a bad implementation when it comes the CERT part of the design.

     

    Microsoft there must be a step-by-step guide with real explanations. I'm in production. I can’t rebuild, restart, etc. I NEED a resolution.

     

    I'm spending on average 30% of my project time on PXE. I'm not selling this feature anymore, there is simple to many issues.

     

    If clients ask me I will show them many unsolved posts on the internet.

     

    I’m at a client now and PXE is not working. I have spent 48 hours fault finding. All our profits as a partner go down the drain when we try to sell Operating System Deployment feature.

     

    I have work with SMS since version 1.1. I saw some pain points in SMS 2.0. I’m seeing those same pain points in SCCM.

    In my smsts.log

    CryptMsgControl (hMsg, 0, CMSG_CTRL_VERIFY_SIGNATURE, pCert->pCertInfo), HRESULT=8009100e (e:\nts_sms_fre\sms\framework\osdmessaging\libcrypt.cpp,240)

    ipCertContext != listpServerCertContext.end(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2230)

    signature check failed:

    DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,4674)

     

    failed to request for client

     

    Friday, April 11, 2008 2:31 PM
  • Hi @all,

    is there any news or resolution on this?

    I am playing around with OSD and SCCM2007 R2 and am facing the same issue. I have gone step-by-step by the windows.noob.com guide for capturing a reference computer and ended up the same WinPE reboot without error like many others did ( I would have expected at least a dialog on screen, that tells a human understandable reason. ).

    Digging into the logs ( and it took me a long time until I understood where to look ). I found similar issues like Robert.

    <![LOG[Setting _SMSTSx64UnknownMachineGUID TS environment variable]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:551">
    <![LOG[Setting _SMSTSx86UnknownMachineGUID TS environment variable]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:551">
    <![LOG[MP Public Certs=308201E03082014DA0030201020210EBDAC7B4856E9EBA4ABDF7A2FEA637BF300906052B0E03021D05003025311530130603550403130C57324B335343434D32303037310C300A06035504031303534D533020170D3039303531313231303632345A180F32313039303431383231303632345A3025311530130603550403130C57324B335343434D32303037310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100CF766BC6F76743B38A5F001D97E254CA0A12C6C259078E795B4BB5936BE2558E38AEE4F8A1D5368E6E4146596B5D11A6F77B8122D4D12EDF486FF8A4E0412F39D0BF722BD7E2D9156E981FADB4330B3CE984DC17F162DB783C7B6E9B99D1952BFBD72CE6AF9FCAD82739F16A0D1D1E7443F446F239E814AFCE0A2188BD935DFB0203010001A317301530130603551D25040C300A06082B06010401823765300906052B0E03021D0500038181000086C6EAA50D6513D31C685AA59C9F9F80EB01ED199955BD5C605AB85182801B51267BC9B0B9AD10160B697EA639DFC081122B43A4229214F79C5D6312A351C26736E5042530C473E58F2CF10FD6DE7C3F5550F8C11146672F0CD9CACC35137A654944D66E97DD0E9526107B9E6CADDC1A5F5AB45828CA2B6A9B12EE14DF27C5]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:564">
    <![LOG[MP: server=w2k3sccm2007.XXX.dyndns.org, http=80, https=443, default=80]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:571">
    <![LOG[Root CA Public Certs=]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:576">
    <![LOG[Missing root CA environment variable from variables file]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:582">
    <![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:615">
    <![LOG[No custom hook found]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:452">
    <![LOG[No Need to create Authenticator Info]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:741">
    <![LOG[Getting MP time information]LOG]!><time="23:49:12.656+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmediawizardcontrol.cpp:752">
    <![LOG[Requesting client identity]LOG]!><time="23:49:12.703+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="libsmsmessaging.cpp:4910">
    <![LOG[Formatted header:]LOG]!><time="23:49:12.703+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="libsmsmessaging.cpp:1500">
    <![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>a401dfc8-321d-4622-b037-4569006b2a3d</SourceID><SourceHost/><TargetAddress>mp:[http]MP_ClientIDManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-05-31T07:49:12Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="306"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>MP_ClientIDManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
    ]LOG]!><time="23:49:12.703+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="libsmsmessaging.cpp:1501">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: w2k3sccm2007.XXX.dyndns.org:80  CCM_POST /ccm_system/request]LOG]!><time="23:49:12.718+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="libsmsmessaging.cpp:7446">
    <![LOG[Error. Status code 405 returned]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="libsmsmessaging.cpp:7742">
    <![LOG[pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2072)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="libsmsmessaging.cpp:2072">
    <![LOG[reply has no message header marker]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="3" thread="404" file="libsmsmessaging.cpp:2072">
    <![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,5010)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="libsmsmessaging.cpp:5010">
    <![LOG[Failed to get client identity (80004005)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="3" thread="404" file="libsmsmessaging.cpp:5269">
    <![LOG[ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,814)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="tsmediawizardcontrol.cpp:814">
    <![LOG[failed to request for client]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="3" thread="404" file="tsmediawizardcontrol.cpp:814">
    <![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="tsmediawizardcontrol.cpp:1107">
    <![LOG[GetPolicy(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2058)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="tsmediawizardcontrol.cpp:2058">
    <![LOG[RunWizardForPXE(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2383)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="tsmediawizardcontrol.cpp:2383">
    <![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,936)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="tsmbootstrap.cpp:936">
    <![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1105)]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="0" thread="404" file="tsmbootstrap.cpp:1105">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSPxe" context="" type="1" thread="404" file="tsmbootstrap.cpp:1117">
    <![LOG[Execution complete.]LOG]!><time="23:49:12.812+000" date="05-30-2009" component="TSBootShell" context="" type="1" thread="832" file="bootshell.cpp:624">
    <![LOG[Finalizing logging from process 796]LOG]!><time="23:49:12.828+000" date="05-30-2009" component="TSBootShell" context="" type="1" thread="832" file="tslogging.cpp:1736">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="23:49:12.828+000" date="05-30-2009" component="TSBootShell" context="" type="1" thread="832" file="tslogging.cpp:1578">
    <![LOG[Successfully finalized logs to X:\SMSTSLog]LOG]!><time="23:49:12.828+000" date="05-30-2009" component="TSBootShell" context="" type="1" thread="832" file="tslogging.cpp:1635">
    <![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="23:49:12.828+000" date="05-30-2009" component="TSBootShell" context="" type="0" thread="832" file="tslogging.cpp:578">

    My system looks like this:
    - All runs in Hyper-V on W2K8 SP1
    - SCCM Machine is a W2K3 R2 all patches applied
    - SCCM 2007 R2 applied
    - WDS installed with no errors
    - The PXE client ( the reference machine ) is a Hyper-V Machine with 1 GB RAM an empty VHD as a disk
    - MAC address and GUID have been published to the collection, TS advertised to the collection ( I followed the guide as much to the word as possible )

    I will rebuild my system now, but I'll keep the original VHD. I hope I will not face the same issue on a new and clean SCCM install ... let's see what i happening.
    I totally agree Robert ... rebuilding can't be a solution, but after troubleshooting this for 3 nights of my free time, this will be the final attempt of deploying an OS using OSD in SCCM. BTW ... I also tested plain WDS with XP and Vista ( and mixed ) and both went very easy, so I don't understand, why deploying this with SCCM seems such a trouble. But probably I am doing something wrong.

    CU Daniel

    EDIT1:
    I completely set up the environment from scratch ... cost me the sunday ... ending in the same result.

    EDIT2:
    OK ... I got a little closer ... at least it seems so ... I F8 into the booting WinPE and using the command line I see, that the FQDN of my SCCM gets resolved to the outside IP adress of my router.

    so the http request against w2k3sccm20072.XXX.dyndns.org ( w2k3sccm20072 ... is the new server ... ;-) ... ) gets resolved to some 91.x.x.x IP instead of the local 192.x.x.x. Of course that request is bound to fail.

    I already tested to simply route all port 80 traffic back to w2k3sccm20072, but that didn't help ( didn't expect it would ). Other machines on the same 192.x.x.x network are able to resolve w2k3sccm20072 by full and short name.

    That leaves me with 2 ways to resolve and on both I don't know how to do it at the moment ... a) either I make WinPE resolve the IP adress correctly, or b) I stop WinPE from using the FQDN. Which leaves me with the question ... where does the FDQN come from. Does it get in, when installing SCCM and configuring the site? or does it get in, when creating the task sequence? Does the FQDN come from the IP configuration and therefore from the DNS suffix in the router or does it come from the FQDN of the server, that comes from the Domain ( and is seen in Control Panel -> System -> Name )? I have no idea how to do a) so the question is how can I get rid of the FQDN and let SCCM only use the short name?

    Any suggestions ???

    with kind regards
    Daniel

    EDIT3:

    OK ... now I did the following ... I changed my router, so that DHCP clients get the DC as DNS. The DC is able to resolve the FQDN to the local IP adresses of the machines and does not point to the outside IP adress of the router.

    This got me a step further and the http request as seen above does no longer fail.

    However now another name resolution fails:

    <![LOG[Attempting to connect to "\\W2K3SCCM20072.XXX.dyndns.org\SMSPKGE$\BDH00003".]LOG]!><time="23:07:00.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="23:07:00.557+-120" date="05-31-2009" component="TSPxe" context="" type="1" thread="924" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\W2K3SCCM20072.XXX.dyndns.org\SMSPKGE$\BDH00003".]LOG]!><time="23:07:03.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="23:07:03.557+-120" date="05-31-2009" component="TSPxe" context="" type="1" thread="924" file="tsconnection.cpp:508">
    <![LOG[Attempting to connect to "\\W2K3SCCM20072.XXX.dyndns.org\SMSPKGE$\BDH00003".]LOG]!><time="23:07:06.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tsconnection.cpp:501">
    <![LOG[Retrying download...]LOG]!><time="23:07:06.557+-120" date="05-31-2009" component="TSPxe" context="" type="1" thread="924" file="tsconnection.cpp:508">
    <![LOG[dwErr, HRESULT=80070005 (e:\nts_sms_fre\sms\framework\tscore\tsconnection.cpp,517)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tsconnection.cpp:517">
    <![LOG[Failed to connect to "\\W2K3SCCM20072.XXX.dyndns.org\SMSPKGE$\BDH00003" (5)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="3" thread="924" file="tsconnection.cpp:517">
    <![LOG[!slistSMBPaths.empty(), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2161)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="resolvesource.cpp:2161">
    <![LOG[FALSE, HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1635)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tspolicy.cpp:1635">
    <![LOG[Content location request for BDH00003:2 failed. (Code 0x80040103)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="3" thread="924" file="tspolicy.cpp:1635">
    <![LOG[pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tspolicy.cpp:2330">
    <![LOG[(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040103 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tspolicy.cpp:2862">
    <![LOG[m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040103 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1207)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tsmediawizardcontrol.cpp:1207">
    <![LOG[Failed to resolve selected task sequence dependencies. Code(0x80040103)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="3" thread="924" file="tsmediawizardcontrol.cpp:1207">
    <![LOG[ResolveAndExecuteSelectedTaskSequence( 0, 0, 0 ), HRESULT=80040103 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2099)]LOG]!><time="23:07:09.557+-120" date="05-31-2009" component="TSPxe" context="" type="0" thread="924" file="tsmediawizardcontrol.cpp:2099">

    Now the client is not able to resolve the share on which dependend packages for the Task Sequence reside ... Gr8.

    Stay tuned.

    Daniel

    Sunday, May 31, 2009 10:03 AM
  • ok ... I got EDIT3 resolved ... when trying to fix EDIT2 I messed up the computer name of my server so it couldn't be resolved using \\servername.domain.name ... I had to take the server of the domain and put it back in to resolve ... mia culpa.

    However EDIT4:
    I am now stuck with some other problem. My task sequence now starts, partitions the disk, formats it. When it tries to apply the OS I get an error on screen that says:
    Capture Sequence stopped with error 8000405 ( sorry the message went away too fast ). However the smsts.log does not give a clue, what went wrong.

    <![LOG[OSDDiskPart.exe completed successfully]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="OSDDiskPart" context="" type="1" thread="1144" file="main.cpp:1495">
    <![LOG[Process completed with exit code 0]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="commandline.cpp:1102">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="instruction.cxx:3010">
    <![LOG[Successfully complete the action (Partition Disk 0) with the exit win32 code 0]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="instruction.cxx:3036">
    <![LOG[Sending status message . . .]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:292">
    <![LOG[Send a task execution status message SMS_TSExecution_ActionCompleteInfo]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:314">
    <![LOG[MP server W2K3SCCM20072.blackbirddh.dyndns.org and port 80. SSL=false. CRL=false.]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:458">
    <![LOG[Site code: BDH]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:489">
    <![LOG[Client machine name: VistaBuild01]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:494">
    <![LOG[Client Identity: GUID:DA7C7646-1262-4DE9-AB8E-CBEFA60B137E]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:496">
    <![LOG[Advertisement ID: BDH20002]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:505">
    <![LOG[Package ID: BDH0000B]LOG]!><time="02:38:05.219+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="utility.cxx:507">
    <![LOG[Sending StatusMessage]LOG]!><time="02:38:05.235+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="libsmsmessaging.cpp:3806">
    <![LOG[Formatted header:]LOG]!><time="02:38:05.235+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="libsmsmessaging.cpp:1500">
    <![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>23467f10-cb60-43dd-949c-64835f6f92b3</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2009-06-01T00:38:05Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="4218"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
    ]LOG]!><time="02:38:05.235+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="libsmsmessaging.cpp:1501">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: W2K3SCCM20072.blackbirddh.dyndns.org:80  CCM_POST /ccm_system/request]LOG]!><time="02:38:05.235+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="libsmsmessaging.cpp:7446">
    <![LOG[The request has succeeded. 200 OK]LOG]!><time="02:38:05.266+-120" date="06-01-2009" component="TSManager" context="" type="0" thread="1088" file="libsmsmessaging.cpp:7734">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="02:38:05.266+-120" date="06-01-2009" component="TSManager" context="" type="0" thread="1088" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="02:38:05.266+-120" date="06-01-2009" component="TSManager" context="" type="0" thread="1088" file="executionenv.cxx:668">

    a little farer up in the log there are some error messages, but the disk partitioning and formatting starts fine after this:

    <![LOG[Failed to save environment to  (80070057)]LOG]!><time="02:37:47.922+-120" date="06-01-2009" component="TSManager" context="" type="2" thread="1088" file="environmentlib.cpp:643">
    <![LOG[TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842)]LOG]!><time="02:37:47.922+-120" date="06-01-2009" component="TSManager" context="" type="0" thread="1088" file="executionenv.cxx:842">
    <![LOG[Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="02:37:47.922+-120" date="06-01-2009" component="TSManager" context="" type="3" thread="1088" file="executionenv.cxx:842">
    <![LOG[SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420)]LOG]!><time="02:37:47.922+-120" date="06-01-2009" component="TSManager" context="" type="0" thread="1088" file="executionenv.cxx:420">
    <![LOG[Failed to persist execution state. Error 0x(80070057)]LOG]!><time="02:37:47.922+-120" date="06-01-2009" component="TSManager" context="" type="2" thread="1088" file="executionenv.cxx:426">
    <![LOG[Failed to save execution state and environment to local hard disk]LOG]!><time="02:37:47.922+-120" date="06-01-2009" component="TSManager" context="" type="2" thread="1088" file="engine.cxx:250">
    <![LOG[Start executing an instruciton. Instruction name: Restart in Windows PE. Instruction pointer: 1]LOG]!><time="02:37:47.922+-120" date="06-01-2009" component="TSManager" context="" type="1" thread="1088" file="engine.cxx:117">

    I will probably rebuild the task sequence and see what happens ... ( after I slept )

    stay tuned ...
    Daniel


    EDIT5 ... ok redoing the task sequence didn't do it ... I am stuck for now ...
    Monday, June 01, 2009 12:58 AM
  • EDIT6 ... so ... 
     
    now the setupapi.app.log has something to complain. ... seems like it is missing video drivers ...

    >>>  [DIF_SELECTBESTCOMPATDRV - PCI\VEN_1414&DEV_5353&SUBSYS_00000000&REV_00\3&267A616A&0&40]
    >>>  Section start 2009/06/01 03:55:34.609
          cmd: wpeinit.exe -winpe
         dvi: No class installer for 'Video Controller (VGA Compatible)'
         dvi: No CoInstallers found
         dvi: Default installer: Enter 03:55:34.609
         dvi:      {Select Best Driver}
    !    dvi:           Selecting driver failed(0xe0000228)
         dvi:      {Select Best Driver - exit(0xe0000228)}
    !    dvi: Default installer: failed!
    !    dvi: Error 0xe0000228: There are no compatible drivers for this device.
    <<<  Section end 2009/06/01 03:55:34.609
    <<< [Exit status: FAILURE(0xe0000228)]

    ... I would have expected that an installation in a Hyper-V guest will do withouth video drivers ... but it doesn't look so ...
    so I'll add the Hyper-V integration disk drivers to the task sequence ... but I need to sleep first .... ;-) ...

    Stay tuned ...

    EDIT 7
    Now I added all drivers of the Integration disk to SCCM, a package and the boot image ( and therefore implictily to the task sequence ... because that says to use all available drivers )

    However ... now WinPE crashes in storflt.sys from the Hyper-V Disk Acceleration Filter Driver .... I will remove that on

    ... stay tuned ...

    EDIT8 ... ok it boots now again, but the install stops with another error ... stay tuned ...

    EDIT9 ... so ... first of all ... now that a couple of things worked the smsts.log has stopped logging in \smstslog\smsts.log, but now resides in \windows\temp\smstslog\smsts.log ... took a moment to find that out ( I knew it would move from other posts on technet, but didn't remember from what point on ) 

    I know have this: 
    <![LOG[The detected setup program architecture does not match the current boot image. You must correct your task sequence so that the installation package matches the boot image.

    ... so what is happening ... before I tried to use OSD on SCCM I played around with WDS. There I used a x86 Vista and it just worked. Now I wanted to do something similar in SCCM ... a simple PXE boot OS installation for starters. However I already found out, that a task sequence with a x86 boot image will not fire, if the device is x64 capable ... 
    (see also ... http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/bebfeaea-10e0-4e54-b948-5927e3ef72e3)

    Now the above error message tells me, that I also need the x64 installation image ... in other words it looks like I now have to install x64 event though I would rather do a x86 ... anybody got a additional info on this? 

    ... I will now import the x64 Vista Installation Image and see what happens ... stay tuned ... 

    Daniel 
    P.S.: ... is there a way to make my Hyper-V Client VM non x64 capable? ... something like the Limit Processor Functionality switch? Maybe we'll find out later ... 

    EDIT 10: 
    OK after this final fix Vista is installing ... let's see whether the capture is doing well? ... I'll report back, when it's done ... gotta sleep while this is running ... ;-)

    EDIT 11:
    The capture now went through, also the deployment of the capture worked as descibed in the windows-noob.com walkthrough ( thx ... again, that article is great ).

    To sum it up:
    1)
    WinPE was unable to resolve IIS on the SCCM server to get the client identitiy, because it was using FQDN that my router resolved to the outside IP adress instead of the servers IP adress 
        a) Anlalysis: I activated command mode on WinPE and pinged the server using the URL in the failing request
        b) Resolution: I changed my DHCP to give the DC as the primary DNS. The DNS on the DC know the clients and was able to resolve the clients.
    2) ... ;-) .. reinstall is not the way to resolve issues ... find the root cause for your problems ... ;-) ...
    3) 1) also applies to the shares on your server, if getting files from your server failes ... F8 into command mode and check whether you can "net use" the shares that WinPE/the task sequence is trying to hit.
    4) if smsts.log does not help to locate the error, remember that the log moves to "windows\temp\smstslog\smsts.log" at a certain point of time. If that does not help remember to check the other logs for errors. I connected a drive to a share on another computer and copied the log files there for better analyis with other tools. I user bartail which has nice color highlighting ... makes finding errors, successes and fails much easier of they are red and green. If you are not sure, you can also do a "xcopy x:\*.log z:\mylogfolder\ /s /c" to copy all logs and analyze them on another computer using your favorite tool. In my case setupapi.app.log pointed to a driver that could not be loaded by WinPE. Remember ... even later during the OS install the smsts.log moves to a folder on c: under \_smststasksequence\ (... not sure anymore, but it was obvious once I saw it ) and the log was being split into two (the copy from WinPE and a new one), at the end, when OS installation is finished the log will be in c:\smstslog\smsts.log, so make sure to get the right one depending on where in the OS deployment process you are.
    5) Make sure, your boot image architecture matches the capability of your computer (if it can do x64, give it a x64 boot image).
    6) Also make sure, to use the same installation image architecture as the boot image.
    7) When testing on Hyper-V I removed the defaulted "normal" network adapter and added a legacy network adapter, because only that one is listed in the boot device list ... not sure whether it would work with the "normal" adapter.
    8) To deploy a x86 installation image on a x64 capable machine ... I read the following thread before, but didn't quite get the point of it: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/4ab2494f-ad8d-48fd-a454-be92bd003ff4
    The point is that to install an x86 image using an x86 boot image on a x64 capable machine you need a x64 boot image added to SCCM and distributed to an distribution point. Read Michael Kelley's post and you will understand what is happening. I just changed my system by adding a task sequence that has an x86 boot image and a x86 installation image, added a fresh client to my "capture collection" and it boots up and uses the x86 task sequence. I had to remove the vmbus.inf from WinPE as a driver to have things run smothly. Ohterwise I got an error, but deployment of the image continued. The deployment of the x86 image also went through all right.
    9) The Windows-Noob Guide on deploying Vista is a fantastic walthrough. Thx guys ... great job ... there is also a good troubleshooting thread on the forum. http://www.windows-noob.com/forums/index.php?s=1a906469866d2826623e4d31abf9aaee&showtopic=511

    OK ... I hope whoever reads this does not get unnerved by my lenghty thread and by me talking about my beginner mistakes trying to test SCCM OSD. I hope it helps others to troubleshoot their environment by getting ideas on where to look.

    Cheers,
    Daniel

    • Edited by blackbirddh13 Wednesday, June 03, 2009 5:24 PM added result of x86 test
    Monday, June 01, 2009 2:30 AM
  • I am seeing this same error 2 and a half YEARS after it was initially reported. Is there any solution for this?

    I agree with Rob - it is totally unacceptable to have to re-install everything from scratch. I have spent nearly a week trawling through every post(and there were hundreds) i could find regarding the pxe boot error and THIS is the best solution! How about a real fix.

     

    Why is this thread listed as answered when there is no solution for this ?

    Wednesday, September 15, 2010 5:45 AM
  • Hi guys, in my case the issue turned out to be the Expand network optimization device not sending through the SMS_POST command to our central site server at another site.

    We were getting the following after the initial PXE boot when the PC was looking for policy (also similar errors from a client advertised OS deployment):

    CLibSMSMessageWinHttpTransport::Send: URL: servername:80  CCM_POST /ccm_system/request TSManager 9/18/2010 1:06:29 AM 1820 (0x071C)
    Error. Status code 400 returned TSManager 9/18/2010 1:06:29 AM 1820 (0x071C)
    pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2072) TSManager 9/18/2010 1:06:29 AM 1820 (0x071C)
    reply has no message header marker TSManager 9/18/2010 1:06:29 AM 1820 (0x071C)
    DoRequest (sReply, false), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3835) TSManager 9/18/2010 1:06:29 AM 1820 (0x071C)
    Failed to send status message (80004005) TSManager 9/18/2010 1:06:29 AM 1820 (0x071C)

    The trick is to try and replicate the command that SCCM is failing on, that is: CCM_POST /ccm_system/request to the MP (in our case this was happening from a remote site where we have a secondary and the client was trying to connect over the WAN for policy from the primary).  If you do:

    telnet servername 80

    CCM_POST /ccm_system/request HTTP/1.0

    Then hit enter twice

    You should get a 200 OK response from the IIS SCCM web server.  In our case we got an invalid request error (400) from the Expand network device.

    Now for our network guys to respond to the call I logged to fix it!

    Friday, September 17, 2010 8:16 PM
  • Kevin, did you end up getting a resolution from your networking team? I am seeing this at my customer site:

      Failed to get client identity (80004005)

    Although we are running ConfigMgr 2012.  When I attempt the telnet command above, I don't get a chance to enter the CCM_POST, it replies back with a HTTP error 400 The request verb is invalid".  It seems to me though this may not be a valid way to test the site.


    Levi Stevens Technical Consultant - End User Computing - West Region Dell | Services

    Tuesday, July 24, 2012 11:07 PM
  • Hi Levi

    Didn't get notification of your message.  It turned out that the Expand network device was running on an expired license, and once the network team resolved this, the problem was fixed.

    I've just tested the telnet syntax on a test SCCM 2012 box and I'm getting the same result as you.  Looks like the syntax is no longer valid in 2012.  If you figure out a way of doing this, please post back.

    Cheers

    Kevin 

    Wednesday, August 22, 2012 2:19 PM
  • Same error here while trying to PXE a client on a ConfigMgr 2012 site.

    Failed to get client identity (80004005)

    Client PC had wrong BIOS clock (minus one year). Entering correct time in BIOS resolved this problem.

    • Proposed as answer by jeffdus Thursday, September 27, 2012 2:06 AM
    Friday, August 24, 2012 12:04 PM
  • Thanks Lars

    I was experiencing this same error on a new laptop that we just got from the supplier. I checked the bios, and the date was off by 6 months.

    Corrected the date in the bios, and the problem has now been resolved.

    Thursday, September 27, 2012 2:09 AM
  • Same situation here. Thank you for solution and contributing to this thread!
    Wednesday, September 18, 2013 10:58 AM
  • Thank you so much Lars! The BIOS clock was off by a few months, and correcting that lead to a nice boot and the subsequent imaging of the laptop.
    Thursday, February 13, 2014 10:47 AM