I've set up a shiny new base image on a Pentium 4 3ghz Dual Core machine (Hyperthreading?)
Anyway we're getting some new Intel Core 2 Duo machines in and I was wondering if I should expect to face any issues relating to the tranfer of this image to the new machines. I have changed the disk controllers to Standard ones.
SID is not relevant on our network setup.
Thanks
Hi,
Most problems you will meet are to do with motherboard drivers - particularly Lan and Video drivers. You will probably need to run the drivers setup disk after you push the image out to the new machine. That said it also depends on how you are applying the image, GHost, RIS WDS, etc. There will/may be a way of adding drivers during the image load process. There are loads of posts on this area under WDS/RIS on this site.
Cheers
Peter
I'd echo that. I personally use Ghost and ghostcast with sysprepped images.
Drivers, yes. HAL..maybe not so much..HT to 2core might work.
What I always do (which is where I differ from our LEA and their builds) is I build on VM, install as usual, then the final pre-sysprep step I take is to go into device manager, right click on "computer" in device manager, and change it from "ACPI" to "Standard PC" and let it reboot and redetect hardware.
I added 1 line in sysprep to direct XP to look at the hardware and choose the appropriate HAL on boot, then I run sysprep and ghost the image.
I'm on my 6th build now...and it'll run on anything.
Hi,Originally Posted by Sirbendy
Can you put a bit more 'meat' around the method you use please?
Alan
oh oh oh, share!. a kingdom for your line!.
I think he means
UpdateUPHAL - for uni-processors
UpdateHAL - for multi processors
UpdateInstalledDrivers - to detect drivers
- Using UpdateUPHAL and UpdateHAL Within SysPrep.inf
UpdateUPHAL values within sysprep.inf require you to specify a Unprocessed HAL to install. The list of available UniProcessor HAL’s that can be used with UpdateUPHAL are:
UpdateUPHAL = “ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf”
UpdateUPHAL = “ACPIPIC_UP,%WINDIR%\Inf\Hal.inf”
UpdateUPHAL = “MPS_UP,%WINDIR%\Inf\Hal.inf”
UpdateHAL values within sysprep.inf require you to specify a MultiProcesser HAL to install. The list of available MultiProcessor HAL’s that can be used with UpdateHAL are:
UpdateHAL = “ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf”
UpdateHAL = “MPS_MP,%WINDIR%\Inf\Hal.inf”
UpdateHAL = “SYSPRO_MP,%WINDIR%\Inf\Hal.inf”
Make sure you are picking the proper HAL’s for your computers as this can BSOD your cloned computers or give you extreme performance hits if the wrong one is picked
"Standard PC," Non-ACPI PIC HAL (Hal.dll)
• Standard PC
"MPS Uniprocessor PC," Non-ACPI APIC UP HAL (Halapic.dll)
• Standard PC
• MPS Uniprocessor
• MPS Multiprocessor
"MPS Multiprocessor PC," Non-ACPI APIC MP HAL (Halmps.dll)
• Standard PC
• MPS Multiprocessor
"Advanced Configuration and Power Interface (ACPI) PC," ACPI PIC HAL (Halacpi.dll)
• Standard PC
• Advanced Configuration and Power Interface (ACPI) PC
"ACPI Uniprocessor PC," ACPI APIC UP HAL (Halaacpi.dll)
• Standard PC
• Advanced Configuration and Power Interface (ACPI) PC
• ACPI Uniprocessor
• ACPI Multiprocessor
"ACPI Multiprocessor PC," ACPI APIC MP HAL (Halmacpi.dll)
• Standard PC
• Advanced Configuration and Power Interface (ACPI) PC
• ACPI Multiprocessor
• MPS Multiprocessor
Last edited by somabc; 16th July 2008 at 02:09 PM.
strawberry (16th July 2008)
Well it worked
Probably not the most effective way to do things but if they're ghosted at factory using our image at least we don't have to be pressured into getting loads of new images built during the summer.
Spot on...That and running "Sysprep -bmsd" from the command line to prepopulate the sysprep mass storage section. As I say - it's worked on all of our kit. We have everything from P2/350, through P3 400-900, P4, P4HT, Duron, Athlon, X2, C2D, Xeon etc, desktops and laptops, IDE and SATA.
I've yet to find a machine it won't run with. It even runs on my home rigs/VAIO/inspiron. I did a "flat" version containing just XP and office for staff machines, to save the headache when they bring in machines and say "it's broken". Boot with ghost, hand it back 20 minutes later, job done.
Come to that, I've got a nicely sorted image for my/family PCs in the same vein. Makes repair a doddle.
sorry to be entirely dim, have you got an example to hand?. I would test it but it's hard to do so without destorying machines!.
an example of...?
how it would be used, is it just a case of dropping in the following into the unattended section?
UpdateUPHAL = “ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf”
UpdateUPHAL = “ACPIPIC_UP,%WINDIR%\Inf\Hal.inf”
UpdateUPHAL = “MPS_UP,%WINDIR%\Inf\Hal.inf”
or would you just use the 1 you need?
Last edited by strawberry; 18th July 2008 at 09:42 AM.
I use the second...seems to work fine.
As I say - before you sysprep, do the "device manager", "computer", "set to standard PC" bit. Then that line in sysprep and the "sysprep -bmsd" command...and run sysprep to do the job.
strawberry (18th July 2008)
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote