Prompted for PGP Desktop License on a Managed Client

Article:TECH149877  |  Created: 2010-07-15  |  Updated: 2012-02-03  |  Article URL http://www.symantec.com/docs/TECH149877
Article Type
Technical Solution


Issue



PGP Desktop client users are prompted to input license information in a PGP Universal Server managed environment.

 


Solution



This can occur when the installer downloaded from the PGP Universal Server is not using a customized client installer. When downloading an installer for managed clients, make sure to place a checkmark next to Customize, specify any additional settings if necessary, and then click Download.

This enables the license and other policy settings to be applied to the client during enrollment.

When selecting Customize, you can choose to Auto-detect Policy Group or use a Preset Policy Group, specify the PGP Universal Server name, and Mail Server name.

 

  • Auto-detect Policy Group - PGP Desktop coordinates with the PGP Universal Server to identify the correct policy group for the consumer. Sort consumers into groups by user type, or by matching consumer attributes to domains, dictionary entries or through LDAP values. Based on these attributes, the appropriate policy is applied. If you later create a new group and the users attributes match that group, the policy for the consumer switches to the policy for that new group. If you have not created any custom groups, the consumer policy for the default Everyone group applies.

     
  • Preset policy - Select a consumer policy to apply to the installer you are creating. All users who get this installer are bound to the selected policy. If you change the settings of the policy later, those settings that are not implemented at installation (such as creating a PGP Virtual Disk volume) are modified for the PGP Desktop users who are bound to this policy. If you have not created any custom consumer policies, the default policy is the only user policy you can apply to the installer.

 



Legacy ID



2135


Article URL http://www.symantec.com/docs/TECH149877


Terms of use for this information are found in Legal Notices