awesome - nothing ever goes right here.. go to mount the wim and get an error stating that dism.exe is not a valid win32 app. GREAT!
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Burke, John Sent: Monday, May 13, 2013 2:40 PM To: [email protected] Subject: [MDT-OSD] RE: MDT boot wim - now i have to mount and edit it - which one do i use? Ok. so use the WINPE.wim then. Thanks. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Monday, May 13, 2013 2:30 PM To: [email protected] Subject: [MDT-OSD] RE: MDT boot wim - now i have to mount and edit it - which one do i use? The larger one with the packageID appended to it is generated by SCCM when you update the distribution points. If you add anything to that WIM just know that it'll be lost if you up the DPs for that package. SCCM takes the WinPE.WIM source file, injects the drivers, binaries and any other additions and creates the second WIM file. It then uses that to boot your machines. From: [email protected] [mailto:[email protected]] On Behalf Of Burke, John Sent: Monday, May 13, 2013 1:23 PM To: [email protected] Subject: [MDT-OSD] MDT boot wim - now i have to mount and edit it - which one do i use? I created a new 32bit boot wim - it's completed. I notice there are 2 .wim files in my package source. a wnipe.wim that is 142mb and a winpe.ns2003f0.wim that is 155mb. I have to mount this file and add a few little things. Is it safe to assume i had to add the larger one or do i do the plain WINPE.wim? ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
