After successfully licensing and using PGP Command Line on a system on a VMware machine, the software license displays as invalid.
PGP Command Line is licensed based on the number of processors on the computer. If the processor allocated to the VMware instance changes, the PGP Command Line license can be affected by the change and display the license as invalid.
This issue can be resolved by configuring the processor affinity for the instance of VMware machine where PGP Command Line is installed. This prevents VMware from allocating different processors to the VMware instance for your PGP Command Line.
If DRS is enabled for your VMware, the option to configure your CPU affinity options are not available. A workaround to this issue is to include the licensing information with the batch file when performing encryption.
Licensing PGP Command Line 10.1.0
To license PGP Desktop, you must enter a Name, Organization, and License Number. For versions of PGP Desktop 10.1 and above, the license number for your software is obtained by logging into your account on the Symantec Licensing Portal and then authorizing the software using the following for the Name and Organization:
Name: Authorized User
Organization: Authorized Company
Note: All PGP Desktop products are authorized using the same Name and Organization. Contacting the PGP License Authorization Server is no longer required to authorize a PGP software license.
Your License Number and order information is included on the Symantec Licensing Portal. This information includes a Product Description, License Type, Number of Seats and the Maintenance Level purchased. Your Symantec Licensing Portal account login name and a link to login are included in your order confirmation email.
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.