Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

Farmer Pete — Mon, 04 Aug 2008 16:28:49 GMT

I know this isn't supported by Microsoft in any way, shape, or form, but the following site has a MDT script to change your HAL. I had to modify the script to point to where I was storing the i386 folder (not in the default MDT location) so that it can get the dll files it needs.

http://myitforum.com/cs2/blogs/jhuston/archive/2007/08/09/hal-replacement-in-bdd.aspx

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

Daniel Oxley — Mon, 04 Aug 2008 16:36:15 GMT

Pete,

You are right in saying that it works. However, I have to stress the importance of the issue of support. That process is totally unsupported by Microsoft.

I do not recommend it at all, particuarly if you plan on installing many computers from the same image using that process.

Imagine the scenario where you use that process to install 20,000 computers. Then, further down the road you discover a problem and Microsoft refuses to give any support at all because the computers were installed using that unsupported process.

Regards,

Daniel

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Mon, 04 Aug 2008 17:55:37 GMT

As Daniel said, scripted or manual HAL swapping is definitely completely unsupported. I know of support cases where customers had to redeploy thousands of machines at great expense because of an issue that occurred on images where the HAL was swapped that did not occur when the image with the correct HAL was placed on the system. This is not a hypotheical scenario, it has happened to real customers. Even though HAL file swapping may seem to work I have personally encountered performance and other issues when doing this. There are interrupt tables built in the Registry during Windows setup that are not rebuilt during Sysprep/Minisetup. KB 315973 is the absolute final word on this from Development and Support. Please, please, please do not do this. Only Vista and Server 2008 are HAL independent on the same architecture with a Sysprep image.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

Farmer Pete — Mon, 04 Aug 2008 18:14:29 GMT

I'm sure some people have had great experiences with MS support, but my company has pretty much figured out that in general, we are on our own with software issues. This doesn't apply just with Microsoft, but also with IBM, Symantec, etc. Sure, there are people that can help us if we are doing something wrong, but if there is a flaw in the software itself, it's typically a..."Wait until the next version due out in 6 months, and maybe the issue will be fixed." Microsoft typically claims the problems aren't theirs, but either chooses not to or can't substantiate those claims with facts.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Mon, 04 Aug 2008 19:04:04 GMT

This has nothing to do with whether you have an issue with the quality of our software support. I am telling you that if your computers experience an issue at some point that impacts your end users ability to work that turns out to be caused by HAL swapping, you will be reimaging those machines. (I know in one of those customer cases the issue manifested itself after deployment of an update.) There will be no hotfixes issued to fix the problem and you will unlikely be able to find a fix "on the net". This is not a flaw in the software, it is how Windows was designed at that time.

The potential impact of doing this is too large vs. the benefit of having one or two less images.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

Dustin Martin — Tue, 05 Aug 2008 17:03:11 GMT

HAL Changing is supported to an extent by microsoft (at least, its built into the sysprep.inf)

I can attest for these working together:

# Advanced Configuration and Power Interface (ACPI) PC

# ACPI Uniprocessor

# ACPI Multiprocessor

These do NOT need two images. But it is 100% dependant on your 'core build' machine. You *MUST* build it on a machine specified as

# Advanced Configuration and Power Interface (ACPI) PC. You can do this using your unattend file simply by specifying the "ComputerType" variable.

From there, sysprep can Up-Invert the HAL into ACPI UP or ACPI MP simply with a line in the sysprep. The trick is detecting which line is needed.

More info can be found here:

http://www.myitforum.com/articles/15/view.asp?id=8997

I've been using this method for months and it works just fine. I was able to get my Nc6000s to work with every other model of computer we run, though it shouldn't in essence. This is completely done automatically by windows and has worked 100% for me across 21 models of HPs and Dells with no issue.

I don't run any MPS Hal's however, so i have no info on those.

*********************************

In regards to .NET errors in the Tablet PC Edition Conversion - i've personally experienced this problem. You *can* put .NET 3.5 into your core build, however you will need to re-install it for the tablets only. The reinstallation resolves all the corruption issues with the .NET classes . I simply added a task for tablets only to run this installation during their build-out phases.

Also note - there is one other quirk i've noticed with the Tablet PCs so far. 90% of them have Quicklaunch drivers that need fully installed, not just enumerated for the screen-spinning functionality amongst other options to function properly. Keep this in mind - you'll need to add them as packaged apps or these options will not work and will not be available.

