Ghost Advice for Cloning Systems

[nevets2001uk]

We have just purchased a copy of Norton Ghost 14 with the intention of using it to clone systems to cut down our rebuild times.

We have numerous Dell systems from accross 5 years of PC buying so we will probably need to create a number of different images so that the drivers etc work.

Do we need to use sysprep first to allow us to set different computer names? If so are there any guides around to help me learn the process?

One recommendation that was made was to install the dell system without adding the specific drivers which may allow us to utilise a single image for all systems which after restoring to a system we then install the drivers seperately. Does this approach work?

Steve G (MCSE / MCSA:Messaging)

 

[linney]

Anything here?

How to use Sysprep with Ghost

http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2000081610075225

http://www.google.com/search?q=ghost+sysprep+computer+name&rls=com.microsoft:

 

[wahnula]

One recommendation that was made was to install the dell system without adding the specific drivers which may allow us to utilise a single image for all systems...

Unless all the systems have the same chipset I don't think this will work. You will have to clone from a system, that means that system's chipset drivers will already be loaded. When you go to install to another chipset, you could be out of luck and XP will refuse to boot.

How many PCs in the fleet? It might be wise to group them by chipset, then make an image that will work for each chipset. It won't matter if the LAN, audio, etc. are different, like you say you can reload the drivers after the fact.

Personally I don't see the value to this method, unless there's tons of apps to install, configure and activate. A slipstreamed XP CD like BartPE or NliteOS for each machine might be a better option, but I've been wrong before.



Tony

Users helping Users...

 

[SimonDavies]

You could however look into UIU (from the guys who first made Ghost all those years ago).

http://www.uiu4you.com/uiu_description.html

Essentially it replaces Sysprep (actually it uses Sysprep but you run UIU instead), replaces the HAL and installs the drivers onto the image, that way you have a completely hardware independant build that you can roll out across the board. The only downside is that of course it will cost money.



SimonD.

The real world is not about exam scores, it's about ability.

 

[DTSMAN]

I work in the point of sale industry with many different hardware platforms and device drivers and OPOS drivers. We have pc specific images stored away for each hardware platform we turn out.
We also have an image of a bootable hard drive, with the I386 folder and all the utility folders we need containing the drivers to build any pc we service. A tech can install this hard drive in any pc and run setup from the I386 and then point the installation to the folder that contains this piece of hardware's drivers. It loads quickly this way. Haven't used the UIU, we just change its name and ip manually.
Works good for us, may work for you?.

Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com