[wds] The parameter is incorrect

[Bluetooth]

Hi Guys

 

I have WDS installed on server 2003 and im having an issue with WDS. Its all setup, tested and functioning correctly however:

 

I am trying to image some new netbooks the school purchased just before the holls. These are Eee PC 1001P's. They are the second batch of netbooks we have purchased in the last year.

 

The first set were 1001HA's and imaged and deployed fine via WDS however the second set, whenever i try to capture the image after sysprep WDS reports "the parameter is incorrect" after about 5 seconds after i click next to begin the capture.

 

Anyone have any clue why this error is coming up?

 

THanks

[Bluetooth]

Hi Guys

 

Anyone got a clue?

[Bluetooth]

Well after some discussion with another technician elsewhere we have come to an idea that WDS doesnt have the drivers to boot the hard drive.

 

Is there any way to put drivers into WDS so they can read from the disks?

 

Its odd because WDS detects the drive was sysprepped but would not image it.

 

Id REALLY like it if someone would reply ;P

[Bluetooth]

Yea thats what i did which is why we came to the conclusion about WDS not being able to work with the drive.

 

Machine 1 (eee pc 1001ha): N270, seagate sata hdd

Machine 2 (eee pc 1001p): n450, Western Digital hdd

 

So clearly something within WDS cant see the hard drive or work with it. which is why my question is, is there a way to put drivers in so that WDS can see the hard drive and image it?

[Bluetooth]

Bumping.

 

No one has seen this? Someone must use WDS enough to have seen this/resolved it?

[Bluetooth]

Not from what i can remember. The only settings i could change would be the sata mode from ahci to ide but would that make any difference? Theres also the extra work of repairing the os if i do change it as well.

[Bluetooth]

Right... since ive had oh so much help on this ive tried working on it a bit more.

 

Yesterday i had done a gut transplant on two machines. one of the HDD's was up to date but the other was not. So i think simple job, sysprep, image, drop image.

 

First two steps went fine. When i started to drop the image i get a WDS client error saying there is no compatible network card within the windows pe image. So i research on how to update drivers into a WIM image and finally start working on it. I locate the boot.wim file (under boot\images) and mount it, inject the driver, and commit the changes.

 

When i boot the computer again it gives me the same crap about not having the right driver.. yet i checked on the other machine and it IS the right driver.

 

So my next question is WHICH image should i edit to inject drivers to so that WDS will pick up the hard drive and networking?