Skip to main content

Creating a Capture image with WDS

The Capture image in Windows Deployment Service allows you to capture an image without having to create a WindowsPE boot disk.  This process will automatically transfer the captured image to the image storage location that you created when you set up WDS.

First you need to have the WDS server setup correctly. Once you have installed your images from an installation DVD, click Boot Images.

Right click the boot image and click Create Capture Image.

image

Enter the Image name and a description for it.

Click Browse.

You now need to go to the Sources folder on your installation media and find the file called boot.wim.

image

Click Next

Once the image loads, check Add image to the Windows Deployment Server now and click Next.

Click Next three times.

Click Finish


Next you need to boot your client to LAN.  You may have to reconfigure your BIOS settings or press a function key to get to your boot menu.

Take note that depending on your configuration, you may have a couple of steps to perform. 
You may need to set the PXE boot policy.  To do this, open Windows Deployment Services

Right click your server name and then click Properties.

image

Click the Boot tab.

Depending on whether or not you pre-staged the client, you will have two options.  The first one for Known clients is for pre-staged clients.  The second set of options for Unknown clients controls clients that you have not pre-staged.  In the example below, I want my non pre-staged client to go ahead with a PXE boot.

image


If you client hangs, such as below, you must provide for administrator approval.

2010-12-30_16-47-27_363

To set this policy, go to your server properties again, but this time click the PXE Response tab.
The default setting of requiring Administrator approval for unknown clients is recommended.  This prevents rouge clients for obtaining a copy of your images.

image

To allow this process to continue, we need to approve the PXE boot of this client.  Click Cancel to close the WDS server properties.

Click Pending Devices.

image

The above image shows a client that is waiting for the administrator to approve its loading the organization PXE environment,

Right click the client in click Approve.

image

Click OK

The PXE environment will start to load in a few seconds.

2010-12-30_16-59-42_923

Once the GUI loads, select you language and click Next

You will now need to enter an account that is authorized to allow images to be deployed.  It is in the format of domain\user. Enter the credentials and click OK.

At the Welcome to the Windows Deployment Services Image Capture Wizard click Next.

2010-12-30_17-25-45_991

On the Directory to Capture Window, you will be able to choose the volume that you ran SYSPREP on.

Select the volume.  (Note: the volume label may have changed)

Provide both a descriptive name and description.  Click Next

2010-12-30_17-33-47_132

On the New Image Location, you can choose to store the image locally, or transfer it to a WDS server.
Browse to a location where you want to store this image locally and give it a name.  I had to right click in Windows Explorer and create a text file.  This is the one that I selected.  A little odd and I have not found a suitable explanation for this, but it worked.

In this scenario, we are uploading to a WDS server.

Check Upload image to a Windows Deployment Services Server (Optional)

In the Server Name: field, type the name of the server and click Connect

You will be prompted for administrative credentials.

In the Image Group Name: drop down box, select the image group that you want to store this image in.  The Image group is created in WDS.

Click Next.

The image will be captured. Do not be alarmed if it takes a few minutes before the progress bar starts moving.

The client will reboot once the capture is completed.  If all went well, you should now have this image listed in WDS under Images.

Comments

Fara7 said…
i have a question ..
what if the boot Image was x-86 ?
can i create a capture image using it and Capture 64 bit windows using it?
Fara7, I am sorry to say that you will have to try this out or hopefully someone else has and is willing to comment. If you have a bare metal 64 bit machine, go ahead and remove the 64 bit Boot Image from WDS. Attempt to do an install from there. If it does not work, no harm done. Just reload the 64 bit boot image and let us know how it went. Since the 64 boot image is provided from the Windows 7 DVD, you might as well just use it. is there a specific reason for this PXE environment?

Jason

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.