Upgrading PGP installations with RDD clients enrolled prior to 3.2.MP3
|Article:TECH181104|||||Created: 2012-02-09|||||Updated: 2012-02-13|||||Article URL http://www.symantec.com/docs/TECH181104|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
The Intel RDD feature in PGP Desktop 10.2.MP3/Universal Server 3.2.MP3 is incompatibile with previous versions of Intel AntiTheft. When upgrading from a version prior to MP3 you must follow this procedure to prevent problems with machines rendezvousing with the Universal Server.
If this procedure is not followed, you may see the following error:
Error: could not load client context for <machine ID>
To upgrade the clients and server:
1. Group any machines that are currently managed by RDD into a policy that does not have RDD enabled, or disable RDD in the current policy.
2. Force a policy update from the client side (PGPTray->Update Policy).
3. Force a disk decryption from the client. This will decrypt the disk and set the RDD chip to "AT Decommissioned".
4. Update the PGP Universal Server to version 3.2.MP3 or later.
5. Upgrade PGP Desktop(s) to version 3.2.MP3 or later.
6. Configure the effective policy to enable RDD.
7. Update policy from client. If automatic encryption is enabled disk encryption will start, otherwise start encryption from the client.
8. When encryption starts the RDD chip will get placed into an "AT Activated" state.
If you did not decrypt the clients prior to the upgrade, please contact PGP Technical Support for assistance.
Article URL http://www.symantec.com/docs/TECH181104