How to customize Ghost for individual users

Article:TECH106600  |  Created: 1998-01-12  |  Updated: 2014-03-19  |  Article URL http://www.symantec.com/docs/TECH106600
Article Type
Technical Solution

Product(s)

Environment

Issue



You want to limit Ghost's capabilities so that your users do not have full access to Ghost features.

 


Solution



Limiting Ghost's capabilities for individual users requires creating a customized copy of the Ghost.exe file. When users run the customized Ghost.exe, they do not have access to features that you restricted. For instance, you can customize Ghost.exe so that it can restore image files, but not create image files, or so that it can create image files, but not restore image files.

To customize Ghost.exe to perform only specific types of cloning operations, use any text editor to modify the Switches line in the Ghost license file, Ghost.env, and then bind the license file to Ghost.exe.

To limit Ghost functions

  1. Open the copy of the Ghost license file, Ghost.env, in any text editor.
    The original file is located on the hard disk in C:\Program Files\Symantec\Ghost. If your license file is not Ghost.env, make a copy of your license file rather than a copy of Ghost.env.
  2. Go to the Switches line. If the Switches line does not exist, add one.
    Edit only the switches line. Note that the licensing information cannot be altered.
  3. Make sure that the Switches line is at the top of the list.
  4. Use parameters for the switches line that are appropriate to how you want to limit Ghost's functionality. See the section The Switches line.
  5. Save the file.


To bind the license file to Ghost32.exe

  1. Make a copy of Ghost32.exe.
  2. Copy the modified license file, Ghost.env, to a new folder.
  3. Move a copy of the original Ghost32.exe file to the same folder as Ghost.env.
  4. Run Ghost32.exe from a Run Command line using the following syntax:

    ghost32 -#e=filename.env -envexe= exetobemodified.exe (Add the full path name. For example: "C:\Program Files\Symantec\Ghost\ghost32.exe" -#e=c:\test\ghost.env -envexe=c:\test\ghost32.exe -file)

    Running Ghost32.exe from the same folder as the license file "binds" the files together, which modifies Ghost32.exe to use the parameters that you specified in the license file. Note that if you have changed the Ghost.env file to another file name, specify the file name when you run Ghost32.exe.
  5. Provide the new copy of Ghost32.exe to the user.


When the user runs the new copy of Ghost32.exe, the user can perform only specific types of cloning operations.

To bind the license file to Ghost.exe

  1. Copy both Ghost.exe and Ghost.env from the C:\Program Files\Symantec\Ghost folder to a floppy disk.
  2. Boot the computer to DOS.
  3. At the DOS prompt, type:

    Ghost.exe

    and then press Enter.
  4. If you do not receive the message, "Ghost successfully registered", use the following syntax:

    C:\ghost>ghost.exe -#e=filename.env

    Replace filename.env with the name of your license file. The default Ghost file name is Ghost.env.
  5. Press Ctrl+C to exit Ghost.


When the user runs the new copy of Ghost.exe, the user can perform only specific types of cloning operations.

To restore Ghost functions

  1. Open and edit the modified Ghost.env file in any text editor.
  2. Change all N values on the Switches line to Y.
  3. Save the file.
  4. Copy the newly modified Ghost.env to a new folder to bind the Ghost.env license file to Ghost.exe.
  5. Copy the previously modified Ghost.exe to the same folder.
  6. Run Ghost.exe from the new folder.
    Running Ghost.exe from the same folder as Ghost.env "binds" the files together, which modifies Ghost.exe to use the parameters that you specified in Ghost.env.
  7. Provide this copy of Ghost.exe to the user.



More information

The Switches line
The Switches line in the Ghost license file, Ghost.env, includes the parameters for permitting or limiting Ghost's functionality. Use any text editor to include a Switches line as the top line in the file, as in the following example:

Switches: Load=Y,Dump=Y,Disk=N
Keynum  : 002030
License : KRS1420365
MaxPCs  : 25
Name    : John Smith
Address1: XYZ Corp
Address2:  
Keycode : L8N6X75R3U0L9Z