I'm supporting about 1000 tablets right now across 3 models and these are my only issues so far.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Tue, 05 Aug 2008 18:25:48 GMT

Dustin,

Just because the tools allow you to force a HAL change does not make it supported. The following is the relevant section from MS KB article 309283. If you do anything else, it is unsupported.

===========================================

From KB 309283:

When you create a Sysprep image, the image must contain the correct HAL type for the target computer. The following list describes the computers that you can deploy a particular Sysprep image to based on the HAL type in the source computer:

• You can deploy a Sysprep image created on a computer that uses a Standard PC, Non-ACPI PIC HAL (Hal.dll) to a computer that uses the following HAL types:

• Standard PC, Non-ACPI PIC HAL (Hal.dll)

• You can deploy a Sysprep image created on a computer that uses an Advanced Configuration and Power Interface (ACPI) PC, ACPI PIC HAL (Halacpi.dll) to a computer that uses the following HAL types:

• Advanced Configuration and Power Interface (ACPI) PC, ACPI PIC HAL (Halacpi.dll)

• You can deploy a Sysprep image created on a computer that uses a MPS Uniprocessor PC, Non-ACPI APIC UP HAL (Halapic.dll) to a computer that uses the following HAL types:

• MPS Uniprocessor PC, Non-ACPI APIC UP HAL (Halapic.dll)

• MPS Multiprocessor PC, Non-ACPI APIC MP HAL (Halmps.dll)

• You can deploy a Sysprep image created on a computer that uses a MPS Multiprocessor PC, Non-ACPI APIC MP HAL (Halmps.dll) to a computer that uses the following HAL types:

• MPS Multiprocessor PC, Non-ACPI APIC MP HAL (Halmps.dll)

• MPS Uniprocessor PC, Non-ACPI APIC UP HAL (Halapic.dll)

• You can deploy a Sysprep image created on a computer that uses an ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll) to a computer that uses the following HAL types:

• ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll)

• ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll)

• You can deploy a Sysprep image created on a computer that uses an ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll) to a computer that uses the following HAL types:

• ACPI Multiprocessor PC, ACPI APIC MP HAL (Halmacpi.dll)

• ACPI Uniprocessor PC, ACPI APIC UP HAL (Halaacpi.dll)

===========================================

This is from the Windows XP Deployment Tools help file (Deploy.chm):

If you use images as part of your manufacturing process, you can preinstall the same Windows image on both multiprocessor (MP) and uniprocessor (UP) computers, as long as the master computer and the destination computer are both Advanced Programmable Interrupt Controller (APIC) computers or both Advanced Configuration and Power Interface (ACPI) APIC computers.

This table illustrates the type of destination computers where you can install a given master image, depending on the hardware abstraction layer (HAL) type of the computer used to create the master installation.

HAL of Master Installation	HAL of Destination Computer
HAL of Master Installation	ACPI APIC UP	ACPI APIC MP	Non-ACPI APIC UP	Non-ACPI APIC MP
ACPI APIC UP	X	X
ACPI APIC MP	X	X
Non-ACPI APIC UP			X	X
Non-ACPI APIC MP			X	X

===========================================

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

Rich Coulter — Wed, 06 Aug 2008 19:03:57 GMT

Mike,

The process is very solid. I've had no issues at all deploying to Tablet PCs in my environment. Thanks again for all your hard work. Because we are an XP SP2 shop, this has allowed us to streamline our deployments with a single XP SP2 Gold Image.

Cheers,

Rich C.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

MattS — Wed, 13 Aug 2008 19:40:01 GMT

Hi Michael,

I am attempting to deploy a SP3 Tablet edition install. I have been through the post, but obviously I am missing something…

The source files have been taken from the instillation CD. CMPNENTS folder copied to the same level as i386.

The error I am getting during deployment is “The Tablet PC Edition components (C:\$WIN_NT$.~BT\source\Cmpnents) are missing”. However, I can see the cmpnents folder in the C:\$WIN_NT$.~LS\ folder on the target machine. My understanding is that this means the folder has been copied over from the distribution folder. But obviously it needs to be in the “~BT” folder, which it is not.

Yes, this is SP3, but I am happy to have separate images for PRO and Tablet, so I don’t think this is my issue. Any ideas?

Thanks!

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Thu, 14 Aug 2008 16:42:42 GMT

MattS,

