OSD error 0x80004005 on Win7x64 deployment
Trying again....
I am trying to deploy & capture Win7 x64, on a HP ProBook 6550b. The task sequence seems to run just fine, but then it gets to the "setup windows and ConfigMgr" part and fails. It says "task sequence has completed with the error code 0x80004005".
Now I would go through the smsts.log file, but I can't find it anywhere (and yes I have tried everywhere), so if someone could point me in the right direction that would be nice.
October 8th, 2010 10:37am
Did you have any driver packages added in ur Task sequence ?
check out this link
http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/
post smsts.log
//Eswar Koneti @ http://eskonr.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
October 8th, 2010 12:11pm
Cheers. Got the smsts.log file now and am running sequence again to find out what's wrong.
October 8th, 2010 12:33pm
from smsts.log
Expand a string: WinPEandFullOS TSManager
08.10.2010 14:01:57 1132 (0x046C)
Executing command line: OSDSetupWindows.exe
TSManager 08.10.2010 14:01:57
1132 (0x046C)
==============================[ OSDSetupWindows.exe ]===========================
OSDSetupWindows 08.10.2010 14:01:57
1800 (0x0708)
Command line: "OSDSetupWindows.exe" OSDSetupWindows
08.10.2010 14:01:57 1800 (0x0708)
Installing BOOTMGR bootsector OSDSetupWindows
08.10.2010 14:01:57 1800 (0x0708)
Command line for extension .exe is "%1" %*
OSDSetupWindows 08.10.2010 14:01:57
1800 (0x0708)
Set command line: "bootsect.exe" /NT60 SYS /MBR
OSDSetupWindows 08.10.2010 14:01:57
1800 (0x0708)
Executing command line: "bootsect.exe" /NT60 SYS /MBR
OSDSetupWindows 08.10.2010 14:01:57
1800 (0x0708)
Process completed with exit code 0 OSDSetupWindows
08.10.2010 14:01:58 1800 (0x0708)
The package NIH0007A is found locally in the cache C:\_SMSTaskSequence\Packages\NIH0007A
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
!Directory::Exists(sNormalizedPath), HRESULT=800700b7 (e:\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,154)
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Setting hive location to "C:\_SMSTaskSequence\OSD\Vista\Windows\System32\SMI\Store\Machine"
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Loading existing answer file "C:\_SMSTaskSequence\unattend.xml"
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Adding "C:\_SMSTaskSequence\drivers" to plug and play driver path.
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Getting namespace "Microsoft-Windows-PnpCustomizationsWinPE" for architecture "amd64"
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Writing configuration information to C:\_SMSTaskSequence\unattend.xml
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Successfully saved configuration information to C:\_SMSTaskSequence\unattend.xml
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Successfully initialized driver information
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Command line for extension .EXE is "%1" %*
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Set command line: "C:\_SMSTaskSequence\Packages\NIH0007A\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Executing command line: "C:\_SMSTaskSequence\Packages\NIH0007A\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot
OSDSetupWindows 08.10.2010 14:01:59
1800 (0x0708)
Process completed with exit code 31 OSDSetupWindows
08.10.2010 14:02:08 1800 (0x0708)
Windows Setup completed with exit code 31
OSDSetupWindows 08.10.2010 14:02:08
1800 (0x0708)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\NIH0007A
OSDSetupWindows 08.10.2010 14:02:08
1800 (0x0708)
reference count 1 for the source C:\_SMSTaskSequence\Packages\NIH0007A before releasing
OSDSetupWindows 08.10.2010 14:02:08
1800 (0x0708)
Delete source directory C:\_SMSTaskSequence\Packages\NIH0007A
OSDSetupWindows 08.10.2010 14:02:08
1800 (0x0708)
Released the resolved source C:\_SMSTaskSequence\Packages\NIH0007A
OSDSetupWindows 08.10.2010 14:02:09
1800 (0x0708)
exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)
OSDSetupWindows 08.10.2010 14:02:09
1800 (0x0708)
Windows setup failed, code 31 OSDSetupWindows
08.10.2010 14:02:09 1800 (0x0708)
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707)
OSDSetupWindows 08.10.2010 14:02:09
1800 (0x0708)
Exiting with code 0x80004005 OSDSetupWindows
08.10.2010 14:02:09 1800 (0x0708)
Process completed with exit code 2147500037
TSManager 08.10.2010 14:02:09
1132 (0x046C)
!--------------------------------------------------------------------------------------------!
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Failed to run the action: Setup windows and ConfigMgr.
Unspecified error (Error: 80004005; Source: Windows)
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Sending status message . . . TSManager
08.10.2010 14:02:09 1132 (0x046C)
Send a task execution status message SMS_TSExecution_ActionFailError
TSManager 08.10.2010 14:02:09
1132 (0x046C)
MP server nihsrvv20-24.nih.no and port 80. SSL=false. CRL=false.
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Site code: NIH TSManager
08.10.2010 14:02:09 1132 (0x046C)
Client machine name: Cortess TSManager
08.10.2010 14:02:09 1132 (0x046C)
Client Identity: GUID:7CE07BD9-7547-4279-8E35-6306C2635285
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Advertisement ID: NIH200C6 TSManager
08.10.2010 14:02:09 1132 (0x046C)
Package ID: NIH0007F TSManager
08.10.2010 14:02:09 1132 (0x046C)
Sending StatusMessage TSManager
08.10.2010 14:02:09 1132 (0x046C)
Formatted header: TSManager
08.10.2010 14:02:09 1132 (0x046C)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>6b857b30-05d7-456e-98ea-e325032d9622</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-10-08T12:02:09Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="4260"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 08.10.2010 14:02:09
1132 (0x046C)
CLibSMSMessageWinHttpTransport::Send: URL: nihsrvv20-24.nih.no:80 CCM_POST /ccm_system/request
TSManager 08.10.2010 14:02:09
1132 (0x046C)
The request has succeeded. 200 OK TSManager
08.10.2010 14:02:09 1132 (0x046C)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Set a global environment variable _SMSTSLastActionSucceeded=false
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Clear local default environment TSManager
08.10.2010 14:02:09 1132 (0x046C)
Let the parent group (Build the Reference Machine) decides whether to continue execution
TSManager 08.10.2010 14:02:09
1132 (0x046C)
The execution of the group (Build the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Failed to run the last action: Setup windows and ConfigMgr. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Sending status message . . . TSManager
08.10.2010 14:02:09 1132 (0x046C)
Send a task execution status message SMS_TSExecution_TaskSequenceFailError
TSManager 08.10.2010 14:02:09
1132 (0x046C)
MP server nihsrvv20-24.nih.no and port 80. SSL=false. CRL=false.
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Site code: NIH TSManager
08.10.2010 14:02:09 1132 (0x046C)
Client machine name: Cortess TSManager
08.10.2010 14:02:09 1132 (0x046C)
Client Identity: GUID:7CE07BD9-7547-4279-8E35-6306C2635285
TSManager 08.10.2010 14:02:09
1132 (0x046C)
Advertisement ID: NIH200C6 TSManager
08.10.2010 14:02:09 1132 (0x046C)
Package ID: NIH0007F TSManager
08.10.2010 14:02:09 1132 (0x046C)
Sending StatusMessage TSManager
08.10.2010 14:02:09 1132 (0x046C)
Formatted header: TSManager
08.10.2010 14:02:09 1132 (0x046C)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>6b857b30-05d7-456e-98ea-e325032d9622</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-10-08T12:02:09Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="2124"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 08.10.2010 14:02:09
1132 (0x046C)
CLibSMSMessageWinHttpTransport::Send: URL: nihsrvv20-24.nih.no:80 CCM_POST /ccm_system/request
TSManager 08.10.2010 14:02:09
1132 (0x046C)
The request has succeeded. 200 OK TSManager
08.10.2010 14:02:09 1132 (0x046C)
Executing command line: X:\WINDOWS\system32\cmd.exe /k
TSBootShell 08.10.2010 14:02:14
792 (0x0318)
The command completed successfully. TSBootShell
08.10.2010 14:02:14 792 (0x0318)
Successfully launched command shell. TSBootShell
08.10.2010 14:02:14 792 (0x0318)
////////////////////////////////
I noticed that not all drivers were installed as well, but that shouldn't cause this much of a problem, or? It should be able to complete the setup process without USB and audio drivers....!?!
Free Windows Admin Tool Kit Click here and download it now
October 8th, 2010 3:09pm
Can you try applying Apply Driver Package Action instead auto apply drivers and see if that resolves.
Are you using any Product Key if so,can you leave it blank and try again.//Eswar Koneti @ http://eskonr.wordpress.com/
October 8th, 2010 3:58pm
"Windows Setup completed with exit code 31"
This is usually related to using the wrong windows key during the deployment.
Is this a deployment or build & capture? Are you using a windows key in the task sequence?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
October 9th, 2010 6:18pm
as Jason and Eswar say it's most likely key related
try the following: in the Product Key field of the Apply Windows Settings step leave the value for the key blank
then try the deployment again, does it work now ?
cheers
niall
My step by step
SCCM Guides
I'm on Twitter > ncbrady
October 9th, 2010 9:42pm