PGP Desktop 10 license displays incorrectly after renewal
|Article:TECH149571|||||Created: 2009-09-30|||||Updated: 2011-04-26|||||Article URL http://www.symantec.com/docs/TECH149571|
After renewing and updating the license on the PGP Universal Server for PGP Desktop, the PGP Desktop client license does not display the correct expiration date.
This issue may be resolved by stopping and restarting the PGP Services on the client computer. This forces the client to retrieve a policy update from the PGP Universal Server. To stop and restart the PGP Services:
- Click the PGP Tray icon and select Exit PGP Services.
- Click Start > All Programs > Startup > PGPtray.exe
If restarting the PGP Services does not update the license on the client, try deleting the PGP preferences then re-enroll the client with the PGP Universal Server. Use the following steps to re-enroll the client.
- Stop PGP Services by clicking the PGP Tray icon and selecting Exit PGP Services.
- Delete the PGP preferences file on the client system by deleting the PGP folder. The folder is located in the following directory:
Windows XP - C:\Documents and Settings\%username%\Application Data\PGP Corporation
Windows Vista - C:\Users\%username%\AppData\Roaming\PGP Corporation
Note: You may need to change the view settings in Windows Explorer to Show hidden files and folders to display the Application Data/AppData folders.
- Click Start > All Programs > Startup > PGPtray.exe. The PGP Enrollment Assistant is displayed.
- After re-enrolling the client, the PGP License information should properly display the update on the PGP Desktop client.
|Caution: If re-enrolling a Whole Disk Encrypted PGP Desktop client with a version which does not match the version of the server e.g. PGP Desktop 9.8.0 with PGP Universal Server 9.9.1, it is recommended to create and send a new WDRT for the client to the server.
Use the following command to create a new WDRT from the command line from the C:\Program Files\PGP Corporation\PGP Desktop directory:
pgpwde --new-wdrt --disk <number> --admin-authorization --admin-passphrase <phrase> --recovery-token <string>
Article URL http://www.symantec.com/docs/TECH149571