Notes:

  • Ghost provides full functionality when the Switches line is not included and when the line is included with the default values. The default values are: Load=Y,Dump=Y,Disk=Y,Peer=Y,Write=Y,Fprnt=Y
  • Use the format switchname=y or switchname=n to activate or deactivate options on the Switches line. Note that the value for the parameter IMGTMO must be a number.


Edit the Switches line to provide the values that are appropriate to your situation. The following table lists the available options and values.

 

Switch Value Description Typical Usage
LOAD Y or N Controls whether Ghost can use the restore functions Image-to-Disk and Image-to-Partition.

Y allows Ghost to use the contents of an image file to write over the destination disk or partition. N prevents this operation.
LOAD=Y
LOAD=N
DUMP Y or N Controls whether Ghost can use the image-creation functions Disk-to-Image and Partition-to-Image.

Y allows Ghost to create an image of a disk or partition and save that image as a file. N prevents this operation.
DUMP=Y
DUMP=N
DISK Y or N Controls whether Ghost can use the dynamic-cloning functions Disk-to-Disk and Partition-to-Partition.

Y allows Ghost to copy one disk or partition directly to another, which results in writing over the destination disk or partition. N prevents this operation.
DISK=Y
DISK=N
WRITE Y or N Controls whether Ghost can write to a destination disk or partition when performing a LOAD operation. Using WRITE=N provides the same functionality as the command-line switch -FNW.

When you use LOAD=Y and WRITE=N, Ghost permits the user to choose the options for restoring an image file. The operation will appear to work, however, the operation completes quickly and the operation does not succeed because no data is written to the disk.
WRITE=N
PEER Y or N Controls whether Ghost can work over the following peer-to-peer connections: LPT, USB, and TCP/IP.

Y allows Ghost to perform cloning operations through an LPT, USB, or TCP/IP peer-to-peer network. N prevents the operation.
PEER=Y
PEER=N
TIMEOUT Y or N Controls whether Ghost can restore images that are old.

When TIMEOUT is set to Y, Ghost compares the current date to the date that the image file was created. If the number of days between those dates is larger than the value that is set for IMGTMO, Ghost does not restore the image.

When TIMEOUT is set to N, Ghost does not prevent the user from restoring older image files.
TIMEOUT=Y
IMGTMO Number of Days Specifies the acceptable age of an image file. When IMGTMO is used with TIMEOUT=Y, Ghost does not restore image files that are older than the specified number of days.

When used with TIMEOUT=N, the IMGTMO parameter has no effect on Ghost operations.
IMGTMO=<# of days>
FPRNT Y or N When a user performs an Image-to-Disk, Image-to-Partition, Disk-to-Disk, or Partition-to-Partition operation, this switch controls whether Ghost stores additional (fingerprint) information on the destination disk or partition.

Y sets Ghost to store the information, and N sets Ghost to not store the information.

The information is:
  • What process was used to create the drive or partition
  • The time the operation was performed
  • The date the operation was performed
  • The disk number

For more information, see the document How to determine whether Ghost wrote to a disk or partition.
FPRINT=Y



Examples of the Switches line:

Example 1:
This example configures the license file so that the user can write (load) a disk image onto a disk, writing over the previous data that was on the disk.
The user cannot write a partition image to a disk, cannot create disk or partition image files, and cannot perform a Disk-to-Disk or Partition-to-Partition operation.

Switches: Load=Y,Dump=N,Disk=Y

Example 2:
In this example, the user appears to have the ability to write an image to a disk, writing over the existing data on the disk, but no data is actually written to the disk. The user can create an image file and save that image file to a disk.

Switches: Load=Y,Dump=Y,Write=N

Example 3:
In this example, the user can restore image files that are 15 days old or less. The user can also create image files. The user cannot perform a Disk-to-Disk or Partition-to-Partition operation.

When creating an image file, Ghost marks the source disk with a fingerprint, which provides information on the current operation. To examine that information after cloning, see the document How to determine whether Ghost wrote to a disk or partition.

