The Realm of the Verbal Processor

Error Creating MDT Boot Image

First of all, I’ll admit that this post is a bit of a stupid mistake. It stems from a miscommunication between a co-worker and I who were working on an internal (not client) server. I should have confirmed what he had done instead of assuming.

We have been building a new ConfigMgr server. My co-worker had some time while I was working on a client project, so he installed ConfigMgr.

This morning I started building out the rest of the server for OSD purposes. After configuring the MDT integration with ConfigMgr, I went into the ConfigMgr console to “Create Boot Image using Microsoft Deployment”. After entering in all the info it asked for, the wizard started but fairly quickly popped up an error stating, “Error while importing Microsoft Deployment Toolkit Task Sequence. Details: The ConfigMgr Provider reported an error.” When I checked the log file (located in C:\Users\<username>\AppData\Local\Temp\2\NewBootImage_x86.log), I found the following error:

PEIMG failed to use the servicing stack shim library (ssshim.dll) to locate a servicing stack that matches the target image (0x901f0005).

Hmmm…that sounds like a WAIK issue. After looking, I confirmed that my co-worker had installed the previous version of WAIK instead of the version for Windows 7/Server 2008 R2. So, I removed the old version and installed the new WAIK. Got a different error. Unfortunately I didn’t take note of what the error message was at the time, but I do remember that the SMS Provider log file (smsprov.log) had the following phrases in a couple of error entries (I know this because of my bing.com search history.)

failed to get the peimg tool installation location

failed to get peimage command line

That sent me hunting for more info and finally led me to ask the question…”What version of ConfigMgr did my co-worker install?” After checking the version, I discovered that we had somehow miscommunicated. I thought he had installed the Release Candidate of ConfigMgr SP2 (because I am doing Windows 7 deployments…SP2 is required for this). Turns out he had installed SP1.

So…after installing both R2 and SP2, I was finally able to create the boot image using the MDT integration.

Perhaps someone searching on the above search strings will see this and be able to get back up and going faster than I did!

September 14, 2009 - Posted by Jarvis | ConfigMgr