[engert100]

I have another topic here: http://www.msfn.org/board/Windows-Deployme...es-t120835.html but i think no one visits that category.

I now have a unattended dvd of Windows Xp. How do i covert this into a .wim file for Windows Deployment.

Can someone point me into the right direction?

Thanks.

This post has been edited by engert100: 24 July 2008 - 06:22 AM

[Altruist]

Is this what you're looking for?
http://technet.micro...s/aa905070.aspx

[engert100]

Yes, that is helpful but i can't convert my c:\xpcd directory structure to a .wim file using imagex /capture command.
What would you suggesst i try next? Or if you could give me a hand with some of the imagex commands.
Does this actually work though? Using imagex to convert a dir structure to a .wim file?

[IcemanND]

What exactly are you trying to do?

WIM is not an installation method, it is an imaging technology. So if you were to create a WIM containing your UA and deploy it to a system all the system would have on it is an exact copy of your UA.

[engert100]

I think i've figured it out but i've got to test it.

Here's the scenario.
I have a customized copy of Windows XP sitting in C:\xpcd .
This copy has all the updates and some applications.
I can convert this to .iso and boot a pc, and it will work fine.

What i wanted to do is convert this Directory into a .wim format so i can deploy it with WDS.

By using this command from the WAIK tool: imagex /capture c:\xpcd c:\xpsp3.wim "Windows XP" it has converted the dir structure to a .wim file.
Now, i just have to upload this file into my WDS and see if it actually works.
Will keep you updated.

[engert100]

No dice.

When i try to add this .wim image to WDS i get: This file does not contain a valid install image.

What does it mean by valid? Are there any special switches in WAIK to make this a 'valid' image?

[Innocent Devil]

u might need to provide /NOPREFIX switch to imagex

This post has been edited by Innocent Devil: 25 July 2008 - 12:21 PM

[engert100]

I tried it and it didn't work.
This is driving me insane for the past week.
Are there any WinPe experts here?

What's a valid .wim image? Are there any special files or directories that .wim is looking for?
If there are, i can manually create these files or folders into my c:\xpcd folder and capture it again.
If my supervisor approves it, then i'll call microsoft for $150 an hour.
Don't know if that's going to happen though.

[Innocent Devil]

usually the wim technology needs a system directory in th root of drive in order to consider it as a system image (AFAIK) like C:\windows etc.

or u need another switch /BOOT ?? dunno

or try following IcemanND's XP WIM deployment guide

only syspreped images are used for deploying through wim technology.
doing from the install DVD/CD require winPE to copy the files and start install wia WDS
in RIS i dunno the procedure how to do that.

by converting a install source dir to wim might not going to help or work with wim

[engert100]

I've tried all the switches of /capture command even tried /flag which is not listed in help /?

There is another way around this (theoreticaly) which i'm going to test this week.

Here it goes.

1. Capture the directory with imagex and create a .wim file
2. Store this file somewhere in the network
3. Create a WinPe cd/dvd/flash drive
4. Boot PC with this cd/dvd/flash drive and automate the mapping of the network drive with a script, automate disk partitioning with the DISKPART command.
5. The script will create two partitions both active. Formats them both in NTFS. One is named INSTALL the other one WINDOWS
6. The script then unmounts the .wim file and lays it down in the INSTALL partiton, then the script reboots machine
7. When PC starts it will start installing Windows from the INSTALL partiotion just like if you were to install it from the CD/DVD

And all this work because i want an HAL independed Windows Xp image.
PHEW!

Like i said, this is all theoretical don't know if it'll actually work.
First i got to check that after copying windows files into a NTFS volume will setup.exe work or will i386/winnt32.exe work?
I'm getting tired with this.

[gotenks98]

This isnt going to work because are not understaning how wim works. Wim is not an install method. Basically during an vista install it extracts the wim to the harddrive. It is just a faster complete vista install. In a sense a wim is a zip file. You simply cant do this with a naked xp discs. Now if you were to install xp, sysprep it and then capture the image you might have something you can distribute easily. As for it being hal independent I dont see the point in that unless you got some real old stuff that shouldnt be running xp anyways.

[Tripredacus]

Actually, there IS a way to create a WIM of the XP install, but its tricky. This is just a crazy idea I just had, and I have no clue if this will work but you can try it out.

OK so we know that when you install XP, it goes into the blue setup screen, wants you to press buttons like R and L and F8 and stuff. Then it shoots that red bar across the screen to reboot.

What happens here is that the XP CD copies the install structure of the CD onto the Hard Disk. When the computer reboots, it runs the install from the Hard Disk and not the CD. It may be possible to capture Drive C between the reboot prompt and the start of installation.

However, I do not know if the installer makes any reference to the CD during install, but it may be possible to create a RAMDRIVE with applicable files to fool the installer if this is at all possible.

[daniel1908]

