Can I inject drivers into a .wim file on usb boot media?

Hi,
I have been working for days trying to install win7 64 bit on a HP Z620 machine and I keep getting the error “Windows failed to load because of a critical system driver is missing, or corrupt.” 0xc0000359
iastore.sys. I am fairly new to SCCM and I don't want to mess with the productive boot image so I was wondering can I inject the iastore.sys drivers into the boot wim file on a thumb drive? All I have found is examples only using config manager and modifying
the productive boot wim. Is this possible? Thank you

The Boot .wim file has nothing to do with loading Windows and the drivers needed there. That error is typically because Windows did not have the driver needed to load the Storage controller.
Are you using Auto Apply Drivers or Apply Driver Package to install the drivers into Windows for the Z620 in your task sequence?
Review below for information about loading drivers into SCCM:
http://hayesjupe.wordpress.com/sccm-osd-driver-best-practices/
http://gerryhampsoncm.blogspot.com/2013/02/sccm-2012-sp1-step-by-step-guide-part-9.html
http://www.deploymentresearch.com/Research/tabid/62/EntryId/69/The-Drivers-Saga-continues-How-to-Master-Drivers-in-ConfigMgr-2012.aspx
Daniel Ratliff | http://www.PotentEngineer.com

Similar Messages

SCCM 2012 Injecting Drivers in to WIM File fails

Hi All,
I am currently having issues updating the boot wim file x86 I keep getting the following
Error: Boot image to update:
• Microsoft Windows PE (x86)
Error: Actions to perform:
• Add ConfigMgr binaries
• Add custom background
• Set scratch space
• Enable Windows PE command line support
• Add drivers
Error: Failed to import the following drivers:
• Intel(R) 82945G Express Chipset Family (Microsoft Corporation - WDDM 1.0)
• Intel(R) 82579LM Gigabit Network Connection
• ASIX AX88772B USB2.0 to Fast Ethernet Adapter
• Intel(R) 82567LM Gigabit Network Connection
Optional components:
• Scripting (WinPE-Scripting)
• Startup (WinPE-SecureStartup)
• Network (WinPE-WDS-Tools)
• Scripting (WinPE-WMI)
Error: The wizard detected the following problems when updating the boot image.
• Failed to install required components into the boot image
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4630;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"NZP00041\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
I have searched Google and read up other people's issues, and there seems to be many different options to resolve this.
Tried most out there so far, going to try downloading the network driver again and test that, incase its the INF files issue.
Just wanted to see if anyone else has resolved this and what was there method.
Cheers in advance.

