|
|
请看发行说明：
===============================================================
Symantec Ghost Solution Suite 2.0.2 README.TXT
Copyright ?2007 Symantec Corporation. All rights reserved.
Symantec, the Symantec logo, Symantec Ghost, Ghost Walker,
Ghost Explorer, GDisk, GhostCast, and OmniFS are trademarks or
registered trademarks of Symantec Corporation or its affiliates
in the U.S. and other countries. Other names may be trademarks
of their respective owners.
The Licensed Software and Documentation are deemed to be
"commercial computer software" and "commercial computer
software documentation" as defined in FAR Sections
12.212 and DFARS Section 227.7202.
December 2007
===============================================================
Symantec Ghost 11.0.2 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. Installation Note
2. New Features
3. Defect fixes and enhancements
4. Known issues
5. Technical support details
6. Reporting problems to Technical Support
===============================================================
1. Installation Note
===============================================================
The standalone Symantec User Migration Wizard is not supported
by LiveUpdate. After updating Ghost Console, apply the
installation package located in [Program Files]
\Ghost\SUMWizardInstall to each client installation
===============================================================
2. New Features
==============================================================
The following new features have been added:
The ability to create local user account objects when you
restore User Migration packages.
The ability to enable the Shortcut Resolution Check
feature. This prevents the restoration of shortcuts that
point to network resources, and other shortcuts that cannot
be automatically resolved during the restore process.
Creating local user account objects
-----------------------------------
You can now create local user account objects when you restore
User Migration packages.
All local account objects are created with the "User must
change password at next logon" attribute enabled. Optionally
accounts can be created with the "Account is disabled"
attribute set. When migration is complete, an administrator
may enable each account (as required) locally, or remotely
using the MMC computer management snap in.
To set or change these settings, edit the following
registry entry:
HKLM\Software\Symantec\Symantec User Migration
The following key creates local user account objects:
- LocalAccountPassword
If this key is not present, no local user account objects
will be created when you restore User Migration Packages.
This key is of type String.
The key Value is the initial password for all local user
accounts that are created. Each user will be prompted to
change their password when they log on for the first time.
If the Value is not specified, an empty password is
created.
--------------------------------------------------------------
Note
----
The initial password must comply with local security policy
and password complexity rules. If the value specified for the
password does not comply with local security policy, the
account object will not be created.
Windows security policy for local accounts is displayed in
Control Panel > Administrative Tools > Local Security
Settings > Account Policies > Password Policy.
For example, setting the LocalAccountPassword value to
My_Password99 passes the default password policy complexity
checks for Windows 2000, XP, and Vista domains.
-------------------------------------------------------------
The following key sets the "Account is disabled" attribute
for local user account objects that are created by the
LocalAccountPassword key:
- CreateLocalAccountDisabled
This key is of type DWord.
The key Value must be any non-zero value to set the
"Account is disabled" attribute. The accounts must be
enabled by an administrator before the users can log in.
To turn off this key so that the "Account is disabled"
attribute is not set, change the Value to 0.
Preservation of shortcuts
-------------------------
All shortcuts are now restored automatically. This includes
shortcuts for which the target cannot be found on the local
computer. Network shortcuts are currently included in the
unresolved shortcuts category.
To change this setting, edit the appropriate registry entry:
HKLM\Software\Symantec\Symantec User Migration
The following key controls the restoration of unresolved
shortcuts:
- RestoreUnresolvedShortcuts
This key is of type DWord.
The value must be any non-zero value to restore
unresolved shortcuts.
To skip unresolved shortcuts set the value to 0.
===============================================================
3. Defect fixes and enhancements
===============================================================
The following defect fixes and enhancements have been made:
- Fixed support for RIS in Ghost Boot Wizard
- Fixed support for two bootable Vista installations on a
single disk
- Some Ghost clients were not shown in the Console due to
duplicate IDs in some models of computer (as supplied by
the manufacturer). Ghost now handles this situation
correctly and every client is displayed in the Console.
- Fixed aiobuf sync() position error on client machines.
- Fixed bug that caused "Cannot find DHCP server" error when
using network boot disks created with Ghost Boot Wizard.
- Fixed bug that caused files added to the second partition
of an image using Ghost Explorer to display in the first
partition. All files are now displayed correctly.
- Fixed bug that caused Ghost client to crash (with a general
protection fault) when rebooting into DOS.
- Exclusions now work correctly in Console User Migration.
- When using the DOS version ghregedt.exe, the command-line
switch "addvalue" now works correctly.
- Outlook email is now correctly migrated when PST or PAB
files are included in the migration templates
(for example, stored in the My Documents folder).
===============================================================
4. Known Issues
===============================================================
Ghost Walker (GhWalk32.exe)
---------------------------
Scenario:
Create a Windows Vista WinPE USB drive and then copy
GhWalk32.exe to the USB drive. When you press Enter after
Ghost Walker asks you to "Continue and Update", Ghost Walker
exits without any warning.
To avoid this issue, run Ghost Walker using the following
command line syntax:
GHWALK32 /AV=NONE
This specifies that all other volumes are not to be included
as additional volumes.
Installing a client
-------------------
If you install the Ghost Console on Windows 2000 Professional
or Server on a FAT32 partition then a remote client install
returns an error message that the install has failed, even
if the install was successful.
A workaround for this error is to install the Ghost Console
on an NTFS platform or to check the client install in the Ghost
Console.
Disk order
----------
When a computer is installed with Microsoft Vista, the disks
might not be ordered as they are in the BIOS.
The Ghost Implementation Guide details how to determine disk
order.
Symantec Ghost Console
----------------------
Ghost Console Service account credentials
-----------------------------------------
If you install the Ghost Console on a computer with a
computer name that has more than 15 characters then you cannot
add the service account when you add a supported domain. The
following message is displayed:
The specified username is invalid.
Error code: 2147944602
Operation failed
The work around for this error is to edit the Console service
account user name and password and ensure that they are
15 characters or less.
Entering arguments for a command in a Execute Command task
----------------------------------------------------------
If you enter arguments for a command in a Execute Command task
between single quote then you cannot save the task.
The workaround for this problem is to save the arguments
between double quotes.
Symantec Ghost Console and mixed domain
---------------------------------------
If you have installed the Symantec Ghost Console on a
Windows 2000 SP 4 computer that is a member of a Windows
2000 mixed domain, then the Console does not add client
computers to Windows 2003 native domains.
Console client connected to multiple networks
---------------------------------------------
Deploy AI package and Transfer Files tasks on a Windows 98
computer do not complete if the Console client is connected
to multiple networks.
Runtime Error
-------------
If there is not enough available space to create a user
migration package then the Console client fails with the
following error:
Runtime Error
Program <Ghost directory> ngctw32.exe
R 6025 - pure virtual function call
The workaround for this problem is to ensure that there is
enough space available to create the migration package.
The package is always stored locally, and then transferred
to the Console.
Windows 98SE Console client failed to restart
---------------------------------------------
If a Console client computer running Windows 98SE fails to
reboot into the virtual partition then a possible workaround
is to increase the virtual partition size.
Image create task error
----------------------
You are executing an image create task and you get the
following error:
Connection reset by server with GhostCode 19945
This error may be caused by lack of space to create the image
file. Ensure that you have enough disk space in which to create
the image file.
Incremental backup of Symantec AntiVirus 10.0.2
-----------------------------------------------
An incremental backup of a computer installed with Symantec
AntiVirus 10.0.2 fails to restore Symantec AntiVirus
successfully.
The backup is successful, but on the client the following error is
displayed:
Symantec AntiVirus Auto-Protect failed to load.
The workaround for this problem is to repair the installation
of Symantec AntiVirus after restoring the backup.
int86_16.dll file
-----------------
The Symantec Ghost Implementation Guides states that you can
find int86_16.dll in the Symantec Ghost Solution Suite
folder. This is incorrect. To obtain this file, you must install
the Console client on a Windows 9x computer. You can then find
this file on the client computer.
VMWare computer
---------------
A VMWare client with a fixed MAC address with the prefix suggested
by VMWare (00-50-56-xx-yy-zz) does not appear in the Console.
Fixed MAC addresses in VMWare are not supported.
Client computer with two network cards
--------------------------------------
A Console task fails in the following situation:
The client is installed on a client computer with a network
card. You unplug the network card and plug in a second network
card. After executing a Configuration Refresh, the last known
machine configuration displays the correct network card.
However, on the Properties dialog box, the Network Settings
when using Virtual Partition field shows the original card.
A Console task will fail as it looks for the incorrect card.
On the client computer, you can see the following message:
Client polling for server
This indicates that the client can't connect to the server.
This scenario occurs only when the network cards use different
drivers.
Workaround: Remove the client computer from the Console and
let the Console redetect the client computer. Alternatively,
you could use the UNDI driver.
A task run from DOS fails in the following situation:
If you have two network cards in a client computer that use
the same driver then the client might not be able to connect
to the server.
On the client computer, you can see the following message:
Client polling for bound server
Workaround: Halt the task and use Ghreboot to restart the computer
back into Windows. Use the UNDI driver to run the task.
A Console task fails in the following situation:
A client computer has one connected card without a NIC driver,
and one disconnected card. The remote install of the Console
client selects the disconnected card as the recommended network card.
When a Console task is run it cannot connect to the client.
Workaround: Manually assign the correct NIC driver in the Ghost
Console client properties dialog box or use the UNDI driver.
Sysprep
-------
Using Sysprep in an image create task
-------------------------------------
An image create task using Sysprep fails in the following setup:
You run a Sysprep task and it fails. If you run a Sysprep
task again on the same computer, then the task fails because
the Sysprep files cannot be copied over the existing Sysprep
files that are read-only.
Casual tasks and Sysprep
------------------------
If you change the unattend files of a casual task then the
unattend files of the template task from which the task was
created is also updated with the new files.
Joining a Vista computer to a domain after a clone and
using Sysprep
------------------------------------------------------
An error occurs with the following operation:
You clone a Vista computer after using Sysprep and then
apply configuration changes including joining the computer to
a domain. The following error displays on the client computer:
Windows can't complete the installation
The workaround for this problem is to join the computer to
a domain using a different task after the clone task.
Running a configuration refresh task
------------------------------------
If you run an image restore task that includes a configuration
refresh step and the image that has been prepared with Sysprep,
then the client IP address and subnet mask are reported
incorrectly as 0.0.0.0.
Do not include a refresh step in a task if the image in the
restore has been prepared with Sysprep.
The workaround for this problem is to run the refresh step in a
separate task after the restore image task.
Restoring a Vista image that has been prepared with Sysprep
-----------------------------------------------------------
If you restore a Vista image file and apply static IP in a
configuration template after the task has been executed then
the WINS server address is not applied to the Vista client
computer.
Client inventory
----------------
win32_product
-------------
Windows Server 2003 and Windows XP x64 do not install
win32_product.
Therefore, Symantec Ghost cannot collect the Application Product
information using the Inventory feature of the Symantec Ghost
Console on the following computers:
* Computers that are installed with Windows Server 2003
* Computers that are installed with Windows XP x64
NT client computers
-------------------
On NT computers, the client inventory is not fully collected.
The workaround for this error is to restart the client service
in one of the following ways:
* On the Console client restart the client service
* From the Ghost Console transfer to and execute on the client
computer a batch file with the following commands:
net stop "symantec ghost client agent"
net start "symantec ghost client agent"
Once you have restarted the client service you can run an
inventory refresh task to collect the full inventory.
Preserved files on Vista computers
----------------------------------
Sometimes Windows Explorer in Vista does not show the correct name
for folders that were preserved and renamed from a Vista
partition after a clone task. This problem occurs if the
renamed folder contains a copy of desktop.ini.
Workaround: Find and delete the hidden file named desktop.ini
inside the affected folders. Windows Explorer should then
correctly display the folder name.
Ghost32 error 29005
-------------------
If you restore an image to a disk configured as a dynamic disk
with a single simple volume on it on a Vista RTM Ultimate
computer then Ghost32 fails with the following error:
write sector failure 29005
Workaround: In Disk Manager, convert the disk to an mbr disk
and then restore the image.
AutoInstall
-----------
Drag-and-drop
-------------
On Vista operating systems, in AI Builder, drag-and-drop
operations between windows with different privileges are
disabled.
VMWare computers
----------------
Using a Mapped Network Boot Package made with PC-DOS and the
UNDI driver can cause the following error:
Network drive no longer exists reading drive <drive>
The work-around for this problem is to use MS-DOS under VMWare,
or use a custom network driver.
Ghost disk layout switch
------------------------
By default, Symantec Ghost informs the operating system about
the disk layout after a clone operation. However, this might
cause the crc files created by Symantec Ghost to return a false
result, i.e. that the disks are not identical when they are
identical.
For example, after an image-to-disk restore, a crc32 verify
operation might return an inaccurate crc result because WinPE
could change the destination file systems on the drive.
In a disk-to-disk copy operation under WinPE, the source disk
remains mounted by Windows. Therefore a CRC create on the source
disk and then a verify on the destination disk may return an
inaccurate crc result because WinPE could change the source drive.
The -noOsLayout switch will prevent Ghost from updating the
operating system with the destination disk changes. However
the source is still mounted by Windows and therefore the
CRC value may change due to system file changes by Windows.
If the source image and destination disk have similar
partition layouts, then to ensure the crc checks do not give
false negatives, it is also advisable to use GDisk32 to
delete all existing partitions on the destination disk.
This prevents the operating system from mounting a file system
driver once the clone is complete. This can happen on
similarly partitioned disks even when you use the
-noOsLayout switch.
Peer-to-peer Ghost operation with preserve switch
-------------------------------------------------
Error Number: 672
Message: Ghost could not locate or lock the volume containing preserved
file/directory.
This error is displayed when using Ghost in peer-to-peer TCP mode with
the -preserve switch.
Symantec Ghost does not support the preserve file feature in a peer-
to-peer operation.
User Migration Wizard
---------------------
You can use XML Options to control user profile selection for
the standalone user migration wizard.
To use these options, add values to an exported user migration
template SCMMigrationOptions.xml just before the </Tables> tag.
You can use the following as an example:
<migrationOptions type="load" version="1.0">
<userProfiles>
<profileType>MatchName</profileType>
<profileName>MyDomainName\MyUserName</profileName>
<lastAccessed>30</lastAccessed>
</userProfiles>
</migrationOptions>
Be sure you remove any tag pairs for unused options and
specify the required values.
Values for <profileType> include the following:
All
Domain
Local
LastLoggedIn
MatchName
Values for <profileName> (used with MatchName only) include
the following:
2K3N\* - all users of the 2K3N domain
2K3N\Sue_User - the 2K3N domain user Sue_User
Joe_User - the local user Joe_User
*Joe_User - Local and domain users called Joe_User
2K3N\Sue_User, 2K3N\Joe_User - both Sue and Joe from 2K3N
Values for <lastAccessed> (number of days) include the
following:
1-365
After you add the required options, open the XML file using
Internet Explorer and check that the options you have specified
are viewable.
Restoring Files
---------------
Any files that are not associated with a user and cannot be
restored to a specified destination are restored to
\Desktop\Recovered Migration Files\ for one of the following:
* The logged-in user if the user is in the package
* The first user in the package
Naming a package
----------------
The Symantec Ghost documentation incorrectly states that a user
package is named with the format scmpkg#. A user package is
named with the computer name and a date-time stamp. The same
format for the package is displayed in the Ghost Console.
Migrating Word 2003 to Word 2007
--------------------------------
Settings stored in Normal.dot for Microsoft Word 2003
cannot be migrated to Microsoft Word 2007. This is due to
file format changes.
Therefore many settings cannot be migrated from Word 2003
to Word 2007.
LocalDrive on Windows 98SE
--------------------------
On Windows 98SE, the files from local drives cannot be captured in a
migration package using the system variable $LocalDrive$.
The workaround for this problem is to use individual drivers
letters.
For example, c:\*.txt and d:\*.txt.
Linux support
-------------
The Symantec Ghost Implementation Guide lists Ubuntu as a
supported Linux version. This information is incorrect.
Symantec Ghost does not support Ubuntu.
Formatting a partition in GDisk or GDisk32
-----------------------------------------
If you create a partition and formatting it as NTFS in GDisk or
GDisk32, the format is quick regardless of whether or not the
/q switch is used.
Changing the Symantec Ghost database account and password
---------------------------------------------------------
The Symantec Ghost Implementation Guide details how to change
the Symantec Ghost database account and password using a script.
However, the script in the Guide is not accurate. Following is
the correct script:
' This script allows the user to get and also reset the Ghost Console's
' database account and password by using the scripting API to the Ghost
' Configuration Server service.
'
' It can be used three ways:
' - with no arguments, it retrieves the current user account name and
' password used by the Ghost Console to access the configuration database.
' - with one argument, it sets the password for the user account used by
' the Ghost Console to access the configuration database
' - with two arguments, the first being the string "dba", it will allow
' a password to be set for the built-in DBA user account that some
' existing users may have code that depends on. In Ghost Solution Suite
' 1.1 and above, this user account is disabled at installation time for
' additional security; running this script allows it to be re-enabled.
<job id="PasswordUtility">
<script language="VBScript">
' Access the Configuration Server service's root COM scripting object
set server = CreateObject("ConfigServer.Application")
' Get the database configuration object from the configuration server
set dbInfo = server.ConfigDatabase
' Obtain the current database username and password
user = dbInfo.Username
pass = dbinfo.Password
set args = WScript.Arguments
if args.Count = 0 then
WScript.Echo "User: " & user
WScript.Echo "Password: " & pass
elseif args.Count = 1 then
pass = args.item(0)
call dbInfo.SetCredentials (user, pass)
WScript.Echo "User: " & user
WScript.Echo "Password set to: " & pass
elseif args.count = 2 and args.item(0) = "dba" then
pass = args.item(1)
call dbInfo.SetCredentials ("dba", pass)
WScript.Echo "DBA Password set to: " & pass
end if
</script>
</job>
Trialware
---------
You can not install the trialware version of Ghost over any
other version of Ghost, or install any version of Ghost over
the trialware version. In all cases uninstall the currently
installed product first.
If you have created an image file using the trialware version
of Symantec Ghost of a computer that includes Ghost.exe, the
trialware version of Ghost.exe is included in the image.
Because the trialware version of Ghost.exe expires after 30 days
you must uninstall the trialware version and then install
the licensed version of Ghost.exe.
If you have created an image of a computer with the trialware client
installed, you must first uninstall the trialware client before
installing the licensed version of Symantec Ghost client.
This is because in some situations the trialware Ghost.exe remains
on the client computer.
Symantec DeployCenter
--------------------
For all Symantec DeployCenter issues please see the
DeployCenter readme, which is included in Symantec Ghost
Solution Suite.
===============================================================
5. 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.
===============================================================
6. 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 |
|
IP卡
狗仔卡
发表于 2008-2-3 14:23:05
收藏
支持
反对
提升卡
沉默卡
喧嚣卡
变色卡
千斤顶
显身卡
发表于 2008-2-3 21:22:27
