Resources for IT Professionals >
System Center Configuration Manager Forums
>
Configuration Manager Operating System Deployment
>
MDT sccm sp2 boot images
MDT sccm sp2 boot images
- Ok, current situation is I had an SCCM R2/SP1 with MDT 2008 environment.
I upgraded to SP2 (for Windows 7/2008r2 support) and I'm having problem I suspect are due to Boot images/MDT boot images/etc.
(I'm receiving an 0xC0000001 error when deploying a Windows 7 WIM).
I had some boot images created with MDT 2008 which I'm under the impression need to be upgraded to MDT 2010 boot images. so my questions are as follows:
1). Can I simply upgrade to MDT 2010 or do I need to remove MDT 2008 and install MDT 2010?
2). once MDT 2010 is installed, what is the process to ensure my Boot images are "up to date"?
THANKS as always
Answers
Okay.. wanted to Update this as I called MS and got a resolution.
In our situation I was running SCCM SP2 on a 64 bit OS.
Check your PATH system variable and ensure the path DOES NOT include a x86 bit path for Windows Imaging. In my case the PATH system variable included "C:\Program Files (x86)\Windows Imaging\" (which I'm thinking is a 32 bit version of AIK).. in the path was also "C:\Program Files\Windows Imaging\" (64 bit version of AIK), but apparantly there was an erroneous reference to a x86 version causing the issue.
Took out the (x86) path from the PATH System Variable and Custom MDT boot images are back..
THANKS much especially to Niall who spent many hours with my trying to get resolved.- Marked As Answer bydndoorlag Thursday, January 07, 2010 8:18 PM
All Replies
I was able to resolve installing MDT 2010 by simply installing MDT 2010 (it seems to supercede MDT 2008), and by running the step to "Configure ConfigMGR Integration".
On to resolving issues with the Boot images.- i find the best way is to remove the configmgr PXE extensions while still runnin MDT 2008 first (or mdt 2008 sp1), in server 2008 do this by right clicking on it and choose Run As Administrator on the Configure WDS PXE Filter option, then choose Remove .
If you have accidently installed MDT 2010 and you find that you can no longer start Windows Deployment Services (you get an error which is like The Windows Deployment Services Server service terminated with service-specific error 126 (0x7E)) then uninstall MDT 2010, reinstall MDT 2008 and do the above again.
Once you have MDT 2010 installed AND you have verified that the Windows Deployment Services service is starting ok, then you can add the ConfigMgr extensions for MDT 2010, to do that, close the ConfigMGr console, right click on Configure ConfigMgr Extensions, choose Run As Administrator... the rest is easy.
Once you have done all this you can then rebuild your Microsoft Deployment Toolkit boot images in SCCM by creating a new MDT task sequence.
If your non-mdt boot images are causing you grief after upgrading to SP2 then did you remember to update the distribution points for your boot images
cheers
niall
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - THANKS Nial,
I'm at the point where I have Installed MDT 2010 and have run the "ConfigurationMGR Integration" and all seems to come back with no errors.
Here is MY problem.
Why I PXE boot I still seem to be picking up the "old" MDT Boot images (instead of the NEW SP2 boot images I have Distributed to my Distribution Points)?
HOW do I get the PXE boot to use the "new SP2 boot images" instead of the old MDT boot images?
Secondly I want/need to get the MDT 2010 Boot images created (as I have scripts/etc. I call in my task sequence which I guess can't run in the "standard" SP2 Boot Images). What I've tried to do is go to BOOT IMAGES and right click and select "Create Boot Image using Microsoft Deployment" and selected the appropriate entries (Include ADO) and select NEXT to I presume create a "new" MDT Boot image and I receive an error:
"Could not load file or assembly 'system.management.automation, version 1.0.0 0, culture=neutral, publickeytoken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified"
THANKS for any help you can give me. - the boot images used will depend on what Task Sequences you are advertising to the collection that these computers end up in,
you can decide what boot image is used by right clicking on the task sequence and choose properties/advanced
when you did the configmgr integration with mdt2010 did you get any error ?. try again see what it says...
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Hi Nial,
I have advertised MULTIPLE TS to the "unknown computer collection".... the LATEST TS I advertised to it I had specified to use Boot image "Boot Image (x86)" (which is the SP2 boot image)... however when I PXE Boot it still loads the "old MDT Boot image"... once I select the "Latest TS".. it then loads that boot image... which will not work as my first step is to run an HTA script to gather computer name/etc. which will not work with the "base Boot image".
I get NO errors when doing the configmgr Integration (all says it went well). when I PXE boot and hit F12 to network boot.. I load BOOT.SDI and then it loads WINPE.XXX00025.WIM which is my "old MDT Boot image".
It then comes up with the List of advertisement, which I then choose the "latest" TS I advertised and it loads the x86 Boot image I associated with the TS I selected, but then the COMMAND PROMPT Call I have in the TS fails.
I can't seem to create a "custom MDT 2010" boot image because of the error above.- start up Microsoft Deployment toolkit, click on components, and click on check for updates, do you see the same errors ?
if so startup Server Manager, click on Features, click on Add Features, scroll down to windows PowerShell and install it.
close MDT, start MDT again, and then try again, the error should be gone.
Now please verify the same process in SCCM.
cheers
niall
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Maybe I'm missing something, but all I see is "Microsoft Deployment Toolkit" under programs, with 5 options (Configmgr Integration, Deployment Workbench, Release Notes, Toolkit documentation, WDS Pxe filter)... where do I find the TOOLKIT & components?
I Checked the features under Server Manager and don't even see PowerShell listed as an available feature? (might be on to something)?
THANKS again for all the help. - are you running server 2008 as the server os or something else ? i wrote about the problem here
http://www.windows-noob.com/forums/index.php?/topic/1409-strange-error-when-creating-mdt-2010-task-sequence/
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Thank Niall... I think you Nailed it (no pun intended)..
See WINDOWS POWERSHELL is NOT loaded as a feature, so think that is the core problem here.
I'll be loading Powershell (in the morning) and trying my luck from there.
Do I need to UNINSTALL MDT 2010 before loading powershell and reload MDT 2010?
THANKS Again.. - you dont need to uninstall MDT, just install the windows powershell feature and you should be ok from then on, please let me know how it goes.
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 THANKS Niall, that took care of that issue.
How when I try to create a MDT 2010 Boot image I'm getting in issue where it says "Unable to mount image" for winpe.wim and PE20_mount.x86 (looking in the TEMP folder).. on to searching down this issue.
- in the MDT mmc, did you download the X86 WAIK ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - THANKS Niall
I was/am under the impression the AIK was installed automatically with SCCM SP2? (maybe it was installed but I still need to do this download)?
Are there INSTRUCTIONS on installing/configuring/working with SCCM R2/SP2, MDT 2010, AIK, and all the other variations of add-on/configurable products that can make up this "easy deployment process" :) - So under MDT Components Under INSTALLED section is the WAIK (x64) which says REQUIRED and if I highlight it it says download? (Is it downloaded already as it say INSTALLED?)
I see the WAIK (x86) under the "Available for Download" section which I guess implies I need to download this before I can create MDT 2010 boot images?
Are there other "Available for Download" tools I should download (Guess that depends on what other "features" I want MDT to do for me)? :) - if you want X86 boot images for mdt then you'll need to download that waik or install it separately, i'd just go with the download option
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Ok.. it's been "downloaded".. Guess there is some additional steps to get it "installed" (or whateve status it needs to be in so I can create a boot image).
Is there documentation somewhere on the steps neccesary to create a MDT Boot image? (don't need to continue wasting your time).... But honestly, the documentation about the various components here (SCCM... various versions/release levels, PXE, MDT, AIK, etc. etc. etc.) I think is VERY fragmented. Seems this could be improved quite a bit.
THANKS as always.. you guys have been a lifeline, but seems you could be enjoying some time on a beach somewhere if this stuff was documented better. - a vacation would be nice indeed,
have you looked at the print ready documentation,
it's here and is very detailed
http://go.microsoft.com/fwlink/?LinkId=163310
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Actually YES I did.. but didn't see any mention of the steps we've taken so far..
I ONLY want to create a boot image so I can call command line HTA and OSDAPPChooser from within an SCCM task sequence..
I'll dig through it some more. - I'm actually trying to create a "ZTI Boot Image" as documented in the "Using the Microsoft Deployment Toolkit.docx" and I"m getting the error: "Unable to mount image" for winpe.wim and PE20_mount.x86 (looking in the TEMP folder)..
As Niall states I guess I'm missing some prerequisite MDT 2010 steps.. I don't remember having to do anything with MDT 2008 to get a custom boot image created. - Any ideas here?
(briefly to recap.. I had been running SCCM R2/SP1 with a custom MDT Boot image to allow me to call a custom HTA script to gather information for my task sequence.
I put SP2 on to provide support for Windows 7/W2K8 R2 and I'm having problems creating a custom MDT Boot image, which I still need for my HTA scripts as part of my Task sequence).
As far as I can tell I've installed SP2 (core Boot images capture the Windows 7 image/etc. perfectly), but I can't use the core boot image for my custom HTA scripts).
I have MDT 2010, AIK (I'm guessing the latest version that I believe comes with SP2)...
Are there some prerequisite steps in MDT or AIK to create MDT Boot images in SCCM?
THANKS - Ok.. lets try this angle.
Since I'm guessing some MDT/AIK prerequisite isnt' met when I try to create Custom Boot Images in SCCM r2/sp2 I'm digging deeper into MDT to see if that is setup properly.
In my MDT 2010 "workbench", I see under Installed section the WAIK (x64) and the status shows "required".. If I highlight this I see a "Browse" button in the details section which brings me to MDT\Compoenents\WAIK20 folder on the server with some CAB and MSI (msxml6_x64.msi, waikx86.msi, waikamd64.msi)...
Do these MSI need to be manually installed to allow custom Boot images to be created in SCCM?
(not finding much direct information in the 12 MDT guides)
THANKS - how are you trying to create the mdt boot image, are you createing a new Microsoft Deployment Toolkit task sequence from within SCCM ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Nope, I"m simply trying to "Create Boot Image using Microsoft Deployment" by right clicking Boot images in SCCM and choosing this option.
It fails out for me saying "Error while importign Microsoft Deployment Toolkit Task Sequence. Details: Unable to mount image" pointing to winpe.wim and PE20_mount.x86 in a TEMP location.
I do not want/need a MDT task sequence.. I simply want the "updated" boot image to use in deploying W7 and W2K8 R2.
THANKS - So (reading between the lines).. you need to create a MDT Task sequence BEFORE you can create a MDT Boot image?
- to test your problem i have right clicked in boot images, chosen Create boot image using Microsoft Deployment
specified the package source to be created as a network path
\\WIN-CILZXI45G1Q\temp\test mdt boot file
clicked next, filled in the details, clicked next
chosen X86 and selected the following option ADO and 'Add media hoook...'
clicked next
clicked next again at the summary
then it starts Capturing new boot image WIM file (takes quite some time...) and then copying WIM image to packge source directory
finally when done the boot image was listed in my boot images, it worked.
can you tell me at what point above, yours fails ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Sure.. (Thanks Niall),
Right click and select Create Boot Image using Microsoft Deployment, specified the package source as network path (\\servername\mdt2010x86), select NEXT
Fill in NAME (MDT2010x86), Version (blank), Comments (blank), select NEXT
Leave Defaults in Image options (x86, ADO, no media hook, etc.) and select NEXT
Summary click NEXT
Comes up with a message saying "Generating Boot Image" and then fails with message:
Error
Error while importing Microsoft Deployment Toolkit Task Sequence. Details:
Unable to mount image
c:\Users\myname\appdata\local\temp\2\winpe.wim to
c:\Users\myname\appdata\local\temp\2\PE20_mount.x86
with an OK option
I have NOT gone through create a MDT TASK Sequence and I really only want the MDT Customized Boot image to allow me to call various HTA, OSD++, OSDAPPChooser "applications" in my Task sequence to customize my OS deployment.
THANKS as always - ok well i know that i have created a ts using MDT before this, it may help, maybe not, can you at least test that theory ?
or are your user permissions in some way insufficient ? based on the errors you are seeing
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Yup, I'll try that tommorow morning and report the results.
THANKS - Ok.. consistency (and Errors) are still there.
Went through the process to create a MDT 2010 Task sequence. (using steps in the MDT Deployment Toolkit step 3).. fill out the information and select FINISH.. and SURPRISE, SURPRISE.. I get the same error regarding creating Boot images.
Comes up with a message saying "Generating Boot Image" and then fails with message:
Error
Error while importing Microsoft Deployment Toolkit Task Sequence. Details:
Unable to mount image
c:\Users\myname\appdata\local\temp\2\winpe.wim to
c:\Users\myname\appdata\local\temp\2\PE20_mount.x86
Idea's?
OBVIOUSLY something is amiss with either MDT or AIK - Any general direction someone can point me to?
Is there a log somewhere that might shed some more information on this problem?
I've already uninstalled/reinstalled MDT 2010 2/3 times throughout this process, so I'm not sure what purpose that would serve again.
Seems amiss that it is point at a TEMP location above when it is trying to mount this image?
Is there "support" for MDT? (or since its a "solution accelerator" (I'll withhold my comments here) is it not fall under technical support?
THANKS - what user permissions do you have when trying this ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Admin of ALL.. Domain, Computer, SCCM, SQL.. (king of the world) :)
THANKS again.. this is driving me (and I'm probably driving you) NUTS!!!!! - do you want to try a remote assistance session ? if so contact me on msn and we'll try something
anyweb AT hotmail DOT com
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Has there possibly been any resolution for this issue?
I am having the exact same problem that dndoorlag is describing: when attempting to create a win-32 boot image, I follow the following steps -
Right click "Boot Images" under the OSD list in the console -> click Next
Enter \\02-imgsccm\Packages$\Boot\ZeroTouchWinPE to the target directory -> click Next
Enter the details of the package: Name, version, etc. -> Next
Ensure Platform is x86, and that ADO is selected ->
Summary page -> Next
and then the progress bar will get to two bars - and fail.
Error
Error while importing Microsoft Deployment Toolkit Task Sequence. Details:
Unable to mount image
c:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim to
c:\Temp\PE20_mount.x86
I am using a Windows 2003 SP2 server w/ SCCM R2 SP2, WAIK 1.1, and MDT 2010. I installed PowerShell after reading through this thread and that still didn't resolve my issue. I have permissions set on the TEMP directory for read/write for just about EVERYBODY - Admins, Domain Admins, Schema Admins, Enterprize Admins, my own account, SYSTEM, and Everyone. Taking some other advice from another thread I checked to see if there was already a mounted image by running the command:
imagex /unmount
and it displays that there are no mounted images anywhere.
If anyone has a solution - or any other things I can look at for possible resolutions, I'd really appreciate it. I originally set up my test lab environment using the guidelines in Johan Arwidmark's "ZT01 - Installing the Deployment Server for MDT 2008 Zero Touch and SCCM 2007 R2" on the Deployment CD, and this is the point I've reached and can go no further. - i can try a remote assistance session with you if you wish, just let me know
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - As much as I would appreciate that assistance, unfortunately due to my work security policies that's not an option that's available to me (and in any event, the test lab I'm working with is on an isolated network).
Apparently the issue that dndoorlag and I are having is not very common - there's very little information related to this problem online, and most of what's out there consists of someone asking for help when they get the "Unable to mount image [PATH] to [PATH]" and that's where the thread ends.
Was dndoorlag able to resolve this issue? Were Niall and dndoorlag able to connect and figure out where the problem exists?
I also have uninstalled and re-installed MDT 2010 (and 2008 before that a couple times) several times with no results, as well as WAIK 2.0. However - I did not install WAIK 1.1 prior to updating SCCM 2007 to SP2... I was unaware that SP2 updated WAIK 1.1 to WAIK 2.0. Could that be the issue (even though I've completely removed WAIK from my system and installed WAIK 2.0 a couple times now through the troubleshooting process)?
One question I would like to put forward too is : what account does SCCM 2007 use to create those boot images when it utilizes the "Create Boot Image using Microsoft Deployment" applet? Is it possible that account doesn't have the required priviledges to the system and as such is denied write access to the drive / folder when attempting to create the image (or even mount it first)? - we didn't do a ra session yet so i don't know if dnoorlag's problem is resolved yet.
when I am updating my boot images I'm always logged on to the sccm server using an account with full local administrative permissions on the box, and full access to the configmgr console,
are you using such a user ? do you see any unusual errors in your event viewer when trying this ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - sorry for no updates, but this issue took a back seat to other tasks.
Here is the latest. I was able to spend some time with Niall (HUGE KUDOS to NIALL for spending the time/effort to try and get this resolved).
Unfortunantly I'm still experiencing the same problem.
What Niall and I have tried to date is pretty much the following:
- Remove MDT2010 and AIK and REINSTALL SP2
(Still no change).
- Removed PSP, WDS, cleaned up the REMINST share (thinking was a permission issue on this share). Removed files from c:\window\temp and then reinstalled WDS, PSP and used the WDSUTIL to "configure" the WDS Server (so the WDSSERVER would show properly on the REMINST share..
Unfortunantly the SAME error is still occuring.
No offense MCHARVES, but I'm glad I'm not the only one experiencing this issue.
ANY other ideas I'd be interested in hearing. If I find a resolution/work around I'll post it here. Okay.. wanted to Update this as I called MS and got a resolution.
In our situation I was running SCCM SP2 on a 64 bit OS.
Check your PATH system variable and ensure the path DOES NOT include a x86 bit path for Windows Imaging. In my case the PATH system variable included "C:\Program Files (x86)\Windows Imaging\" (which I'm thinking is a 32 bit version of AIK).. in the path was also "C:\Program Files\Windows Imaging\" (64 bit version of AIK), but apparantly there was an erroneous reference to a x86 version causing the issue.
Took out the (x86) path from the PATH System Variable and Custom MDT boot images are back..
THANKS much especially to Niall who spent many hours with my trying to get resolved.- Marked As Answer bydndoorlag Thursday, January 07, 2010 8:18 PM
- great to hear that it is resolved ! and thanks for the update
i wonder how the path statement got in there... gonna check my servers..
my home 64bit server also as that statement but i didnt have your problem....
look
C:\Users\smsadmin>path
PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files (x
86)\Microsoft SQL Server\80\Tools\Binn\;D:\Program Files\Microsoft SQL Server\90
\DTS\Binn\;D:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files
(x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Smart Projects
\IsoBuster;C:\Program Files\Windows Imaging\;C:\Program Files (x86)\Windows Imag
ing\;D:\Program Files\Microsoft SQL Server (x86)\90\Tools\binn\;D:\Program Files
\Microsoft SQL Server (x86)\90\DTS\Binn\;D:\Program Files\Microsoft SQL Server (
x86)\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual
Studio 8\Common7\IDE\PrivateAssemblies\;C:\Program Files\System Center Operation
s Manager 2007\;C:\Windows\System32\WindowsPowerShell\v1.0\
cheers
niall
My step by step SCCM Guides
Follow me on Twitter- Edited byNiall C. Brady Thursday, January 07, 2010 8:36 PM
- THANKS Again for the help.. we (YOU) were close to resolving looking at the System variables.. we just never looked at the PATH variables.
Ya but it looks like your x64 path is before you x86 path (so no problem).. in my case the x86 path was before the x64 path..
Don't know HOW/WHY this Path was I'll say incorrectly set?? That is still the mystery.
- Hi Niall
This solution worked for me like a dream.
Cheers
PS For those who don't have the old MDT 2008 handy it's now here:
http://www.microsoft.com/downloads/details.aspx?familyid=02A2605D-51E8-469F-BE4A-1DD2AF580502&displaylang=en - Just another report of this error, I just upgraded my 2008 R2 X64 server to SCCM R2 SP2, and had an error attempting to create new Boot images with an error:
Error while importing Microsoft Deployment Toolkit task Sequence. Details: Unable to mount image C:\Users\<UserID>\AppData\Local\Temp\Winpe.wim to C:\Users\<userID>\AppData\Local\Temp\PE20-Mount.x86
After a lot of hair pulling I found this post and I too had the reference to the C:\Program Files (x86)\Windows Imgaing in my Path.
Removed it and it is now functioning without an issue.
Great detective work guys.
Brett Moffett
