I've been working on setting up OS deployments using SCCM and have run into a problem with the Task Sequence failing to start.
If I use a virtual machine (running Hyper-v) everything works perfectly. It PXE boots and the SCCM task sequence kicks off and installs everything properly.
So, I made the jump to using real hardware for a client and hooked up a new Dell E6400 laptop. It PXE boots and SCCM comes up and starts the "Initializing Windows PE", but the last step it displays is "Windows is Starting Up". At this point the message box clears and I'm left with the SCCM wallpaper and a moment or two later the system reboots.
On the Hyper-V virtual machines I normally use for testing, this "Initializing Windows PE" clears and then the task sequence progress messages come up.
I thought that maybe SCCM didn't like data existing on the laptop's hard drive so I deleted all the partitions. It was a long shot I know, but it couldn't hurt.
I'm trying to deploy a 32bit Vista test image, and the laptop registers that it's 64bit. I wouldn't think that would be a problem though. I'm sure people deploy 32bit images to 64bit hardware all the time.
Have you attempted the boot-up on other PCs or hardware configurations? Just to rule out the possibility of a bad hardware component on that machine?
Next step would be the SMSTS.log file located on the client computer. While the PC is booting up, try hitting the F8 key and it should bring up a Command Prompt. The SMSTS.log file should be located in the c:\_SMSTaskSequence folder. Just copy it over to your workstation and see what it says.
My gut reaction is that it's probably a driver issue? You might need to update your boot images with hardware specific NIC drivers and Mass Storage drivers.
Carl...
Proposed as answer byCD ShriverTuesday, January 20, 2009 3:18 PM
Have you attempted the boot-up on other PCs or hardware configurations? Just to rule out the possibility of a bad hardware component on that machine?
Next step would be the SMSTS.log file located on the client computer. While the PC is booting up, try hitting the F8 key and it should bring up a Command Prompt. The SMSTS.log file should be located in the c:\_SMSTaskSequence folder. Just copy it over to your workstation and see what it says.
My gut reaction is that it's probably a driver issue? You might need to update your boot images with hardware specific NIC drivers and Mass Storage drivers.
Carl...
Proposed as answer byCD ShriverTuesday, January 20, 2009 3:18 PM
I concur with Carl's assessment of a missing driver. Make sure that you are integrating in Vista drivers for PE as the PE used is based on Vista and make sure that your updated boot images have been updated on the DP.
A quick correction though, the SMSTS.log file is initially located in X:\Windows\Temp\SMSTS on the system booted into PE.
Thanks. It was a driver issue. An older laptop worked just fine. Of course then I had to deal with the problem of Dell's drivers for the Intel NIC not working in WinPE 2.x. Once I got the NIC drivers straight from Intel everything fell into place.
Thanks again. I'm going to keep the log file in the back of my head too for next time I run into problems!
