[wds] Tips for beginners

[maniac]

More info on this problem. Worked out how to add network drivers, but still got the same error, never managed to solve it, so moved on to the next machine type.

 

Had the same problem with another type of IBM machine today, but one machine of the same type did work ok, very puzzling considering they should be identical machines. Anyway, started looking at this machine to find the differences between it and the others. Same network card, motherboard etc. Same BIOS versions, but I updated the BIOS anyway, no difference.

 

I Then noticed purely by chance the machine that worked has 512mb RAM, where as all the rest have 256mb. Added 256mb ram from another machine into one, and it worked!

 

So if you get a communications error while trying to image machines, check the amount of RAM in the machine. This problem only seems to affect IBM machines in my school (8098-72g is one of them)

 

Cheers,

 

Mike.

[ChrisH]

The problem will be realted to the Win PE needing 256 meg and im guessing you have shared graphics which will take you below the minimum.

[maniac]

I didn't realise it needed 256mb minimum! Strange thou, as we have a lot of fujitsu machines with only 256mb ram and shared graphics memory, and they all cope OK.

 

Why can't it just give me an error that tells me it's the memory that's the problem thou! Damned microsoft!

 

Mike.

[ChrisH]

That is the case with PE normally. I am assuming it si the case here although it may not be.

[PiqueABoo]

we have a lot of fujitsu machines with only 256mb ram and shared graphics memory

 

Perhaps they're set to share less memory. I've encountered 256MB boxes with the BIOS configured to use 64MB for graphics.

[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:

---

 

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:

---

 

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

 

http://www.oakdome.com/lab/wp-content/wds_mmc_add_boot_image.gif

 

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.

 

http://www.oakdome.com/lab/wp-content/wds_mmc_vista_boot_images.gif

 

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.

 

http://www.oakdome.com/lab/wp-content/create-capture-boot-image-for-xp-machines.gif

 

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.

 

http://www.oakdome.com/lab/wp-content/create-capture-image-wizard-settings.gif

 

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

 

http://www.oakdome.com/lab/wp-content/wds_mmc_add_boot_image.gif

 

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.

 

http://www.oakdome.com/lab/wp-content/xp-capture-boot-image-appears-in-boot-images-folder.gif

 

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.

http://www.oakdome.com/lab/wp-content/xp-deployment-boot-image-image-metadata.gif

 

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

 

http://www.oakdome.com/lab/wp-content/xp-deployment-boot-image.gif

 

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

 

http://www.oakdome.com/lab/wp-content/add-image-group-to-wds.gif

 

---

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.

[Netwacky87]

Got a problem at the very begining saying:

 

error code: 0xe0000102

 

And it doesnt go any further, anybody ever encountered this?

 

Thanks

[m25man]

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

 

You need to be very clear about this!

 

General recommendations for FSMO placement

• Place the RID and PDC emulator roles on the same domain controller. It is also easier to keep track of FSMO roles if you cluster them on fewer machines.

 

If the load on the primary FSMO load justifies a move, place the RID and primary domain controller emulator roles on separate domain controllers in the same domain and active directory site that are direct replication partners of each other.

• As a general rule, the infrastructure master should be located on a nonglobal catalog server that has a direct connection object to some global catalog in the forest, preferably in the same Active Directory site. Because the global catalog server holds a partial replica of every object in the forest, the infrastructure master, if placed on a global catalog server, will never update anything, because it does not contain any references to objects that it does not hold. Two exceptions to the "do not place the infrastructure master on a global catalog server" rule are: • Single domain forest:

 

In a forest that contains a single Active Directory domain, there are no phantoms, and so the infrastructure master has no work to do. The infrastructure master may be placed on any domain controller in the domain, regardless of whether that domain controller hosts the global catalog or not.

• Multidomain forest where every domain controller in a domain holds the global catalog:

 

If every domain controller in a domain that is part of a multidomain forest also hosts the global catalog, there are no phantoms or work for the infrastructure master to do. The infrastructure master may be put on any domain controller in that domain.

 

• At the forest level, the schema master and domain naming master roles should be placed on the same domain controller as they are rarely used and should be tightly controlled. Additionally, the domain naming master FSMO should also be a global catalog server. Certain operations that use the domain naming master, such as creating grand-child domains, will fail if this is not the case.

 

In a forest at the Forest Functional Level Windows Server 2003, you do not have to place the domain naming master on a global catalog.

 

Hope this helps.

[rush_tech]

Hi

 

I'm new to WDS and I used this guide

to help me (excellent by the way)

 

I've come across a problem I've created to boot images fine,

syspreped client,

booted client up to network client finds WDS Server,

selected Boot image get to the wizard,

select volume to capture and name it,

On the image capture screen I've ticked upload image to WDS Server

in the box below that entered its name clicked connect.

 

I get a error "the network is not present or not started"

 

Has anyone had this before?

 

Any help would be appreicated :?

 

Thanks in advance

[maniac]

As promised, how to add drivers to windows PE

 

First you need to install the windows Automated Installation Toolkit. This contains a couple of important programs you will need to edit the image, and add the drivers.

 

The Windows AIK can be downloaded from Microsoft here It is a big download, and you will need to burn it to a DVD to install it.

 

Once you have the AIK installed;

 

1. Locate the .wim file containing the windows PE image you want to add drivers to.

 

2. Create a local copy of this on the machine you're working on. If this is the server, then make an alturnate copy somewhere else on the server.

 

3. You need to mount the Windows PE image into a directory using the ImageX untility. this is installed as part of the AIK.

 

e.g imagex /mountrw C:\install.wim 1 C:\wim_mount

 

You can then use the PEIMG utility to add the driver into the windows PE image. You will need the drivers you want to add in another directory on your computer.

 

e.g peimg /inf=c:\drivers\intelpro1000\e1000325.inf c:\wim_mount\windows

 

This will install the specified driver into the windows PE image. The last step is to write these changed back to the WIM image, which you do by using the command;

 

imagex /unmount /commit C:\wim_mount

 

This will update the WIM file with the changes made. Then simply add it as a new boot image in WDS. I wouldn't recommend overwriting the existing boot image, incase the new one has problems.

 

I've written these instructions from some scribbled notes I took at the time I was preparing our images at the beginning of August, so apologies if there's in-accuracies in them. I'm sure that's it thou.

 

@rush_tech. Adding the correct network drivers into your boot image might solve your problem. However you can just create the .WIM file on the local hard drive and manually copy it to your WDS server after, you don't have to upload it straight to the WDS server.

 

However, you will still need to install the required network drivers into windows PE to download this image onto workstations.

[Uraken]

priceless maniac good man