Symantec Ghost 8 Problem - HELP

  • Thread starter Thread starter DMc2005
  • Start date Start date
D

DMc2005

Hi

Let me explain the setup of what I am trying to do.

We currently have about 80 machines that we have to Ghost (Symantec Ghost 8)
with different versions of Office, ie 97, 2000, XP and 2003. The machines
are split into 8 rooms.

At present I am trying to remote gohst the machines via a network and
mutlicast. This works on some models with no problems. The machines rename
themselves with unqiue names. However on one model, the image is copied onto
the machine successfully but then then when the machine reboots a message
similar to the following appears,

polling 123.123.123.123 to imageserver.

We have to hide the partition and rename the machines manually.

Any ideas, this is causing big problems. Anyone had experience of GHost
doing this?

D
 
From: "DMc2005" <[email protected]>

| Hi
|
| Let me explain the setup of what I am trying to do.
|
| We currently have about 80 machines that we have to Ghost (Symantec Ghost 8)
| with different versions of Office, ie 97, 2000, XP and 2003. The machines
| are split into 8 rooms.
|
| At present I am trying to remote gohst the machines via a network and
| mutlicast. This works on some models with no problems. The machines rename
| themselves with unqiue names. However on one model, the image is copied onto
| the machine successfully but then then when the machine reboots a message
| similar to the following appears,
|
| polling 123.123.123.123 to imageserver.
|
| We have to hide the partition and rename the machines manually.
|
| Any ideas, this is causing big problems. Anyone had experience of GHost
| doing this?
|
| D
|

Why do you think this is related to Win2K and NOT just to Symantec Enterprise Ghost v8.
problem ?

I read this and the post in Symantec News Groups. No where do you sate what the platforms
boot from. Are you booting destination PCs from a Ghost Boot Disk ? Is the machine using
Ent. Ghost 8 a Win2K (I call it the Ghost Server). Are there and Ethernet devices blocking
Multi-Cast IP between the PCs and the Ghost Server ? Is the Ghost server optimized for many
PCs connected to it (NIC buffer sizes) and it is a server or workstation NIC ?
 
David H. Lipman said:
From: "DMc2005" <[email protected]>

| Hi
|
| Let me explain the setup of what I am trying to do.
|
| We currently have about 80 machines that we have to Ghost (Symantec
Ghost 8)
| with different versions of Office, ie 97, 2000, XP and 2003. The
machines
| are split into 8 rooms.
|
| At present I am trying to remote gohst the machines via a network and
| mutlicast. This works on some models with no problems. The machines
rename
| themselves with unqiue names. However on one model, the image is copied
onto
| the machine successfully but then then when the machine reboots a
message
| similar to the following appears,
|
| polling 123.123.123.123 to imageserver.
|
| We have to hide the partition and rename the machines manually.
|
| Any ideas, this is causing big problems. Anyone had experience of GHost
| doing this?
|
| D
|

Why do you think this is related to Win2K and NOT just to Symantec
Enterprise Ghost v8.
problem ?

I read this and the post in Symantec News Groups. No where do you sate
what the platforms
boot from. Are you booting destination PCs from a Ghost Boot Disk ? Is
the machine using
Ent. Ghost 8 a Win2K (I call it the Ghost Server). Are there and Ethernet
devices blocking
Multi-Cast IP between the PCs and the Ghost Server ? Is the Ghost server
optimized for many
PCs connected to it (NIC buffer sizes) and it is a server or workstation
NIC ?
Click to expand...
Windows 2000 is the operating system and it is from the network image server
it is being run. no floppy disks are being used.
The server can handle many images being copied at one as it works on one
model of machines where we have 3 rooms of them.

Sorry, It support is not my main job. I have followed the procedures i used
for the working machines. Still cannot work out what is wrong, could it be a
on board network card problem?
 
From: "DMc2005" <[email protected]>


