anyweb

how can I CAPTURE an Image using WDS



18 posts in this topic

This guide assumes you have already setup WDS as described here

 

Part 1 - add boot.wim to WDS

 

 

Step 1. Get your Windows Vista DVD ready.

 

Step 2. Insert the DVD and start WDS (windows deployment services) gui.

 

wds_gui.jpg

 

Step 3. In the Left Pane of WDS, select boot images

 

Step 4. In the Right Pane, right click the mouse and choose 'Add Boot Image'.

 

Step 5. In the Add Image Wizard, click the Browse button and browse to the Sources folder on your Vista DVD that you inserted in Step 2.

 

file_location.jpg

 

Step 6. Highlight the file called boot.wim and click Open, once done Click Next

 

add_boot_wim.JPG

 

Step 7. In the next window, change the Image name from "Microsoft Windows Longhorn Setup (x86)" to 'WDS - Windows XP/Vista Deployment'

 

Step 8. Change the image description to 'WDS to capture/deploy images from windows-noob.com'

 

Step 9. Click next to review the settings, and next again to proceed.

 

wds_capture_deploy.JPG

 

Step 10. After the file copying is complete click on Finish.

 

wds_review.JPG

Share this post


Link to post
Share on other sites


Part 2 - create Capture file

 

Step 1. Highlight the 'WDS - Windows XP/Vista Deployment' image name in the right pane of the WDS gui (this is the image you just created in Part 1 above).

 

Step 2. Right-click on it, and choose Create Capture Boot Image

 

create_capture.JPG

 

Step 3. In the next Windows (capture image metadata) leave the Image Name and Image Descriptions alone, and click on the Browse button.

 

Step 4. Browse to the RemoteInstall\Boot\X86\Images folder (or X64 if using X64), this folder is part of the original WDS setup.

 

Step 5. Give the filename you are about to create a name eg: RemoteInstall\Boot\X86\Images\windows-noob_capture and click open, then click next, the wizard will auto append .WIM to the filename.

 

wds_windows_noob_capture.JPG

 

Step 6. The wizard will now start to extract the image from the source image file.

 

wds_extracting.JPG

 

Once it is complete, click Finish.

 

wds_complete.JPG

 

 

 

 

Part 2a - add Capture file to WDS

 

Step 1. In WDS, select Boot Images in the left pane.

 

Step 2. in the Right Pane (in an empty area) right-click and choose Add Boot Image

 

Step 3. In the add image file window, browse to RemoteInstall\Boot\X86\Images and select the capture file you created above, click open and then next.

 

wds_select_wim.JPG

 

Step 4. set the Image name to 'Windows Vista/XP WDS capture' and the Image description to 'WDS to capture images from windows-noob.com', click next.

 

wds_image_metadata.JPG

 

Step 5. Review the choices and click next to add this capture boot image.

 

wds_review.JPG

 

once done WDS will look like this

 

wds_gui.JPG

Share this post


Link to post
Share on other sites

Part 3 - PXE boot target computer and capture image

 

Step 1. Ensure that PXE boot is enabled in boot sequence, and PXE boot (using your onboard NIC) to the WDS server. Press F12 when prompted for Network Service boot.

 

Step 2. In the Windows Boot Manager Menu, select Windows Vista/XP WDS Capture from the available options.

 

Step 3. After Windows PE has booted, you should see a welcome screen which says

 

Welcome to the Windows Deployment Services Image Capture Wizard.

 

Click next to begin.

 

If you do not see this welcome screen (for example if you see an Install Windows wizard with keyboard layout options) then power off the computer and re-attempt step 1.

 

DSC00036.jpeg

 

Step 4. Image capture source:

 

There are three options here, Volume to capture, Image name, and image description.

 

