OS Deployment - Failed to get client identity 80004005

Question

Hello all,
Hopefully someone will have a solution to this issue. I've only found one site with a similar problem (http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2352753&SiteID=17) and the solution was to rebuild the SCCM server, which I have done. Yet the issue persists. After working my way through countless issues with SCCM, this seems to be the only obstacle in my way. Here is the situation:
1. I boot the bare metal client system to PXE and the boot image loads
2. The SCCM status messages appear "Windows is starting up..." and then "Preparing Network Connections..."
3. The client machine hangs for a minute or so, then reboots.
I have enabled the command prompt shell in the boot image and can ping the SCCM server and name resolution work fine, so I know it isn't an issue with the network drivers. Below is the log information from the client. Just as an FYI, the Server is running in "Mixed Mode", so I'm not really understanding the why the identification is an issue. As best I can understand the client is requesting information from the server at a certain point and getting a blank reply.
<![LOG[MP Ports: http=80, https=443, default=80]LOG]!><time="09:20:53.765+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="tsmediawizardcontrol.cpp:551">
<![LOG[Missing root CA environment variable from variables file]LOG]!><time="09:20:53.765+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="tsmediawizardcontrol.cpp:561">
<![LOG[Custom hook from X:\\TSConfig.INI is ]LOG]!><time="09:20:53.765+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="tsmediawizardcontrol.cpp:594">
<![LOG[No custom hook found]LOG]!><time="09:20:53.765+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="tsmediawizardcontrol.cpp:442">
<![LOG[No Need to create Authenticator Info]LOG]!><time="09:20:53.765+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="tsmediawizardcontrol.cpp:720">
<![LOG[Getting MP time information]LOG]!><time="09:20:53.781+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="tsmediawizardcontrol.cpp:731">
<![LOG[Requesting client identity]LOG]!><time="09:20:54.000+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="libsmsmessaging.cpp:4574">
<![LOG[CLibSMSMessageWinHttpTransport:end: URL: sccm.mpmc.hos:80  CCM_POST /ccm_system/request]LOG]!><time="09:20:54.062+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="libsmsmessaging.cpp:6043">
<![LOG[pNext != NULL, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,1825)]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="libsmsmessaging.cpp:1825">
<![LOG[reply has no message header marker]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="3" thread="1324" file="libsmsmessaging.cpp:1825">
<![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,4674)]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="libsmsmessaging.cpp:4674">
<![LOG[Failed to get client identity (80004005)]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="3" thread="1324" file="libsmsmessaging.cpp:4795">
<![LOG[ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,793)]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="tsmediawizardcontrol.cpp:793">
<![LOG[failed to request for client]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="3" thread="1324" file="tsmediawizardcontrol.cpp:793">
<![LOG[Exiting TSMediaWizardControl::GetPolicy.]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="tsmediawizardcontrol.cpp:1083">
<![LOG[GetPolicy(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2007)]LOG]!><time="09:20:54.109+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="tsmediawizardcontrol.cpp:2007">
<![LOG[RunWizardForPXE(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2308)]LOG]!><time="09:20:54.125+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="tsmediawizardcontrol.cpp:2308">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,936)]LOG]!><time="09:20:54.125+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="tsmbootstrap.cpp:936">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1045)]LOG]!><time="09:20:54.125+000" date="06-10-2008" component="TSPxe" context="" type="0" thread="1324" file="tsmbootstrap.cpp:1045">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="09:20:54.125+000" date="06-10-2008" component="TSPxe" context="" type="1" thread="1324" file="tsmbootstrap.cpp:1057">
<![LOG[Execution complete.]LOG]!><time="09:20:54.171+000" date="06-10-2008" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:620">
<![LOG[Finalizing logging from process 824]LOG]!><time="09:20:54.171+000" date="06-10-2008" component="TSBootShell" context="" type="1" thread="844" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="09:20:54.171+000" date="06-10-2008" component="TSBootShell" context="" type="1" thread="844" file="tslogging.cpp:1578">
<![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="09:20:54.250+000" date="06-10-2008" component="TSBootShell" context="" type="1" thread="844" file="tslogging.cpp:1635">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="09:20:54.250+000" date="06-10-2008" component="TSBootShell" context="" type="0" thread="844" file="tslogging.cpp:578">
I'm at my wits end with this software, if I can't find a solution to this problem pretty soon, I will tell management here to can the whole idea and stick with the norton ghost setup.

Answer 1

i had this problem today on a virtual lab ive got setup here (windows 2008 server, with sccm 2007sp1 deploying windows server..)
i had to rewrite my task sequence as it was giving me problems - (configuring ADDS) and after going through all the steps I tried yet another pxe boot and it failed, this time with the pxe error Failed to get client identity 80004005 in the SMSTSlog
I checked this log against a know good one from earlier on the same server and indeed the time/date are processed shortly after words, however i pxe booted again and verified time/date on the virtual pc and they were absolutely correct
I tried this and that for 2 hours with no positive result, lastly i rebooted the server and lo and behold the pxe error was gone.
I agree that we need a decent troubleshooting option from Microsoft about this as the documentation appears to be whatever is here or on other forums and in a lot of cases there are no solutions
does changing a task sequence somehow reprogram the PXE setup for WDS/sccm ? I have another server (real) beside me that now wont process PXE boot requests anymore even though it was working fine !
PXE-E51: no DHCP or proxyDHCP offeres were received....
no switch just a crossover network cable between server and client, client was  successfully deployed hours before with windows server 2008 via sccm via pxe boot.....
tried all the usual, not much hair left now....
found this site http://susanaguedes.spaces.live.com/Blog/cns!830A1768E1B27E94!350.entry
PXE-E51: No DHCP or proxyDHCP offers were received
The PC cannot contact the DHCP server. Possible causes (see ref [19]):
There is a problem with the DHCP server
The network card or PXE boot portion of the network card is faulty
The network cable is faulty
tested the client PXE boot to another server, worked fine using same network card and cable
the DHCP server on the server reports no problems and has worked fine since I set it up some months ago, indeed if i boot the client into windows server it will get an ip no problem from the dhcp server
so what is wrong here ? how can WDS/ SCCM pxe boot functionality turn itself on or off at will with no user intervention ???
restarted the server 3 times, no difference, restarted WDS many times, no difference, restarted DHCP server service and now I get
PXE-E55: proxyDHCP service did not reply to the request on port 4011
As slightly less common one, with various causes (see ref [19]). Usually the PC has successfully contacted the DHCP server and the PC will even report its DHCP assigned IP address along with the error, but the RIS process could not continue for some reason.
restarted the WDS service and it booted in Windows PE via pxe finally after hours of repetive tasks, only to bring me back to square one with the Windows PE rebooting itself immediatly after loading network support,
ok, back to troubleshooting....