none
Dell 12G | M620 | Fail to install OS | W2K8 R2

    Question

  • I'm trying to install 2008 R2 onto a 12G M620 Dell Server.  I get through all my steps of my TS up until it starts to drop the OS on the server.  It immediately fails at 0%.  I'm trying to figure out if I've got a bad driver (which it doesn't seem to be since I get to the OS install section) or if its something weird between the TS and the hardware.

    MDT2010 U1 also...

    LiteTouch.log (from the connection success)

    Successfully established connection using supplied credentials.	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    DeploymentType = NEWCOMPUTER	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    ResourceRoot = \\BLDMDT001\MDTTest$	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Property ResourceDrive is now = Z:	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    ResourceDrive = Z:	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Property _SMSTSPackageName is now = Lite Touch Installation	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    SMS Task Sequencer already found on X:\Deploy\Tools\X64	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Copying \\BLDMDT001\MDTTest$\Control\W2K8_STD_R2_BLD\TS.XML to X:\Deploy\Tools\X64	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to X:\Deploy\Tools\X64\VARIABLES.DAT	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Copy File: \\BLDMDT001\MDTTest$\Tools\x86\Microsoft.BDD.Utility.dll to X:\WINDOWS\TEMP\Tools\x86\	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    RUN: regsvr32.exe /s "X:\WINDOWS\TEMP\Tools\x86\Microsoft.BDD.Utility.dll"	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Copy File: \\BLDMDT001\MDTTest$\Tools\x64\Microsoft.BDD.Utility.dll to X:\WINDOWS\TEMP\Tools\x64\	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    RUN: regsvr32.exe /s "X:\WINDOWS\TEMP\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Determining the Disk and Partition Number from the Logical Drive	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Property DestinationDisk is now = 0	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Property DestinationPartition is now = 2	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    The logical drive was found on Disk 0 and Partition 2	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Verifying that the Disk and Partition exists	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Found Disk and Partition	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    About to run command: "X:\Deploy\Tools\X64\TsmBootstrap.exe" /env:SAContinue	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG.	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    Property RetVal is now = -2147467259	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    CleanStartItems Complete	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    About to run command: MSHTA.exe "X:\Deploy\Scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)

    Bdd.log (from connection successful)

    Successfully established connection using supplied credentials.	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    DeploymentType = NEWCOMPUTER	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    ResourceRoot = \\BLDMDT001\MDTTest$	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Property ResourceDrive is now = Z:	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    ResourceDrive = Z:	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Property _SMSTSPackageName is now = Lite Touch Installation	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    SMS Task Sequencer already found on X:\Deploy\Tools\X64	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Copying \\BLDMDT001\MDTTest$\Control\W2K8_STD_R2_BLD\TS.XML to X:\Deploy\Tools\X64	LiteTouch	3/14/2012 10:50:03 AM	0 (0x0000)
    Copying D:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to X:\Deploy\Tools\X64\VARIABLES.DAT	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Copy File: \\BLDMDT001\MDTTest$\Tools\x86\Microsoft.BDD.Utility.dll to X:\WINDOWS\TEMP\Tools\x86\	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    RUN: regsvr32.exe /s "X:\WINDOWS\TEMP\Tools\x86\Microsoft.BDD.Utility.dll"	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Copy File: \\BLDMDT001\MDTTest$\Tools\x64\Microsoft.BDD.Utility.dll to X:\WINDOWS\TEMP\Tools\x64\	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    RUN: regsvr32.exe /s "X:\WINDOWS\TEMP\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Determining the Disk and Partition Number from the Logical Drive	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Property DestinationDisk is now = 0	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Property DestinationPartition is now = 2	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    The logical drive was found on Disk 0 and Partition 2	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Verifying that the Disk and Partition exists	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Found Disk and Partition	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    About to run command: "X:\Deploy\Tools\X64\TsmBootstrap.exe" /env:SAContinue	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Property LogPath is now = D:\MININT\SMSOSD\OSDLOGS	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    Microsoft Deployment Toolkit version: 5.1.1642.01	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    	Open Control File: OperatingSystems	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    ------  Applying Windows image using Setup.exe ------	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    LTI applying image \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim using SETUP.EXE	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    Found a matching SETUP in \\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    Cleaning off old operating system	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    Installing image from \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim using command: "\\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources\setup.exe" /noreboot /unattend:D:\MININT\unattend.xml /m:"\\BLDMDT001\MDTTest$\$OEM$"	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    About to run command: "\\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources\setup.exe" /noreboot /unattend:D:\MININT\unattend.xml /m:"\\BLDMDT001\MDTTest$\$OEM$"	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    Return code from command = 31	LTIApply	3/14/2012 10:52:11 AM	0 (0x0000)
    Setup failed applying image \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim, rc = 31	LTIApply	3/14/2012 10:52:11 AM	0 (0x0000)
    ZTI ERROR - Non-zero return code by LTIApply, rc = 31	LTIApply	3/14/2012 10:52:11 AM	0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG.	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    Property RetVal is now = -2147467259	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    CleanStartItems Complete	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    About to run command: MSHTA.exe "X:\Deploy\Scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    Property definition is now = Summary_Definition_ENU.xml	Wizard	3/14/2012 10:52:12 AM	0 (0x0000)
    Microsoft Deployment Toolkit version: 5.1.1642.01	Wizard	3/14/2012 10:52:12 AM	0 (0x0000)
    Not Wizard = False	Wizard	3/14/2012 10:52:12 AM	0 (0x0000)
    Property WizardComplete is now = N	Wizard	3/14/2012 10:52:13 AM	0 (0x0000)

    Full LTIApply.log

    Microsoft Deployment Toolkit version: 5.1.1642.01	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    	Open Control File: OperatingSystems	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    ------  Applying Windows image using Setup.exe ------	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    LTI applying image \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim using SETUP.EXE	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    Found a matching SETUP in \\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    Cleaning off old operating system	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    Skipping C:\Drivers	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    Skipping C:\MININT	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    Skipping C:\_SMSTaskSequence	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    Installing image from \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim using command: "\\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources\setup.exe" /noreboot /unattend:C:\MININT\unattend.xml /m:"\\BLDMDT001\MDTTest$\$OEM$"	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    About to run command: "\\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources\setup.exe" /noreboot /unattend:C:\MININT\unattend.xml /m:"\\BLDMDT001\MDTTest$\$OEM$"	LTIApply	3/13/2012 2:01:52 PM	0 (0x0000)
    ZTI Heartbeat: command has been running for 6 minutes (process ID 1316)	LTIApply	3/13/2012 2:07:00 PM	0 (0x0000)
    Property LogPath is now = D:\MININT\SMSOSD\OSDLOGS	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    Microsoft Deployment Toolkit version: 5.1.1642.01	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    	Open Control File: OperatingSystems	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    ------  Applying Windows image using Setup.exe ------	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    LTI applying image \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim using SETUP.EXE	LTIApply	3/14/2012 10:50:05 AM	0 (0x0000)
    Found a matching SETUP in \\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    Cleaning off old operating system	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    Installing image from \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim using command: "\\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources\setup.exe" /noreboot /unattend:D:\MININT\unattend.xml /m:"\\BLDMDT001\MDTTest$\$OEM$"	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    About to run command: "\\BLDMDT001\MDTTest$\Operating Systems\Windows Server 2008 R2 x64\Sources\setup.exe" /noreboot /unattend:D:\MININT\unattend.xml /m:"\\BLDMDT001\MDTTest$\$OEM$"	LTIApply	3/14/2012 10:50:06 AM	0 (0x0000)
    Return code from command = 31	LTIApply	3/14/2012 10:52:11 AM	0 (0x0000)
    Setup failed applying image \\BLDMDT001\MDTTest$\Operating Systems\W2K8_STD_R2_PREP\W2K8_STD_R2_PREP.wim, rc = 31	LTIApply	3/14/2012 10:52:11 AM	0 (0x0000)
    ZTI ERROR - Non-zero return code by LTIApply, rc = 31	LTIApply	3/14/2012 10:52:11 AM	0 (0x0000)


    • Edited by Graeme Bray Wednesday, March 14, 2012 4:57 PM MDT 2010
    Wednesday, March 14, 2012 4:19 PM

