Freigeben über

ConfigMgr 2007: OSD Task Sequence fails to join the PC to the domain during Windows setup

  • Artikel

I'm sure you all noticed a remarkable lack of activity over the past week but I'll be cranking things up again very soon.  I've been out since November 20th on a much needed vacation to celebrate Thanksgiving with friends and family but I'm back in the office now and working to get caught up.  It was great taking a few days off as it gave me the chance to get caught up on a few things around the house and spend some time with the wife and kids, but at the same time I'm excited to get back and see what's new since I was out and start posting again on all the cool things we're up to. 

To start things off, here's a tip from long time contributor Frank Rojas on an issue you may see when you try to join your machines to the domain during an OS Deployment:

========

Issue: When running a SCCM 2007 OSD Task Sequence deployment to a PC, the PC will be successfully download the image, however when it runs through Windows Setup, the PC will eventually fail to join the domain and the Task Sequence will fail. Inspecting the "Apply Network Settings" task in the Task Sequence shows that all settings and accounts being used in the task are correct.

Looking at the SMSTS.log, the following error message will be repeat throughout the log:

Sending StatusMessage
Formatted header:
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>1dc5ca47-2e4e-42ef-9c32-231959eb878e</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2008-11-03T21:10:05Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2070"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>

CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 5 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 10 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 22 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
Will retry in 45 second(s)
Retrying...
CLibSMSMessageWinHttpTransport::Send: URL: <MP_Server>:80 CCM_POST /ccm_system/request
Error. Received 0x80072ee7 from WinHttpSendRequest.
unknown host (gethostbyname failed)
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714)
sending with winhttp failed; 80072ee7
End of retries
Send (pReply, nReplySize), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,2052)
failed to send the request
DoRequest (sReply, false), HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,3835)
Failed to send status message (80072ee7)
smStatusMessage.Send(), HRESULT=80072ee7 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\utility.cxx,529)

Cause: This is caused by a missing NIC driver in the Windows installation. Either the NIC driver was missing or not available during the driver injection (Apply Device Drivers, Auto Apply Drivers, or Apply Driver Package tasks) of the Task Sequence and driver installation portion of Windows Setup. Because of this reason, the PC has no network connectivity, cannot join the domain, and the Task Sequence eventually fails. However, a NIC driver was present as part of the WinPE Boot Image, which allowed the deployment to get far along enough in the deployment process where it dropped the image down on the PC.

Resolution: To correct the problem follow the steps below:

1) Make sure that the appropriate NIC drivers for the model PC, Windows OS version, and architecture have been imported into the Operating System Deployment --> Drivers node in the SCCM 2007 Admin console.

2) Make sure that the imported NIC drivers from step 1 have been added to a Driver Package under the Operating System Deployment --> Driver Packages node in the SCCM 2007 Admin console.

3) Make sure that the Driver Package from step 2 has been copied to distribution points (DPs) that are accessible to the PC during the OSD Task Sequence deployment.

4) If using the "Apply Driver Package" task in the Task Sequence, make sure that Driver Package that contains the NIC driver is selected in the "Apply Driver Package" task next to the field "Driver Package". If filtering Driver Package by model using WMI queries under the Options tab of the "Apply Driver Package" task, ensure that the WMI query is correct and you choose the correct model PC.

========

Thanks Frank!

J.C. Hornbeck | Manageability Knowledge Engineer

Comments

  • Anonymous
    January 01, 2003
    thank you