WDS - Tips for beginners

[Oakie]

After a bit of fiddling, I've sorted out a method to deploy XP in my computer lab using WDS in Native mode.

The main steps are:
[hr]

1) Configure WDS server to capture and deploy images.
2) Configure client to boot from network card and sysprepping XP for automatic installation.
3) Capturing sysprepped XP image from client to WDS server.
4) Deploying sysprepped XP image from WDs server to client.

Here's a look at step one:
[hr]

1. Configure WDS server to capture and deploy images.
Install WDS on your Windows 2003 Server. On Windows Server 2003 SP2, go to Start > Control Panel > Add or Remove Programs > Add / Remove Windows Components > Windows Deployment Services. If you are using Server 2003 SP1, you have to install RIS first, then upgrade to WDS using the Windows AIK.

Download the Windows Automated Installation Kit (AIK). Windows (AIK).
Burn the Windows AIK image file to a DVD with IMGBURN (free)
or mount the Windows AIK .img file to a Virtual CD/DVD Drive.

On the desktop create a folder called WDS temp to store the following 3 files:
Right click on the Windows AIK disc and find the WinPE.Cab file and extract the F1_WINPE.WIM and F3_WINPE.WIM bootable files. We need these in order to capture an image from our base machine. Put those in the WDs temp folder.

Next, insert the Windows Vista DVD and copy the boot.WIM file located in the “sources’ folder. Paste that file in the WDS temp folder.

Start and Configure WDS

1. On the Start menu, click Administrative Tools, and then click Windows Deployment Services.
2. In the left pane of the Windows Deployment Services MMC snap-in, expand the server list.
3. Click the server that you want to manage.
4. If the server is not in the servers list, right-click the Servers node to add a server.
5. In the Add Server(s) dialog box, click Another computer, and then browse to select the computer to manage.
6. In the Add Server Warning dialog box, click Yes to add the server.
7. Right-click the server that you want to manage, and click Configure Server to start the Windows Deployment Services Configuration Wizard.
8. At the Welcome page, click Next.
9. At the Remote Installation Folder Location page, click Next to accept the default location (C:\RemoteInstall).
10. If the Microsoft DHCP service is on the server that is being configured as a Windows Deployment Services server, set DHCP Option 60 to PXEClient and set Windows Deployment Services to Do not listen on Port 67.
11. On the PXE Server Initial Settings page, click Respond to all (known and unknown) client computers.
12. Click Finish to complete the configuration.
13. Clear the Add images to Windows Deployment Services now check box, then click Finish.

Add the Boot Images F1_WINPE.WIM and F3_WINPE.WIM to WDS

In the WDS control panel, right click the “Boot Images” folder and select “Add Boot Image”.



Browse to the WDS temp folder on the desktop where you saved the F1_WINPE.WIM and F3_WINPE.WIM files.

Add both images, the restart WDS and 2 new boot images will appear in the “Boot Images” folder. We will use the “Windows Vista PE (X86)” image.



Create a Capture Boot Image for your XP machinesRight click the “Windows Vista PE (X86)” image and select “Create Capture Boot Image”. We will use this boot image to capture (transfer) the sysprepped XP image from the client to the WDS server.



Name the capture image “XP Capture Boot Image” and save it to C:\RemoteInstall\CaptureBootImages (you’ll need to create the capturebootimages folder) and click Next.



Import the XP Capture Boot Image into the WDS “Boot Images” folder.



Browse to the CaptureBootImages folder and choose the “XP Capture Boot Image.WIM file you created previously. Click Next to add the image. When the image is added you will see it in the “boot images” folder.



Import the boot.wim image into the WDS “Boot Images” folder. This image file is used for the DEPLOYMENT of images to client computers.

In the WDS control panel, right click the “Boot Images” folder and select “Add Boot Image”. Browse to the WDS temp folder on the desktop and select the boot.wim image file. Click Next and name the file “XP Deployment Boot Image”. Click Next to add the image to the Boot Images folder.


When the image is added you will see it in the “boot images” folder.




