HOW TO: Re-enroll PGP Desktop for Mac OS X Clients
|Article:TECH178358|||||Created: 2012-01-05|||||Updated: 2012-08-29|||||Article URL http://www.symantec.com/docs/TECH178358|
This article describes the steps to re-enroll PGP Desktop for Mac clients.
For instructions on how to re-enroll PGP Desktop for Windows clients, please see the following KB:
Enrollment is the binding of a computer with PGP client software installed to a PGP Universal Server. After a client is bound it receives feature policy information from the PGP Universal Server; for example, encryption keys, email policy, or PGP Whole Disk Encryption administration.
In some circumstances, you may need to re-enroll PGP Desktop clients if the client is experiencing connection problems with the PGP Universal Server, the client license does not update after renewing the client license on the server, or in rare circumstances the client PGP preference file become corrupted.
Use the following steps to re-enroll a PGP Desktop for Mac client with a PGP Universal Server.
- Stop the PGP Services by pressing the Option key, click the PGP icon on the menu bar and select Quit.
- Browse to the ~/Library/Preferences folder.
Note: The ~ refers to the user profile (home) directory.
- Move all the com.pgp.* files to Trash (there will be com.pgp.desktop and other com.pgp plist files that should be moved to Trash).
- For PGP Desktop 9.x, follow the next steps. For PGP Desktop 10.x and above, simply re-launch PGP.app.
- Open the Terminal application.
- Type defaults write com.pgp.pgp configurationString "ovid=example.keyserver.com&mail=*&admin=1"
Note: Steps (5-6) is only necessary when using PGP Desktop 9.x clients.
Launch PGP Desktop to start the PGP Enrollment Assistant.
For PGP Desktop 10.x,if enrollment does not begin: Check under /Applications/PGP.app/Contents/Resources/policy.txt ---- This should contain a string similar to this 'ovid=keys.example.com&mail=*&admin=1'. If there is any trouble resolving the hostname found in the string then enrollment will not function as expected.
Article URL http://www.symantec.com/docs/TECH178358