Multiple Menu Deploy OS in USB .WIM Files

Hi
We SCCM 2012 and I create bootable USB to install windows 7 in standalone workstation
Now, My concern is I have 4 Images (e.g WinXP x86, WinXP x64, Win 7 x86, Win 7x64)
and my problem every OS images with the extension of .WIM files , I need to create A USB files which is time consuming and effort from my end. Imagine every .wim or Images I need to create a USB
Is there a way or option That I can select which images I want to deploy for the target machine
Menu List:
Option 1: WinXP x86
Option 2: WinXP x64
Option 3: Win 7 x86
Option 4: Win7 x64
Please advise
Robert

This question is ambiguous. You say that you have four *.wim files, however please be clear, *.wim files can be used in windows for both storage (Like an large *.zip file or *.gho Ghost file) file to store the OS itself, or it can be used as the storage
mechanism for a WinPE *boot* image.
If you have more than one Task Sequence, you can publish to all machines, and it should appear when you boot your SCCM Boot image.
If you have more than one SCCM boot image, there are ways to modify a USB file to have more than one USB boot image. However, this is confusing to me, if the task sequences are on the same SCCM Server. Really SCCM Boot images are per Site Server, not per
OS Image, so there is no need to create more than one boot image.
Keith Garner - keithga.wordpress.com

Similar Messages

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

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

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

How to edit a captured custom .wim file?

Hi folks,
I am in process of gaining experience with capturing and deploying Windows 7 SP1 from our WDS server using unattend file.
Everything is working, since we installed our applications, ran sysprep, and captured a custom .wim file.
Now we deploy it using unattend file and everything works.
I am trying to figure out if there is a best practice here for adding applications to this new custom .wim file?
I've tried deploying this new image to a unit, installed app, and run sysprep but fails with this error:
A fatal error occurred while trying to sysprep the machine.
I am thinking this has to do with multiple syspreps or something?
I am trying to avoid having to use a default install.wim and app install automation with MDT or something like that. We are strict to WDS only right now.
Appreciate any comments,
Thanks! romatlo

Offline servicing allows for adding/removing drivers and updates in MSU/CAB files.
I do not use MDT either. If you want to "install" a new application to an image that is "out of arms" then you will need to install it after deployment. If your image has an answer file, you can mount your image. Then copy the installation files to it or
you can keep it on a network share. Then in the answer file, you can put in the commands to install it using FirstLogonCommands.
I typically like to reference a .cmd file in my unattend that I can add/remove commands to finalized images. So if a client wants to install a new program but doesn't want to recreate the image, then I can have it installed that way.
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<Description>Set up Service Account</Description>
<CommandLine>cmd /C start /wait c:\folder\FirstLog.cmd</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>

Adding custom WIM files to a bootable thumb drive

Hi, I have setup an WDS 2008 that works fine for deploying and capturing images over my network. I am trying to find a solution to create a bootable thumb, that would contain those custom images captured with WDS. So what I did until I got stuck:
Created a bootable thumb drive from an Windows 7 Pro installation disk, using Se7en Lite. Mounted the custom image in a folder and used "imagex" to append it to the "install.wim" file on the thumb drive. Checked with "imagex /info"
and indeed the custom image showed with index 5 and description "Windows7_x64_patched". Booted a PC off the thumb drive and got to the screen that asks which version of Windows I would like to install. Here, only one option shows up "Professional",
which would be the untouched Windows 7 Pro version. So no Basic, Premium or Patched version would show up, even though I can see them and their indexes with "imagex /info".
Questions:1) Is there an easier/faster way of creating a bootable thumb with multiple custom WIMs?
2) If "imagex /append" is a good solution and I'm on the right track, then what I should do so that the appended image would show as an option when installing off the thumb drive?
Thanks!