Hi Gerry,
I tried this and it updated the WIM file, but I still couldn't get it to capture the OS once I filled in all the details.
The look file TSMBAutorun.log says this -
<![LOG[TSMBAutoRun started]LOG]!><time=13:0:0 date=0-1-1970 component="TSMBautorun" context="" type="1">
<![LOG[Unknown system architecture 0]LOG]!><time=13:0:0 date=0-1-1970 component="TSMBautorun" context="" type="1">
The smsts.log says
<![LOG[Activating Welcome Page.]LOG]!><time="12:13:02.255-720" date="04-22-2014" component="OSDCaptureCD" context="" type="0" thread="5372" file="infopage.cpp:68">
<![LOG[InfoPage::OnWizardNext()]LOG]!><time="12:13:05.609-720" date="04-22-2014" component="OSDCaptureCD" context="" type="0" thread="5372" file="infopage.cpp:113">
<![LOG[Activating Finish Page.]LOG]!><time="12:13:05.609-720" date="04-22-2014" component="OSDCaptureCD" context="" type="0" thread="5372" file="finishpage.cpp:59">
<![LOG[Saving capture information in the environment.]LOG]!><time="12:13:06.264-720" date="04-22-2014" component="OSDCaptureCD" context="" type="1" thread="5372" file="wizardcontrol.cpp:499">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="12:13:06.295-720" date="04-22-2014" component="OSDCaptureCD" context="" type="1" thread="5372" file="osdcapturecd.cpp:157">
<![LOG[Process completed with exit code 0]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="commandline.cpp:1123">
<![LOG[Succeeded loading resource DLL 'E:\SMS\bin\i386\00000409\TSRES.DLL']LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="util.cpp:963">
<![LOG[AllocateCDRoms=1]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="tsmediawizardcontrol.cpp:2265">
<![LOG[AllocateCDRoms is set; will not start TSManager]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="3" thread="5132" file="tsmediawizardcontrol.cpp:2269">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="0" thread="5132" file="commandline.cpp:228">
<![LOG[Set command line: "E:\SMS\bin\i386\TsProgressUI.exe" /Unregister]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="0" thread="5132"
file="commandline.cpp:731">
<![LOG[Executing command line: "E:\SMS\bin\i386\TsProgressUI.exe" /Unregister]LOG]!><time="12:13:06.373-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132"
file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 4284 ]==========]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:330">
<![LOG[Command line: "E:\SMS\bin\i386\TsProgressUI.exe" /Unregister]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="0" thread="4276" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TsProgressUI" context="" type="1" thread="4276" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="utils.cpp:2320">
<![LOG[ExecuteSelectedTaskSequence(fpCallbackProc,pv,hCancelEvent), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1527)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap"
context="" type="0" thread="5132" file="tsmediawizardcontrol.cpp:1527">
<![LOG[ResolveAndExecuteSelectedTaskSequence( 0, 0, 0 ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2421)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap"
context="" type="0" thread="5132" file="tsmediawizardcontrol.cpp:2421">
<![LOG[Unattended(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2762)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context=""
type="0" thread="5132" file="tsmediawizardcontrol.cpp:2762">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, false ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,910)]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap"
context="" type="0" thread="5132" file="tsmbootstrap.cpp:910">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1183)]LOG]!><time="12:13:06.405-720" date="04-22-2014"
component="TSMBootstrap" context="" type="0" thread="5132" file="tsmbootstrap.cpp:1183">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="tsmbootstrap.cpp:1195">
<![LOG[Finalizing logging from process 5128]LOG]!><time="12:13:06.405-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132" file="tslogging.cpp:1741">
<![LOG[Successfully finalized logs to SMS client log directory from C:\Users\NCR\AppData\Local\Temp]LOG]!><time="12:13:06.498-720" date="04-22-2014" component="TSMBootstrap" context="" type="1" thread="5132"
file="tslogging.cpp:1542">

Can't inject drivers into boot images as they don't appear

Hello,
I have a problem trying to inject some drivers into the boot image using SCCM 2012.
I right click on the specific driver, I choose Edit > Boot image and there no boot images show up! The list is empty.
We do have 2 boot images (x32 and x64) and they are working just fine!
Does anybody have a clue what is going wrong here?
Thanks.

What version of ConfigMgr (RTM, SP1, or R2) are you using and what version are the boot images?
Each version of ConfigMgr can only directly manage (including driver injection) specific boot image versions.
RTM -> WinPE 3.1
SP1 -> WinPE 4.0
R2 -> WinPE 5.0
Thus, you are most likely trying to edit downlevel (or maybe uplevel) boot images.
Jason | http://blog.configmgrftw.com

SCCM 2012: Failed to insert OSD binaries into the WIM file' error when you create a MDT Task Sequence

Hi,
When I try to import the MDT boot image X86, I get the following error:
Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-mdac
Adding extra content from: C:\Users\ADMINI~1.afO\AppData\Local\Temp\3\sfup2yp2.0rt
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence.
Failed to insert OSD binaries into the WIM file
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Put(PutOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
Note: previous x86 image was deleted some time ago.
Please advise.
J.
Jan Hoedt

This is the error in smsprov.log
*********** WBEM Missing property TransformAnalysisDate    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
************ WBEM Missing property TransformReadiness    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:10    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
ERROR> Error -1073741502 returned to execute the command line: "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount" /Add-Package
/PackagePath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-Scripting.cab"    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
Failed to install required components into the boot image C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3766) : Failed to insert OSD binaries into the WIM file~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
*~*~Failed to insert OSD binaries into the WIM file ~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
Auditing: User FAC\administrator called an audited method of an instance of class SMS_BootImagePackage.    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=9281008    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
Jan Hoedt

Back Screen when Injecting Drivers into Discovery Image

I am using windows server 2012 with ADK 8.1
The discovery wim was created from a windows 7 enterprise boot wim
The drivers I am using are windows 7 drivers for Optiplex 7010 downloaded from here
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx#WinPE
I created two driver folders one dell x32 and one dell x64.
I have tried injecting only the network drivers into 32 and 64 bit discovery images making sure only x64 drivers were used with 64 bit images and the same for 32 image only using 32 bit drivers.
I retried the above steps however I injected all available drivers available in addition to the network drivers and had the same result.
After the windows 8.1 splash screen appears and then goes away the screen remains black. What may be the cause of this?

Hi,
I wonder which driver did you injected. Boot.wim contain a widows PE image, and windows 7 code based windows PE version is winPE3.0.
So I suppose we need a winPE3.0 driver but not the one for windows 7.

How do I get the music from the I tunes store thing onto my computer I want to put some music into a presentation but can't get it into my computer files

I am trying to figure out how to get music out of the I tunes Store and into my computer files ?

Davs,
When you say "presentation," are you by any chance talking about Power Point? If so, the music must be in one of the formats that is compatible with Power Point, which includes MP3.
The files sold in the iTunes Store are in AAC format, which is not compatible with Power Point. You can convert AAC to MP3 by following this guide:
http://support.apple.com/kb/PH12367

How to obtain the number of words of a protected pdf file that can't be converted into a word file?

I need to get the number of words of pdf files. I usually convert them into word files to get the word count. Some pdf files are protected and can't be converted into word files. Is there another way to get the number of words of these protected pdf files? I use adobe professional XI Pro.

Scroll through and read the answers available in the thread below. You may find the information helpful.
Trying to write Javascript code to get word count
Be well...

Can't separate funds into separate FrameMaker files

We have an automated process that was internally created in FrameMaker that takes a FrameMaker Book file that contains a large number of individual mutual fund files and breaks out each mutual fund into an individual file using the fund’s unique product code, removes sector tabs, and removes page numbers, then creates a postscript file. The user selects the functionality from a menu choice within an internally created “Marketing” menu on the FrameMaker menu bar. It is not functioning properly.
Instead it is generating error messages.
Adobe FrameMaker (Structured): FrameMaker.exe - Application Error:
The instruction at "0x00cc1940" referenced memory at "0x00000000". The memory could not be "read". Click on OK to terminate the program.
and
Error:
Internal Error 8004, 6343116, 8 483344, 0. FrameMaker has detected a serious problem and must quit.
A file named "C:\Program Files\Adobe\FrameMaker8\FrameLog_11.10.17_07.52.51.txt" has been generated which contains information that may help Frame development improve the product for future release.
We have looked at the FrameLog_11.10.17_07.52.51.txt but it is not helping us diagnose the issue.
Can you help us determine what the problem is and how to resolve it?
Thanks for your help.

Well, there's a reply I've never heard before, but I don't mean to make light of this situation, especially if the individual was your friend. In any case, my condolences.
With the source code, it should be a simple matter to run this process through a debugger to at least identify the point where the memory violation is occurring. In my personal experience, problems are usually caused by a simple mistake and therefore corrected quickly once the errant code is identified. If you don't have someone on staff that could do this, I'd strongly recommend that you get somebody for a few hours or a day to figure this out. Otherwise, you are dealing with a ticking time bomb that will certainly blow up on you again sometime (at the worst possible moment), even if a reinstall or some other trick seems to fix it.
I don't know that there is much more that I can tell you. There is either a bug with the plugin or FM and I think somebody needs to get into the debugger to find it.
Russ

I upgraded to Lightroom 3.4 and can't move photos into collections or files

I upgraded to Lightroom 3.4 and can't move photos into collections or files

To move a photo into a collection, you point your mouse at the photo(s) (not the gray rectangle around the photo) and drag it into a collection.
You can't move a photo into a file. Perhaps you meant something else?

WIM file applied. Boot error of BOOTMGR is missing.

My desktop computer has 2 physical hard drives
I booted with a USB drive to capture images using the ImageX tool.
Drive G is recognized as being the USB 'capture image' boot device that has ImageX tool.
Disk 0 is recognized as drive C.
Disk 1 is recognized as drive D.
I captured the C:\ drive and the D:\ drive with the following commands.
Both completed successfully.
G:>ImageX /compress fast /BOOT /verify /check /flags "Enterprise" /capture C: G:\Drive_C_install.wim "Windows 7 Professional" "Windows 7 Professional Custom"
G:>ImageX /compress fast /verify /check /flags "Enterprise" /capture D: G:\Drive_D_install.wim "Windows 7 Professional" "Windows 7 Professional Custom"
I then replace the 2 physical disks with new ones. I used diskpart to select disk 0, create a partition, format, assign a size , assign letter C and mark C as active. Disk 1 also the same (except I did not mark disk 1 as active.
I then boot with bootable USB and now successfully apply the .wim files with the following commands.
G:>ImageX /apply /verify G:\Drive_C_install.wim 1 C:\
G:>ImageX /apply /verify G:\Drive_D_install.wim 1 D:\
However, when I boot up expecting to see a clean boot into Windows, instead I get the error of:
"BOOTMGR is missing. Press Ctrl+Alt+Del to restart"
I am thinking I did not capture the image properly? (I am able to see the files and folders actually did apply to the new hard drives by using a SATA hard drive docking station and seeing them on another PC)
Any assistance is greatly appreciated.

Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
As the question is off topic here, I am moving it to the
Where is the Forum... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Installing WIM file using USB

Hi,
I want to install captured image using USB. Not sure where I went wrong. here is what I did.
I captured an image(windows 8.1 x64 ) using MDT . I have used the captured image in WDS it works fine. But I wanted to use USB (as the file size is 6GB cant use DVD) to install on remote machines.
Than I converted it to ISO. I followed a step in http://www.ehow.com/how_5750929_convert-wim-file-iso-file.html
Finally I created bootable USB using Rufus (also tried ultraiso). easy ah
But when I boot from the USB it is giving me "windows failed to start"error as if there is no windows file on the USB.
Can anyone please help me.
Thank you very much
Serki

You can use the wim you captured, and create a new task sequence in MDT. You should then be able to create media to a folder, and copy the files to a USB drive. Once booted, the process should be similar to the WDS process you have used, assuming you used
a MDT task sequence for the WDS deployment.
Here is a walkthrough for Windows 8.1.
https://technet.microsoft.com/en-us/windows/dn481547.aspx

What *Can't* I export into a .swf file?

Hey all!
I have a short, 5 slide presentation which includes a few slide transitions, some text animation (dissolves, disappears, timing) an aiff file and a little QT movie at the end.
When I export the movie and throw it to Freeway Pro, all I see is the beginning of the first slide.
A friend says you can't create flash files from certain types of animation in Keynote (to me, that would seem to defeat the export-to-flash purpoase).
Is he right? If so, can you tell me what I need to be sure NOT to use in the slideshow?
-James

I'd like to help, but this is the Pages forum. I think you'd get better responses if you posted your question in the Keynote forum.

Can't get back into os x after os 9 boot.

I've never booted into os 9 on my old imac g3, so I decided to try it. After i selected os 9 as the startup disk and restarted, it showed up as a floppy disk with a question mark installed. I guessed something isn't installed right. I don't really care about os 9 now, i'm just trying to get back into os 10.4 tiger. I've tried holding the option key during restart, and it only shows a refresh button, macintosh hd in the middle, and an arrow pointing toward the right. The refresh doesn't do anything, and the arrow takes me back to the floppy disk with the question mark. Can anybody help me boot back into os x??? Thanks.
-Aaron

Sometimes you can call Apple and get replacemebt disks reasonably with your Serial# handy!
Tough without a Tiger Disk, but try fsck...
To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
1. Start up your computer in single-user mode to reach the command line. Hold CMD+s keys down at bootup. Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
2. At the command-line prompt, type /sbin/fsck -fy
3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found: ** The volume (nameofvolume) appears to be OK  If fsck found issues and has altered, repaired, or fixed anything, it will display this message: *** FILE SYSTEM WAS MODIFIED ***   Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
http://docs.info.apple.com/article.html?artnum=106214
Then Safe Boot , (holding Shift key down at bootup), off the HD & use Disk Utility from there to Repair Permissions, reboot once more.

How do I use copyprofile, image manager and create a wim file to Sysprep a reference Windows 8 computer.

Im trying to deploy a reference machine (configured) to other machines (exact or close image) with different hardware.
I have successfully used sysprep in out of the box, generalise, shutdown mode although i havent tried to deploy this to another device. Unfortunately it doesnt copy the profile to default.
I understand that I have to create an answer file using image manager based on that image, save it to a usb drive and attach this in the sysprep command line when sysprepping it.
My problem is I dont know how to easily capture an image of windows 8 into a wim file so that i can add this into image manager to create a answer file. Im also not sure what I have to do in image manager, is it a simple matter of creating and saving
the answer file or do i have to configure it to copy the profile specifically (theres only one account anyhow).
I also want to know if i have to attach the drivers or are all the standard drivers put into the sysprep image as standard. I would like the machine to be an exactly replica, same as doing a clone (but with the drivers for the new machine installed
so it will boot) same as doing a clone and then repair? If thats possible.
Any specific instructions on this would be helpful. I have read the microsft links but they are somewhat confusing.

I know this is a very late response but I thought I'd post for others who search.
The easiest way to create the .wim file is via WinPE, this guy's two YouTube videos explain the entire process in detail -
Windows 8 ADK Part 1: Capture an OS image - https://www.youtube.com/watch?v=XJ8zKX_8E9w
Windows 8 ADK Part 2: Windows Image Deployment - https://www.youtube.com/watch?v=HHIvoqSw_FI
Here's a quick rundown from my notes:
WINPE
Create WinPE via imaging tools command prompt
copype amd64 c:\winpe
makewinpemedia /iso "c:\winpe" "c:\winpe\winpe64.iso"
UNATTEND
Open Windows System Image Manager
Configure unattend.xml
Save unattend.xml to sysprep folder
Create script and save it to sysprep folder to launch sysprep with unattend
@echo off
cd C:\Windows\System32\sysprep
Sysprep /oob /generalize /unattend:C:\Windows\System32\sysprep\unattend.xml
SYSPREP
C:\Windows\System32\Sysprep
Run as administrator
OOBE/Generalize
Shutdown
CONFIGURATION of WINPE
Set IP - netsh int ip set address "Local Area Connection" static 192.168.1.2 255.255.255.0 192.168.1.1
Set DNS - netsh int ip set dns name = "Local Area Connection" source = static addr = 192.168.1.4 validate = no
Map Network Name - net use z:
\\WindowsADK\reflex\images password /USER:domain.local\username
DISKPART
diskpart
list disk
select disk zero
list partition
select partition 2 (OS partition #)
Assign letter=S (assigns drive letter to partition)
Exit
DISM
dism /capture-image /imagefile:z:\image.wim /capturedir:s:\ /name:"Windows 8.1 Custom"
Verify image is saved in the image share (z:)
http://www.microsoftfanboys.com

Adding patches to an offline .WIM file

Hi guys
I am trying to update my companies Windows Server 2008 R2 x64 install.wim file with some patches I have downloaded from the Microsoft Catalogue.
So a little background, I have taken the install.wim file from the sources directory of our server image which is saved on our deployment server, and I have copied it locally to my PC. I am a domain admin and I am also a local admin on my PC.
I downloaded the latest ADK and ran the Deployment and Imaging Tools Environment tool as an administrator. I mounted the install.wim file to a mount folder with no problems.
When I try to inject a single patch using this command line DISM /image: <mount_directory> /Add-Package /Packagepath: <msu_file> (obviously replacing mount_directory and msu_file with the correct paths) I get the below error.
Image version: 6.17600.16385Processing 1 of 1 – adding package…………(package path details ect)
99.5%
An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
Error: 0x80070005
Error: 5
Access is denied.
Edited copy of the log file:
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to process package changes in unattend file. - CPackageManagerUnattendHandler::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Unattend Manager: PID=9880 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:400 - CUnattendManager::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed applying the unattend file from the MSU package. - CMsuPackage::ApplyMsuUnattend(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to apply the MSU unattend file to the image. - CMsuPackage::Install(hr:0x80070005)
When looking at the Security tab under properties of the mount folder I can see that the account CREATOR OWNER has no permissions. When I tried to give it full control I get access is denied on the following folders:
C:\mount\program files
C:\mount\program files (x86)
C:\mount\windows
If I check the permissions for my account name, it does have full control of the mount folder.
I am wondering if anyone can help me get rid of this error?
Or even better still as I have 63 patches to inject into this .wim file, can anyone suggest an easier way, as I wouldn’t like to sit here all day doing one patch at a time?
Thanks in advance.
Dave

Hi David Smale,
From your current description and base on my experience, it usually caused by the WIM file corrupt, please try to copy a new Wim file then try to patch again, if it not work,
please post your DISM error log, you can refer the following KB to get the DISM log.
This error also can caused by the Mcafee AV.
DISM.exe generates an Error: 5 or Access Denied when VSE 8.8 Access Protection is enabled
https://kc.mcafee.com/corporate/index?page=content&id=KB76867&locale=zh_CN
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Can I inject drivers into a .wim file on usb boot media?

Similar Messages

Maybe you are looking for