Sysprep and Ghost

[U2World]

Hi all,

Can anyone help me use sysprep and ghost togher to successfully ghost a
2000 server?
I have HP LP1000r with a symbios ultra3 pci scsi (lsi logic) and a HP
DL360 with a smart arrray 5i. I can't seem to get the sysprep.inf file
written correctly or it's just not getting into the ghost image that
I'm creating.

Has anyone succussfully done this??

Thanks,

Josh

 

[David H. Lipman]

From: <[email protected]>

| Hi all,
|
| Can anyone help me use sysprep and ghost togher to successfully ghost a
| 2000 server?
| I have HP LP1000r with a symbios ultra3 pci scsi (lsi logic) and a HP
| DL360 with a smart arrray 5i. I can't seem to get the sysprep.inf file
| written correctly or it's just not getting into the ghost image that
| I'm creating.
|
| Has anyone succussfully done this??
|
| Thanks,
|
| Josh

You can't cross different platform models. If both platforms were the chances are highly
likely it will work.

However, going from a HP LP1000r to a HP DL360 is bound to fail.

 

[U2World]

David,

Thanks for input David. But according to Microsoft you can use sysprep
in conjuction with ghost to cross platforms. Using sysprep you can add
the new hardware drivers. I'm just now doing it right.
If there is anyone out there who has done it, please help.

Thanks,

Josh

 

[David H. Lipman]

From: <[email protected]>

| David,
|
| Thanks for input David. But according to Microsoft you can use sysprep
| in conjuction with ghost to cross platforms. Using sysprep you can add
| the new hardware drivers. I'm just now doing it right.
| If there is anyone out there who has done it, please help.
|
| Thanks,
|
| Josh
|


You can. It is possible but... only with *much work* in setting up drivers for the
difference in the hardware and setting up the appropriate INF and INI files to use the
varied hardware drivers. It has been discussed in the Symantec hierarchy News Groups.
Example groups;
symantec.support.network.ghost.general

and

symantec.customerservice.general


Basically as a rule of thumb, if the motherboards of the two different platforms don't share
at least 90% of the same chip-sets then the Clone will fail upon restoration. Add to that
the complexity of the OS and HAL considerations with disk array considerations. There are
also notes on Suymantec's web site about the use og Ghost inconjunction with disk arrays.

 

[U2World]

David,

I understand that the hardware differences may not allow this to
happen. Maybe you can answer this for me. Let me give you a little
more detail.
I'm using ghost 8 corporate edition, and the sysprep 1.1 as suggested
by microsoft. I'm trying to ghost win2k server sp4.
I can get ghost to successfully run sysprep, I beleive that I have my
sysprep.ini file edited properly, but not 100% sure. When I push the
image to the new hardware, the little progress bar only gets anywhere
from 1/2 to 3/4 of the way through, then it blue screens. The error is
a stop 7B, INACCESSABLE_BOOT_DEVICE.
Should this boot into pcDOS or go straight to windows? When I reboot
the image source, it boots to pcDOS, then reboots to windows, and I get
the mini wizard....

 

[David H. Lipman]

From: <[email protected]>

| David,
|
| I understand that the hardware differences may not allow this to
| happen. Maybe you can answer this for me. Let me give you a little
| more detail.
| I'm using ghost 8 corporate edition, and the sysprep 1.1 as suggested
| by microsoft. I'm trying to ghost win2k server sp4.
| I can get ghost to successfully run sysprep, I beleive that I have my
| sysprep.ini file edited properly, but not 100% sure. When I push the
| image to the new hardware, the little progress bar only gets anywhere
| from 1/2 to 3/4 of the way through, then it blue screens. The error is
| a stop 7B, INACCESSABLE_BOOT_DEVICE.
| Should this boot into pcDOS or go straight to windows? When I reboot
| the image source, it boots to pcDOS, then reboots to windows, and I get
| the mini wizard....
|

I have used Symantec Enterprise v7.x ~ v8.

You need to fully understand the concept of how arrays are seen by the OS. Is the RAID
performed by the OS or are you using a RAID Controller. If the OS handles RAID then you
WILL have problems. If you have a RAID controller then the RAID controller passes one large
virtual drive to the OS. Either the Win2K Server OS or PC/MS-DOS used on the Ghost Boot
Disk.

I again suggest you go to...

symantec.support.network.ghost.general
or
symantec.customerservice.general

This is NOT a windows problem but a Ghost problem and Ghost is by Symantec.

PDF Manuals...

ftp://ftp.symantec.com/public/english_us_canada/products/ghost/manuals/symghost_8/

