[wds] No images available - HELP!

[jamin100]

ok, so i'm new to WDS (can you tell) as I previously always used ghost but hey i'm giving this ago.

 

I have followed a guide on how to create a HAL independent image using vmware (from @Hightower i believe) I have created the image and sysprep'd it fine.

 

I have setup WDS and captured the image and copied it over to the WDS server. All great so far.

 

NOW, i'm trying to deploy it to a Toshiba A200 and its just not working I PXE boot to the network, go through the menu and at the point where it asks me to select the image to deploy it says "There are no images available"

 

I have tried the image on another machine and it works as it should, I just cant get it to deploy onto these ******* A200's.

 

The image created was x86 so i'm wondering if the toshiba is for some reason only looking for x64 images and therefore cant see the x86 image?

 

HELP

[jamin100]

ok, its defiantly just these laptops it wont work on as I've tried the image on 4 different types of machine and it works fine, so any help would be appreciated.

 

UPDATE:

Ok, I have disabled multi-core support in the BIOS and it can now see the images and is pulling one down as we speak. So i'll see what happens when I re-enable it after its imaged!

 

Odd as the image was built set as uniprocessor so i presumed that it would work on a multi too

 

UPDATE 2:

 

BSOD error 0x0000007B

 

any ideas?

Edited May 12, 2011 by jamin100

[Gatt]

7B is hardware related and usually regarding hard drives..

Is SATA mode set to IDE in the BIOS?

Do they need any specifc Mass Storage drivers?

[jamin100]

7B is hardware related and usually regarding hard drives..

Is SATA mode set to IDE in the BIOS?

Do they need any specifc Mass Storage drivers?

 

Yup, I reckon it needs Mass Storage Drivers

Can I get these into my WDS image by putting them in the $OEM$ folder on my WDS server?

[Gatt]

the latest version of WDS allows you to inject them straight into the image via the WDS Console (Driver Packages i think - I dont use WDS directly now as I have SCCM)

If not then you'll need to use imagex to mount the boot image...

[Duke5A]

Yup, I reckon it needs Mass Storage Drivers

Can I get these into my WDS image by putting them in the $OEM$ folder on my WDS server?

 

I'm assuming you're building an XP image since you're dealing with HALs. No you can't add the drivers, WDS only supports driver injection on Vista and 7 images. You'll have to sysprep the VM again with the drivers added to the mass storage section of your sysprep.inf.

 

As far as the HAL goes, which one did you use? If you used the Advanced Configuration and Power Interface then it's only going to utilize one core on multicore systems, and ignore hyperthreading. This could also account for why WDS isn't allowing you to image the machine with this image. Instead, make your VM a multiprocessor systems and build your image with the ACPI Multiprocessor PC HAL. Then use this line in your sysprep.inf to specify the HAL type:

 

UpdateUPHAL="ACPIAPIC_UP,%windir%\inf\hal.inf"

 

Now the image will downgrade to the ACPI Uniprocessor PC HAL type on single core P4 machines, and use the multi on hyperthreading enabled processors and multicore rigs.

 

Also, if you're placing your sysprep file in the image directory on the WDS server, be sure to strip out any lines in your sysprep.inf regarding partition setup. WDS does this on its own, and having these options specified will bork image. What'll happen is it will work on some hard disk geomoetries and not others. It will usually result in a BSOD after the first reboot (mini setup). These are the lines you'll want to remove...

 

[unattended]

Repartition=Yes

ExtendOemPartition=1

FileSystem=ConvertNTFS

 

Good luck.

[jamin100]

Thanks, I'll have a go at this today