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.