Create an Image Group in the Install Images folder.

Image Groups organize images into similar types. You must have at least one image group to upload images. In this example there are three groups, Administrative desktops, Computer lab desktops and Servers. Right Click on the Install Images folder and “Add Image group”.




[hr]
We are finished preparing the WDS server.

You can see the rest of the steps to the tutorial on my website. I added the tutorial to help others get started with WDS and as guide to help myself remember how to do it since I only tend to image the lab once or at most twice a year.
For the bandwidth challenged, note that there are several more screen caps.
http://www.oakdome.com/lab/?page_id=78

[Chufty]

Hidden files/folders are no longer hidden after installing Windows XP with WDS. It's really annoying and I can't find any evidence of the error anywhere. Does anyone know why?

Thanks

[Andi]

THANKS VERY MUCH OAKIE!

That's by far the most comprehensive guide I've found so far, saved my bacon.

[Gatt]

Our Image Partition has ran out of space, so I've added a 250GB drive in, but cannot figure out how to tell WDS to point to the new drive..

Anyone got any ideas?

[Andi]

Everything is going ok with creating the images etc, but after the capture the upload of the image fails.

The error is:
"Uploading image to the WDS server
The system cannot find the file specified."

I've checked the permissions on the reminst share and given everyone full control (for troubleshooting) of that and the NTFS but that hasn't made any difference.

I am running low on space on the drive that the reminst share is on, but not low enough to affect this yet I don't think. I have approx 4GB spare.

I'm getting a BINLSVC error in eventvwr:
"Event Type: Error
Event Source: BINLSVC
Event Category: BINLSVC
Event ID: 522
Date: 12/09/2007
Time: 09:01:52
User: N/A
Computer: THEODEN
Description:
An error occurred in the Active Directory Connection Manager while querying a Global Catalog server. Verify that a Global Catalog server is available on the network.

Error Information: 0x2AF9"

Could this have anything to do with it?

[Geoff]

Run DCDiag on the Domain Controller that's running as the Global Catalog to figure out why it's broken (Also check the event logs).

[Andi]

Oooh, I have both my DCs set to be a global catalogue server. Is that a bad thing?

[Geoff]

It's a little excessive.

[Andi]

OK, I've removed the global catalogue tick from the second DC just leaving it on the one that has WDS. Trying again....

[Andi]

Nope, still the same problem. DCDIAG passed everything.

[Andi]

OK. I have tried a new way. Instead of uploading the image using winpe I left out the upload tick and copied the file to the images folder of the reminst share and added the image to the install images of WDS. This all appears to run correctly.

However, now I boot to WINPE and choose the deployment image. After it takes a while to load files I get:
"Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your windows installation disc and restart your computer.
2. Choose your language settings and then click "next"
3. Click "repair your computer."

If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

File: \windows\system32\boot\winload.exe
Status: 0xc000000f
info: The selected entry could not be loaded because the application is missing or corrupt."


This is doing my heaad in, RIS was so simple in comparison with this!!!!

[Andi]

Righty-dokey!

Sorted the upload problem by attaching the station to a GB link. That now works a treat.

Sorted the deploy problem by using the boot.wim file from a Vista DVD rather than the vista Beta DVD which is what I had before.

Now I need help with the automation. I've build a basic XP image for now with no extra drivers or programs. Created a sysprep.inf file and resealed the station.

Firstly I just tried deploying the image as it is, but the station did not join the domain etc.
Then I put the sysprep.inf file I created into the images folder using the $oem$ structure that microsoft recommended. This also did not join the domain.

Has anyone achieved this successfully? If so, what method did you use?

[Uraken]

maniac
you never told us how you eventually managed to add nic drivers to wds image can you share? please

[maniac]

Sorry I didn't think to, should have really to increase the knowledge base.

I'll have to get my WDS notes out on Monday and refresh my memory, but it wasn't too hard once I'd figured out the correct way of doing things!

I'll post a follow up on monday.

Mike.

[Uraken]

brilliant thanks.its a bit of a stumbling block for me at the moment.