Ghost Tips
(Imaging / cloning hard disc drives using Symantec Ghost)

All of the information, instructions, and recommendations on this Web site are offered on a strictly "as is" basis. Remember "Murphy's Law." Please take the proper precautions before attempting any of the tips or modifications listed here.

Contents


Imaging Windows Vista using Ghost
Spanning Ghost Images
Creating a Multi-NIC CD-ROM
Creating Bootable CD-ROMs for Restoring Ghost Images
Nero File Naming Issues
Filename Length Issues with Spanned Images
Ghost Console: Remote Client Install
Reducing the Size of the Image
Creating and Configuring Ghost Console Tasks
Bind Client to a Different Ghost Console
How to move the Ghost Console to a different computer or retain Console settings during a reinstall
Stuck in the DOS Virtual Partition
Compaq Presairo 4230ES Issues
  • DOS NDIS Driver Does Not Recognize the NIC
  • How to Add the driver for the 4230ES to the Ghost Boot Disk Wizard
  • Manually Select the Compaq 4230ES driver in Ghost Console
Serial ATA Hard Disc Drives and Ghost.exe issues
Sysprep Issues with Ghost Console
HAL (Hardware Abstraction Layer) List : (a.k.a. Computer Type)
Determine which computer will be the master computer and which computer will be the slave
How to change the Managed Server for Symantec AntiVirus
Ghost compatibility with dynamic partitions
Bulk Uninstall of Ghost Console Clients
Error Loading Operating System after Executing a Console Task
Executing Commands from the Ghost Console
 
Documentation: Symantec Solution SuiteExternal Link o
Ghost Solution Suite TutorialExternal Link
Universal Imaging UtilityExternal Link by Binary Research reduces HAL dependencies
Computer Tips Index

 


[ Top ] [ Home ]

 

Spanning Ghost Images

You can use the following parameters to run Ghost to allow splitting images into smaller parts.

ghost.exe -split=690 -auto -z2 -afile=NUL

Parameter Description

-split=690

splits an image file into multiple parts. The number is the size in megabytes. So 690 will fit on a 80min/700MB CD-R.

-auto

names split parts without prompting

-z2

highest level of file compression

-afile=NUL Don’t write any error information to ghost.err

 

 

 


[ Top ] [ Home ]

 

Creating a Multi-NIC Boot CD

This is an outline for creating a Multi-NIC Boot CD that will work with optical drives that are on either an IDE or a SATA interface.

  1. Create a bootable floppy disk containing:
  2. Create a non-compressed image (.ima) of the bootable floppy disk using WinImage.

  3. Create a bootable CD-ROM project in Nero by selecting "CD-ROM (boot)"
  4. Write the project to CD-R

- - -

Update: For Step 3: You can also use ImgBurn to create the bootable CD-ROM instead of Nero.

    1. Ez-Mode Picker... What would you like to do? Choose "Create image image file from files/folders"
    2. Select Advanced tab > Bootable Disc
    3. Enable "Make Image Bootable" under Options
    4. Set "Emulation Type:" to "Floppy Disk (1.44 MB)." This will automatically set the required "Load Segment" to 07C0.
    5. For "Boot Image," select the .ima image of the NDIS boot floppy disk.
    6. Drag the files you want on the CD portion of the bootable CD, that will be access as R:, to the Source window in ImgBurn.
    7. Click the Build button to create the image.

 

Reference

 


[ Top ] [ Home ]

 

Creating Bootable CD-ROMs for Restoring Ghost Images

See: How To Create A Bootable Ghost Rescue CD Tutorial

 

 


[ Top ] [ Home ]

 

Nero File Naming Issues

Situation:

