Question/Issue:
This document describes how to use Ghost to clone a Windows NT 4.0 Server, Windows 2000 Server, Windows 2000 Advanced Server, or Windows 2003 Server.


Solution:
Ghost can clone a server if this is done for backup or migration purposes. However, in most cases, Ghost cannot clone a server for rolling out that server to many computers, and Symantec does not support Ghost when used for this purpose. For more information, see the document 'Does Symantec Ghost work with Server operating systems?' at
http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2007121716430960?Open&seg=ent


How the SID affects the cloning process
Windows NT, Windows 2000, Windows XP, and Windows 2003 Server do not allow two computers with the same Security ID (SID) to log on to the same network.

Backup
When cloning a server for backup purposes, the SID does not need to be changed and Ghost should be successful, provided the system's hardware is not changed after the backup has been made. If hardware was changed, the computer might not be able to boot up after restoring the backup. For a description of hardware considerations, see the document Introduction to cloning a Windows NT, Windows 2000, or Windows XP computer.

Migration
When cloning a server for migration purposes (to move the server installation to another hard drive or computer), the SID does not need to be changed and Ghost should be successful, provided the hardware is identical on the source and destination hard drives or computers. For a description of hardware considerations, see the document Introduction to cloning a Windows NT, Windows 2000, or Windows XP computer.

Different networks
In some cases, Ghost can clone a server if the two servers will log on to two totally different networks, as long as the two servers cannot see each other on the network. This requires that the source and destination computers have identical hardware, and that other configuration considerations do not interfere with a successful bootup and logon. For a description of hardware considerations, see the document Introduction to cloning a Windows NT, Windows 2000, or Windows XP computer.

Cloning to many computers
When cloning a server to roll it out to more than one computer, the SID needs to be changed on each destination computer. Ghost Walker and Ghost Console can successfully change the SID on Windows NT, Windows 2000, and Windows XP Workstations.

Due to the increased security needs of servers, the SID propagates to a much higher degree on servers than on workstations. It is nearly impossible for Ghost Walker to effectively change all instances of the SID on Windows servers. In most cases, the destination computer cannot successfully boot up into Windows, or the computer will encounter errors while performing normal server functions.


Other configuration considerations
In most situations, Ghost cannot successfully clone a Windows NT, Windows 2000, Windows 2000 Advanced Server, or Windows 2003 Server installation to another computer.

In addition to SID considerations, Windows maintains many configuration settings that are unique to each server. For example, the choice of Domain Name Service (DNS) or Dynamic Host Configuration Protocol DHCP might affect whether a server can boot up, or whether that computer can log on to a particular network or be recognized on the network.

Ghost does not automatically configure such settings. Enabling a cloned server to boot up, log on to the network, and perform normal server functions, requires manually changing such settings. Symantec does not support Ghost when used in this situation, and information on such settings is beyond the scope of this document. For further information, consult your Windows and networking documentation.

Terminal servers
Ghost cannot successfully clone Windows NT 4.0 Terminal Servers or Windows 2000 Terminal Servers. For related information on using Ghost with terminal servers, see the document Ghost Compatibility with terminal services such as Citrix Metaframe and Windows 2000 Terminal Services.

RAID arrays
Ghost is not compatible with RAID systems. That is, Symantec Ghost 8.0 and earlier do not support RAID controllers on the computers that are being imaged. Although Ghost might successfully clone a RAID system in some circumstances, Symantec does not provide technical support when Ghost is used for this purpose. For more information, see the document Ghost compatibility with RAID.

Large drive support
Norton Ghost 2003, Symantec Ghost 7.5, and Symantec Ghost 8.0 support large hard drives.

For drivers larger than 137 gigabytes (GB), Ghost requires the operating system to be Windows XP with Service Pack 1 (SP1), Windows 2000 with Service Pack 3 (SP3), or Windows 2003 Server. These operating systems support 48-Bit Logical Block Addressing (LBA), which is required for drives larger than 137 gigabytes (GB).

For more information on support for large hard drives with Windows 2000 SP3, read the Microsoft document 48-Bit LBA Support for ATAPI Disk Drives in Windows 2000 (305098).

References:
For information about cloning mirrored or stripped drives, read the documents Ghost compatibility with dynamic partitions and Ghost compatibility with RAID.

Document ID: 1999012108164025
Last Modified: 01/04/2008
Date Created: 01/21/1999
Operating System(s): Windows NT, Windows 2000
Product(s): Symantec Ghost 7.0, Symantec Ghost 7.5, Symantec Ghost 8.0, Symantec Ghost Solution Suite 1.0
Release(s): Ghost 7.0 [All Releases], Ghost 7.5 [All Releases], Ghost 8.0 [All Releases], Symantec Ghost 8.2, Symantec Ghost Solution Suite 1.0 [All Releases]