Sysprep

[Guest]

I want to use Sysprep in conjunction with Symantec Ghost to create an image
of Windows 2000 that can be deployed on machines with different hardware
configurations (i.e., different chipsets, hard drives types and sizes, etc.).
I was told this is possible through the use of Sysprep but how do you
configure it so that it will work on any machine regardless of what hardware
is installed? Thanks!

 

[David H. Lipman]

NO !

The platforms have to be the same. For example cloning a Dell GX240 to another GX240 will
work. Cloning a Dell GX240 to a Dell GX400 will fail. You need to keep an image for each
model platform.

--
Dave




| I want to use Sysprep in conjunction with Symantec Ghost to create an image
| of Windows 2000 that can be deployed on machines with different hardware
| configurations (i.e., different chipsets, hard drives types and sizes, etc.).
| I was told this is possible through the use of Sysprep but how do you
| configure it so that it will work on any machine regardless of what hardware
| is installed? Thanks!

 

[hallstein]

The platforms have to be the same. For example cloning a Dell GX240 to another GX240 will
work. Cloning a Dell GX240 to a Dell GX400 will fail. You need to keep an image for each
model platform.

Mike, do not listen to David.
He is VERY incorrect. We run the same image on both workstations and
Laptops.

Learn more about ghosting at e.g. http://www.gc.peachnet.edu/www/wbeck/

 

[David H. Lipman]

No I am very correct. I have used Enterprise Ghost v7 ~ 8 and have maintained NUMEROUS
Ghost images and have experimented much. The source and destination must have 99% of the
same motherboard chip-sets or a lock-up or BSoD will be the result. Now a repair install
*may* fix the destination platform. The chances however of a successful repair install is
higher with WinXP than Win2K. No matter how you slice it, separate images for each model
platform need to be kept.

If you have a desktop and notebook that a cloned image can be performed than you are in the
minority and have been lucky since the two have 99% of the same chip-sets.

What was the Desktop platform ?
What was the Notebook model ?

How did you transfer the Ghost image from the Desktop Platform to the Notebook Platform ?

--
Dave




| David H. Lipman wrote:
| > The platforms have to be the same. For example cloning a Dell GX240 to another GX240
will
| > work. Cloning a Dell GX240 to a Dell GX400 will fail. You need to keep an image for
each
| > model platform.
|
| Mike, do not listen to David.
| He is VERY incorrect. We run the same image on both workstations and
| Laptops.
|
| Learn more about ghosting at e.g. http://www.gc.peachnet.edu/www/wbeck/

 

[John John]

Seems to me that if you "path" sysprep to the proper hardware drivers it
should work. Shouldn't it? Or am I missing something?

John

 

[David H. Lipman]

It may be possible but you would have to identify all the different hardware aspects, create
a tree of installation files and edit the SYSPREP.INF. Not an easy task without much
research, experimentation and testing.

--
Dave




| Seems to me that if you "path" sysprep to the proper hardware drivers it
| should work. Shouldn't it? Or am I missing something?
|
| John
|

 

[Guest]

Hi,
In order to deploy an image using sysprep, you must have the same hal type
and kernel on the source abd target systems. There are ways with which you
can install third party mass storage drivers and nic drivers by making
changes in the textsetup.oem and sysprep.inf files, so there might be a faint
chance of a way to edit these files in order to identify all hal types. But
as David said, this must be very complicated and to my knowledge this gut
feeling, this may be impossible too. You cal also refer the following links
to check the sysprep requirements.

http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/depovg/depxpii.mspx
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/default.mspx
http://support.microsoft.com/default.aspx?scid=kb;en-us;216915
http://support.microsoft.com/default.aspx?scid=kb;en-us;814616
http://support.microsoft.com/default.aspx?scid=kb;en-us;838856
http://support.microsoft.com/default.aspx?scid=kb;en-us;830958
http://support.microsoft.com/default.aspx?scid=kb;en-us;228908

Lukesh