Thank you for your reply! So I edited the ei.cfg file (deleted "Professional" from [EditionID]. Now it shows me the four untouched versions "Basic", "Home Premium", "Professional" and "Ultimate" but not the custom one. I can still scroll down one more
row, so there is something without a description available seems. But if i scroll down to the 5th row and press enter, then I get the error: "Windows could not display the image available for installation". Referring to the first question and answer now, if
I replace the original "install.wim" on the thumb with my custom WIM, then I only have one image, as the WIM container would only have my captured image. So what I was asking is there an easier way to stick MORE THAN ONE installation image on the same bootable
device, without using the huge time consuming "imagex /append" command?
Here's a copy of my "imagex /info" on the modified "install.wim" from thumb:
WIM Information:
Path: e:\sources\install.wim
GUID: {65caf905-5e50-4a42-900b-5e14084871e9}
Image Count: 5
Compression: LZX
Part Number: 1/1
Attributes: 0x8
Relative path junction
Available Image Choices:
<WIM>
<TOTALBYTES>5643506813</TOTALBYTES>
<IMAGE INDEX="1">
<DIRCOUNT>13365</DIRCOUNT>
<FILECOUNT>64285</FILECOUNT>
<TOTALBYTES>11710161360</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x0027D0DC</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>HomeBasic</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 HOMEBASIC</NAME>
<DESCRIPTION>Windows 7 HOMEBASIC</DESCRIPTION>
<FLAGS>HomeBasic</FLAGS>
<HARDLINKBYTES>4497873056</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Home Basic</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Home Basic</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="2">
<DIRCOUNT>13614</DIRCOUNT>
<FILECOUNT>65339</FILECOUNT>
<TOTALBYTES>12222587449</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x236D21C7</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>HomePremium</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 HOMEPREMIUM</NAME>
<DESCRIPTION>Windows 7 HOMEPREMIUM</DESCRIPTION>
<FLAGS>HomePremium</FLAGS>
<HARDLINKBYTES>4912986404</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Home Premium</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Home Premium</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="3">
<DIRCOUNT>13701</DIRCOUNT>
<FILECOUNT>65851</FILECOUNT>
<TOTALBYTES>12122886417</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CE98EE</HIGHPART>
<LOWPART>0xCA54650A</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Professional</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 PROFESSIONAL</NAME>
<DESCRIPTION>Windows 7 PROFESSIONAL</DESCRIPTION>
<FLAGS>Professional</FLAGS>
<HARDLINKBYTES>4786527097</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Professional</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="4">
<DIRCOUNT>13737</DIRCOUNT>
<FILECOUNT>66029</FILECOUNT>
<TOTALBYTES>12285492779</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x6D7F6938</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Ultimate</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 ULTIMATE</NAME>
<DESCRIPTION>Windows 7 ULTIMATE</DESCRIPTION>
<FLAGS>Ultimate</FLAGS>
<HARDLINKBYTES>4947144081</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Ultimate</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Ultimate</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="5">
<DIRCOUNT>16853</DIRCOUNT>
<FILECOUNT>80207</FILECOUNT>
<TOTALBYTES>17942171343</TOTALBYTES>
<HARDLINKBYTES>4936766950</HARDLINKBYTES>
<CREATIONTIME>
<HIGHPART>0x01CE9935</HIGHPART>
<LOWPART>0x5B788A49</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CE9935</HIGHPART>
<LOWPART>0x6D5A05EC</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Professional</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>18015</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Win7Pro_x64_patched_nod</NAME>
</IMAGE>
</WIM>

WDS on server 2008 std breaking .WIM files

Hi,
SUMMARY - 'Importing images into WDS seems to break them'
I'm a bit green so i appologise if I'm being stupid. I'm installing and configuring WDS and MDT deployment within a mixed MS 2003 domain environment. We need to be able to deploy 32 bit images and the server will be used for servicing images as well
as deploying and so (I think) I need to use Server 2008 standard as creating catalogue files on x64 systems for x86 images doesn't work.
So - the system is:
Server 2008 standard x86 edition; WDS Deployment Services Role; MDT 2012 Update 1; ADK 8, config manager tools for trace32.exe.
I have imported win7 boot and install images directly from the original DVD .iso files, both x86 and x64. Both capture and setup images work ok. I've added network drivers to these successfully. I can deploy vanilla win7 x86 and x64 using WDS - this works
fine.
So my issue is: I've deployed vanilla windows 7 to a desktop, installed applications, updated config as nessecary etc. Booted using the appropriate capture image and captured a .wim file. I've copied this to my WDS server and imported it as an install
image. When I try and deploy the image it fails just after the 'expanding windows files' stage. After looking in log files the error seems to be 'selected image file does not have a resource section'.
I've gone back to the WDS server, exported these image files and tried to mount them using DISM - I get the same error: "1812 The specified image file did not contain a resource section"
Mounting fails.
Now I've tried mounting the .wim files using dism BEFORE I import them into WDS and they mount without any issues. As soon as I import them and export them again they will not mount any more.
Please help, I don't know what else to try! :)
Some things I've thought but can't find answers to: Can you use 2008 standard to deploy Windows 7 at all? (server is earlier version of windows)
Is the apparent importing into WDS issue a red herring? Could it be that these images are broken from capture? Is there a way to test this without deploying the image using a USB stick instead of WDS?
I've tried uninstalling the ADK and installing WAIK instead. Exactly the same result. Here are some choice extracts from dism.log:
2015-03-02 17:33:18, Info                  CBS    Failed to find a matching version for servicing stack: C:\Users\softset\AppData\Local\Temp\MDTUpdate.2544\Mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.2.9200.16384_none_060a6d2998b13f25\
[HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2015-03-02 17:33:18, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2015-03-02 17:33:18, Info                  CBS    Failed to get proc address for CMP_GetServerSideDeviceInstallFlags [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND]
2015-03-02 17:33:18, Info                  CBS    Failed to load CfgMgr32 DLL. [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND]
2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 Failed to mount the image. - CWimImageInfo::Mount(hr:0x80070714)
2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:999 - CWimManager::InternalOpMount(hr:0x80070714)
2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2247 - CWimManager::InternalCmdMount(hr:0x80070714)
2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070714)
2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0x80070714)
2015-03-03 15:29:27, Error                 DISM   DISM.EXE: WimManager processed the command line but failed. HRESULT=80070714

