OSD Task Sequence from Run Advertised Programs fails to install boot image and reboot on Windows XP with Dell Utility partition
I've been fighting with this for 2 days...Was hoping it was a fluke, but my hopes were dashed today. It seems to be only on the Optiplex 780 with WindowsXP here. It fails right after "staging boot image" and the log on the server gives an unspecified error. I have been Binging AND googling all day. I came across pages discussing the WIMGAPI.DLL files. I updated those and made sure the EnvVar for the System32 and the Windows Imaging folder were listed on that machine as well as my site server(suggested so it was worth it to look). No love on that. I found some pages saying that changing the bios setting From RAID to SATA, that made my system bluescreen, Tried AHCI to no avail. I really think it has something to do with the OEM partition (partition1) on the system because i've never ran into this issue before and it is present on this specific model. I even tried to remove the OEM partition, which ofcourse prevented my sysem from booting for some reason. I'm reaching out for help in hopes that someone has an answer very soon. Tomorrow is my last day on site. Running an image with the same boot media works fine. My workaround at this point is to manually capture user state, push the bare metal, then restore manually. If this was my place of business, that would work but the "1click" solution is what we want for this client. I hope this gets some feedback:) Successfully complete the action (Restart in Windows PE) with the exit win32 code 0 TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Sending status message . . . TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Send a task execution status message SMS_TSExecution_ActionCompleteInfo TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Formatted header: TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:36999248-C194-42D5-B7FD-1F0570B60610</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-09-14T20:10:57Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2652"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Clear local default environment TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Updated security on object C:\_SMSTaskSequence. TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Set a global environment variable _SMSTSNextInstructionPointer=18 TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Set a TS execution environment variable _SMSTSNextInstructionPointer=18 TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Set a global environment variable _SMSTSInstructionStackString=16 TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Set a TS execution environment variable _SMSTSInstructionStackString=16 TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Save the current environment block TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) Staging boot image AJS00010 TSManager 9/14/2011 4:10:57 PM 3988 (0x0F94) WinHttp credentials set TSManager 9/14/2011 4:10:59 PM 3988 (0x0F94) List of files to be downloaded TSManager 9/14/2011 4:11:00 PM 3988 (0x0F94) Downloaded file from http://Something.something.LOCAL:80/SMS_DP_SMSPKGD$/AJS00010/boot.AJS00010.wim to C:\_SMSTaskSequence\Packages\AJS00010\boot.AJS00010.wim TSManager 9/14/2011 4:11:19 PM 3988 (0x0F94) Found boot image C:\_SMSTaskSequence\Packages\AJS00010\boot.AJS00010.wim TSManager 9/14/2011 4:11:20 PM 3988 (0x0F94) Copying boot image locally... TSManager 9/14/2011 4:11:20 PM 3988 (0x0F94) Opening image file C:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 9/14/2011 4:11:24 PM 3988 (0x0F94) Applying image 1 to volume C:\_SMSTaskSequence\WinPE TSManager 9/14/2011 4:11:24 PM 3988 (0x0F94) Closing image file C:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 9/14/2011 4:11:24 PM 3988 (0x0F94) Capturing WinPE bootstrap settings TSManager 9/14/2011 4:11:24 PM 3988 (0x0F94) Environment scope "Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}" successfully created TSManager 9/14/2011 4:11:24 PM 3988 (0x0F94) Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 9/14/2011 4:11:24 PM 3988 (0x0F94) ==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 9/14/2011 4:11:24 PM 3744 (0x0EA0) Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} OSDNetSettings 9/14/2011 4:11:24 PM 3744 (0x0EA0) No adapters found with non-empty DNSDomainSuffixSearchOrder OSDNetSettings 9/14/2011 4:11:24 PM 3744 (0x0EA0) Captured settings for adapter 1 OSDNetSettings 9/14/2011 4:11:25 PM 3744 (0x0EA0) OSDNetSettings finished: 0x00000000 OSDNetSettings 9/14/2011 4:11:25 PM 3744 (0x0EA0) Process completed with exit code 0 TSManager 9/14/2011 4:11:25 PM 3988 (0x0F94) Installing boot image to hard drive TSManager 9/14/2011 4:11:25 PM 3988 (0x0F94) Failed to install boot image. Unspecified error (Error: 80004005; Source: Windows) TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Failed to install boot image AJS00010. Unspecified error (Error: 80004005; Source: Windows) TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Failed to reboot the system. Error 0x(80004005) TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Failed to initialize a system reboot. Unspecified error (Error: 80004005; Source: Windows) TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Fatal error is returned in check for reboot request of the action (Restart in Windows PE). Unspecified error (Error: 80004005; Source: Windows) TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) An error (0x80004005) is encountered in execution of the task sequence TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Sending status message . . . TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Formatted header: TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:36999248-C194-42D5-B7FD-1F0570B60610</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-09-14T20:11:26Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2112"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 9/14/2011 4:11:26 PM 3988 (0x0F94) Task Sequence Engine failed! Code: 80004005 TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) **************************************************************************** TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Task sequence execution failed with error code 80004005 TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Cleaning Up. Removing Authenticator TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Cleaning up task sequence folder TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Successfully unregistered Task Sequencing Environment COM Interface. TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Executing command line: "C:\WINDOWS\system32\CCM\TsProgressUI.exe" /Unregister TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) ==========[ TsProgressUI started in process 3284 ]========== TsProgressUI 9/14/2011 4:11:37 PM 1488 (0x05D0) Unregistering COM classes TsProgressUI 9/14/2011 4:11:37 PM 1488 (0x05D0) Shutdown complete. TsProgressUI 9/14/2011 4:11:37 PM 1488 (0x05D0) Process completed with exit code 0 TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Successfully unregistered TS Progress UI. TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Start to cleanup TS policy TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) End TS policy cleanup TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Error executing Task Sequence Manager service. Code 0x80004005 TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Sending error status message TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Formatted header: TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:36999248-C194-42D5-B7FD-1F0570B60610</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2011-09-14T20:11:37Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="1166"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg> TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Resuming SMS Components TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Waiting for CcmExec service to be fully operational TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) CcmExec service is up and fully operational TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Resume for CCM component SoftwareDistribution requested TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Resume for CCM component SoftwareUpdates requested TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Attempting to release request using {51C98A9B-8D07-44D4-BCC0-3F64513FEC98} TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) ReleaseRequest succeeded TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\System Health Agent. Error code 0x80070002 TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94) Stopping Task Sequence Manager service TSManager 9/14/2011 4:11:37 PM 3988 (0x0F94)
September 14th, 2011 4:40pm

Please make sure you have all the correct drivers in place. Is this is x64 bit installation? Also refer this Blog post by Hornbeck http://blogs.technet.com/b/smsandmom/archive/2008/08/26/configmgr-2007-osd-deployment-errors-out-within-a-few-seconds-after-winpe-loads-and-then-automatically-reboots.aspx Hope this will be helpful.... Zulqarnain Ali | MCTS, MCSA | 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.
Free Windows Admin Tool Kit Click here and download it now
September 15th, 2011 3:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics