Professional Documents
Culture Documents
Copyright Notice
Copyright 1998–1999 Symantec Corporation.
All Rights Reserved.
Any technical documentation that is made available by Symantec Corporation is the
copyrighted work of Symantec Corporation and is owned by Symantec
Corporation.
NO WARRANTY. The technical documentation is being delivered to you
AS-IS and Symantec Corporation makes no warranty as to its accuracy or use. Any
use of the technical documentation or the information contained therein is at the
risk of the user. Documentation may include technical or other inaccuracies or
typographical errors. Symantec reserves the right to make changes without prior
notice.
No part of this publication may be copied without the express written permission
of Symantec Corporation, Peter Norton Group, 10201 Torre Avenue, Cupertino, CA
95014.
Trademarks
Symantec, the Symantec logo, Norton Ghost, Ghost Walker, Ghost Explorer, and
GDisk are trademarks of Symantec Corporation.
Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of
Microsoft Corporation. IBM, OS/2, and OS/2 Warp are registered trademarks of
International Business Machines Corporation. Novell and NetWare are registered
trademarks of Novell Corporation. 3Com and EtherLink are registered trademarks of
3Com Corporation. Compaq is a registered trademark of Compaq Corporation. Zip
and Jaz are registered trademarks of Iomega Corporation. SuperDisk is a trademark
of Imation Enterprises Corporation.
Other product names mentioned in this manual may be trademarks or registered
trademarks of their respective companies and are hereby acknowledged.
Printed in the United States of America.
10 9 8 7 6 5 4 3 2 1
C O N T E N T S
3
Appendix A Console security
Distribution ......................................................................................... 27
Changing Consoles ............................................................................. 28
Generating new certificates ................................................................ 28
NGServer password ............................................................................ 29
4
C H A
Getting started
P T E R
1
This guide outlines the process of rolling out and installing Norton Ghost
client software on machines with no operating system installed and on
Windows 9x/NT machines.
Note: The remainder of this document assumes you have installed Norton
Ghost Console.
Process overview
The following sections outline how to set up machines for cloning and
post-cloning configuration. The process differs for:
■ Machines with no operating systems installed.
■ Machines with Windows 9x/NT already installed.
5
Getting started
6
Process overview
7
Getting started
8
C H A
2
This chapter describes how to prepare your clients to receive images and
how to roll out images once the Console recognizes your client machines.
The process of rolling out and installing Norton Ghost client software
varies depending upon whether Windows 9x/NT is already installed on the
client. See “Process overview” on page 5 for an overview of both scenarios.
The template machine must have the same network card as the machines
that will receive the image. If you have multiple network cards in your
organization, you need an image for each one.
Similarly, especially for Windows NT, if you have machines with major
differences in hardware, like SCSI disks versus IDE disks, you need to have
separate images for these also.
9
Cloning your client machines
You use Norton Ghost Multicast Assist to create the boot partition image.
See “Multicast Assist Wizard” on page 19 for instructions.
You should use the same network card template you did to create the boot
disk. Save the image along with the image created in the previous step.
Both images are used on your client machine.
10
Preparing client machines to receive images
Install Norton Ghost 6.0 Client software on your source machine. The
machine will be discovered by Norton Ghost Console and the machine
configuration captured. The title for the new machine icon is the computer
name and the default user (the last user logged in). These settings may be
useful when cloning many clients, because the settings can be
automatically restored to the machine from which they were taken.
When you start Norton Ghost Console, the client machine appears in the
default machine folder. You can identify it by the computer name and the
default user.
Warning: After this step, the hard drive on the client PC will be completely
erased. The disk will contain only the Ghost boot partition, which is very
small. Do not perform this step unless you are sure you have copied all
data off the machine and that it is safe to proceed.
The next step is to load the boot partition image you created above onto
your client machine.
11
Cloning your client machines
The machine will be running the Norton Ghost Client for DOS. The
client can now be controlled from the Console.
12
Using Norton Ghost Console to clone client machines
13
Cloning your client machines
2 In the Clone tab, specify the image you have created from the source
machine.
14
Using Norton Ghost Console to clone client machines
4 Click OK.
Note: When executing a Console task, avoid using image files that do not
reside locally. Be aware that tasks are executed by the NGServer user, not
the user at the Console, this might affect access rights to remote files. If
problems occur accessing files on the network, grant appropriate rights to
the NGServer user. For more information, see “NGServer Password” on
page 29.
Notes
■ The Norton Ghost boot partition must exist on every client machine or
it cannot be controlled from the Console.
■ The easiest way to put the boot partition on a machine is to create an
image of one with Multicast Assist together with a matching boot disk.
15
Cloning your client machines
Then use the boot disk and Multicast Server to put the boot partition
onto the hard drive.
■ You can take an image of a machine that includes both the boot
partition and a Windows partition. This image is useful for rolling out
new machines.
■ The boot partition must have network drivers that match the network
card. That is why it is created from Multicast Assist.
16
C H A
3
Multicast Server
The Multicast Server efficiently distributes Norton Ghost image files over a
network connection. Using Multicast Server, it is possible to clone many
machines at the same time, using the same network bandwidth as you
would for one clone operation.
Due to the highly specialized nature of this server, the data is delivered
over the network more than twice as fast as over a mapped network drive.
You no longer have to map a network drive in DOS. A TCP/IP stack built
into Norton Ghost allows Ghost to act as a client to the Multicast Server
with only the packet driver loaded, requiring only a single floppy disk.
NDIS2 drivers are also supported in a single disk configuration, although
additional support files and configuration are required.
Another feature of Multicast Server is the ability to pull an image from the
client, so the entire process of image creation and deployment via the
network can be achieved using Multicast Server and a single disk.
17
Using Norton Ghost Multicast Server and Multicast Assist
identified by name. The names must match on the client and server. The
Accept Clients button is selected to activate the server.
Note: Norton Ghost images contain only the actual data on a disk. If
you have a 9 GB drive with only 600 MB of data, the Ghost image is
about 600 MB or smaller if you use compression.
Note: The client must also be configured to dump rather than load. See
the Norton Ghost Implementation Guide for more information.
18
Multicast Assist Wizard
Multicast Assist creates templates specifying the NIC that can be used to
create a boot package. These boot packages support Microsoft Remote
Installation Service (RIS) and the creation of Ghost image files.
The following sections show how to create a disk boot package for loading
an image. A similar package could dump an image (creating an image from
a disk) by changing the Ghost command line or create the image file
necessary for the boot partition. See “Specifying Norton Ghost parameters”
on page 22 for more information.
19
Using Norton Ghost Multicast Server and Multicast Assist
Note: HIMEM.SYS must be present on the disk you supply if you are
running Windows NT. (This is not shown in the panels below).
20
Multicast Assist Wizard
Note: If a template for your card is not available, you can create a new
template if you have the drivers.
3 Click Next.
Note: If you have an existing Multicast boot disk, you can use it to
provide the NDIS files Norton Ghost Multicast Assist requires.
Otherwise, download them from the Microsoft FTP site.
21
Using Norton Ghost Multicast Server and Multicast Assist
Switch Description
22
Multicast Assist Wizard
23
Using Norton Ghost Multicast Server and Multicast Assist
24
Multicast Assist Wizard
Note: This section applies only if you create an entry in the RIS (Remote
Installation Service) Menu under Windows 2000 server. This is for use with
a Network Service Boot on a PXE-enabled PC. No floppy disk is required.
25
Using Norton Ghost Multicast Server and Multicast Assist
26
A P P
Console security
E N D I X
A
The Norton Ghost Console and clients use public-key cryptography
techniques to authenticate the Console to the client. This ensures that only
the authorized Consoles can remotely control, clone, and reconfigure client
machines.
Distribution
When the clients are first installed, a boot disk and a boot partition image
file might be generated with the Multicast Assist Wizard.
As long as you use Multicast Assist from the Console machine, the correct
public certificate file will automatically be included with all boot partition
image files that include the Console client.
The Windows client needs the public certificate to communicate with the
Console. When the client is installed, it prompts you for the Console's
computer name. This is the Windows computer name specified in
27
Console security
Windows Network Settings. The client uses this name to communicate with
the correct Console.
Changing Consoles
If you have more than one Norton Ghost Console in your organization, and
you want to move a client from one to the other, you need to change the
public certificate on the client.
There are two certificates for the Console on each client, one in the Norton
Ghost boot partition, and one with the Windows client in the Norton Ghost
directory. You only need to update the boot partition copy because the
Windows client copy automatically refreshes from the boot partition.
28
NGServer password
NGServer password
On Windows NT systems, an NT service is installed called ngserver. This
service is responsible for Task execution and client communications. One
of its roles is to create machine accounts in NT Domains if machines are
added to domains during execution of a Task. To perform this role, a user
is created during installation called ngserver with the password ngserver.
The ngserver service logs in as this user. The ngserver user does not have
interactive login rights, is not a member of any groups, and only has the
privilege to manage machine accounts.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\
Services\Ngserver\Params.
29
Console security
30