I have an idea that may work.
If you are running Server 2003 SP1, you will have the option to install RIS. During the RIS installation you will be asked for the media with the Operating System Setup Files. Insert your XP CD and allow RIS to copy the Files.
Now upgrade your Server 2003 to SP2 and Install WDS. After Installing WDS, run it and it should find all RIS OS Installation files. These would be located in the Legacy Images Folder in WDS. If you right click the XP setup file in the Legacy Images folder, there should be an option to Convert to WIM. Use this to convert the XP image to WIM. Now you should have a hardware independent XP image. You can now copy the XP Wim image to keep as a backup copy.

This is just an idea I had. I am yet to test it. If it works can someone please post here?

[Matt A. Tobin]

BUMP

Easy WinXP CD Install to WIM Conversion

This basically encapsulates the standard windows xp install method inside a wim file.

Because it will install completely from the hard drive the installation time is decreased significantly.

Step 1
- Boot to WinPE 2 or higher

Step 2
- Setup a regular drive or partition using diskpart

Step 3
- Use Standard Windows XP CD
- Run winnt32.exe /syspart:c: /makelocalsource
(where c is the letter of the drive)
- enter product key etc

Step 4
- use imagex to capture the drive

Step 5 - DEPLOYMENT
- boot to WinPE 2 or higher
- set up partition or drive using diskpart (be sure to assign a drive letter and make it active.. etc)
- bootsect /nt52 /force /mbr
- imagex /apply xpinst.wim 1 c:

Step 6
- reboot and run though text mode and gui setup as normal

Brought to you by Binary Outcast
- http://binaryoutcast.com/

[Kelsenellenelvian]

One MAJOR drawback!!

XP images are proccesor dependant...

[wimb]

You can Restore a Universal XP Image file in 5 minutes.

But to create such file takes more time .....

http://www.911cd.net...showtopic=23553
http://reboot.pro/13...post__p__120249

This post has been edited by wimb: 26 January 2011 - 04:26 AM

[Tripredacus]

Kelsenellenelvian, on 25 January 2011 - 08:37 PM, said:

One MAJOR drawback!!

XP images are proccesor dependant...

Any XP SP2 or SP3 images created on a single core (UP HAL) and sysprepped will automatically redetect a system using a multi-proc (MP HAL). SP1 and older could not do this. Also it doesn't work backwards, so an image created on an MP will not install the UP HAL if deployed. Best way to handle this is to totally lock down your configs so you use your images appropriately.

[LieboOSBA]

Matt A. Tobin, on 25 January 2011 - 03:59 PM, said:

BUMP

Easy WinXP CD Install to WIM Conversion

This basically encapsulates the standard windows xp install method inside a wim file.

Because it will install completely from the hard drive the installation time is decreased significantly.

Step 1
- Boot to WinPE 2 or higher

Step 2
- Setup a regular drive or partition using diskpart

Step 3
- Use Standard Windows XP CD
- Run winnt32.exe /syspart:c: /makelocalsource
(where c is the letter of the drive)
- enter product key etc

Step 4
- use imagex to capture the drive

Step 5 - DEPLOYMENT
- boot to WinPE 2 or higher
- set up partition or drive using diskpart (be sure to assign a drive letter and make it active.. etc)
- bootsect /nt52 /force /mbr
- imagex /apply xpinst.wim 1 c:

Step 6
- reboot and run though text mode and gui setup as normal

Brought to you by Binary Outcast
- http://binaryoutcast.com/

Having trouble following this guide, anyone else used it?

[jaclaz]

LieboOSBA, on 20 December 2011 - 06:06 AM, said:

Having trouble following this guide, anyone else used it?

No.
http://homepages.tes...no-answers.html

How would knowing if anyone else used it help you in following it?

However, basically that post is about a way to deploy a XP initiated-from-hard-disk install.

The imagex and wim usage are just means to replace *any* disk/drive imaging software.

Just as an example, you could use DRIVEIMAGEXML to the same effect. (and you would note need a PE 2 or higher).

jaclaz

[LieboOSBA]

Thanks for replying.

If anyone else has tried to use it (responding with a "yes"), they could have reported as to the success of following the instructions.

The issue with following the instructions is that the WIM is captured what I believe to be successfully, the hard drive doesn't boot and you get "Disc read error, press control + alt + delete to restart" or something to that affect. I believe the problem is the formatting/partitioning/MBR creation part of the process that isn't working.

The ultimate goal would be to have a WIM image that can be deployed via WDS of the setup files for Windows XP (the hard drive install as you put) with an unattended script including drivers and post-SP3 hotfixes slipstreamed. This is because as we all know, Windows XP images are HAL dependant and having a few different types of PC, making separate "sysprepped" images and maintaining them is unfeasible.

I know Windows FLP is basically XP with "WIM" deployment (using a version of WIM from a Longhorn build IIRC) so it must be possible to deploy HAL "independent" Windows XP via the method I quoted or similar.