Switches: Load=Y,Dump=Y,Disk=N,Fprint=Y,Timeout=Y,Imgtmo=15

Example 4:
In this example, the user cannot restore image files, regardless of their age. The user can create image files. The user cannot perform a Disk-to-Disk or Partition-to-Partition operation.

Switches: Load=N,Dump=Y,Disk=N,Timeout=Y,Imgtmo=15

Example 5:
In this example, a company has 100 laptops in use by the sales staff. For fast system restoration by the users, each of the laptops has a CD disc that contains a copy of Ghost and an image file. To enable the users to use the CD disc for system restoration and not for other purposes, the IT administrator customizes Ghost.exe to allow only image restoration, and not image creation.

To accomplish this, the IT administrator uses the instructions To limit Ghost functions with the following notes:

  • When customizing Ghost.env, the administrator edits a copy of the file, rather than the original so that the IT administrator can continue to access all Ghost functions from the original Ghost.exe.
  • When editing the copy of Ghost.env, the administrator uses the following Switches line:
    Switches: Load=Y,Dump=N,Disk=N,Peer=N,Write=Y,Fprnt=Y
  • When binding Ghost.env to Ghost.exe, the administrator runs Ghost.exe from a folder on the hard disk (or a folder on a floppy disk). Ghost.env is located in the same folder. After binding Ghost.env to Ghost.exe, the administrator uses the newly bound copy of Ghost.exe when copying files to the CD disc.
     

Example 6:
In this example, Ghost is used as a backup tool. In this case, disabling the LOAD option prevents users from accidentally overwriting their local drive. With the following Switches line, the user can create image files but cannot restore image files. The user also cannot perform a Disk-to-Disk or Partition-to-Partition operation.

Switches: Load=N,Dump=Y,Disk=N,Peer=N,Write=Y,Fprnt=Y

In this situation, the user could use Ghost Explorer to restore individual files and folders from the image file. The user cannot restore the image file unless they have a separate Ghost.exe file that permits restorations. Alternatively, the system administrator can restore the image file by using a different copy of the original Ghost.exe file, which has not been customized to prevent restorations.

Example 7:
To prevent Ghost from storing information about previous cloning operations on the disk, use the switch FPRINT=N to turn off the fingerprinting option:

Switches: Load=Y,Dump=Y,Disk=Y,Peer=Y,Write=Y,Fprnt=N


Ghost license file
The Ghost license file, also known as the Ghost environment file, is a text file that provides information for the Ghost executable file. This information includes Ghost customization information and some Ghost licensing information. The licensing information cannot be altered.

The Ghost license file is Ghost.env. After you install Ghost, Ghost.env is available on your hard disk in the C:/Program Files/Symantec/Ghost folder.

In Symantec Ghost 7.0 and later, binding the license file to Ghost.exe is only necessary when you customize your copy of Ghost.exe, as in the procedure in this document, or when you replace your copy of Ghost.exe. Binding the license file to Ghost means to run Ghost.exe once from the same folder that the license file is in.

In Symantec Ghost 7.0 and later, Ghost automatically creates the license file, Ghost.env.

The license file includes:

  • Licensed user's details
  • Maximum number of licensed concurrent users
  • Additional product licensing information
  • Functionality switches


For older Ghost versions, see the documents How To Create the Ghost License File and How to update Ghost 5.x to the latest version.


Using a license file that has a different name
In some situations, your license file may have a file name that is not Ghost.env. This happens when you use an older Ghost version, which is no longer supported, or when your Symantec sales representative provided you with a customized license file.


Advanced customization
Customization of the Ghost license file affects Ghost functionality but does not affect how Ghost appears to the user. For instance, Ghost.exe does not include advanced customization options such as a means for displaying your company name in the Ghost user interface. For further information regarding advanced customization, contact your Symantec sales representative.




 



Legacy ID



1998081216393425


Article URL http://www.symantec.com/docs/TECH106600


Terms of use for this information are found in Legal Notices