Using Windows XP Image on a different type of motherboard

[pilonbrad]

Hey,

At the High School I work at we are using Netware 6.5 as our N/OS and Zenworks 4.01ir7.

We have several different king of Windows XP Professional SP2 images, one image for each below:

1) Dell GX260
2)Dell GX280
3) Dell GX620
4) Dell Optiplex 170L
5) IBM Netvista Tye 6792
6) IBM Netvista Type 6578
7) Seanix Victoria
8) Tandex PIV

There are few other different vendors and model numbers as well but the above are the main ones.

Recently we got several Dell GX260 computers in and at the time we didn't have an image made for this model.

Because the Dell GX280 is similar (i.e. uses IDE hard drives), but it did have a different motherboard and chipset, I decided to try and drop the image from the Dell GX280 on to the Dell GX260.

The image did get dropped down, but when I booted up the Dell GX260 there were a lot of problems with it such as not being able to log into the network etc. I got all the drivers and INF files for the Dell GX 260 and ran them to match the Dell GX260 as the original image dropped down was from the Dell GX280 as mentioned above.

I decided to try and run a Windows XP Repair Install and there were still problems.

When I decided to do a full clean install on the Dell GX260 aall the problems I was having went away and everything worked great.

I know Windows XP uses a file called Hal.dll (hardware access layer).

Because my supervisor at the Board usually order all kinds of different computers (i.e. different motherboards, chipsets etc.) is there a way I could use a previous image made which has a different motherboard and chipset (i.e. Dell GX280) on to another computer with a different motherboard and chipset (i.e Dell GX260)?

If it is possible how would I go about doing this? Is there a program or something that would allow this?

The reason I wish the above was possible is to save valuable time. Building an image from scratch is very time consuming when you factor in all the configuration and applications needed on the image.

If it is possible to drop an image from one computer with a different motherboard and chipset on to another computer that has a different motherboard and chipset, all I would have to do is update the drivers and INF files, but as mentioned previously I wasn't successful at doing it.

Thanks for your time!

 

[bcastner]

Hal.dll is not the issue. Chipset level drivers -- including USB, 1394, any ports, video adapter drivers, drive controller drivers, Network adapter drivers, etc. are independent of the Hal.dll

Hal.dll choices essentially reflect ACPI BIOS capability, and multiprocessor support. They are "canned" hal.dll's and not customized during installation other than selecting which canned hal.dll to use.

[c]Reading List[/c]

A very good guide:

http://episteme.arstechnica.com/eve/...4/m/1400925745

This KB is no longer on US sites, but provides valuable information

http://support.microsoft.com/default...d=kb;nl;314070

Copy and paste the listing at article end into Notepad. File, Save as, controllers.reg This has to be a record for the length of a .REG file in a MS KB article.

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

Then double click controllers.reg and merge with your registry.

All the possible options for accomplishing your move:

http://www.windowsreinstall.com/inst...oard/win2k.htm

You can usually "fix" any problems after the move by a repair reinstall of XP. ; I like how Fred Langa explains the process:

http://www.informationweek.com/LP/sh...leID=189400897

Look at Snap Deploy and the Universal Deply by Acronis:

http://www.acronis.com/enterprise/products/snapdeploy/

.

Users Helping Users

 

[pilonbrad]

Hey bcastner,

Thanks for the information it's helpful.

I'm really interested about the products for Acronis.

I noticed on the acronis website of a program called True Image 9.1 which uses a snap in utility called universal restore which allows you to take an image of a computer and restore it to a computer with completely different hardware.

So will the Acronis Snap Deploy allow me to do the samething, where I can take an image of one computer and put it on a computer which as different hardware?

Also, what other companies out there other than Acronis have imaging utilties where you can make a master image on a Windows XP computer and image other computers with different hardware (i.e. diferent motherboard, processor etc..)?

Before I decide to purchase a product I want to make sure I'm purchasing the best imaging product for what I need to do!

Thanks again for your help!

 

[bcastner]

True Image Server for Windows or True Image Enterprise Server allows you to use Universal Restore. True Image for Workstation does not.

Snap Deploy allows you to use Universal Restore, which is why I gave the the information and link above.



____________________________
Users Helping Users

 

[DTracy]

Mr. Castner,

When you move an image of XP from one workstation to another what happens when the election is held and all the controllers don't match the original install? Does XP cancel the license?

Regards,

David.

 

[bcastner]

You will be asked to re-activate an installation to a computer that is not the original; and since April,2005 will be asked to activate even a reinstallation to the original machine if using OEM images of XP. You will be required to use the phone re-activation method to explain what you have done, as the internet activation option will not be available. This is true for all images except VLK since April 18, 2005.

Installing a replacement motherboard will change the IDE controller, and usually will mean that you change to a new, faster, processor. If the processor is one with a serial number (Pentium III), then you lose a third vote — including when you change to a processor with no serial number, such as an Athlon. If you also add RAM, or if the motherboard is one with an on-board SCSI adapter, that makes four or five categories now voting No — you would need an unchanged NIC to avoid having to call in for reactivation. If the new motherboard also has inbuilt video (and possibly even a NIC of its own!), you run right out of Yes votes with this one hardware change.

Again, this doesn’t stop you from making such a hardware change, nor from using Windows XP thereafter. The phone-in reactivation option was created for just this type of situation. Also, this is an extreme example. Due to the onboard features of some motherboards, this one hardware change is equivalent to several changes at once.

Source:

http://www.aumha.org/win5/a/wpa.htm

http://www.microsoft.com/technet/prodtechnol/winxppro/evaluate/xpactiv.mspx

The activations will not be accepted if using the same COA key in more than one instance unless the image is created using the original SLP installation by the OEM manufacturer -- and multiple installs will not be accepted by an installation done using the computer case COA and restore media provided by the OEM.


____________________________
Users Helping Users