Hello JPNhingy,
How to do you capture the .wim file?
About the question: Can you use 2008 standard to deploy Windows 7 at all? The answer is: Yes, you can use the Windows Server 2008 to deploy Windows 7.
You could create a capturer image in WDS, for more information, please take a look at the following article.
http://social.technet.microsoft.com/wiki/contents/articles/11680.creating-a-capture-image-in-wds.aspx
Additionally, you could use the sysprep to generalize the install image.
https://technet.microsoft.com/en-us/windows/preparing-an-image-using-sysprep-and-imagex.aspx
Best regards,
Fangzhou CHEN
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Combining Spanned WIM Files

I am trying to combine about 12 swm files back into 1 single wim file. I would like to be able to use this with DISM to deploy images to multiple machines at once. I am using this command to combine the swm files:
imagex /ref C:\install*.swm /check export c:\install.swm * C:\install.wim (any name you want) COMPRESS /maximum
Thing is, I have 12 files all together, but it only seems to combine the first two, and then states that it's completed. When looking at the size of the wim file, it's not a combination of all them together (tops out at about 8 gig when it should be
much closer to 24 gig). So I don't believe that it's actually combining all of the files. Did I miss something? Or is there another command that needs to be run to finish combining the other files?

https://social.technet.microsoft.com/Forums/zh-CN/137bcb32-8546-4237-a2e1-51fecd8c365d/solved-how-to-mount-split-or-merge-combine-split-wim-files?forum=mdt
This may help

Can I have multiple images on a single USB drive?

I would like to save an image from my T400 (XP), then upgrade the hard drive to an SSD, then upgrade the OS to Windows 7 (or 8), and take another image.
I have several questions that I hope someone can help me with...
Can I use Rescue and Recovery to save multiple images to a single USB drive?
If so, how does the sw keep the files separate?
Will it still work if I use two different Rescue and Recovery versions (4.3 for XP, and 4.5 for W7)?
Is there a way to store the images in separate folders on the USB drive, or is that unnecessary?
Is there a better way to do this (including using different sw)?
Thanks in advance,
Ron
Solved!
Go to Solution.

If you open Disk Management, you'll see Disk 0 with more than one partition. If you want to rebuild a HD back the same you'll want all or at least two of the partitions. You'll notice the Active Boot partition is not C the Windows drive but a partition called System_Drv (at least in my system). Those two will be mandatory when you image a new drive. Otherwide you'll have some fixing with external tools to get it booting.
T520 Model 4239 Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz
Intel Sandy Bridge & Nvidia NVS 4200M graphics Intel N 6300 Wi-Fi adapter
Windows 7 Home Prem - 64bit w/8GB DDR3

