WDS - Native - No Install Images

[ahuxham]

Hi Guys,

 

Small query. I'm having trouble getting WDS on Server 2008 to work correctly.

 

WDS is installed perfectly, and the boot.wim image added from the WAIK sources, from there I created a Capture CD (When Syspreping machines).

 

BOOT.WIM - Works fine, loads the WinPE 2.1 Environment

CAPTURE.WIM - Works fine (Only when a machine has been syspreped otherwise it cant read the HDD)

 

Earlier today, I did the norm. Installed Windows XP, all updates, all programs, all required changes and the likes to get a flat working XP version for rebuilding use. I sysprepped the machine on RESEAL after chaning HAL and adding various other pre-changes.

 

F12 booted into WDS > Capture > Image Captured and Uploaded to WDS Server > Showing in "Install Images"

 

However... whenever I F12 boot, I cannot see this install image. Any ideas why I can't? I followed the Microsoft WDS Step-by-step and it says it should be showing.

 

I tried to change the default boot program from pxeboot.com to wdnlsr.com or whatever its name, but that provided an infinte loop.

 

Just cant seem to get the install images to show. Suggestions?

 

Cheers

[Gatt]

I think you need the boot.wim file from a Vista SP1 or Win2k8 DVD for WDS?

[ahuxham]

I think you need the boot.wim file from a Vista SP1 or Win2k8 DVD for WDS?

 

So my Server 2008 DVD should have this *.wim file?

[Gatt]

yep - it should be in the :\soruces\ folder

along with the install.wim

 

Same files in same place on your VIsta DVD too.

 

Once the right boot.wim file is in you can create the Capture (Save Image) WIM file and the Discover (Load/Deploy Image) WIM file

[ahuxham]

yep - it should be in the :\soruces\ folder

along with the install.wim

 

Same files in same place on your VIsta DVD too.

 

Once the right boot.wim file is in you can create the Capture (Save Image) WIM file and the Discover (Load/Deploy Image) WIM file

 

Let me just clarify this for myself.

 

Copy boot.wim from 2008 DVD, add as image, right click and create capture image, right click and create discover image.

 

boot.wim = the standard WinPE 2.1 environment with the command prompt?

 

capture.wim (created) = capture environment with the step-by-step instructions for capturing.

 

discover.wim (created) = deployment environment, from here I should be able to select my install image?

[plexer]

To deploy images you need to use the boot.wim from vista business or server 2008 dvd.

 

Is the image you wish to deploy showing in the wds console app thingy? i.e did it get uploaded to the server correctly?

 

Ben

[ahuxham]

To deploy images you need to use the boot.wim from vista business or server 2008 dvd.

 

Is the image you wish to deploy showing in the wds console app thingy? i.e did it get uploaded to the server correctly?

 

Ben

 

Yeah its showing as an Install Image and is online, however as Gatt said above I need to use the Vista/2008 boot.wim file to create boot/capture/deploy images.

[plexer]

No you only need to vista/2008 boot.wim to deploy images, the x86 and amd capture images can be created from the files supplied with the windows automated installer kit (AIK)

 

Ben

[plexer]

How to Deploy Windows XP Professional Using Windows Deployment Services (WDS) Lucius Craig MCSA, CCNA

 

Deploy XP Images in the Computer Lab with Windows Deployment Services on Server 2003.

[ahuxham]

How to Deploy Windows XP Professional Using Windows Deployment Services (WDS) Lucius Craig MCSA, CCNA

 

Deploy XP Images in the Computer Lab with Windows Deployment Services on Server 2003.

 

Perfect! Thanks Plexer.

 

Problem was not using the correct boot.wim file, I used the one from the WAIK installation.

 

Cheers

[plexer]

Cool let us know how you get on, mine stuck on deploying the image.

 

Ben

[ahuxham]

Cool let us know how you get on, mine stuck on deploying the image.

 

Ben

 

Working perfectly actually now that its actually going.

 

Have tested the following sysprep images: (We used to use the WinPE disk, imagex capture etc, not one touch deployment which it is now)

 

- Windows XP Pro, no drivers no software, just a clean install. (Three minutes for deployment, 2 for Sysprep mini-setup to run)

 

Need to test the other images. Our ICT image is 15.2GB :/ May take a while.

[plexer]

hmm wonder why I had problems then.

 

Is your wds a physical server?

 

Ben

[ahuxham]

hmm wonder why I had problems then.

 

Is your wds a physical server?

 

Ben

 

Yeah, HP Proliant, it's also our 2008 IPv4/6 DHCP Server as well, as this was needed for McAfee and Windows NAP enforcement.

[PiqueABoo]

Mine stuck on PXE booting, specifically WDS TFTP doesn't respond (to a sensible request from the workstation) after the exchange of a few network packets.

 

[Only installed WDS for MDT LiteTouch PXE booting so gave up and I'm happily using SolarWinds TFTP instead]

[ahuxham]

hmm wonder why I had problems then.

 

Is your wds a physical server?

 

Ben

 

Yeah but saying that Plexer I am now running into problems. I have 6 install images imported - however problems are occuring.

 

When using the boot.wim to boot, I am only offered 1 image as an install image, the other 5 do not show, these are sysprepped images I created.

 

I created a capture.wim from the boot.wim and that works fine, every now and again it moans that it cannot contact the server, but reboot, PXE back in and it runs fine.

 

It's a bit hit and miss and I'm not sure if hit & miss is acceptable.

[Ste_Harve]

I think the problem could be hal related, i've got about 15 images on my WDS server and it only shows the ones that are relevant to that hal. ie dual core machines on pull in images created on a dual core machine. single core only get the single core images.

 

think there is a way to switch off hal detection in WDS though so it will show all images.

[ahuxham]

I think the problem could be hal related, i've got about 15 images on my WDS server and it only shows the ones that are relevant to that hal. ie dual core machines on pull in images created on a dual core machine. single core only get the single core images.

 

think there is a way to switch off hal detection in WDS though so it will show all images.

 

Exactly the problem. I read the guides and the likes, and said switch to ACPI, and it should be compatible to all machines, and like crap is it.

 

I do wish their was a way to turn HAL off, as its rather annoying and frustrating.