I have a Win2008 R2 WDS server that has been up and running for quite some time. I have a Windows 7 x86 image that is hosted on that server.

I recently updated the Win7 image, syspreped, and uploaded to my WDS server as a new (v2) image. In the past this has always been quite simple, but for some reason i cannot get the new v2 image to display at the WDS client image selection screen.

The WDS server allowed me to add the new v2 image to my install image group, and says its online and working properly.

The WDS Client will only display the old v1 image and not the newly updated v2 image.

Both images were created on the SAME computer, x86, acpi multiprocessor. I am using the SAME computer to test/deploy the image.

The source of the problem seems to be from the install image missing the HAL details

If i use the WDS console and drill down to my old and new install images, right click and look at the properties this is what i get:

v1 Image: HAL Type ACPIAPIC

v2 Image: HAL Type (ITS F"N BLANK!!!!)

I get the same results looking at the <HAL>  </HAL> parmeters using ImageX /info blah.wim

SO, Why the HELL does WDS/Sysprep not recognize my HAL type of my new v2 image???? I have tried 3 different computers to generate/capture the install image and ALL are missing the HAL type.

Anyone have a clue why the WDS/SYSPREP process does not identify the HAL type and leaves me with a blank string - and hence a useless image?

I have previously tried this KB with no change:

"An ACPI APIC UP HAL operating system image cannot be deployed if a Windows 7 boot image or a Windows Server 2008 R2 boot image is used in the deployment process

http://support.microsoft.com/kb/980711

Post your output from imagex /info.

The other thread you replied in had invalid XML, so your case may not be related.

I cant post that online. Its from a secure network. So this is hand typed...

v1 Image that works:

<WIM>
<TOTALBYTES>3465086</TOTALBYTES>
<IMAGE INDEX=1>
<NAME> WINDOWS 7 V1 </NAME>
<DESCRIPTION> THIS IS MY DESCRIPTION </DESCRIPTION>
<WINDOWS>
<ARCH>0</ARCH>
<PRODUCTNAME> Microsoft Windows Operating System </PRODUCTNAME>
<EDITIONID>PROFESSIONAL</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>18229</SPBUILD>
<SPLEVEL>0</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>

v2 Image that does NOT work:

<WIM>
<TOTALBYTES>3510306</TOTALBYTES>
<IMAGE INDEX=1>
<NAME> WINDOWS 7 V2 </NAME>
<DESCRIPTION> THIS IS MY DESCRIPTION </DESCRIPTION>
<WINDOWS>
<ARCH>0</ARCH>
<PRODUCTNAME> Microsoft Windows Operating System </PRODUCTNAME>
<EDITIONID>PROFESSIONAL</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>18229</SPBUILD>
<SPLEVEL>0</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>

Notice that the v2 image is missing the following from the xml:

<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>

Im lost as what to try next. Anyone have any ideas why my new v2 image is missing information from the .wim file?

How did you capture the image. If you used DISM or Imagex, what exact commands?

I sysprepped the image, then booted into a Capture boot image. Then used the WDS capture image to generate the image. So im assuming ImageX is the method being used at that point.

Has anyone found a fix for this?!?!?

I just spent several weeks building and testing a different image and again have this same problem.

It is missing the HAL type and does not show up as a selectable image when i network boot my WDS client.

We have many STIG, SCAP, Retina, and other IA controlls in place. Trying to figure out witch one is causing this problem is proving the be incrediable difficult.

Does anyone have any advice ??

Did you find a fix Drumgod?