| Windows 2000 is the operating system and it is from the network image server
| it is being run. no floppy disks are being used.
| The server can handle many images being copied at one as it works on one
| model of machines where we have 3 rooms of them.
|
| Sorry, It support is not my main job. I have followed the procedures i used
| for the working machines. Still cannot work out what is wrong, could it be a
| on board network card problem?
|

If I am to uderstand this correctly...

You have Ent. Ghost 8 on a Ghost server, Win2K. All workstations are Win2K and all
workstations have Ent. Ghost 8 installed. And you are trying to push an image ? An image
of a completely setup PC or a differential setup so you can push an application to the
workstations ?
 
The same PC setup but a different version of Office installed. I think I
have also been responding to your posts in Google Groups, there might have
been something I have done different, as i had to manually add a network
card to ghost boot disk wizard, as it was not in the list, the machines that
work did not need this!

D
 
From: "DMc2005" <[email protected]>

| The same PC setup but a different version of Office installed. I think I
| have also been responding to your posts in Google Groups, there might have
| been something I have done different, as i had to manually add a network
| card to ghost boot disk wizard, as it was not in the list, the machines that
| work did not need this!

So you are using a Ghost Boot Disk on the destination PCs. Then you are not booting Win2K
to access the Ghost Server. You are booting from a DOS (PCDOS or MSDOS ?) based Ghost Boot
Disk to acquire an fully setup imge from the Ghost server.

If that is the case, what exactly is the NIC in the affected PC and is this an embedded NIC
or a PCI card ?
 
From: "DMc2004" <[email protected]>

| The card is a SIS 900 model network card and from my understanding it is
| onboard.

So it is an embedded chip-set. Are you using Crynwar Packet Drivers or NDIS drivers in the
..\NET directory ?

Do you have spare 3COM 3c905 NICs available ?
 
Hi
as far as i can tell we are using ndis drivers that come with the downaloded
from the sis.com website.

We are only using the buildin card on the machines and do not have any other
cards availalbe. There are about 40 machines of this type.

Is it becuase it is onbaord that the probelms are arising or is it becuase
of network driver!

This should work because we can run the ghost from floppy disk no probelm,
but are faced with the problem of having to use disks and rename the machines
is time we ghost them.

D
 
From: "DMc2004" <[email protected]>

| Hi
| as far as i can tell we are using ndis drivers that come with the downaloded
| from the sis.com website.
|
| We are only using the buildin card on the machines and do not have any other
| cards availalbe. There are about 40 machines of this type.
|
| Is it becuase it is onbaord that the probelms are arising or is it becuase
| of network driver!
|
| This should work because we can run the ghost from floppy disk no probelm,
| but are faced with the problem of having to use disks and rename the machines
| is time we ghost them.
|

I would have to say it is either a problem with the NDIS2 driver or a configuration problem
in PROTOCOL.INI

You might want to see if you can switch to Crynmwar Packet Drivers. I believe Ghost.EXE is
Packet Driver comopliant and actually uses a 'shim' to make NDIS useful for a packet Driver
compliant software.

You might also want to double check the .\ghost\WATTCP.CFG is configured properly and if it
is, when you boot off the Ghost Boot Disk you should be able to "ping" the IP address of
that PC from a Win2K PC.
 
That solved the problem. I have one more issue that has developed. When i
reghost an image back to the image server i get the message about a NTFS
logfile that has not been flushed and checkdisk should be run. i have been
running it on the client machine but the message always appears!

not sure why.
 
From: "DMc2005" <[email protected]>

| That solved the problem. I have one more issue that has developed. When i
| reghost an image back to the image server i get the message about a NTFS
| logfile that has not been flushed and checkdisk should be run. i have been
| running it on the client machine but the message always appears!
|

I figured the Crynwr Packet Driver would do the trick.

See, it wasn't a Win2K problem at all. I never thought it was.

The message "...NTFS logfile that has not been flushed and checkdisk should be run..."
Sounds like the platform was not shutdown properly after executing Sysprep and prior to
creating the Ghost image. It is basically telling you that running CHKDSK /F was warranted
on the source PC.
 
Back
Top