Offline OSD using USB is failing

[Robbie]

Hi guys,

 

I've got a pretty urgent issue that I hope you could help with:

 

* I've built a USB key from my ususal task sequence to enable us to build machines at our warehouse. Upon testing the USB key, joining the domain is failing! (we have a VPN into the business from the warehouse and it is working when adding a machine manually)

 

Does the "join domain or workgroup" task sequence section have to be at the begging of task sequence after Apply Windows settings? Or can it appear further down the task sequence after applying custom device drivers (to make sure the nic driver is working on these horrible new HP machines). The smsts.log is complaining about not been able to find an unattend.xml, however, I've never made an unattended.xml for my task sequence as it's a pretty simple build that asks for the machines name, throws on a standard windows 7 enterprise image with Office 2010 pro and installs very few device drivers.

 

Anyhow, here is the smsts.log extract. totally stumped. Please help!

 

 

Start executing an instruciton. Instruction name: Apply Network Settings. Instruction pointer: 40 TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a global environment variable _SMSTSCurrentActionName=Apply Network Settings TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a global environment variable _SMSTSNextInstructionPointer=40 TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a local default variable OSDDomainName TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a local default variable OSDDomainOUName TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a local default variable OSDJoinPassword TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a local default variable OSDJoinAccount TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a local default variable OSDNetworkJoinType TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a global environment variable _SMSTSLogPath=C:\Windows\SysWOW64\CCM\Logs\SMSTSLog TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Expand a string: osdnetsettings.exe configure TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Expand a string: TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Command line for extension .exe is "%1" %* TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set command line: osdnetsettings.exe configure TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Start executing the command line: osdnetsettings.exe configure TSManager 04/01/2012 15:36:47 2280 (0x08E8)

!--------------------------------------------------------------------------------------------! TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Expand a string: WinPEandFullOS TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Executing command line: osdnetsettings.exe configure TSManager 04/01/2012 15:36:47 2280 (0x08E8)

==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

Command line: "osdnetsettings.exe" configure OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

CoCreateInstance(CLSID_SettingsEngine, 0, CLSCTX_INPROC_SERVER, IID_ISettingsEngine, (LPVOID*)&m_spSettingsEngine), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\osdcore\smiinterface.cpp,803) OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

initialize( pszWindowsDir, wProcessorArchitecture, false ), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\osdcore\smiinterface.cpp,740) OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

m_pSMIInterface->initFromWindowsDir( pszSourceDir, wProcessorArchitecture ), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\osdcore\xmlanswerfile.cpp,572) OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

pXMLSysprepAnswerFile->Init( sAnswerFile, sTargetSystemDir, wProcessorArchitecture ), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\osdcore\infanswerfile.cpp,1433) OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

Failed to initialize unattend answer file C:\Windows\panther\unattend\unattend.xml. Code 0x80040154 OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

SysprepAnswerFile::InitSysprepAnswerFile( pSysprepAnswerFile ), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\osdcore\infanswerfile.cpp,333) OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

Failed to initialize Sysprep answer file (0x80040154) OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

OSD::Utility::BaseAnswerFile::CreateAnswerFile( pAnswerFile ), HRESULT=80040154 (e:\nts_sms_fre\sms\client\osdeployment\osdnetsettings\main.cpp,177) OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

Failed to initialize answer file OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

OSDNetSettings finished: 0x80040154 OSDNetSettings 04/01/2012 15:36:47 2208 (0x08A0)

Process completed with exit code 2147746132 TSManager 04/01/2012 15:36:47 2280 (0x08E8)

!--------------------------------------------------------------------------------------------! TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Failed to run the action: Apply Network Settings.

Class not registered (Error: 80040154; Source: Windows) TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Sending status message . . . TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Do not send status message in full media case TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a global environment variable _SMSTSLastActionRetCode=-2147221164 TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Clear local default environment TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Let the parent group (Join Domain) decides whether to continue execution TSManager 04/01/2012 15:36:47 2280 (0x08E8)

The execution of the group (Join Domain) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows) TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Failed to run the last action: Apply Network Settings. Execution of task sequence failed.

Class not registered (Error: 80040154; Source: Windows) TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Sending status message . . . TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Do not send status message in full media case TSManager 04/01/2012 15:36:47 2280 (0x08E8)

Launching command shell. OSDSetupHook 04/01/2012 15:37:57 308 (0x0134)

executing command: C:\Windows\system32\cmd.exe /k OSDSetupHook 04/01/2012 15:37:57 308 (0x0134)

executed command: C:\Windows\system32\cmd.exe /k OSDSetupHook 04/01/2012 15:37:57 308 (0x0134)

Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767) TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Task Sequence Engine failed! Code: enExecutionFail TSManager 04/01/2012 15:38:19 2280 (0x08E8)

**************************************************************************** TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Task sequence execution failed with error code 80004005 TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Cleaning Up. Removing Authenticator TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Clean up boot image stage path C:\_SMSTaskSequence\WinPE TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Cleaning up task sequence folder TSManager 04/01/2012 15:38:19 2280 (0x08E8)

DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508) TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Successfully unregistered Task Sequencing Environment COM Interface. TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Command line for extension .exe is "%1" %* TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Set command line: "C:\Windows\SysWOW64\CCM\TsProgressUI.exe" /Unregister TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Executing command line: "C:\Windows\SysWOW64\CCM\TsProgressUI.exe" /Unregister TSManager 04/01/2012 15:38:19 2280 (0x08E8)

==========[ TsProgressUI started in process 2716 ]========== TsProgressUI 04/01/2012 15:38:19 2712 (0x0A98)

Command line: "C:\Windows\SysWOW64\CCM\TsProgressUI.exe" /Unregister TsProgressUI 04/01/2012 15:38:19 2712 (0x0A98)

Unregistering COM classes TsProgressUI 04/01/2012 15:38:19 2712 (0x0A98)

Unregistering class objects TsProgressUI 04/01/2012 15:38:19 2712 (0x0A98)

Shutdown complete. TsProgressUI 04/01/2012 15:38:19 2712 (0x0A98)

Process completed with exit code 0 TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Successfully unregistered TS Progress UI. TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Setting program history for GMG001E7:* TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Opening the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Deleting the package ID from registry key HKLM\Software\Microsoft\SMS\Task Sequence\Package TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Deleting the program ID from registry key HKLM\Software\Microsoft\SMS\Task Sequence\Program TSManager 04/01/2012 15:38:19 2280 (0x08E8)

Start to cleanup TS policy TSManager 04/01/2012 15:38:19 2280 (0x08E8)

[Peter33]

You need to add the network drivers for every machine type to your PE boot wim.

[Robbie]

You need to add the network drivers for every machine type to your PE boot wim.

 

Sorry, but your reply provides me with no information other than what I already know. Or PE image does include the drivers needed, otherwise the machines we have currently building from PXE would not work.