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.

Create WIM image of Windows XP for system. Install Windows XP SP3 (Do not join. Temp Windows XP Image.wim is the path and file name you want to save the. This will install a file called. Will be used to mount the WIM image. Earlier downloaded updates for your WIM file. So, if your WIM file is Windows 7.

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. 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. 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. 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. 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. 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.

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. 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?

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.

Windows 7: Deploying Windows 7 Using deployment images is the best way to roll out Windows 7, whether to dozens or thousands of desktops. Posey The process for deploying Windows 7 should be relatively similar, whether you work in a small office with just a few employees or a large enterprise with hundreds or thousands of desktops. You’ll most likely base your new Windows 7 deployments of any scale on deployment images. This is the most efficient way, but it does require some work in advance. You’ll need to create an initial deployment image you can use to set up Windows on your corporate desktops. Although there’s a bit of work involved in creating a deployment image, doing so saves work in the long run because you don’t have to worry about configuring each system individually.

Using images for deploying Windows 7 also ensures that each system is set up in a uniform manner. There are many different techniques for creating and managing Windows deployment images.

The Windows Automated Installation Kit (AIK), which you can download, is one of the more straightforward techniques. You’ll also need a Windows 7 installation DVD. While it’s impossible to address every configuration option here, we’ll examine the techniques for building and capturing an initial deployment image.

Create an Initial Image The first step in creating a customized Windows 7 deployment image is to create a base image. From this image, you can tailor it to suit your organization’s needs. Begin the process by installing the Windows AIK and launching the Windows System Image Manager (which is located on the Start menu under All Programs Microsoft Windows AIK Windows System Image Manager). Next, insert your Windows 7 installation DVD into the system. Right-click on “Select a Windows Image,” or “Catalog File” within the Windows System Image Manager and choose the “Select Windows Image” command from the shortcut menu. The system will prompt you to select a Windows Image. Use the browse window to navigate to the Windows 7 installation DVD Sources folder and select the INSTALL.WIM file.

Depending on where you got your Windows 7 installation DVD, you might see a prompt asking you which version of Windows you want to manage. Select the appropriate version and click OK. Create an Answer File The next step in the deployment project is to create an answer file. You’ll use this for unattended installations. Start by creating an empty XML file, and then populate that answer file with the required information. Create the empty answer file by choosing the “New Answer File” command from the Windows System Image Manager File menu.

Next, choose the “Safe Answer File” command from the file menu. Windows will try to place the answer file onto your installation DVD. Because that’s not really an option, you should create a separate directory and store the answer file there. Create a folder named Answer and call the answer file UNATTENDED.XML.

When you do, the Windows System Image Manager should display both the Windows image and the answer file (see Figure 1). Figure 1 The console should display the image and the answer file. You’ll notice in Figure 1 that the Answer File portion of the console displays a Components container.

This stores seven different sub-containers. When you build a Windows deployment image, the Windows System Image Manager has to add the Windows components to the image in a specific sequence.

The seven Components containers correspond to the seven stages of the sequencing process. You’ll also notice the Windows Image section includes a container called Components. If you expand this container, you’ll see a list of the various Windows components. Add the Windows components you want to use to the appropriate sequencing containers within the Answer File section.

You can do this by right-clicking on a component and choosing the Add Settings to Pass command from the shortcut menu. This process can be a bit tricky, but Windows helps you in that each component is only valid for use within certain containers. The console only lets you place a component within a valid container (see Figure 2). Figure 2 Add the Windows components to the appropriate containers. Every organization’s needs are different in terms of which components you’ll need to add. Even different environments within the same organization may have different needs. As you begin to add components, the console will take shape (see Figure 3).

As you select a component, the console displays the properties and the settings for that component. Any settings you configure during this stage of the process will be added to your answer file. When you’re done, be sure to save your answer file before closing the console. Figure 3 Many components include configurable settings. Building a Windows PE Boot Disk You’ll eventually use the answer file you’ve just created to prepare a Sysprep Windows image. The problem with doing that, however, is that once you Sysprep a PC, you’ll need a way to copy the image off the PC from outside the main OS. The easiest way to do this is to build a Windows PE boot disk.

To create a Windows PE boot disk, open an elevated Command Prompt window and enter the following commands. IMAGEX.EXE /UNMOUNT /COMMIT C: WINPE MOUNT CD WINPE COPY WINPE.WIM C: WINPE ISO SOURCES BOOT.WIM /Y OSCDIMG –N –H –BC: WINPE ETFSBOOT.COM C: WINPE ISO C: WINPE WINPE.ISO These commands will write a file called WINPE.ISO to the C: WINPE folder. Burn this file to a DVD. This is your Windows PE boot disk. Creating the SYSPREP Image Now that you’ve created both an answer file and a Windows PE boot disk, it’s time to create the actual deployment image. Install Windows 7 onto a spare PC.

When you get to the point during installation when you’re asked to provide your name and a name for the computer, press Crtl+Shift+F3 instead of entering the requested information. This will force Windows to reboot into audit mode. When the system boots, you’ll see a Sysprep dialog box (see Figure 4).

Close the dialog box and begin making any required configuration changes to the system. You can also install any applications and drivers you want. It’s OK if any of the applications you’re installing require a reboot, because the system will boot back into audit mode. Figure 4 Ignore the Sysprep dialog box upon reboot.

When you’ve finished configuring this PC, it’s time to bring in the answer file that you created earlier. Copy the answer file to the C: Windows System32 sysprep folder.

Keep in mind that the answer file you created probably contains sensitive information. You don’t want this information copied to other desktops set up with this deployment image you’re creating, so you need to create a script to get rid of the answer file when it’s no longer needed (don’t forget to make a copy of the answer file for yourself first). To do this, create a folder named C: Windows Setup Scripts. Загрузить Трудовой Договор На Администратора Автомойки.

Create a text file within that folder named SetupComplete.cmd. Add two commands to this file.

Delete /Q /F C: Windows system32 sysprep unattended.xml Delete /Q /F C: Windows panther unattended.xml When you’re done configuring the system and creating the script to get rid of the answer file, you’re ready to run Sysprep. Open an elevated Command Prompt window and enter the following command: SYSPREP /GENERALIZE /OOBE /SHUTDOWN /UNATTEND:UNATTEND.XML When you run this command, Sysprep will generalize the system to deploy your configuration to other systems.

When it finishes, the system will shut down. Don’t turn the computer back on until you read the next section. Capture the Image Now that you’ve Sysprepped the system, you must capture the computer’s current state. Because booting the computer into Windows will ruin the generalization you’ve just performed, you need to boot the system using the Windows PE boot disk you created earlier.

When the system boots into the Windows PE environment, run the following commands. C: MD Images CD windows system32 Imagex /capture h: c: images captured.wim “Windows 7 x64” This process will create a file named C: images captured.wim. You can use this file to install Windows. Simply copy it to the machine from which you will run your Windows deployments. Now that you’ve created your image, you may need to add drivers, add or remove Windows features, or perform any other management tasks. You can do this with a tool included in the Windows AIK called the Deployment Imaging Service and Management Tool. Access this tool by opening an elevated Command Prompt window and navigating to the C: Program Files Windows AIK Tools AMD64 Servicing folder.

Mounting a WIM Before you can make any modifications to your deployment image, you’ll need to copy it to the PC upon which you installed the Windows AIK. For the purpose of this article, assume that the.wim file is located in a folder named C: Images. Before using the.wim image, you’ll have to mount it.

Enter the following command at an elevated Command Prompt: DISM /Mount-Wim /WimFile: /index:1 /MountDir:C: demo Figure 5 shows an example of a Windows image file. Figure 5 You can use DISM to mount.wim or.vhd files. List the Packages and Features Once you’ve mounted the Windows image file, there are several things that you can do. You might want to see which packages it’s installing as part of the image. You can do so with the following command (see Figure 6): DISM /image:C: demo /Get-Packages Figure 6 Use the DISM command to view the packages included in an installation image.

You could also use the DISM command to view the device drivers or the Windows features included within the package. To do so, you would use these two commands.