Do the Service Pack levels of the installation CD files (i386 folder, etc.) and the Tablet CMPNENTS folder match. It is only supported to do an unattended installation from Service Pack 2 files, then update to SP3 after installation.

If you want to deploy a Tablet SP3 image, you must use a Sysprep image based deployment, not an unattended installation.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

MattS — Thu, 14 Aug 2008 21:11:15 GMT

Hi Michael,

Thanks for your quick response. When I originally posted my comment, no, they did not match. However I realized that this was an issue and I have since attempted to do a straight SP2 Tablet edition (files imported from the installation cd) unattended install, and am having the exact same issue. The full error I get is:

The Tablet PC Edition components (C:\$WIN_NT$.~BT\source\Cmpnents) are missing. Exiting. ZTI ERROR – Non-zero return code by ZTI-XPTabletSingleImage, rc = 1

Non-zero return code executing command “X:\Deploy|Tools\X86\TSMBootstrap.exe” /env:SAStart, rc= -2147467259

As I said, I can the cmpnents folder is appearing in C:\$WIN_NT$.~LS\ on the source machine.

I am using MDT, not SCCM. I am executing the script during Postinstall, immediately after “Inject Drivers”.

Any advice would be greatly appreciated!

Cheers!

~Matt

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Fri, 15 Aug 2008 06:00:48 GMT

MattS,

What script are you executing during PostInstall? ZTI-XPTabletSingleImage.wsf is not intended for use with an unattended installation.

If you want to create a Tablet PC Edition installation, you simply have to use XP Pro media with the CMPNENTS folder included at the same level as the i386 folder and run the unattended install using a Tablet PC Edition volume license key. My scripts are not needed for this.

My scripts are only for converting a Sysprep XP Pro image to Tablet PC Edition at deploy time.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

MattS — Fri, 15 Aug 2008 19:56:57 GMT

Michael,

Awesome. "Once you have XP SP2 added as an Operating System and have added the CMPNENTS folder to it, you can then use MDT Lite Touch to build..." I only read this line a dozen times and for some reason felt it didn't apply to me.

I have removed the scripts and my install is working fine now.

Thanks for all your help. Believe me, after 2 days of banging my head against the wall,I've learned my lesson. :)

Cheers!

~Matt

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

EricS — Mon, 18 Aug 2008 21:46:10 GMT

"...Well, the good new is that in an upcoming post I will show you how to create a single WIM file that contains all four images with a single MDT Lite Touch Task Sequence (rerun four times). And I will show you how you can deploy these images from that WIM file onto the correct target hardware using either a single MDT Lite Touch Task Sequence or a single MDT Zero Touch Task Sequence in SCCM."

I could sure use THAT future article right now!!! :)

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

Patrick C. — Thu, 02 Oct 2008 20:16:47 GMT

I was having a hard time accepting that I would need two images. I believe I have something that is working well.

I image the tablet from an image of XP SP3 with .NET 1, 2, & 3, just as I did with my previous image (Thanks for the help on understanding this). But with the tablet I script the removal of .NET 3, 2, & 1. Then I re-install .NET 1, 2, & 3.

BTW… We are using Altiris Deployment Solution to script everything. I can determine the model automatically and inject proper drivers before the mini-setup runs. I also inject a sysprep.inf file that is automatically customized with the computer name from the console, so there is no stopping during the build process.

I didn’t realize there was a .NET issue with the tablet, until we started to install Guardian Edge encryption software and portions of the process were failing on the tablet, but not any other system.

Thanks for all the help this web site has provided.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Thu, 02 Oct 2008 20:38:55 GMT

Patrick C.,

The need for more than one image has nothing to do with the .NET Framework Issue (although you have to deal with it if you do the conversion from Pro to Tablet). As I explained above, if you are deploying XP SP2 images, then you will likely need multiple images if you have hardware with incompatible HAL types (an "Advanced Configuration and Power Interface (ACPI) PC" image and an "ACPI Uniprocessor" image with most modern hardware). If you are deploying XP SP3, then you will need to have separate Pro and Tablet PC Edition images for each HAL type. Doing anything else will not be supported by Microsoft.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

davec — Wed, 14 Jan 2009 22:31:24 GMT

Does the following KB resolve the .NET issue?

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

This worked for us with our XP SP2 images containing .NET 1/1.1/2/3

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

C Martin — Fri, 23 Jan 2009 23:01:29 GMT

