Welcome to Sign in | Join | Help
in
Home Blog Forums

The Lazy Admin

Capturing a custom Image using ImageX and a Generic WinPE Disk

Sponsor


I have had a lot of people ask me about capturing a custom image manually using ImageX. First before I go into details on how to do this let me just point out a few things first.

1) You can use the process we went through previously to recapture a custom iteratively. Meaning you can slowly build up your image as you like using the custom tasks in the builds node to perform customer installs of customizations.

2) If you choose to manually customize an image make sure that you run sysprep, or use a utility like newsid to generalize the install before joining it to a domain or network. Note: Microsoft PSS does not support using New Sid so really you should use Sysprep to generalize your image.

Note: Generalizing an image means removing data about the Windows install that makes it unique. Usually this means removing the SID, and the name of the computer. The most important element here is the SID you really don't want to machines with the same SID living in your network

The first thing we need to do before capturing our image is get a generic version of WinPE up and running on our WDS server. (Or burnt to a bootable CD)

  • To do this we first need to create a generic version of WindowsPE.
  • In the BDD workbench open the Deploy node.
  • Click on Deployment points.
  • Double click on the Lab option in the details pane.
  • This will bring up the Lab Properties. Choose the Windows PE tab.
  • Check off the Generate generic flat bootable ISO image, and the Generic bootable RAM disk ISO image.
  • Click OK.

Right click on LAB and click choose Update.

This will build the Generic Windows PE.

Now if you look in the \Distribution\boot folder on your BDD drive you should notice a Generic_x86.wim and .iso has been created. (or X64 if you are deploying to 64bit.)

Open Windows Deployment Services

  • Right Click on Boot Images then click add boot image.
  • Click browse,
  • browse to the Distribution\boot folder.
  • Choose the Generic_x86.wim file.

  • Click open.
  • Click Next
  • Click Next
  • Click Next
  • The Image will be added to the WDS service. When it's done click Finish.

You should now see the Generic Windows PE image in the details pane.

Now go to the PC that has your customized XP image. Boot the PC using the PXE network boot. (Or use your Generic Windows PE boot up cd you burnt from ISO)

Once you have booted up you will now be presented with a boot manager menu. You can choose to boot using the Lite Touch Windows PE or the Generic Windows PE.

Choose Generic Windows PE and hit Enter.

Once the Generic PE image has booted up to the command prompt we need to Map the distribution share on the BDD server:

Net use m: \\<BDD_server>\ditribution$

M: is an arbitrary value. You may use whatever letter works best for you. You will be prompted for valid credentials to log into the server.

Type "m:" to switch the prompt over to the newly mapped drive.

Cange Directories into the Tools\x86 folder. This is where you can find ImageX:

ImageX creates file based images of your hard drive. This is great especially if you want to perform offline servicing. That is updating OS images with drivers and files without rebuilding the entire install image.

To create an image a typical command would be:

Imagex /compress maximum /capture c:\ m:\captures\custom.wim "custom_image_1"

This will create a new wim file called "custom.wim" with an image in the wim file call "custom_image_1" it will also use maximum compression. To see all the options for imageX check out the very useful help file included with the Windows AIK documentation.

To restore the Image use the /apply switch:

imagex /apply m:\captures\custom.wim 1 c:\ /verify

 





Published Tuesday, June 19, 2007 9:21 AM by daniel.nerenberg

Comments

 

klowenst said:

Thanks for the article, this worked great to capture a customized XP image.

Applying the image to first time works fine, but when applying again to the same machine, Sysprep mini-setup encounters a Fatal Error: SamChangePasswordUser returned status: c000006a.

Apparently sysprep can not change the administrator password if it is not already blank. The first load is OK, but once the password is set future loads fail. I'm guessing this is related to the wim image being file based as this issue does not occur with Ghost images.

It works if you format the drive before re-imaging, but manually setting the password to blank before re-imaging makes no difference and the same error occurs.

Has anyone else ran into this? Any suggestions or comments would be appreciated!

October 9, 2007 1:10 PM
 

Ariel said:

How do you sysprep for windows xp. I sysprep a custom pc but dont know how to add this image to my WDS.

Thank You,

March 4, 2008 12:45 AM
 

trod said:

You need to create a capture image first then use it to pull the image to the WDS server.

May 2, 2008 1:41 PM
Anonymous comments are disabled

About daniel.nerenberg

I am an MCT, Consultant based out of Montreal Quebec Canada. As the "new" Lazy Admin on the block I am working to make TheLazyAdmin.com the best website for MS Software tips and tricks out there!

This Blog

Powered By

 

Syndication

Sponsors

  
Get a free 5GB e-mail account @isalazyadmin.com

Certifications & Awards




All postings are provided "AS IS" with no warranties, and confer no rights.
Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.