ed2kers 电驴资源下载站

《诺顿克隆8.0 企业版》(Symantec Ghost 8.0 Corporate Edition )

《诺顿克隆8.0 企业版》(Symantec Ghost 8.0 Corporate Edition  )
类别:
软件 - 应用软件
状态:
普通资源
摘要:
无
发布:
2004-05-17 08:20:12
更新:
2004-05-17 08:20:12

电驴资源

用户共享的电驴资源列表
Ghost2004.ISO 179.47 MB
179.47 MB

电驴资源简介

简介:
诺顿的克隆2004英文光盘版,iso镜像文件。(第一次上传,不会插图)
===============================================================
Symantec Ghost 8.0 Corporate Edition README.TXT
Copyright 1998 - 2003 Symantec Corporation
All Rights Reserved 30 September 2003
===============================================================
Symantec Ghost 8.0 Corporate Edition Release Notes
===============================================================
This file covers contents of the installation CD,
licensing, late-breaking news, and references other
related information. The following topics are discussed:
1. Known issues
2. Cloning Windows 2000 and XP
3. Technical support details
4. Reporting problems to Technical Support
===============================================================
1. Known Issues
===============================================================
Symantec Ghost Console
======================
Client inventory
----------------
Symantec Ghost client inventory relies on the data provided
by Microsoft Windows Management Instrumentation (WMI).
The accuracy of the data returned by WMI depends on the
version of the client OS, its service pack and the version of
WMI installed. Consult the Symantec on-line knowledge base to
find out more information.
Within a filter when you specify a restriction for an
attribute which is of type float or double, you ll need to
specify the whole value.
E.g. if the value is 6.000 , you should specify 6.000 and
not 6 as this will not match.
Client inventory filters
------------------------
The data provided by WMI is dependent on the language of the
client OS. The filters have been developed for US English
clients. Filters used with clients that are not US English may
return an incorrect number of Clients.
Default inventory views
-----------------------
Problem
After upgrading, none of the upgraded clients have any default
inventory views.
Cause
Inventory views are only set when the client is first added to
the Console.
Solution
1) Delete the machines. When they are added again they will
get the default views
2) In the machine group folder, choose to set inventory views.
In the Set Inventory views dialog choose to Override
individual machine settings .
Clone tasks
-----------
Problem
On client machines when you have multiple hard drives, and the
hard drives are of different types, e.g. SCSI and IDE or SATA
and IDE, the drive which gets cloned is not as expected.
Cause
When you have a mix of hard drive types the way that the BIOS
orders hard drives is sometimes different from the way that
Windows orders them. In addition the BIOS will order the hard
drives differently depending on what type of device was used
to boot. Ghost.exe will use the BIOS ordering.
Solution
You should test what Ghost will see when run from a Console
task before running a clone task. To do this:
1) Go to the client machine and run the command
ngctw32 -recovery
This will boot the client into the boot partition.
2) Once the client is in the boot partition, type [CTRL+X] to
exit the DOS client.
3) Run Ghost to determine which order the hard drives are in.
4) Once you have done this, exit Ghost and run ghreboot,
this will return the client to Windows.
Using shares to the Primary Domain controller (PDC) from the
Console machine
------------------------------------------------------------
The Ghost Configuration Server has a domain login that is used
to create machine accounts for Windows NT, 2000 and XP clients.
However, only one session is allowed from a client to
a server when using Microsoft networking. Therefore, if you
have mapped a drive to a share on the PDC, the Configuration
Server cannot login to the domain. The console error log
reports the following reason for not creating the account:
Conflict with existing set of credentials .
For more information, see the Microsoft knowledge base article
Q106211.
Client initiated tasks
----------------------
All resources, for example, image files, which are used by a
client initiated task must reside on the Console machine. This
is because the Console only has local rights when executing
client initiated tasks. This does not apply to resources which
are on the client machine.
Ghost Console invalid characters
--------------------------------
The following characters #@% )(-.^_{}~ may be invalid for
use in Windows computer names, domain names, and workgroup
names, depending on which version of Windows you are using.
The Console may allow the use of these characters in tasks.
Ensure that the names that you use are valid on the
target platform.
Joining client computers to Domains after upgrade
-------------------------------------------------
Problem
After upgrade, Windows 2000 and Windows XP clients fail to
join a domain using existing configurations.
Cause
In Symantec Ghost 8.0 a new configuration type has been added,
Windows 2000/XP . After upgrade all configurations will be
set to Windows NT4 .
Solution.
If you wish to use these configurations with Windows 2000 or
XP clients you will need to change the configuration type to
Windows 2000/XP .
Joining client computers to Active Directory Domains
----------------------------------------------------
If you are having problems joining clients to Active Directory
based Domains please check that Domain Name Server (DNS) is
configured correctly. You must configure DNS correctly to
ensure that Active Directory will function properly.
Please see the following Microsoft Knowledge Base article for
more information:
http://support.microsoft.com/?kbid=260371
In addition, you may want to use the DCDIAG tool available
from the Windows 2000 Server resource kit.
Joining client computers to Active Directory Domains
----------------------------------------------------
Problem
Windows 2000 and Windows XP clients do not join a supported
Domain in the specified container. You have specified the
Domain in the Supported Domain List using the Domain s NETBIOS
name.
Solution
Please use the fully qualified domain name, i.e. in the form
domain.company.com , when adding the Domain to the Supported
Domain List.
Joining client computers to Active Directory Domains
----------------------------------------------------
Problem
NT4 clients do not join a supported domain. You have specified
the domain in the Supported Domain List with a fully
qualified domain name.
Solution
Please use the NETBIOS domain name when adding the Domain to
the Supported Domain List. A fully qualified domain name is in
the form domain.company.com . The NETBIOS name is a short
form of the fully qualified name, e.g. DOMAIN .
Joining client computers to Active Directory Domains
----------------------------------------------------
Problem
You have tried the solutions above but are still unable to
join clients to the domain using the Console.
Comment
There are many configuration and environmental issues related
to Domain joining. Many of the programmatic aspects are not
documented by Microsoft and may not work in all cases.
Therefore, we offer the following as a fallback solution:
Microsoft provide a tool called NETDOM. This tool is available
in resource kits and in the Deploy.Cab file on the Windows XP
CD. This tool is a command line tool for joining a client to a
Domain. Please see the following Microsoft Knowledge Base
article for more information on NETDOM:
http://support.microsoft.com/?kbid=266651
You can create a simple batch file to run the NETDOM command
with suitable parameters. Transfer the batch file and the
NETDOM program to the clients and execute the batch file using
a Console task. Note that this solution has a drawback: the
credentials of a Domain Admin are transmitted to the clients
in plain text.
Wake On LAN (WOL)
-----------------
WOL does not work correctly for some hardware and software
configurations when you fully shut down the computer.
In all cases, the Console sends the required message to the
computer, but sometimes the computer does not wake up. A
computer in standby mode always wakes up using WOL.
Check the following:
- Ensure that WOL is enabled on the card itself using DOS or
Windows configuration programs for the card.
- Ensure that WOL is enabled in the network card drivers under
the operating system.
- Ensure that WOL is enabled in the BIOS of the computer.
Standby mode
------------
The Console may lose contact with the database when it comes
back from standby mode. If this happens you may need to
restart the Console machine. We recommend you disable standby
mode on the Console machine.
Incremental backups
-------------------
Symantec Ghost scans the Windows System32 directory for
changes to a user s computer. If changes have been detected
then a new baseline is created. The administrator should
monitor client computers for any changes so that a new
baseline image can be forced manually if an application has
been installed or uninstalled, or an operating system or
user change has been made.
Clone step fails when preserving files
--------------------------------------
Problem
the clone step fails when you attempt to do a clone operation
with preserved files. The machine is running NT4 and has a
SCSI hard drive. When you look at the ghost error file you see
the following message
Message: Ghost could not find a unique volume matching the
specified attributes
Cause
For Ghost to successfully complete a preserve operation it
needs to gather unique information about the hard drives in
Windows and then match that with information it can get in
DOS. In some scenarios this is not possible.
Solution 1:
Modify the DOS template used for the client to include an ASPI
driver. To do this:
1) Start the Ghost Boot Wizard, and select the network
boot disk.
2) Select the template used for the client, and click Modify.
3) In the Modify screen, select the Advanced tab and add the
ASPI driver.
Having the ASPI driver available for a SCSI hard drive enables
Ghost to obtain the serial number of the hard drive.
Solution 2:
Go to the client machine and run disk administrator. Disk
administrator writes an unique ID to each disk in the
computer which can be used by Ghost in both Windows and Dos.
Clone step in task log
----------------------
Problem
When running a task which uses local resources there is an
unexpected clone step logged in the task log.
Cause
The console incorrectly reports any local path evaluation of
local resources as a clone step. The problem is only in the
task log and does not affect any functionality.
Overwriting the Ghost boot partition
------------------------------------
Problem
You have upgraded your Console and clients. You then attempt
to do a clone operation and choose to overwrite the ghost
boot partition. The clients display a non-system disk or
disk error message and fail to boot.
Cause
In the process of overwriting the Ghost boot partition,
Ghost needs to relocate it. The boot partition contains an
older version of PC DOS which does not boot in its new
location. The Ghost boot partition and any files in it will
still be available.
Solution
To recover clients which are in this state, load a new boot
partition. This will delete any preserved files, you can
recover preserved files from the boot partition by using
Omnifs.
To prevent the problem from happening you can delete the Ghost
Boot Partition from the client before running the task. This
will cause the client to create a virtual partition with a
newer version of PC DOS.
File transfer to clients with Multiple Network Interfaces
---------------------------------------------------------
Problem
You are attempting to transfer files to one or more client
machines and the file transfer portion of the task times out.
The client machine has Multiple Network Interfaces; this can
include machines with only one physical network card but have
software interfaces, e.g. a VMWare client.
Cause
The Ghost Windows multicast client is choosing the incorrect
network interface to use.
Solution
In the Task Properties window, in the Network tab,
choose to use Unicast.
File transfer to clients that have Firewalls installed
------------------------------------------------------
Problem
You are attempting to transfer files to one or more client
machines and the file transfer portion of the task times out.
The client machine is using the default Windows XP firewall.
Cause
The built-in Windows XP firewall prevents multicast packets
from being seen by the Ghost client.
Solution
In the Task Properties window, in the Network tab,
choose to use Unicast.
Alternatively, disable the XP firewall.
Transferring multiple files
---------------------------
Problem
When using the Console to transfer multiple files to client
machines the task takes longer than expected.
Cause
When doing a multicast file transfer there is a 20 second
delay between each file transfer.
Solution
There is no solution to this.
Multiple file transfer tasks
----------------------------
Problem
When executing more than one task that have file transfer
steps, the tasks do not execute in parallel.
Cause
The Ghost Console only supports one multicast file transfer at
any one time. If multiple tasks need to do file transfers, the
file transfer steps are put in a first-in first-off queue.
Solution
There is no solution to this.
Remote client uninstall
-----------------------
Problem
When you perform a remote client uninstall, the machine record
is not removed from the Console.
Cause
The client machine may be part of a task or other Console
item. Therefore the Console does not delete the machine
record.
Solution
After the uninstall, remove the machine from any tasks and
then delete it.
Remote client install
---------------------
Problem
Remote client install fails with the following message:
Connection: Credentials conflict
Cause
The Console already has a connection to the client machine.
Solution
1) Run net use machine c command from the command-line
to establish a connection to the client machine.
2) Run net use /delete machine c to force shut the open
connection to the client machine.
3) Try the Remote Client Installation process again. If this
still doesn t work, reboot the Console machine.
Remote client install
---------------------
Problem
You cannot do a remote client install to an XP Pro machine
which is a member of a Workgroup.
Solution
1) On the client machine, open Windows Explorer.
2) In the Tools menu, select Folder Options .
3) On the View tab, in the Advanced Settings list, uncheck
the Use simple file sharing (Recommended) checkbox.
4) Save the settings.
Remote client install
---------------------
You cannot remotely install the client on 9x machines or
Windows XP home machines.
Remote client install
---------------------
If you are unable to remotely install Windows 2000 or
Windows XP clients which are members of an active directory
domain, you should check that the time on the client machine
matches the PDC time. Windows 2000 and Windows XP clients use
the time as part of their security authentication.
Upgrades
--------
Problem
After upgrading Symantec Ghost 7.5 you go to launch one of
the components and you get the following message:
Installation source is not available for this product... .
Cause
This is due to a difference in the version of MSI used for
the 7.5 installation and the current installation.
Solution
Reboot your Console machine.
Executing commands in the Ghost partition
-----------------------------------------
Problem
You have specified an invalid command to be executed on the
client in the Ghost partition. The task completes and
reports success.
Cause
There is a problem in the way the DOS client starts tasks.
If a command is invalid then the client incorrectly reports
success.
If the command is valid but fails, then the client correctly
reports that the command failed.
Solution
Ensure that any command you specify to execute in DOS is
valid.
NT4 terminal server
-------------------
Problem
You can not run the Console on an NT4 terminal server machine.
The Console produces the following error:
The procedure entry point DsGetDcNameA could not be located
in the dynamic link library NETAPI32.DLL.
Cause
The Console is not supported on NT4 terminal server.
Solution
There is no solution to this.
Configuration change
--------------------
Problem
You have a clone and configuration change task. The image
contains an old client. The configuration specifies that
the client be added to an Active directory container or that
the Netbios name be overwritten. The configuration change
fails.
Cause
The old client does not support active directory containers or
Netbios names to be overwritten.
Solution
Either recreate the image with a new client or change the
configuration.
AutoInstall
===========
Deploying AI packages using HTTP
--------------------------------
Tasks which deploy AutoInstall packages using an HTTP
connection may be slow in responding. You should wait for the
HTTP connection to be confirmed before launching a second HTTP
task.
Deploying AI Packages
---------------------
Installing any AI package that contains a shortcut to a UNC
path, network path, or CD location on Windows NT 4 will time
out and fail installation when being deployed via
console/client. The workaround for this is to modify the
installation in AIBuilder before building the installation,
and comment-out or remove any shortcut that points to a UNC
path, network path, or CD location.
If you have used AutoInstall to install Norton AntiVirus
Corporate Edition on a client, do not use AutoInstall to
uninstall Norton AntiVirus. AutoInstall deletes some driver
settings, causing the Found New Hardware wizard to launch
after the computer is restarted.
When using AISnapshot to create an installation script that
will be built into an AI package executable, you need
to perform the comparison scan and build the executable
before allowing any reboot for all Microsoft products.
For all non Microsoft products, it is acceptable to allow
reboots and even configure the application before comparing
and building. Since all AI packages of Microsoft products
were built before the reboot, the installation continues
installing after the deployment and registers itself for
each user that logs into the target machine.
The uninstall using agent/console feature is not designed to
work with Microsoft products, due to limitations of having
to build the AI package before any reboots. Doing so may
result in corrupting the installation, and cause damage
to the target operating system.
Lotus Smart Suite Millennium Edition cannot be installed to
multiple users on a single computer. The installation is
installed for each user as a licensing protection. If the
related AI package is deployed when a user is logged on to the
machine, it will be installed for that user. If the machine is
logged off it will be deployed to the last logged on user.
When deploying McAfee Office Suite using the Ghost Console,
the package will install but may produce an error message when
launching the application.燭he errors are due to a font being
installed to the McAfee installation directory and not the
Windows fonts directory.燭his problem can be corrected by
installing the font:
1) In the Control Panel, open the fonts folder.
2) Use the File- Install new fonts... menu to install the
font.
Creating AI packages of software upgrades
-----------------------------------------
When you are trying to create a package of a software upgrade
(for example, upgrading pcAnywhere 9.2 to pcAnywhere 10), you
should use the following three-step procedure. This creates
three packages. Note the second step is only required for MSI
based installs.
1) Create a package of the uninstall of the old version of
the software, e.g. uninstall pcAnywhere 9.2.
2) If the new software installs a new version of MSI then
create a package of the install of this new MSI version.
3) Create a package of the install of the new software,
e.g.install pcAnywhere 10.
Ghost Explorer
==============
Do not use Ghost Explorer to browse Ghost image files
containing NTFS partitions that are spanned across multiple
CDs. Doing so results in frequent prompts to swap CDs. You
should copy the spans from the CDs onto a hard drive and
then browse them.
Files should not be added to the root folder of Linux ext2/3
partitions. If files are added, the image restores, but the
new files are not visible and e2fsck reports errors.
Files should not be added to the root folder of a Ghost boot
partition image containing PC DOS as computers cloned with
this image do not boot.
Ghost Boot Wizard
=================
During installation a set of folders is created containing
network drivers and other files required to support the Ghost
Boot Wizard.
The location of these folders depends on your Windows version
and would normally be:
Windows 2000:
Documents and Settings All Users Application Data Symantec
Ghost Template
Windows NT 4:
WINNT Profiles All Users Application Data Symantec Ghost
Template
Windows 98:
WINDOWS All Users Application Data Symantec Ghost Template
To customize boot disks and packages to support regional
keyboards and character sets, edit Local.cfg in the
... template common folder. Further instructions are contained
within this file.
This does not support languages requiring double byte
character sets.
Ghost.exe
=========
File preservation restrictions
------------------------------
Due to patent restictions, Symantec Ghost is unable to
preserve files on an existing NTFS filesystem when it is being
cloned over with a new FAT filesystem
USB and Firewire support
------------------------
Problem
Ghost.exe does not start. You have created a boot disk using
the Ghost Boot Wizard and have specified to override BIOS
USB support or override BIOS FireWire support . Or you have
started Ghost with either the -forceusb or -force1394 switch.
Cause
The settings chosen will force Ghost to take control of
either the USB or FireWire controller. Ghost is not always
able to successfully take control of the USB or Firewire
controllers, especially if the BIOS is actively using these.
Solution
Do not force Ghost to take control of the USB or Firewire
controller. If you wish to use either a Firewire or USB device
in most instances Ghost will be able to do so without the use
of these settings.
Booting from a PXE image
------------------------
Problem
When booting from a PXE image, ghost.exe fails to run.
Cause
During testing we have found that on a Dell Dimension 8100
there is a conflict between the PXE BIOS and the Ghost USB
code.
Solution
Run Ghost with the -nousb switch.
Writing to USB CD/DVD
---------------------
Problem
Ghost does not detect that your USB CD/DVD writer is available
to be written to.
Cause
During testing we have found that some USB CD/DVD writers
take several seconds to respond to our test commands. This
results in Ghost not detecting they are available for writing.
Solution
Wait several seconds and then open the file requester dialog
again. In most instances this will have given the device
enough time to respond.
Booting from a CD or DVD
------------------------
Problem
You have used Ghost to create a bootable CD or DVD. When you
try to boot from it, it hangs when loading the mouse driver.
Cause
The mouse driver is trying to write mouse.ini to the CD or DVD
which it cannot do.
Solution
When creating the bootable CD or DVD be sure that the floppy
which is used to make the CD or DVE bootable either has
mouse.ini on it already or does not load mouse.com.
File preservation when running from a CD or DVD
-----------------------------------------------
Problem
While attempting to do an operation which requires Ghost to
preserve files, and Ghost is run from a CD, Ghost aborts.
Cause
Ghost is trying to write the file preservation metadata file
to the CD or DVD.
Solution
Start Ghost with the -pfile switch, and specify a writeable
location for Ghost to write the file preservation metadata
file.
Tutorials
=========
The tutorials require more than 256 colors.
The tutorials on the CD may fail to run, or may crash, unless
the correct video driver for your display adapter is installed.
Other issues
============
Network driver not found or responding
--------------------------------------
If you have problems loading a driver when starting a computer
from a disk then try disabling plug-and-play in the BIOS.
In the BIOS change Plug Play O/S from Yes to No.
Network Interface card (NIC)
----------------------------
If after loading a boot partition and restarting the computer
the following error is displayed:
Unable to obtain IP address via DHCP
Try the following:
Configure the NIC using the utility that came with it. You may
need to alter the speed and duplex setting.
===============================================================
2. Cloning Windows 2000 and XP
===============================================================
Windows 2000/XP boot failures
-----------------------------
Boot failures after cloning Windows 2000/XP systems can
usually be attributed to one of two causes:
Cause 1
-------
Differences between the position and layout of partitions after
the clone resulted in new drive letters being assigned to
existing volumes by the booting system.
Some elements of the Windows boot process appear to access
files using paths with drive letters.
As a result, when the booting operating system fails to locate
the file due to the drive being allocated a new drive letter,
a boot failure occurs.
Solution
--------
When running Ghost, you can use one of the following
command-line options.
a. Initialize the disk signature using the -FDSZ (force disk
signature zero) switch. Initializing the disk signature
forces Windows to discard any existing drive letters
and to start reallocating new drive letters from scratch.
Note: Ghost generally performs this initialization
during a Windows disk load operation. It will not
perform this initialization if you are only loading a
partition. In this case the -FDSZ switch should be used to
fix a boot failure.
b. Alternately, if you wish to retain the allocated drive
letters, use the -FDSP switch (force disk signature
preserve). This will only be required on Windows
disk load operations that result in a boot failure.
Cause 2
-------
Windows does not have the correct mass storage controller
driver configured and loaded for the hardware it is booting on
due to hardware differences between the source and destination
computers.
Solution
--------
The Sysprep INF file (Sysprep.inf) contains a section
[SysprepMassStorage] for specifying one or more mass storage
controllers that you want Windows to load before it
continues to boot.
For more information, see the Microsoft Sysprep documentation
at:
www.microsoft.com/windows2000/library/planning/incremental
/sysprep11.asp
Cloning encrypted files
-----------------------
If you clone an image file that includes encrypted files on a
Windows 2000 or XP computer and you perform a SID change, the
encrypted files become inaccessible. Decrypt these files
before creating the image file.
===============================================================
3. Technical support details
===============================================================
Symantec corporation maintains a comprehensive Technical
Support Web site for Ghost at:
http://service.symantec.com
You can also contact our Technical Support department by phone.
See the Ghost manual for the telephone numbers and an
explanation of your phone support options. The telephone
numbers can also be found online.
At the above Web site, enter your Ghost version, and proceed
through the windows to find options such as Customer Contact,
Customer Service, or Technician.
Currently available online options include:
Ghost Frequently Asked Questions (FAQ)
--------------------------------------
The online version of the FAQ includes the top issues for
your version of Ghost, and is updated as the issues change.
Ghost Knowledge Base
--------------------
Search or browse through a collection of articles that can
answer your technical questions and help troubleshoot problems.
The Ghost Ask Symantec Discussion Forum
-----------------------------------------
This Ghost discussion group is hosted by experienced Ghost
technicians who answer your questions, refer you to the
appropriate knowledge base documents, and help you solve Ghost
problems.
File Downloads
--------------
The File Downloads site has free Ghost files such as the latest
version of the Ghost User Guide, and any additional utilities
for Ghost.
===============================================================
4. Reporting problems to Technical Support
===============================================================
When contacting technical support, make sure you have included
the following information:
- Your name and contact details.
- The Ghost Abort error log file if available. The Ghost
Abort error log file is generated in the current folder and
is named Ghosterr.txt. If this location is read-only, the
-afile=filename command line switch can be used to alter
the abort files output location.
- The version number of the Ghost application and associated
Ghost Utility in use.
- The Abort text displayed.
- The Abort Error Number displayed.
- Whether or not you can reproduce the problem.
- A description of the problem.
- A description of what operation is being performed.
===============================================================
END OF FILE
===============================================================