Note:-If the Volume to Capture drop down menu appears blank (ie: you can't select anything) then verify that you have Sysprepped the image you are trying to capture.

 

In addition, You must sysprep using the generalize switch (Vista ONLY). After sysprepping with the /generalize switch it will show up.

 

For XP, simply regenerate the SID and choose RESEAL.

 

If you need to sysprep the machine then read this guide and return to part 3 when ready.

 

If volume to capture still doesnt show up after sysprepping with the /generalize switch then perhaps WinPE may need storage drivers (SATA). To verify this, once you're in WinPE, press Shift+F10 and see if you can see the hard drive.

 

For Volume to Capture, select C:\ from the drop down menu (will not be present unless you have SYSPREPPED)

For Image Name call it 'Windows Vista Ultimate Capture' (if you are capturing Windows XP, change accordingly)

For Image Description, enter 'WDS - Windows (vista/xp) captured image for windows-noob.com'

 

Step 5. Image Capture Destination:

 

Here you have the possibility of storing the image on a drive (local) by choosing Name and Location, and clicking Browse and giving the image a filename, the wizard will auto-append .wim to the file name eg: c:\test_capture.wim.

 

Next you want to upload the image directly to your WDS server by putting a check mark in the 'Upload Image to WDS server' option, you will have to provide the servername (or use the ip address eg: 192.168.3.1) and then click on the connect button. After some moments you'll be prompted with a username/password prompt for connecting to the server. I entered Administrator as the user and entered the correct password and selected 'remember my password', followed by 'ok'. If you do not get prompted for username/password and it complains about not finding the server then read here.

 

Once you have successfully connected to the server you may get an error which states:-

 

"There is no image group on the WDS server '192.168.3.1'. Please use WDS Management to create an image group."

 

If you do not get this error, skip to Step 6.

To resolve this error simply go back into the WDS management gui, and select 'Install Images' in the left pane. In the right pane that opens, right-click your mouse and choose 'Add Image Group'. Give this group the name 'WDS XP captures' and retry the above step (5). Obviously if you are capturing Windows Vista, change the group name accordingly.

 

wds_add_image_group.JPG

 

Once you've added the image group it will appear in the WDS gui like the below screenshot

 

wds_image_group_added.JPG

 

Step 6. you will now see the 'Image Group Name' option on the Windows Deployment Services Image Capture Wizard allows you to drop down the menu, and from here you can select the captured images group you created above.

 

Step 7. Click Finish to continue (and capture the image). The image capture wizard will start capturing the image and you'll see a 'Percent Complete: x%' dialogue box.

 

Step 8. After a fairly long while of file copying, Click Close to conclude the image capture process, congratulations you've captured an image using WDS !

 

Please note, that at this point Windows PE will exit and the computer will reboot, if you don't want it to boot into sysprep then you'll have to be quick and turn it off at the bios screen.

 

 

 

 

If everything went well as above, the captured image will have been copied to D:\RemoteInstall\Images\captured images (change the drive letter to match your RemoteInstall drive and obviously the last folder name will change if you use a different image group name), in addition it will be stored locally on the computer you captured the image on (c:\test_capture.wim)

 

Here are the contents of my captured images folder:-

 

Directory of D:\RemoteInstall\Images\captured images

 

11/14/2007 04:08 PM <DIR> .

11/14/2007 04:08 PM <DIR> ..

11/14/2007 04:15 PM 2,485,945,229 Res.RWM

11/14/2007 04:15 PM 2,297,798 test_capture.wim

2 File(s) 2,488,243,027 bytes

2 Dir(s) 11,278,798,848 bytes free

 

 

 

 

 

At this point you will probably want to Deploy the captured image, to find out how you can do that read this post.

3 people like this

Share this post


Link to post
Share on other sites

Okay. I have followed every step twice. I am unable to see the either the "boot" or "capture" imageun the PXE menu. Please note that my WDS is also maanging legacy RIS images as well.

 

 

Thanks,

Niles

Share this post


Link to post
Share on other sites

"Step 1. Ensure that PXE boot is enabled in boot sequence, and PXE boot (using your onboard NIC) to the WDS server. Press F12 when prompted for Network Service boot."

 

I can't get a boot menu the error I get is:

PXE-E53: No boot filename received

PXE-M0F: Exiting intel boot agent.

 

I check my OU and removed all firewall policies to take that out of the equation and received the same message.

Any ideas how to solve this?

Share this post


Link to post
Share on other sites

in order to troubleshoot your problem i need more info about what you've done and how your network is setup

etc..

Share this post


Link to post
Share on other sites
in order to troubleshoot your problem i need more info about what you've done and how your network is setup

etc..

All items related to Vista x86 and x64 have been solved! Thanks anyweb

Share this post


Link to post
Share on other sites

so what was the solution then in case others might have a similar problem ?

Share this post


Link to post
Share on other sites
so what was the solution then in case others might have a similar problem ?

The PXE Responce Settings was not set to Respond to all known and unknown client computers. This solved the issue. Now to inject drivers to a captured image to make it universal...

Share this post


Link to post
Share on other sites

A question to anyweb,

We are good with the initial capturing of an image. What we cannot find is a good answer to the best way to update or replace a existing image. We are required to update these regularly because of patches and software updates.

 

What I see them doing now is they capture the new image pretty much as you described and give it a new name. Then they delete the old image from the server via the WDS interface. It works in that they capture their new image, but it seems to grow the RWM each time (unnecessarily in my mind). I believe they think deleting it will reduce its size, but what appears to happen is it get larger. I am trying to replicate all images across sites, but found DFSr does not replicate delta changes only on RWMs, it replicates the whole file each time. So this method has grown an RWM to 30GB at one point! I have read in replacing images in the console, but it seems to require capturing, exporting and replacing which does not seem the best way to do it.

 

I am convinced we are not using WDS correctly or efficiently and I think re-capturing/updating is the biggest issue. Do you have the information or could you point me to a good source on the topic of updating existing images? If you know of ways to modify the images on the server ala driver injection etc please let me know as well. I have done it with a boot.wim, but not sure if the same applies to standard images.

 

Details

2 WDS on Server 2008 64 bit in two separate locations.

Capturing Windows XP images that we sysprep and use an internal unattend to configure.

Replicating the Remoteinstall folder, excluding the boot, tmp and mgmt folders per MS recommendation.

 

Any help would be greatly appreciated! Thanks.

Share this post


Link to post
Share on other sites

have you familiarised yourself with this section in Technet yet ? it does go into some detail about DFS for WDS

 

you can easily update content within offline images using imagex, the following post will give you some clues about how to inject drivers into an image

 

The switch you need to make your images smaller is called /append

 

you can get a full list of imagex command line switches here on Technet

 

i hope this helps

 

cheers

anyweb

Share this post


Link to post
Share on other sites

Hello all,

I'm new to this site, but found your posts on this topic very useful. However, all works well for me in WDS up until I get to the point of capturing my target PC image. After selecting the option to upload my image directly to the WDS server and connecting successfully, my FINISH button is greyed out. I can only get the button to work if I select a local disk to copy my image to as well as the upload. I enabled both options and WDS says the process completed successfully, but I do not see the image on my WDS server with the Install Image Group that I originally selected. Any ideas?

ck

Share this post


Link to post
Share on other sites

what user did you do that as and did you try a Refresh in the WDS gui ?

Share this post


Link to post
Share on other sites

I connected as a local administrator to the WDS server.

 

Per your question, I closed the WDS console and re-opened. The image was there...sometimes we as techs forget to try the simplest of things... :blink:

 

However, I'm still not understanding why the FINISH button only activates when selecting a local disk to copy the image to. Is selecting the copy to disk option the only way to get this to work with uploading the image to the WDS server?

Share this post


Link to post
Share on other sites

yes i believe that it has to create the image first locally, then it uploads that wim file to the server,

 

at least in my experience it has

 

cheers

anyweb

Share this post


Link to post
Share on other sites
yes i believe that it has to create the image first locally, then it uploads that wim file to the server,

 

at least in my experience it has

 

cheers

anyweb

 

Hi I have used WDS before, more familiar with RIS however, I am running into some problem trying to use the WSIM when I try to select an image it tells me that the location does not contain a valid windows image, which is strange as it is the site image that we use to deploy vista business... any ideas??

I have managed to deploy and capture an image before when I worked for another company?

Share this post


Link to post
Share on other sites

hi there,

 

are you having a WSIM problem ? if so please post it in the Windows SIM section,

 

or if you have a WDS problem post it in this section in a new topic,

 

i'm closing this topic now

 

cheers

anyweb

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.