Temporary wim-files for multicast transmissions still needed for WDS installation in Server 2012 R2?

Acording to
https://technet.microsoft.com/en-us/library/dn281955.aspx one of the new features for WDS in Server 2012 R2 for multicast is:
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
However, this doesn't seem to be activated by default and I still get the following error when installing one or more machines using multicast:
"Windows Setup cannot locate a valid hard drive to store temporary installation files." However, once I remove Multicast from this install image, it installs without any problems at all.
I have also noticed that while multicasting, the installation will use the "Copying Windows files" phase, while downloading and copying the install.wim (or whatever name it is) locally on the hard drive first, so this will require lots of space.
So the question is, how do you enable this new feature that should be a part of WDS in Server 2012 R2???

Full version:
Following steps could help enable the feature:
1. Mount the boot image using dism.
e.g.
>dism /mount-wim /wimfile:c:\remoteinstall\boot\x64\images\boot.wim /index:2 /mountdir:c:\mount
2. Create a metadata file if no existing one. The metadata file should be in mountdir from the first step under mountdir\sources. And the file name should be: WdsClientMetadata.txt
3. Add entry to the metadata file: WDS.Client.Multicast.WIM.Streaming.Enabled=true
4. Save changes and unmount the boot image
e.g.
>dism /unmounts-wim /mountdir:c:\mount /commit
Sorry for the late reply, but I had to test this thoroughly since I didn't get it working right away. I tried both the regedit you first mentioned, and later also creating a textfile in the "/index:2 boot.wim", both without any success. I noticed
that creating the sources\WdsClientMetadata.txt with the data "WDS.Client.Multicast.WIM.Streaming.Enabled=true" gives me an error upon booting into WDS as follows (EUFI/IPv6-boot):
Same happens if I boot using IPv4 (an non-UEFI boot), except that there would be a plain IPv4-address instead in the error msg. Just for troubleshooting I tried writing WDS.Client.Multicast.WIM.Streaming.Enabled=false in the file instead, and WDS would throw
me the exact same error message. Once I delete the file sources\WdsClientMetadata.txt from the WDS/Boot image, the client boots ok, both for IPv4/IPv6. Disabling the firewall on the WDS didn't help, so something in the configuration is still missing? I'm getting
to a dead end here, and I suppose you're all out of advice on this one?
Thank you Shaon Shan for your great effort so far.

ImageX and appending .wim files VERY WEIRD Discovery!

I have a PC with two hard drives. I used ImageX to image each drive to a .wim file independently.
The first image was of the C:\ drive
The second image was of the D:\ drive.
I then used the following command to append the 2nd hard disk WIM file to the first hard disk WIM file.
C:>Program Files\Windows AIK\Tools\PETools>imagex /append /boot C:\1stdrive C:\Users\MyUserName\Documents\zTestFolder\Prec690_HDisk2Install.wim "Win7"
My thinking was that I could then deploy the image as 1 WIM file. But when I get to the familiar 'Install Now' screen, once I click 'Next', I immediately get the following message.
'The product key entered does not match any of the Windows images available for installation. Enter a different product key.'
So, for fun I decide to try something else.
I use my 'Deploy' UFD and only put in the C_Drive install.wim in the proper default location.
I then successfully install the O/S and it boots into Windows no problem!!!
But, HERE is WHERE IT GETS WEIRD
I do the Diskpart portion so disk 1 can now have an image applied to it.
Then, I apply the HardDisk2.wim file and it is successful...ie it doesn't throw any errors. The command I used was imageX /apply F:\HardDisk2.wim 1 D:\
But when I reboot, now the system no longer boots into Windows.
Instead it provides error of: No boot device available!

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$_"}})

Is there a way to keep Deployment Utility from modifying sequence file paths?