Its been 4+ months since this was written and there is still no KB article, updated single image guide or other guidance that state that a SP3 sysprepped image cannot be converted to tablet edition. We've been using the original guide for years to dynamically convert to tablet edition when image on tablet hardware and updated to SP3 with no problem. If the CMPNENTS folders exists in the correct place when you slipstream an SP2 i386 folder to SP3, it updates the NETFX and TABLETPC sub folders with all the updated files that are needed. Can anyone give examples of what isn't working?

Thanks for the guidance on .net issues.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Sat, 24 Jan 2009 00:00:02 GMT

C Martin,

The white paper were just updated a few days ago with notes about the SP3 change in support for this Single Image process. See this post: http://blogs.technet.com/deploymentguys/archive/2009/01/21/windows-xp-tablet-pc-edition-2005-deployment-white-papers-updated-for-service-pack-3.aspx.

The problem is not that it does not work. I have stated previously that it does work when slipstreamed correctly. This issue is that is is not supported. The team that developed SP3 decided not to expend the resources to test integrated or slipstreamed Tablet PC Edition components for release. Since it was not tested by the devepment team, it cannot be supported.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

C Martin — Sat, 24 Jan 2009 02:59:20 GMT

I'm sorry I have to complain, but 1st thanks for responding. I've only recently found this blog and already have some tablets deployed in this fashion. It takes MS 8 months after the release of SP3 to update a Tablet white paper? Its not mentioned anywhere in the SP3 Release Notes, SP3 KB936929, XP support center or the SP3 white patper. Why isn't there a KB article that states this like there is for the HAL supportability issues? What exactly is meant by MS will not support? Does it mean MS will not support SP3 installation issues using this method, or MS won't support any problems (current or future) on these systems at all? Should re-installing SP3 on these tablets make them supportable? I'm sorry to take this out on you, I'm sure its not your fault. However, it seems like its only the deployment team that knows its unsupported. Its a real burden to maintain multiple images. It also makes it error prone for the installers to pick the correct image to install.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Mon, 26 Jan 2009 06:40:17 GMT

C Martin,

You have every right to complain about this. The teams that created Service Pack 3 really dropped the ball on informing customers and the Microsoft field organization about this change in support for having integrated Tablet media and a Single Image process. I only found out because a support engineer asked me how I had gotten it work. He was told by the dev team that it was not supported. That was the first time I had heard this. As far as I know, no one in the field knew about this before that.

I won't get into all the gory details but I'll just say this generated a lot of heated internal e-mails. And if it wasn't for the constant pressure from Scott and Dewitt from our Support organization and myself, even the white paper updates might not have happened.

What "not supported" generally means in this context is that if you deploy Windows in a manner we state is unsupported, then if you encounter an issue that required support on those computers, you may be asked to reproduce the issue on a "supported" installation before we will assist. If it cannot be reproduced on a "supported" installation our recommended solution may be for you redeploy Windows in a supported manner to the affected machines.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

davec — Wed, 11 Feb 2009 19:24:07 GMT

Michael,

Can you comment on my question from 1/14/09? Is this a completely unrelated issue?

Thanks

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Wed, 11 Feb 2009 20:10:42 GMT

davec,

At first glace KB836872 does look like a solution to the .NET Framework issue. However, I have not tested it.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

Scott — Wed, 11 Feb 2009 21:59:20 GMT

I would like to disable the .net installation when the tablet components install, if I make some minor changes to the netfxocm.inf, can I block the forced installation of this older version that breaks the .net 3.5 installation we have captured in our images? I've tried just running a repair but, I always get error messages that pop dialog's. I really don't want to write a screen clicker to click on the OK on the errors so this appears to be my best available option.

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

DeploymentGuys — Wed, 11 Feb 2009 22:42:24 GMT

Scott,

Any modification like that would be unsupported. If you want to stick with the Single Image process you could try either moving the .NET 3.5 install to the post-OS deployment or try KB836872.

Michael Murgolo

re: Implementing the "Windows XP Tablet PC Edition 2005 Single-Image Deployment Supplemental Guide" Process in MDT 2008 - Full Update

hcortez463 — Tue, 19 May 2009 16:16:31 GMT

i have a .wim file that did not have the CMPNENTS and i386 folder in the directorey structure.. I have updated the wim by mounting it and coping the specified folders. i also udated the registry HIVE. Im now trying to push this image out with SCCM and it still just installs as XP not table. what am i missing here