Hi all,
I have recently run into some sporadic issues with our Windows 7 migration that I hope someone can shed some additional light on. On some of the machines we're upgrading we are seeing the behavior that after USMT backs up user data and then initiates the reboot into Windows PE the machine and task sequence seems to "stall." When the computer is in this state our field techs have said that most of the time they can press the space bar or another keyboard key and the machine seems to "wake up" and continue at that point.
The machine models this has happened on are sporadic so I do not believe it is a driver issue in WinPE. Some machines in the deployment collection image with absolutely no issues and are also the same models as one's that have the problem. Also the tech can boot with a SCCM USB boot drive and the machine will image fine, using the same boot image as the task sequence.
One of the techs was finally able to pull the logs from a machine in that state and I noticed a particular error that I did not see on a different machine that imaged fine. Of note though is the machine that did not exhibit this error was an existing Windows 7 PC that I refreshed. The one that showed the error was XP being upgraded to Windows 7. Not sure at this point if that has any affect on what was logged. Anyways, the smsts.log file snippet is below:
Start executing an instruction. Instruction name: Restart to Windows PE. Instruction pointer: 43 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSCurrentActionName=Restart to Windows PE TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a local default variable SMSRebootMessage TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a local default variable SMSRebootTimeout TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSLogPath=C:\WINDOWS\CCM\Logs\SMSTSLog TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Expand a string: smsboot.exe /target:WinPE TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Expand a string: TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Start executing the command line: smsboot.exe /target:WinPE TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
!--------------------------------------------------------------------------------------------! TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Expand a string: WinPEandFullOS TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Executing command line: smsboot.exe /target:WinPE TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
========================= [ smsboot.exe ] ========================= Reboot 11/22/2013 7:08:04 PM 4744 (0x1288)
SMSTSRebootDelay=1 Reboot 11/22/2013 7:08:04 PM 4744 (0x1288)
SMSTSRebootMessage=Initiating system reboot Reboot 11/22/2013 7:08:04 PM 4744 (0x1288)
SMSTSRebootRequested=WinPE Reboot 11/22/2013 7:08:04 PM 4744 (0x1288)
Process completed with exit code 0 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
!--------------------------------------------------------------------------------------------! TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Successfully completed the action (Restart to Windows PE) with the exit win32 code 0 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set authenticator in transport TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Clear local default environment TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Updated security on object C:\_SMSTaskSequence. TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSInstructionStackString=0 40 41 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Set a TS execution environment variable _SMSTSInstructionStackString=0 40 41 TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Save the current environment block TSManager 11/22/2013 7:08:04 PM 2792 (0x0AE8)
Executing command line: "bcdedit.exe" TSManager 11/22/2013 7:08:05 PM 2792 (0x0AE8)
CreateProcess failed. Code(0x80070002) TSManager 11/22/2013 7:08:05 PM 2792 (0x0AE8)
Command line execution failed (80070002) TSManager 11/22/2013 7:08:05 PM 2792 (0x0AE8)
Staging boot image ITC0009A TSManager 11/22/2013 7:08:05 PM 2792 (0x0AE8)
ResolveSource flags: 0x00000000 TSManager 11/22/2013 7:08:07 PM 2792 (0x0AE8)
SMSTSPersistContent: . The content for package ITC0009A will be persisted TSManager 11/22/2013 7:08:07 PM 2792 (0x0AE8)
Set authenticator in transport TSManager 11/22/2013 7:08:07 PM 2792 (0x0AE8)
WinHttp credentials set TSManager 11/22/2013 7:08:07 PM 2792 (0x0AE8)
List of files to be downloaded TSManager 11/22/2013 7:08:07 PM 2792 (0x0AE8)
Downloaded file from http://<Server Name>:80/SMS_DP_SMSPKG$/ITC0009A/sccm?/WinPE.ITC0009A.wim to C:\_SMSTaskSequence\Packages\ITC0009A\WinPE.ITC0009A.wim TSManager 11/22/2013 7:08:12 PM 2792 (0x0AE8)
VerifyContentHash: Hash algorithm is 32780 TSManager 11/22/2013 7:08:12 PM 2792 (0x0AE8)
Found boot image C:\_SMSTaskSequence\Packages\ITC0009A\WinPE.ITC0009A.wim TSManager 11/22/2013 7:08:15 PM 2792 (0x0AE8)
Copying boot image locally... TSManager 11/22/2013 7:08:15 PM 2792 (0x0AE8)
Failed to find ADK installation root registry key TSManager 11/22/2013 7:08:26 PM 2792 (0x0AE8)
Opening image file C:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 11/22/2013 7:08:26 PM 2792 (0x0AE8)
Applying image 1 to volume C:\_SMSTaskSequence\WinPE TSManager 11/22/2013 7:08:26 PM 2792 (0x0AE8)
Closing image file C:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 11/22/2013 7:08:28 PM 2792 (0x0AE8)
Capturing WinPE bootstrap settings TSManager 11/22/2013 7:08:28 PM 2792 (0x0AE8)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 11/22/2013 7:08:28 PM 2792 (0x0AE8)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 11/22/2013 7:08:28 PM 2792 (0x0AE8)
==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 11/22/2013 7:08:28 PM 1468 (0x05BC)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} OSDNetSettings 11/22/2013 7:08:28 PM 1468 (0x05BC)
Captured settings for adapter 1 OSDNetSettings 11/22/2013 7:08:28 PM 1468 (0x05BC)
OSDNetSettings finished: 0x00000000 OSDNetSettings 11/22/2013 7:08:28 PM 1468 (0x05BC)
Process completed with exit code 0 TSManager 11/22/2013 7:08:28 PM 2792 (0x0AE8)
Installing boot image to hard drive TSManager 11/22/2013 7:08:28 PM 2792 (0x0AE8)
Backing up existing boot system before trying to set up new boot system TSManager 11/22/2013 7:08:28 PM 2792 (0x0AE8)
BootLoader::backup: C:\, C:\_SMSTaskSequence\backup TSManager 11/22/2013 7:08:29 PM 2792 (0x0AE8)
BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\ TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Process completed with exit code 0 TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Updated security on object C:\_SMSTaskSequence. TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44 TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSInstructionStackString=0 40 41 TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Set a TS execution environment variable _SMSTSInstructionStackString=0 40 41 TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Save the current environment block TSManager 11/22/2013 7:08:30 PM 2792 (0x0AE8)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 11/22/2013 7:08:31 PM 2792 (0x0AE8)
Updated security on object C:\_SMSTaskSequence. TSManager 11/22/2013 7:08:31 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSNextInstructionPointer=44 TSManager 11/22/2013 7:08:31 PM 2792 (0x0AE8)
Set a TS execution environment variable _SMSTSNextInstructionPointer=44 TSManager 11/22/2013 7:08:31 PM 2792 (0x0AE8)
Set a global environment variable _SMSTSInstructionStackString=0 40 41 TSManager 11/22/2013 7:08:31 PM 2792 (0x0AE8)
Set a TS execution environment variable _SMSTSInstructionStackString=0 40 41 TSManager 11/22/2013 7:08:31 PM 2792 (0x0AE8)
Save the current environment block TSManager 11/22/2013 7:08:31 PM 2792 (0x0AE8)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 11/22/2013 7:08:32 PM 2792 (0x0AE8)
<![LOG[LOGGING: Finalize process ID set to 828]LOG]!><time="13:30:51.969+480" date="12-02-2013" component="TSBootShell" context="" type="1" thread="832" file="tslogging.cpp:1495"> 1/1/1601 12:00:00 AM 1998216043 (0x771A5B6B)
==============================[ TSBootShell.exe ]============================== TSBootShell 12/2/2013 1:30:51 PM 832 (0x0340)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSBootShell 12/2/2013 1:30:51 PM 832 (0x0340)
Debug shell is enabled TSBootShell 12/2/2013 1:30:51 PM 832 (0x0340)
Waiting for PNP initialization... TSBootShell 12/2/2013 1:30:51 PM 840 (0x0348)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 12/2/2013 1:30:51 PM 840 (0x0348)
WinPE boot path: C:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 12/2/2013 1:30:51 PM 840 (0x0348)
Booted from fixed disk TSBootShell 12/2/2013 1:30:51 PM 840 (0x0348)
Found config path C:\_SMSTaskSequence TSBootShell 12/2/2013 1:30:52 PM 840 (0x0348)
Specifically the bolded entries above are what is concerning me as possibly causing this "stall."
Has anyone encountered a scenario such as this or can shed anymore light on the errors logged above? Of possible concern to me is that this started happening in a greater number after configuring and putting in place a second Management Point and Distribution Point. I'm not saying there's a definitive correlation but the timing of this was worrisome. The site shows no errors whatsoever with either of the MP's or DP's.
Any help or comments are greatly appreciated!
Thanks