I wrote a CD-R with "pm-f.gho." (that's a minus sign between m and f). Nero v5.x changed the minus sign to an underscore, without warning, causing ghost.exe to not find the filename specified in ghost.bat, because the filename was changed by Nero.

Solution:
Use underscores instead of minus signs when naming files and using Nero 5.x.
See: Filename Length Issues with Spanned Images.

 

 


[ Top ] [ Home ]

 

Filename Length Issues with Spanned Images

Observed when using Ghost v7.5 with with the following command line parameters: ghost.exe -split=690 -auto -z2

Recommendation

 

 


[ Top ] [ Home ]

 

Ghost Console: Remote Client Install

Remote Client Install allows you to avoid visiting each client computer to manually install the Ghost Console Client software. The installation can be done entirely from the Ghost Console > Tools > Remote Client Install...

The Symantec documentation says:

Remote Client Install only works on client computers that fit the following criteria:

Remote Client Install does not work for client computers that are running Windows 95/98/Me, Windows XP Home Edition, or Windows XP that are members of a workgroup.

See: How to install the Ghost 7.5 Client

Update: Oct. 2007:

Remote Client Install does work for client computers that are running Windows XP Professional SP2 that are members of a workgroup. I've done it myself using Ghost Console v7.5.0.335.

Update: June 2008

Update: July 2008

Workgroup/Domain and/or Computers not listed under "Tools > Remote Client Install…"

If the workgroup/domain or computers that are members of the workgroup/domain are not showing up in Console, try the following DOS command, from the console PC, to see if the the workgroup/domain and all PC's are accessible.

net view /domain:<WorkgroupName>

 

 


[ Top ] [ Home ]

 

Reducing the Size of the Image

1. Delete the C:\Pagefile.sys using the Recovery Console

Note: Since pagefile.sys is a hidden file you have to use the following commands at the Recovery Console to delete it:

copy boot.ini pagefile.sys
del pagefile.sys

2. Use the -z2 paramater at the command line when you run Ghost.exe to use maximum compression.

 

 


[ Top ] [ Home ]

 

Creating and Configuring Ghost Console Tasks

Refers to: Ghost Solution Suite v2.0

Step

Item

Location in Ghost Console

1

Create a target machine group
(All computers that have the Console Client installed, should show up under "Default" )

Important

  • For the Compaq 4230ES’s and CNet PRO/200 NIC's , you need to manually add their NDIS drivers to a new NIC Template via the Ghost Boot Disk Wizard, and set the DOS driver by right clicking on the machine group.
  • For Dell OptiPlex 755's, GSS 2.0's Console detects the NIC as Broadcom, although it's Intel Pro-1000 compatible.
  • For Dell OptiPlex GX620's and newer, you'll need to manually add a new NIC Template for the Broadcom B57n v9.x or newer NDIS driver, and also set the DOS driver to this new NIC template for the machine group.

Machine Groups

2

Add an image

Configuration Resources > Images

3

Create a configuration

Configuration Resources > Configurations

4

Create a Task

Tasks

5

Add the configuration to the task

Task properties > Configuration tab > Template

6

Execute the Task

 

 

 


[ Top ] [ Home ]

 

Bind Client to a Different Ghost Console

To bind the client computer to a different Console Switching the client computer so that it can be controlled by a different Ghost Console requires replacing the file PubKey.crt, located in C:\Program Files\Symantec\Ghost\.

Note that performing a Remote Client Install from a different Ghost Console installation does not bind the client computer to that Ghost Console. The Symantec Ghost 7.5 Implementation Guide, page 160, is wrong in this situation.

Note: Unders Windows 2000 & XP, Modify and Write rights are required to modify files in the C:\Program Files\Symantec\Ghost\ directory. A regular User won't have those rights. Just login as an Admin.

You can find the whole article if you do a search for Document ID: 2001121715570925

I created a batch file, BindClientToDifferentConsole.zip, to zero out the pubkey.crt file, allowing the Ghost Console Client to bind to a different Ghost Console. You need to be logged is with administrative rights to run BindClientToDifferentConsole.bat.

 

 


[ Top ] [ Home ]

 

How to move the Ghost Console to a different computer or retain Console settings during a reinstall

Document ID: 2001050812540225

Situation:

The Ghost Server (sometimes referred to as the Ghost Console) is installed on one computer, and you want to move the server to a different computer without losing Ghost configuration information and without having to reconfigure the client computers. Or, you want to reinstall the Ghost Server to the same computer without losing the Ghost Console settings.

Solution:

Moving the Ghost Console to a different computer, or reinstalling the Console, is a simple process. However, it requires that you visit each Ghost client computer to copy or delete specific Ghost files, as described in the following instructions.

Upgrading to a new Ghost version

If you intend to upgrade the Ghost Server to a new version and move the Ghost Server to a new computer, upgrade the Ghost Server and the Ghost Clients before moving or reinstalling the Ghost Server. Read the document How to upgrade Ghost Enterprise Edition to Ghost 6.5, Ghost 7.0, or Ghost 7.5.

To move or reinstall the Ghost Console

  1. At the current Ghost server computer:
    1. Close the Ghost Enterprise Console.
    2. Click Start > Run. The Run dialog box appears.
    3. Type:
      C:\Program Files\Symantec\Ghost\ngserver –stop
      and click OK. The drive letter and path might be different on your computer. This stops the Ghost Enterprise Console Services.
    4. Copy the following files to a safe location. These files contain Ghost configuration information:
      SymantecGhost.db
      Pubkey.crt
      Privkey.crt
  2. If reinstalling Ghost:
    1. Uninstall Ghost.
    2. Install Ghost.
    3. Click Start > Run. The Run dialog box appears.
    4. Type:
      C:\Program Files\Symantec\Ghost\ngserver –stop
      and click OK. The drive letter and path might be different on your computer. This stops the Ghost Enterprise Console Services.
    5. Replace the following files with the files that you previously copied to a safe location:
      SymantecGhost.db
      Pubkey.crt
      Privkey.crt
    6. Reboot the computer.
  3. If moving the Ghost Console:
    1. Install Ghost to the new Ghost server computer.
    2. Click Start > Run. The Run dialog box appears.
    3. Type:
      C:\Program Files\Symantec\Ghost\ngserver –stop
      and click OK. The drive letter and path might be different on your computer. This stops the Ghost Enterprise Console Services.
    4. Replace the following files with the files that you previously copied to a safe location:
      SymantecGhost.db
      Pubkey.crt
      Privkey.crt
    5. Reboot the computer.
    6. Uninstall Ghost from the original Ghost server computer.

 


[ Top ] [ Home ]

 

Are you stuck in the virtual partition or boot partition in DOS, and can only reboot to DOS?

This often happens when canceling an imaging task. If the DOS system is still communicating with the Ghost Console, just send a new task. If there is a valid Windows operating system on the client machine, and you just need to get out of DOS, use the following commands:

  1. Press Ctrl+C to stop the DOS client from communicating with the console.
  2. Then at the C:\GHOST prompt type in NGCTDOS -HIDE.
    The NGCTDOS.EXE file is the Ghost client in DOS which talks to the Console. The -HIDE switch will delete the virtual partition or hide the boot partition, and then reactivate your Windows partition.

http://ghosttraining.com/ghost_faq.html#5

Ghost Solution Suite adds ghreboot.bat:

  1. Press Ctrl+C to stop the DOS client from communicating with the console. (Note: You may have to press Ctrl+C twice in succession.)
  2. Then at the C:\GHOST prompt type in ghreboot then press <enter>

 

 


[ Top ] [ Home ]

 

Compaq Presario 4230ES NDIS Driver Issues

The NIC in the Compaq Presario 4230ES is a "Compaq Netelligent 10/100 TX PCI UTP Controller." I'll just reference as 4230ES.

DOS NDIS Driver Does Not Recognize the NIC

 

How to Add the driver for the 4230ES to the Ghost Boot Disk Wizard

  1. Create a directory named Compaq 4230 in the Ghost Boot Disk Wizard directory
  2. Copy the OEMSetup.inf file from the Compaq 4230 boot disk to the Compaq 4230 directory
  3. Add the Compaq 4230 NDIS to the Ghost Boot Disk Wizard
  4. The drivername must be “NTFLX3$” to match protocol.ini.

 

Manually Select the Compaq 4230ES driver in Ghost Console

 

 


[ Top ] [ Home ]

 

Serial ATA Hard Disc Drives and Ghost.exe Issues

The Serial ATA (SATA) setting in the BIOS may cause Ghost.exe v7.5 to hang.

Dell OptiPlex GX620

On Dell OptiPlex GX620's, there are two settings for Drives > SATA Operation in the BIOS, Normal and Combination.

When SATA Operation is set to "Normal," (the factory default) Ghost.exe v7.5 hangs before the Ghost user interface is displayed. Adding the -fni parameter when running Ghost.exe, enables Ghost to run.

When SATA Operation is set to "Combination," Ghost.exe v7.5 runs normally without the need for the -fni parameter.

We haven't noticed a performance hit when SATA Operation is set to "Combination."

Dell OptiPlex 755

Dell Optiplex 755 with BIOS vA09

What is "TPM Security"?

Ctrl-P = MEBx ?

Dell Latitude D630

BIOS A13 (07/28/2008)

Reference

AHCI (Advanced Host Controller Interface)

 

 


[ Top ] [ Home ]

 

Cannot save an image file when using Microsoft Sysprep 1.1

Document ID: 2002021914065725

Situation:
You chose the option "Pull an image from a client machine" in the Symantec Ghost Console Wizard or the option Image Dump to create a Task that creates an image of a Windows 2000 installation and saves that image as a file. When you run the Task, the Task fails. Ghost copies the Sysprep file to the client computer but does not execute the Sysprep file. The Ghost Task Log displays a message that indicates Ghost failed to execute a command or the client failed to boot from Ghost Virtual Boot Partition.

You configured the Task to use Microsoft's System Preparation Tool (Sysprep) version 1.1.

Solution:
This problem happens when you use the most recent version of Sysprep for Windows 2000. Microsoft has two versions of Sysprep 1.1. Symantec Ghost 7.5 works with the earlier version, which is build number 5.00.2195.1, and not with the later version, build number 5.00.2195.2104.

To resolve the problem, recreate the image file using Sysprep 1.1 build 5.00.2195.1.


Note: This compatibility limitation only exists in Symantec Ghost 7.5. Symantec Ghost 8.0 is compatible with both versions of Sysprep 1.1.

Sysprep versions

 

 


[ Top ] [ Home ]

 

Determine which computer will be the master computer and which computer will be the slave


WARNING: This relationship is very important; if the wrong computer is set as Master or Slave, it can cause data loss on the drive you intend to copy. Be certain which computer is the Master and which is the Slave. For further clarification, see the section "Assigning the Master and Slave computers."

Assigning the Master and Slave computers
When cloning a disk or partition, the source computer is the Master and the destination computer is the Slave. When restoring an image, the computer that has the image is the Slave and the computer that you will restore the image to is the Master.


Cloning operation
Master
Slave
Cloning: Copy the disk or partition Disk-To-Disk Computer containing the source disk Computer containing the destination disk
  Partition-To-Partition Computer containing the source partition Computer containing the destination partition
Cloning: Create an image file Disk-To-Image Computer containing the source disk Computer receiving the image file
  Partition-To-Image Computer containing the source partition Computer receiving the image file
Restore an image Image-To-Disk Computer containing the destination disk Computer containing the image file
  Image-To-Partition Computer containing the destination partition Computer containing the image file

Source: How to clone or save an image file over a TCP/IP peer to peer connection

 


[ Top ] [ Home ]

 

How to Change the Managed Server For Symantec AntiVirus

  1. Copy GRC.DAT from the VPHOME share on the server to C:\Documents and Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate Edition\7.5\
  2. Delete the existing *.servergroupca.cer in C:\Program Files\Symantec AntiVirus\pki\roots\
  3. Copy the *.servergroupca.cer file from C:\Program Files\Symantec Client Security\Symantec AntiVirus\pki\roots\ to C:\Program Files\Symantec AntiVirus\pki\roots\

See: Moving Symantec Client Security 3.x or Symantec AntiVirus Corporate Edition 10.x clients from one parent server to another.

 

 


[ Top ] [ Home ]

 

Ghost compatibility with dynamic partitions

To clone a dynamic disk

The best way to use Ghost to clone a dynamic disk is to perform a partition-to-image cloning operation and not a disk-to-image cloning operation. To clone the entire disk, perform a partition-to-image operation and select all partitions on the source disk.

Disk-to-Image

Use a disk-to-image operation only as a last resort.

To perform a disk-to-image cloning operation on a dynamic disk, run Ghost with the -IA switch on the Ghost command line.

Ghost supports creating a disk image of a dynamic disk only when using the -IA switch on the Ghost command line.

Source

 

 


[ Top ] [ Home ]

 

Bulk Uninstall of Ghost Console Clients

Question/Issue:

Solution:

The Console Client can be uninstalled for a group of machines using the Ghost Console.

Follow these steps:

1. Obtain the GUID for the Console Client from the registry on a client: HKLM\Software\Symantec\Symantec Ghost\ProductCode.

2. Set up the Ghost Console to run an task of 'Execute Command' in the following form:

msiexec /x {ProductCodeGuid} /q

Note that the command line should include the curly brackets {} since they form part of the product code GUID obtained from step 1.

3. In the task, specify the machine group you would like to uninstall.
4. Execute the task.
5. The clients will reboot and the Console Client will be uninstalled.
6. The clients will not be removed from the Ghost Console. This must be done manually.

Source: Document ID: 2007111215361360

 

 


[ Top ] [ Home ]

 

Error Loading Operating System after Executing a Console Task

Version Ghost Solution Suite 2.0
Operating System Windows XP Professional SP3
Environment Windows SteadyState v2.5 with Windows Disk Protection enabled in Discard mode (Remove All Changes at Restart)

Situation

After executing a Ghost Console task, one or more of the target computers fails to boot into the Ghost Virtual Partition, fails to load Ghost so it can be imaged, and fails to recover by booting into the existing operating system.

The following error is displayed on the failed client computer when it reboots:

Error loading operating system

Cause

Solution

  1. Cancel the task before Ghost Console times out and starts imaging all the other PC’s in the group
  2. Boot the failed computer(s) with a CD/DVD or disk that contains the Windows 98 or newer FDisk.
  3. Run FDisk and select option "4. Display Partition Information" to determine which partition was the original boot partition
  4. Select option "2. Set active partition" to set the original boot partition as the active partition,
  5. Select option "3. Delete Partition or Logical DOS Drive" and delete the 16Mbyte "UNKNOWN" partition.
  6. Exit FDisk then reboot the computer
  7. Disable SteadyState Windows Disk Protection.
  8. Execute the task again

For future imaging, I suggest that you create 3 separate tasks for the one job.

  1. Execute Command only, to disable WDP on all target PC's, "In Target Operating System"
  2. The normal task (Clone, Configuration, etc.) to push the image to all target PC's
  3. Execute Command only, to enable WDP on all the target PC's, "In Target Operating System"

Example Partitions

From: Dell Optiplex 755 with 80GB SATA hard disc drive

The drive was partitioned into two. Drive C: the boot partition and a 10GB D: partition that "My Documents" was moved to so that WDP would leave user data intact between reboots.
The 16 Mbytes “UNKNOWN” is the Ghost Virtual Partition.

Display Partition Information

Current Fixed Disk drive: 1

Partition

Status

Type

Volume Label

Mbytes

System

Usage

C: 1

A

PRI DOS

 

16

UNKNOWN

%

2

 

NTFS

 

65421

 

100%

3

 

EXT DOS

 

10864

 

100%

Total disk space is 10757 Mbytes (1 Mbyte = 1048576 bytes)

Reference

 


[ Top ] [ Home ]

 

Executing Commands from the Ghost Console

Create the Task

  1. Create a task with only the "Execute Command" selected under Task Steps
  2. Select the "Target Machine Group/Machine"
  3. Click on the "Execute Command" tab
  4. Add the command and any parameters
  5. Choose "In Target Operating System"

DOS Commands

If you need to run a DOS command you'll want to use:

cmd is the command interpreter
/c Carries out the command specified by string and then terminates
"String" is the DOS command plus parameters that you want to run

Here's an example to delete a directory tree:

rd removes the specified directory. a.k.a. RmDir
/s Removes all directories and files in the specified directory in addition to the directory itself. Used to remove a directory tree.
/q Quiet mode, do not ask if ok to remove a directory tree with /s
Command: cmd
Arguments: /c "rd /s /q c:\temp\Patcher"

 

 


[ Top ] [ Home ]

 

All items Copyright ©1996 - 2017 Chin. All Rights reserved Reproduction without explicit permission is prohibited. See: Terms of use