- Windows Xp Tablet Pc Edition 2005 Iso Download
- Download Windows Xp Iso 32
- Windows Xp Tablet Pc Iso Download Free
- Windows XP Tablet PC Edition 2005 with Service Pack 3! In VMware Player. Download Link for ISO. Transform Windows XP to Windows XP Tablet PC Edition 2005 - Duration.
- Download Windows ME.iso file OEM for free (direct links). September 14, 20160. Windows XP Professional x64 Edition SP2. Windows XP Professional.
Is this Really a 'Single Image' Process?
- Standard PC
- MPS Uniprocessor
- MPS Multiprocessor
- Advanced Configuration and Power Interface (ACPI) PC
- ACPI Uniprocessor
- ACPI Multiprocessor
- Advanced Configuration and Power Interface (ACPI) PC HAL
- ACPI Uniprocessor HAL
As you can see from a few of the comments below, there are people who are doing scripted changes of the HAL using either direct file replacements, using the Sysprep.inf answer file entries, or some combination of the two. Direct HAL file replacements are always unsupported by Microsoft. Any HAL replacement using the Sysprep.inf answer file entries using combinations not found in the About UpdateUPHal or About UpdateHal sections of Microsoft Knowledge Base article 309283 are also unsupported. While doing this may appear to 'work', if issues occur later that impact your users ability to work that can be traced to unsupported HAL changes you may have a new expensive redeployment project on your hands. I am not speaking of a hypothetical situation here. This has happened to customers who have done this. The benefit of having a 'single' image through HAL swapping is not worth the risk of possibly redeploying large numbers of machines.
Windows XP 'Single Image' Process
After your image has been updated in this manner, you must then update MDT. There are two parts to this process. The first part is determining whether the target computer is a Tablet PC and the second is executing the scripted changes to convert the OS to Tablet PC Edition if the target computer is a Tablet PC. There are a numbers of ways to determine whether the target computer is a Tablet PC. You could add a custom property to Make/Model detection called IsTablet (must have a value of True or False). If you are using CustomSettings.ini to store your Make/Model information, you would put a direct entry in the CustomSettings.ini Make/Models sections. If you are using the MDT database, you could add an IsTablet field to the MakeModelIdentity table, populate the IsTalbet field of the Make/Model rows with True or False, and add a database query to CustomSettings.ini to retrieve the IsTalbet field.
However, I took another approach that I find simpler to maintain. It involves detecting whether the target computer has Tablet digitizer hardware. I add a custom property to CustomSettings.ini called TabletPnpIds. In this property I placed a comma separated list of the Plug & Play Device ID's of the digitizer devices on all supported Tablet PC model. Then a user exit script uses this list to determine if the target computer is a Tablet PC and sets the IsTablet property accordingly.
To update MDT to use my entire process, use the following steps (respecting any change management process or change windows you have, of course). If you want to use your own method of setting IsTablet, then you can skip the Edit CustomSettings.ini for detecting Tablet PC hardware steps and implement you own method.
- Add the Custom Scripts to the MDT Scripts: First, extract the scripts from the attached ZIP file and add them to either your LTI Scripts folder or your SCCM MDT File package. Be sure to update your MDT Files package and Distribution points in SCCM after doing this.
- Edit CustomSettings.ini for Detecting Tablet PC Hardware: You will need to add the following to CustomSetting.ini to use my method of determining whether the target computer is a Tablet PC (additions in blue).
[Settings]
Priority=IsTabletCheck, Default
Properties=MyCustomProperty, TabletPnpIds, IsTablet[IsTabletCheck]
TabletPnpIds=ACPIWACF004,ACPIWACF008,ACPIMAI3310,ACPIFUJ02E5
UserExit=ZTI-DetectHardwareExit.vbs
IsTablet=#DetectDevices('%TabletPnpIds%')#
- The Plug & Play IDs used in the TabletPnpIds entry no longer need the trailing backslash. However, if you forget to remove them it will still work. I have put code in the new script to check for this and remove them from the variable in memory if found.
- The name of the UserExit script has changed. The old script was called ZTI-DetectTabletExit.vbs. The new script, ZTI-DetectHardwareExit.vbs, was designed to allow general purpose hardware detection. See the section later in the post for details.
- The name of the procedure called from the UserExit script has changed. The old one was called DetectTablet and it took no arguments. The new one, DetectDevices, takes the Plug & Play ID list as its input argument.
In the case of the 'Wacom Penabled MiniDriver' shown above, the Device Instance Id is ACPIWACF0044&2F7DB942&0. The portion of this ID up to the last backslash, ACPIWACF004, is the Device ID. The portion after the last backslash, 4&2F7DB942&0, is the Instance ID for this device. The Device ID is one of several hardware ID's embedded in the device by the manufacturer to be used for Plug & Play detection. The Instance ID is a unique identifier assigned to a particular device by Windows when it is detected. The Instance ID allows Windows to uniquely identify a device when there is more than one of the same device present in the system (for example, two of the same model network card). The part we are interested in is the Device ID. Put the Device IDs, excluding a trailing backslash, in the TabletPnpIds entry separated by commas.
You can also use ID's found under the Hardware Ids or Compatible Ids it you want to 'generalize' the detection to a set of devices that share a common Hardware Id or Compatible Id. (The Device ID determined above should be the first Hardware ID listed) Items from these properties should be used as they appear in the dialog box (i.e. there is no Instance ID to remove).
- Edit CustomSettings.ini for Setting the Tablet PC Edition Volume License Key: The next changes to CustomSetting.ini set a custom property called XPTabletProductKey to your Tablet PC Edition Volume License Key. If you do not have one and you are a Select License, Enterprise Agreement, and Enterprise Subscription Agreement customer, then see the Notes section in the Single Image Deployment Guide to obtain one.
Add the following changes to CustomSetting.ini so that XPTabletProductKey will have a value when IsTablet is true. Replace AAAAA-BBBBB-CCCCC-DDDDD-EEEEE with your Tablet PC Edition Volume License Key. (Additions for this part in green):[Settings]
Priority=IsTabletCheck, ByTabletType, Default
Properties=MyCustomProperty, TabletPnpIds, IsTablet, XPTabletProductKey[IsTabletCheck]
TabletPnpIds=ACPIWACF004,ACPIWACF008,ACPIMAI3310,ACPIFUJ02E5
UserExit=ZTI-DetectHardwareExit.vbs
IsTablet=#DetectDevices('%TabletPnpIds%')#[ByTabletType]
Subsection=Tablet-%IsTablet%[Tablet-True]
XPTabletProductKey=AAAAA-BBBBB-CCCCC-DDDDD-EEEEEIf you are using SCCM, remember to update your Settings Package with the updated CustomSetting.ini. - Edit the Task Sequence to Add a Step to Run ZTI-XPTabletSingleImage.wsf: The next step is to edit the Lite Touch or SCCM MDT Task Sequence to run ZTI-XPTabletSingleImage.wsf during the middle of the PostInstall phase. The picture below shows this for an SCCM MDT Task Sequence.
For an SCCM MDT Task Sequence, be sure to check the Package box and select your MDT Files package. - Import Digitizer Drivers: This should go without saying but you must import digitizer drivers into the Deployment Workbench for LTI or into the Drivers library and add them to Driver Package(s) for SCCM. The Single Image Deployment Guide shows how to extract the 'in the box' digitizer drivers. But if you don't have any devices that need them, use the PC manufacturer's drivers instead. You do not need to place any drivers in the C:Sysprepi386Digitizer folder as shown in the Guide. Use the Deployment Workbench Out-of-Box Drivers or SCCM Driver Packages to handle drivers instead.
That completes the setup. When you deploy this XP Task Sequence to a Tablet PC, your Windows XP Professional Image should magically transform into Windows XP Tablet PC Edition 2005. If you want to test this process and don't have any Tablet PC's handy or you want to test using Virtual Machines (Virtual PC, Virtual Server, Hyper-V, VMWare, etc.) then use the following trick. Pick a device on your target computer (it's not really important which one it is) and place it's Device ID, or one of it's Hardware Ids or Compatible Ids in the TabletPnpIds list. This will cause the IsTablet property to evaluate to True for this machine and it will result in Tablet PC Edition being installed on this non-Tablet computer.