After a colleague of mine installed WDS at a client site they found that certain laptops and desktop PCs would not be able to pick up the images that have been captured.
The problem lies in the HAL Type of the PC that was captured and then WDS finds the HAL type for the PC asking for an image and if one doesn’t match then you will most probably get the error: “There are no images available”
My scenario was that we had a generic image built and working for Single CPU and MultiCPU PCs but only the Multiple / Newer PCs could see the image in WDS – that is because the HAL type was “Advanced Configuration and power interface (ACPI) PC” but these older PCs were being recognised as Uniprocessor HAL Types.
The solution: Get the image onto the Older PC type (via Ghost or Clonezilla etc) login to the system. Download DevCon and extract into C:\Windows or any other %PATH% variable you like.
Then run:
devcon sethwid @ROOT\ACPI_HAL\0000 := +acpiapic_up !acpiapic_mp
devcon update c:\windows\inf\hal.inf acpiapic_up
Reboot and Login two times then Sysprep and capture again!
Hopefully your good to go!
Reference: http://www.ngohq.com/processors/11891-how-to-update-the-hal-without-reinstalling-windows.html
Keywords: WDS, Force HALs, Force HAL, Windows Deployment Services, WDS, ACPI Multiprocessor PC, acpiapic_up, acpiapic_mp, No Images after Capture, Change HAL Type