Read p.156
ftp://ftp.symantec.com/public/english_us_canada/products/ghost/manuals/symghost_8/Ghost_ref_guide.pdf

 

[U2World]

Actually, this is a windows problem. The isn't an actual raid. Just a
raid controller. The problem is with sysprep. Mircosoft engineers
have been working on this for the past day and a half. The problem was
with the raid driver. They had to play with the driver to get to work
with the new hardware. So this was not a ghost issue. It is a true
MICROSOFT issue and as soon as I get the information from the engineer,
I will pass it along.
The statement about 90% of hardware should be the same, is also not
true. Microsoft used sysprep and ghost to push and image from a
lp1000r to a Dell 2850. 2 completley different systems.

Thanks,

Josh

 

[David H. Lipman]

From: <[email protected]>

| Actually, this is a windows problem. The isn't an actual raid. Just a
| raid controller. The problem is with sysprep. Mircosoft engineers
| have been working on this for the past day and a half. The problem was
| with the raid driver. They had to play with the driver to get to work
| with the new hardware. So this was not a ghost issue. It is a true
| MICROSOFT issue and as soon as I get the information from the engineer,
| I will pass it along.
| The statement about 90% of hardware should be the same, is also not
| true. Microsoft used sysprep and ghost to push and image from a
| lp1000r to a Dell 2850. 2 completley different systems.
|
| Thanks,
|
| Josh
|


Maybe they did however there is pertinent information on the setup of sysprer and I'm sure
it is NOT a simple sysprerp.exe and sysprerp.inf functionality.

All I can say is -- Good Luck !

 

[U2World]

David,

The problem was, we were using the wrong version of sysprep. There a
couple of different version for w2k. The one that comes with the cd is
good untily you install service pack 2. Anything higher that sp2 you
need the newer version of sysprep. We were using the 1.1 from the
install cd. Then we dowloaded a 1.1 version from ms web site, it was
actually meant for XP and 2003 server. So when the engineer from
microsoft got it working in his lab, he sent us the sysprep.inf file
and that didn't work. So we asked the engineer to send us his copy and
it worked in our lab.
We successfully ghosted the prodution box this weekend. So here is a
copy of the sysprep.inf: It was pretty simple. Nothing speacial. I
think that it's just a disclaimer. Because they do this all the time.
Also winpe will also do this for you as well.

Thanks.

-
;SetupMgrTag
[Unattended]
Driversigningpolicy = Ignore
OemPreInstall = Yes
OemPnpDriversPath = Drivers\cpqcissm



[GuiUnattended]
OEMDuplicatorstring= ghost-test
TimeZone= 20

[UserData]
FullName= mckesson
OrgName= tsh
ComputerName= dbqscan1
ProductKey ="XXXXX-XXXXX-XXXXXX-XXXXXX-XXXXX"
ProductID = "XXXXX-XXXXX-XXXXXX-XXXXXX-XXXXX"
[Display]
BitsPerPel= 32
Xresolution= 1024
YResolution= 768

[LicenseFilePrintData]
AutoMode=PerSeat

[SetupMgr]
DistFolder= C:\sysprep\i386
DistShare= win2000dist

[Identification]
JoinDomain= lab

[Networking]
InstallDefaultComponents= Yes

[SysprepMassStorage]
PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11=
"c:\drivers\cpqcissm\cpqcissm.inf","\", "Smart Array 5x and 6x Driver
Diskette", "txtsetup.oem"

 

[David H. Lipman]

From: <[email protected]>

| David,
|
| The problem was, we were using the wrong version of sysprep. There a
| couple of different version for w2k. The one that comes with the cd is
| good untily you install service pack 2. Anything higher that sp2 you
| need the newer version of sysprep. We were using the 1.1 from the
| install cd. Then we dowloaded a 1.1 version from ms web site, it was
| actually meant for XP and 2003 server. So when the engineer from
| microsoft got it working in his lab, he sent us the sysprep.inf file
| and that didn't work. So we asked the engineer to send us his copy and
| it worked in our lab.
| We successfully ghosted the prodution box this weekend. So here is a
| copy of the sysprep.inf: It was pretty simple. Nothing speacial. I
| think that it's just a disclaimer. Because they do this all the time.
| Also winpe will also do this for you as well.
|
| Thanks.
|

< snip >

Well here is how your array was made easier...

[SysprepMassStorage]
PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11=
"c:\drivers\cpqcissm\cpqcissm.inf","\", "Smart Array 5x and 6x Driver Diskette",
"txtsetup.oem"