All replies

  • Looks like you are getting an return code = 31. What type of activation method are you using, MAK / KMS? Do you have a KMS stood up? Make sure the key you are using is assigned to bits you are deploying... Meaning don't try and use a MAK key if you are using TechNet downloaded bits.

    _JoeG
    Dell - Systems Integration Consultant
    Twitter: @8bits1byte 

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, March 14, 2012 6:46 PM
  • Joe,

    We build the images in our lab which does not have access to our KMS server so we activate using the MAK key.  Once syspreped and captured, we then import the image. (This all works on M610, R710, R910, and previous models).

    It literally fails just as it starts to deploy the image.  Nothing gets put onto the OS Disk (as I can see that when I hit F8 and browse to pull the logs.

    It just fails and I'm not sure why.

    Wednesday, March 14, 2012 7:18 PM
  • The other piece of information I see here is the  following from the LiteTouch.log

    codeAbout to run command: "X:\Deploy\Tools\X64\TsmBootstrap.exe" /env:SAContinue	LiteTouch	3/14/2012 10:50:04 AM	0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG.	LiteTouch	3/14/2012 10:52:11 AM	0 (0x0000)

    Can you open up the SMSTS.log and display the contents here?

    EDIT: A typical 0x80004005 is a generic error and could be anything from broken network connection to an access denied error in disguise. 


    _JoeG
    Dell- Systems Integration Consultant
    Twitter: @8bits1byte 

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Edited by _JoeG Wednesday, March 14, 2012 10:20 PM Edit
    Wednesday, March 14, 2012 10:19 PM
  • Joe,

    Here is part of the smsts.log file that looks like it is detailed to the install piece

    !--------------------------------------------------------------------------------------------!	TSManager	3/14/2012 10:50:05 AM	1564 (0x061C)
    Expand a string: WinPEandFullOS	TSManager	3/14/2012 10:50:05 AM	1564 (0x061C)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"	TSManager	3/14/2012 10:50:05 AM	1564 (0x061C)
    Process completed with exit code 31	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    !--------------------------------------------------------------------------------------------!	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Failed to run the action: Install Operating System. 
    A device attached to the system is not functioning. (Error: 0000001F; Source: Windows)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Sending status message . . .	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Set a global environment variable _SMSTSLastActionRetCode=31	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Clear local default environment	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Let the parent group (Install) decides whether to continue execution	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    A device attached to the system is not functioning. (Error: 0000001F; Source: Windows)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Sending status message . . .	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Task Sequence Engine failed! Code: enExecutionFail	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    ****************************************************************************	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Task sequence execution failed with error code 80004005	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Cleaning Up. Removing Authenticator	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Cleaning up task sequence folder	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Successfully unregistered Task Sequencing Environment COM Interface.	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Command line for extension .exe is "%1" %*	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Set command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Executing command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    ==========[ TsProgressUI started in process 1396 ]==========	TsProgressUI	3/14/2012 10:52:11 AM	236 (0x00EC)
    Command line: "X:\Deploy\Tools\X64\TsProgressUI.exe" /Unregister	TsProgressUI	3/14/2012 10:52:11 AM	236 (0x00EC)
    Unregistering COM classes	TsProgressUI	3/14/2012 10:52:11 AM	236 (0x00EC)
    Unregistering class objects	TsProgressUI	3/14/2012 10:52:11 AM	236 (0x00EC)
    Shutdown complete.	TsProgressUI	3/14/2012 10:52:11 AM	236 (0x00EC)
    Process completed with exit code 0	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Successfully unregistered TS Progress UI.	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,657)	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Sending error status message	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Finalizing logging from process 1560	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Finalizing logs to root of first available drive	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Successfully finalized logs to D:\SMSTSLog	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    Cleaning up task sequencing logging configuration.	TSManager	3/14/2012 10:52:11 AM	1564 (0x061C)
    

    Thursday, March 15, 2012 1:52 PM
  • I am still seeing the same error message in the SMSTS log. 0x80004005 followed by (Error: 0000001F; Source: Windows)

    1F (Hex) = 31 (Dec) which means a device is not functioning properly. Is there a raid setup on the server? Also, can you ping the MDT Server from command line? Have you tried to update the deployment share (right-click your deployment share and choose Update) once your 620 drivers were imported into the Workbench?


    _JoeG
    Dell - Systems Integration Consultant
    Twitter: @8bits1byte 

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, March 15, 2012 11:37 PM
  • Joe,

    I am going to build a new deployment share using MDT 2012.

    We have a Dell employee on-site once a week-ish to assist with any issues.  Is there a way he can get in contact with you if we need further assistance?

    Thanks,

    Graeme

    Wednesday, April 18, 2012 3:29 AM
  • Sure. 

    _JoeG
    Dell - Systems Integration Consultant
    Twitter: @8bits1byte 

    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, April 18, 2012 2:11 PM