Apple Mac OS X Server Migration For Version 10.3 or Later Manuel d'utilisateur télécharger pdf (Page 8)

Note: Starting with PGP Universal Satellite version 3.2, Microsoft Windows 2000 Professional and Microsoft Windows 2000

Server & Advanced Server are no longer supported.

Installation and Upgrade

Symantec Encryption Management Server version 3.3.1 does not support host names longer than 64 ASCII characters. In

addition, Symantec Encryption Management Server version 3.3.1 does not support gTLD (generic Top Level Domain names).

■

If you have a hardware token Ignition Key or a Hardware Security Module (HSM), you must contact Technical Support before you

migrate to Symantec Encryption Management Server 3.3. Migrating to version 3.3 requires that you create a new setting on the

upgraded (3.3) version of Symantec Encryption Management Server before you restore the backup file from your previous system.

This setting can only be added through SSH access with the help of Technical Support. If you migrate to version 3.3 without

adding this preference, you will be locked out of the user interface after the upgrade. As a result, you cannot use your hardware

token Ignition Key to unlock your Symantec Encryption Management Server. [27062/2472017]

■

If you are running PGP Universal Server 3.2 with an older version of PGP Desktop and Certificate Enrollment is enabled,

AutoUpdate fails. However, if you want to perform an update of your clients, you must briefly disable certificate enrollment.

■

In Symantec Encryption Management Server, do the following:

Select Consumers > Consumer Policy > Default policy > Consumer Policy Options > General > Edit.1.

Deselect the Notify users of software updates and automatically download checkbox.2.

AutoUpdate is disabled.

On the Directory Synchronization Settings dialog box, select Deny Certificate Enrollment and click Save.3.

Certificate enrollment is disabled.

If necessary, update Symantec Encryption Management Server to have the desired version of Symantec Encryption

Desktop

Select the Notify users of software updates and automatically download checkbox.5.

AutoUpdate is enabled.

In Symantec Encryption Desktop, complete a manual policy update.6.

It can take up to 24 hours for the client to download the installer and update itself.

Upgrade Symantec Encryption Desktop to the correct version.7.

In Symantec Encryption Management Server, in the Directory Synchronization Settings dialog box, select Allow

Certificate Enrollment and click Save.

Certificate enrollment is enabled. [31480/2476437]

When you try to join a node to a cluster, this node is locked by the ignition key. As a result, the status of this node in the sponsor

node appears as Pending even after the join is complete. [30233/2475190]

■

During a PUP update, some exceptions appear in the logs. These exceptions have been noted and can be safely ignored. After

the PUP update is complete, all services should start up correctly, and no additional exceptions should occur. [31060/2476017]

■

Internal user enrollment is not supported in DMZ node if the Host internal user private keys for Internal Users and Consumer

Groups checkbox is not selected.[30166/2475123]

■

When you select a location to save a backup, if you enter non-ASCII characters in the Backup Name field, an error message

notifies you that your backup is invalid. Because different file systems treat multiple byte characters differently, your backup file

name must consist only of alphanumeric characters. [30140/2475097, 18619/2463811]

■

In the Cluster logs, when you join a node to a cluster, warning messages appear.■

An example of a warning message is:

/usr/share/ovid/pgprep/rep-join-collect.py> pg_dump

These warnings are intended to be informative, and no action is required. [29773/2474729]

Symantec Patch Distribution Center now provides all binary updates, which replaces PGP update servers. Automatic updates

through the PGP update servers are no longer available.[28208/2473164]

■

When joining a node to a cluster, if the sponsoring server is busy (for example, while the nightly key maintenance process is

running) it can take a long time for the join process to complete. If Symantec Encryption Management Server cannot complete the

join at another time, you need to stop crond and possibly shut down the key maintenance process before starting the join. Contact

Symantec Corporation Technical Support for help. [27841/2472796]

■

Upgrading to PGP Universal Server 3.0 removes LDAP query customization. When you upgrade to PGP Universal Server 3.0 and

later, customized LDAP queries must be recreated as necessary. With the enhancements to LDAP support in PGP Universal

Server 3.0, LDAP query customization may no longer be needed. [27366/2472321]

■

A SSH key created and saved as a file using the PuTTY utility (PuTTYgen) cannot be imported as an Administrator key using the

Key File import function. (Select System > Administrators, click the administrator name, and click + to add an SSHv2 key.)

Instead, you must copy the key block from the PuTTY Key Generator and paste it in Key Block. [27325/2472280]

■

e 8 of 13S

mantec Encr

tion Mana

ement Server Version 3.3 Release Notes

1 2 3 4 5 6 7 8 9 10 11 12 13

Commentaires sur ces manuels

Pas de commentaire

Apple Mac OS X Server Migration For Version 10.3 or Later Manuel d'utilisateur Page 8

Commentaires sur ces manuels

Produits connexes et manuels pour Logiciel Apple Mac OS X Server Migration For Version 10.3 or Later