Sysprep and Hyperthreading on Windows XP
I have a lot of uniprocessor computer and one image for them. Actually, we just bought a hyperthread computer and I successfully restore my image on that computer.
So I suppose my image will not see the computer has a dual processor computer. What should be done to make sure my unique image will fit correctly on the HT computers?
So I suppose my image will not see the computer has a dual processor computer. What should be done to make sure my unique image will fit correctly on the HT computers?
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
Francoisracine
19 years ago
Posted by:
olivier
19 years ago
Posted by:
Francoisracine
19 years ago
Personnally, I prefer unattended setup but there is no way to reinstall a big bunch of computers with no need to physically move to those computers (RIS F12). With an image, it is possible to completely reinstall many Computers by using SMS and a good product (OSD, RCD,...)
So the HAL would be uniprocessor or multiprocessor? What is happening when you reenable HT?
No issue with uniprocessor computers using a HT image (taken with HT disable)?
So the HAL would be uniprocessor or multiprocessor? What is happening when you reenable HT?
No issue with uniprocessor computers using a HT image (taken with HT disable)?
Posted by:
olivier
19 years ago
Posted by:
auxiliary
19 years ago
Francoisracine,
Are you meaning that you like unattended over RIS because you have to push F12 on the machine to boot to network? If so... this may help you out.
By default, RIS causes the client computer to display a prompt that tells the user to press F12. To prevent RIS from displaying the prompt, navigate to the folder \\RIS_server_name\REMINST\oschooser\i386. Rename Startrom.com to Startrom.old, then rename Startrom.n12 to Startrom.com
If not, then sorry I said anything hehe. =)
Are you meaning that you like unattended over RIS because you have to push F12 on the machine to boot to network? If so... this may help you out.
By default, RIS causes the client computer to display a prompt that tells the user to press F12. To prevent RIS from displaying the prompt, navigate to the folder \\RIS_server_name\REMINST\oschooser\i386. Rename Startrom.com to Startrom.old, then rename Startrom.n12 to Startrom.com
If not, then sorry I said anything hehe. =)
Posted by:
Francoisracine
19 years ago
1. We can make unattended by using RIS.
2. If you remove the F12, how will you slect which computer would start a RIS or not?
However it is really interesting.
3. What I say is: It is not efficient to have to move to a computer to press F12. If we have to manage a bunch of computer, then to be efficient, you will need to find a way centrally. Our enterprise bought 1e RightClick Deployment to reinstall all computers. So centrally we can just start a computer reinstall and the softwares will be advertise automatically to that computer. We can reinstall 10 computers at a time if we need.
But those methods need computers image not unattended installation. And I would prefer unattended installation but we have to do a compromise to be a little efficient.
2. If you remove the F12, how will you slect which computer would start a RIS or not?
However it is really interesting.
3. What I say is: It is not efficient to have to move to a computer to press F12. If we have to manage a bunch of computer, then to be efficient, you will need to find a way centrally. Our enterprise bought 1e RightClick Deployment to reinstall all computers. So centrally we can just start a computer reinstall and the softwares will be advertise automatically to that computer. We can reinstall 10 computers at a time if we need.
But those methods need computers image not unattended installation. And I would prefer unattended installation but we have to do a compromise to be a little efficient.
Posted by:
rahvintzu
19 years ago
JB347 try this maybe
UpdateUPHAL
Identifies the processor type and loads the appropriate kernel.
Syntax UpdateUPHAL = hwid,%WINDIR%\Inf\Hal.inf
Value hwid,%WINDIR%\Inf\Hal.inf
(where hwid is either MPS_UP or ACPIAPIC_UP)
Example UpdateUPHAL = MPS_UP,%WINDIR%\Inf\Hal.inf
Comments Valid only for Sysprep.inf. Required if the master installation is built on an APIC multiprocessor computer and the image of that master installation is on compatible APIC uniprocessor or multiprocessor destination computers.
Not sure if this helps but here is some additional info regarding master images/sysprep and HT.
From MS
To ensure that Sysprep images are compatible with systems that enable hyper-threading, you must create the master image on one of the following types of systems:
An ACPI-compliant computer that enables hyper-threading
An APIC-based computer running ACPI that Device Manager refers to as "ACPI Uniprocessor PC"
An ACPI-compliant multiprocessor computer
If you do not create the Sysprep image on one of these types of systems, Windows is not able to update the system to use multiple processors. A Sysprep image made on an ACPI-compliant multiprocessor computer will run in a multiprocessor configuration even if support for hyper-threading is turned off in the BIOS.
Windows automatically uses the hyper-threading capabilities of the processor if the following conditions are present:
The computer hardware supports hyper-threading and this functionality is enabled in the computer's BIOS.
Hyper-threading functionality is installed in the computer processor.
The Windows installation uses the ACPI Uniprocessor PC HAL.
Windows detects one or more processors or enabled threads.
When these conditions are present, Windows automatically updates the HAL to the "ACPI Multiprocessor PC" HAL and and installs an additional processor, which is listed under Processors in Device Manager.
When running, the HAL type must be "ACPI Multiprocessor PC" or the hyper-threading capabilities of the processor will not be used. If the HAL type is "ACPI Uniprocessor PC," then one or more of the previously listed conditions is not present.
UpdateUPHAL
Identifies the processor type and loads the appropriate kernel.
Syntax UpdateUPHAL = hwid,%WINDIR%\Inf\Hal.inf
Value hwid,%WINDIR%\Inf\Hal.inf
(where hwid is either MPS_UP or ACPIAPIC_UP)
Example UpdateUPHAL = MPS_UP,%WINDIR%\Inf\Hal.inf
Comments Valid only for Sysprep.inf. Required if the master installation is built on an APIC multiprocessor computer and the image of that master installation is on compatible APIC uniprocessor or multiprocessor destination computers.
Not sure if this helps but here is some additional info regarding master images/sysprep and HT.
From MS
To ensure that Sysprep images are compatible with systems that enable hyper-threading, you must create the master image on one of the following types of systems:
An ACPI-compliant computer that enables hyper-threading
An APIC-based computer running ACPI that Device Manager refers to as "ACPI Uniprocessor PC"
An ACPI-compliant multiprocessor computer
If you do not create the Sysprep image on one of these types of systems, Windows is not able to update the system to use multiple processors. A Sysprep image made on an ACPI-compliant multiprocessor computer will run in a multiprocessor configuration even if support for hyper-threading is turned off in the BIOS.
Windows automatically uses the hyper-threading capabilities of the processor if the following conditions are present:
The computer hardware supports hyper-threading and this functionality is enabled in the computer's BIOS.
Hyper-threading functionality is installed in the computer processor.
The Windows installation uses the ACPI Uniprocessor PC HAL.
Windows detects one or more processors or enabled threads.
When these conditions are present, Windows automatically updates the HAL to the "ACPI Multiprocessor PC" HAL and and installs an additional processor, which is listed under Processors in Device Manager.
When running, the HAL type must be "ACPI Multiprocessor PC" or the hyper-threading capabilities of the processor will not be used. If the HAL type is "ACPI Uniprocessor PC," then one or more of the previously listed conditions is not present.
Posted by:
Francoisracine
19 years ago
Posted by:
MacAddict
19 years ago
I have been able to create an image with a Uniprocessor pc (gx260) and install it on a GX270 and GX280 with hp.
This is what I did:
When installing xp from scratch on the model pc, press F5 right when the blue setup screen appears (it is a hidden option).
Then you need to scroll up (you only see 2 options at a time) until you select ACPI Uniprocessor CPU.
Then continue with the xp install and customization, etc.
Add this line to your sysprep unattended section:
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
DriverSigningPolicy=Ignore
TargetPath=\WINDOWS
UpdateHAL=ACPI APIC_MP,%windir%\inf\hal.inf
Good luck,
MA
This is what I did:
When installing xp from scratch on the model pc, press F5 right when the blue setup screen appears (it is a hidden option).
Then you need to scroll up (you only see 2 options at a time) until you select ACPI Uniprocessor CPU.
Then continue with the xp install and customization, etc.
Add this line to your sysprep unattended section:
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
DriverSigningPolicy=Ignore
TargetPath=\WINDOWS
UpdateHAL=ACPI APIC_MP,%windir%\inf\hal.inf
Good luck,
MA
Posted by:
olivier
19 years ago
Posted by:
Francoisracine
19 years ago
Posted by:
jb347
19 years ago
I'd be interested in finding a solution to this problem as well.
Currently we have two images: one HT (multiprocessor HAL) image and one ACPI (single processor) image. We create the image on the HT computer, sysprep it, and then ghost it for backup. According to MS KB309283 a multiprocessor HAL can go down to an ACPI, but not vice versa.
We then reboot it and disable HT in the BIOS. Then we change the HAL in the device manager, reboot it a couple times, and sysprep/ghost again.
This works OK, but I would really like to get back to 1 image.
Currently we have two images: one HT (multiprocessor HAL) image and one ACPI (single processor) image. We create the image on the HT computer, sysprep it, and then ghost it for backup. According to MS KB309283 a multiprocessor HAL can go down to an ACPI, but not vice versa.
We then reboot it and disable HT in the BIOS. Then we change the HAL in the device manager, reboot it a couple times, and sysprep/ghost again.
This works OK, but I would really like to get back to 1 image.
Posted by:
Francoisracine
19 years ago
Posted by:
olivier
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.