One image for multiple hardware platforms?

[Audiofight]

Here's what I am working on:

I want to build a base image (later to be expanded on when working) and would like to design one image that will work on multiple hardware platforms. We are using 7 or 8 different Toshiba models of laptops ranging from P3 powered to Centrino powered. We have since switched to Dell and have 2 Dell laptops models with Centrino processors as well as 2 Dell desktops models with socket 478 processors. All in all, we are supporting over 2200 systems.

As you can see, having a base image for each laptop/desktop would take up alot of space and time to design. The only difference in each base image is the hardware drivers that are loaded. The same WindowsXP Pro OS is loaded along with the various software.

How can I pull the driver list out of the OS and make it re-detect and re-install the drivers upon the initial boot?

I have all the necessary drivers sorted and stored ready for stuffing into the appropriate directory in the image for Windows to find. Ideally, I would like to have this automate so that any new hires to the company won't have to constantly research which drivers are for which system and what-not.

 

[mikecel79]

Download Sysprep and the documentation from Microsoft. It can eaisly accomplish this for you. I have a single Win2k image that supports over 10 different models of laptops and desktop machines.

With over 2200 machines I'm surprised you haven't been using this already.

 

[Audiofight]

I have only been working here for 2 months and am looking at ways to design and deploy updated images. It makes it a pain to apply an update to 15 different images, especially when you don't have the hardware to work with.

I am starting to look at the Sysprep tool and it hasn't quite done the trick yet, but I am sure it is something I am not doing right.

The problem I am running into with it is the driver installation. I could easily just store the appropriate drivers, all catergorized and labeled, on the image itself and manually install anything that doesn't automatically find itself. But, automation will be much better.

 

[Phoenix86]

I have a writeup on how to swap mobos w/o reinstalling windows. It's basically the sysprep process used for imaging. It's written for replacing mobos, but there's some good info in there for imaging since it discusses sysprep and it's issues.

Text

 

[mikecel79]

If you want to PM me I can give you more details as to what we do where I work. As I said I have a single image running on over 10 different types of machines. Last I checked there were some 80+ different drivers for all the hardware and when Sysprep runs it only install the drivers that are required. Nothing else.

PM and I can give you more details.

 

[Audiofight]

I have figured out how to configure the sysprep.ini to look for additional OEM drivers. Unfortunately, 4 o'clock came around and I just shut the test machine down.

I will pick this up on Monday when I return to work.

But, I also managed to configure the ini file to set my Admin password and prompt the tech for the Workstation ID so we can prevent the duplicate ID problem we are addressing. With 2200 users spread out over 3 states and over 100 locations in Michigan alone, it is a daunting task to achieve.

 

[ktwebb]

I doubt sysprep will work on every single machine via image but I haven't found one yet that has given me a problem. Dell shop. From legacy 1650's to current 6850's.

 

[Audiofight]

Actually, I believe it will because you can specify where the PC looks for additional OEM drivers and can supply as many drivers as you want.

for instance:

make directory under C:\ called "drivers"

C:\Drivers and make additional directores for "Audio" "Video" "NIC" etc

Then point the sysprep.ini to this directory by adding this line to the [unattended] section

OemPnPDriversPath = drivers\audio;drivers\video;\drivers\nic

It will automatically append the %SystemRoot% to the directory and will scan those subfolders for its drivers. By dumping all the different models' drivers into their respective subfolder, it will make adding new hardware drivers easy as well as make the installation silent.

I will post more on Monday morning before lunch on how it goes, but I am very confident that it will work.

 

[Phoenix86]

Originally posted by: ktwebb
I doubt sysprep will work on every single machine via image but I haven't found one yet that has given me a problem. Dell shop. From legacy 1650's to current 6850's.

You'd be surprised, one image will indeed work on almost all machines. There are some limitations with HAL types, check the link I posted. There are MS KB articles linked in that thread about sysprep's limits.

Audiofight,

You are on the right path. Good Luck.

 

[Audiofight]

As of this morning, I have an image that will work on all our Dell models.

However, it is hard-locking my Toshiba test machine. I am not sure what is loading improperly or not loading at all that is necessary.

I will probably have to build the image on a Toshiba and see if it will move upward to the newer Dell systems. Otherwise, I will have to maintain 2 images instead of 14.