Yea, that post is old. :)
Are you running an old version of the WAIK? Or are you using the latest ADK? Do you have any unnecessary drivers installed in your WinPE image? Can you remove them? -k From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, May 29, 2013 9:13 AM To: [email protected] Subject: [MDT-OSD] RE: CMD Window appears after dropping OS - MDT 2012 Update 1 Hi Michael, Thanks for the response. Indeed there is an error installing a device driver in the log file you noted. Info Spent 1170ms installing network components Info Installing device pci\ven_8086&dev_1521 X:\windows\INF\oem17.inf succeeded Info Installing device pci\ven_8086&dev_1521 X:\windows\INF\oem17.inf succeeded Info Installing device pci\ven_8086&dev_1521 X:\windows\INF\oem17.inf succeeded Info Installing device usb\vid_04b3&pid_4010 X:\windows\INF\netimm.inf failed with status 0xe0000219 Info Installing device pci\ven_8086&dev_1521 X:\windows\INF\oem17.inf succeeded Info Spent 14352ms installing network drivers Info STATUS: FAILURE (0xe0000219) Searching for this error led me to this forum post which matches up with the machine that I am currently working with. http://social.technet.microsoft.com/Forums/en-US/mdt/thread/6439cd61-9bca-47 dc-987f-5df631fb1192/ As that post is quite old I was wondering if you would have any other suggestions when working with these uEFI equipped machines? Or is what is suggested in that post still the best approach (mount wim and rename the inf)? Thanks Kevin From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Wednesday, May 29, 2013 10:45 AM To: [email protected] <mailto:[email protected]> Subject: [MDT-OSD] RE: CMD Window appears after dropping OS - MDT 2012 Update 1 >From that command window, look at the X:\WINDOWS\SYSTEM32\WPEINIT.LOG to see what failed. My guess is that there is a problematic driver that didn't initialize in the appropriate amount of time, causing a non-zero return code. And WPEINIT won't reboot if something didn't work right, so you have a chance to investigate. Thanks, -Michael From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected] <mailto:[email protected]> Sent: Wednesday, May 29, 2013 8:05 AM To: [email protected] <mailto:[email protected]> Subject: [MDT-OSD] CMD Window appears after dropping OS - MDT 2012 Update 1 Hello- I am attempting to drop a Windows 2008 R2 server image and every time after the image has been dropped a command window opens which prevents the restart of the computer. Things I have tried: - Regenerated DeploymentShare - Recreated the DeploymentShare - Using a standard server deployment task sequence with no customizations Here are the last lines within the smsts.log file: Successfully save execution state and environment to local hard disk TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Start executing an instruciton. Instruction name: Restart computer. Instruction pointer: 46 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a global environment variable _SMSTSCurrentActionName=Restart computer TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a global environment variable _SMSTSNextInstructionPointer=46 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a local default variable Message TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a local default variable MessageTimeout TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a local default variable Target TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Expand a string: smsboot.exe /target:WinPE TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Expand a string: TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Command line for extension .exe is "%1" %* TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set command line: smsboot.exe /target:WinPE TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Start executing the command line: smsboot.exe /target:WinPE TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) !--------------------------------------------------------------------------- -----------------! TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Expand a string: WinPEandFullOS TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Executing command line: smsboot.exe /target:WinPE TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) ========================= [ smsboot.exe ] ========================= Reboot 5/29/2013 6:01:52 AM 1040 (0x0410) Command line: '"smsboot.exe" /target:WinPE' Reboot 5/29/2013 6:01:52 AM 1040 (0x0410) SMSTSRebootDelay=30 Reboot 5/29/2013 6:01:52 AM 1040 (0x0410) SMSTSRebootMessage=Initiating system reboot Reboot 5/29/2013 6:01:52 AM 1040 (0x0410) SMSTSRebootRequested=WinPE Reboot 5/29/2013 6:01:52 AM 1040 (0x0410) Process completed with exit code 0 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) !--------------------------------------------------------------------------- -----------------! TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Successfully complete the action (Restart computer) with the exit win32 code 0 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Sending status message . . . TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Expand a string: %_SMSTSMDataPath%\Logs TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Deleting file without retry TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Clear local default environment TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Updated security on object C:\_SMSTaskSequence. TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a global environment variable _SMSTSNextInstructionPointer=47 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a TS execution environment variable _SMSTSNextInstructionPointer=47 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a global environment variable _SMSTSInstructionStackString=40 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Set a TS execution environment variable _SMSTSInstructionStackString=40 TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Save the current environment block TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Successfully save execution state and environment to local hard disk TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Reboot to local harddisk TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Skipped RebootSystem() TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) The action (Restart computer) initiated a reboot request TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Sending status message . . . TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) **************************************************************************** TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Execution engine result code: 2 (Success=0, Failure=1, RebootInitiated=2) TSManager 5/29/2013 6:01:52 AM 1548 (0x060C) Process completed with exit code 2147945410 TSMBootstrap 5/29/2013 6:01:52 AM 1608 (0x0648) Exiting with return code 0x80070BC2 TSMBootstrap 5/29/2013 6:01:52 AM 1608 (0x0648) ==========[ TsProgressUI started in process 1036 ]========== TsProgressUI 5/29/2013 6:01:52 AM 852 (0x0354) Command line: "X:\Deploy\Tools\X64\TSProgressUI.exe" /Unregister TsProgressUI 5/29/2013 6:01:52 AM 852 (0x0354) Unregistering COM classes TsProgressUI 5/29/2013 6:01:52 AM 852 (0x0354) Unregistering class objects TsProgressUI 5/29/2013 6:01:52 AM 852 (0x0354) Shutdown complete. TsProgressUI 5/29/2013 6:01:52 AM 852 (0x0354) Anyone have any ideas as to why this is occurring or what to try next? Thanks The preceding email message may be confidential or protected by the attorney-client privilege. It is not intended for transmission to, or receipt by, any unauthorized persons. If you have received this message in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the message. Legal advice contained in the preceding message is solely for the benefit of the Foley & Lardner LLP client(s) represented by the Firm in the particular matter that is the subject of this message, and may not be relied upon by any other party. Internal Revenue Service regulations require that certain types of written advice include a disclaimer. To the extent the preceding message contains advice relating to a Federal tax issue, unless expressly stated otherwise the advice is not intended or written to be used, and it cannot be used by the recipient or any other taxpayer, for the purpose of avoiding Federal tax penalties, and was not written to support the promotion or marketing of any transaction or matter discussed herein. The preceding email message may be confidential or protected by the attorney-client privilege. It is not intended for transmission to, or receipt by, any unauthorized persons. If you have received this message in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the message. Legal advice contained in the preceding message is solely for the benefit of the Foley & Lardner LLP client(s) represented by the Firm in the particular matter that is the subject of this message, and may not be relied upon by any other party. Internal Revenue Service regulations require that certain types of written advice include a disclaimer. To the extent the preceding message contains advice relating to a Federal tax issue, unless expressly stated otherwise the advice is not intended or written to be used, and it cannot be used by the recipient or any other taxpayer, for the purpose of avoiding Federal tax penalties, and was not written to support the promotion or marketing of any transaction or matter discussed herein.
