Thursday, December 6, 2012

Troubleshooting flow for image deployment

This is going to be an ongoing post.  I work on more than one project at a time and even after being away a short while, I forget lessons learned. After many hours of banging my head on the keyboard.

I use MDT.  I image. Sometimes it breaks. Your mileage will vary as this is specific to the custom system I use.

Sometimes you make a change and then the image will not deploy.  Here’s a list of things you should check:

1)      Note the error. At what stage did it happen?

a.       If it was just after Litetouch started, but before choosing the TS or before formatting the drive, check the version of the boot.wim (LiteTouchPE_x64.wim) to see that it is the correct version.  If it is older, it might be missing drivers.

b.      If it was before Litetouch finished, then check the Deploymentshare$\Logs folder for relevant information.

c.       If it was after the image loaded, but before sysprep, boot into BartPE and check %OSDRIVE%\_SMSTaskSequence, and %OSDRIVE%\MININT.

d.      If it was during sysprep, boot into BartPE and check %OSDRIVE%\Windows\Panther and %OSDRIVE%\Windows\system32\Panther. Look for setuperr.log and setupact.log.

2)      Check the task sequence on the MDT server to ensure the proper drivers are being loaded and settings (including unattend file) are correct

If all else fails... sometimes it could be the image. Sysprep it again. To mitigate driver issues, use a VM.

BartPE Loading screen

Everytime I compile BartPE, which is once in a blue moon, it annoys me that I can't change the version that flashes across the load screen.

Look for the following in the plugins folder.


Search for this setting. Compile. Done.

"txtsetup.sif","SetupData","loaderprompt","""Starting Windows XPE [ETS Version 3600_sp2]..."""