While the Deployment Utility appears to be a great tool, it does some things that I'd rather it didn't. One is that it modifies all paths in sequence that it is including from Absolute to Relative. While this is a nice feature for many reasons, it is a show-stopper for our uses. This is because as part of our distribution process, we also use a checksum routine to verify that the sequence files being run by the operators on the Test Stations we deploy to are running the correct (unmodified) version of the test software. By using Absolute paths, we can detect and prevent accidental editing/changing of the sequences or paths that we have deployed, but if we have to use relative paths that is something that we could work with also.
So my questions are: 1. Can this path update 'feature' be disabled? and 2. If not, then will pre-setting all paths in a sequence cause the deployment utility to only copy the file and not update it (thus changing it's checksum)?
I'm going to test the latter when I have time, and if there are any other suggestions that might be useful, I'm love to hear them.
Thanks,
-Jack

Rick,
In my experimentation to see if using relative paths, I was able to prove that a sequence that uses them will not be updated - with one caveat; if the path that is referenced by the sequence is not itself in a sub-directory, i.e.; it's in a different branch of the relative directory structure with respect to the Target (such as the TestStand directory), then the sequence file is always updated and re-saved. An example is that we have a sequence in the Tools directory that calls a DLL in the FrontEnd directory of the Components\User path. This re-saving causes a checksum change and screws up our verification mechanism.
It is unfortunate that I cannot prevent the deployment utility from modifying sequence files - Since we control the entire Test environment, including the location that software gets installed to - Test Station custodians can't go installing the software in a different location, or worse, multiple locations, so we don't have the issue to worry about.
Because of this 'better' method, we now have to re-evaluate how to control the installed version of the software, or use a different installer, such as CVI, which while it has been working for us, has it 's own issues that we're trying to get away from. I'm glad that I am finding out about this now before I've locked down the sequences so that I can probably move the features in the Tools to the Frontend Callback sequence.
It's almost always the case thought that one persons forced enhancement is another's 'feature' or worse 'bug'.
Thanks for confirming the behavior on the Deployment utility for me.
-Jack

How do I open .wim files on my macbook pro?

When my hard drive crashed for the second time on my HP computer, I knew it was time for a change. The HP help menue gave me the option to backup everything onto an external hard drive. I did this and now when I try to open the files inside, they are all "#.wim" files. The #s go from 0.wim-53.wim. How do I open these files? Some might be microsoft word or powerpoint files but I have not got Microsoft word for mac yet. I understand that this will probably prevent me from opening some of the files but wouldnt I be able to open the others? If you know anything about ".wim" files, please help me.

https://en.wikipedia.org/wiki/Windows_Imaging_Format
http://www.eigenlogik.com/entropy/

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.

Deploying bpm 11g project sar file using ant task

I am trying to deploy the bpm project using ant task file. The status I get is [deployComposite] ---->Deploying composite success. However when I check the deployments, they are not there. If I try to deploy this using Jdeveloper it works correctly. I need to get this to work for production deployments. Any suggestions?
C:\Oracle\Middleware\Oracle_SOA1\bin>ant -f ant-sca-deploy.xml -DserverURL=http:
//10.140.183.71:7001 -DsarLocation=N:\RuleBasedProjectInitiate\deploy\RequestPro
ject.ear -Doverwrite=true -Duser=weblogic
Buildfile: C:\Oracle\Middleware\Oracle_SOA1\bin\ant-sca-deploy.xml
[echo] oracle.home = C:\Oracle\Middleware\Oracle_SOA1\bin/..
deploy:
[input] skipping input as property serverURL has already been set.
[input] skipping input as property sarLocation has already been set.
[deployComposite] created temp dir =C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cli
ent_1279894885343
[deployComposite] Creating HTTP connection to host:10.140.183.71, port:7001
[deployComposite] Enter username and password for realm 'default' on host 10.140
.183.71:7001
[deployComposite] Authentication Scheme: Basic
[deployComposite] Username:
weblogic
[deployComposite] Password:
[deployComposite] Received HTTP response from the server, response code=200
[deployComposite] clean up temp dir: C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cl
ient_1279894885343
[deployComposite] ---->Deploying composite success.
BUILD SUCCESSFUL
Total time: 4 seconds
C:\Oracle\Middleware\Oracle_SOA1\bin>

You can always deploy the ADF web apps from the Application (top menu) deploy option. Just make sure you're deploying the EAR profile for the project. Deploying the web projects from the composite deployment wizard can be convenient. But I think it's often the case that you deploy them (the composite and forms) separately (e.g. you make a series of changes to the composite without needed to redeploy the UI projects).
Bottom line is you don't have to delete the projects to be able to modify/deploy them.

Multiple Menu Deploy OS in USB .WIM Files

Similar Messages

Maybe you are looking for