12/27/2023 0 Comments Symantec encryption desktop verifyPost install, when the PGP client attempts to check in, it will attempt to resolve the PGPSTAMP value, or " " FQDN, which will go to the Load Balancer.Īt this point, you will need to consider how the TLS communications should behave.īecause the PGPSTAMP is pointing to " ", the TLS certificate being used for the interface should also match " ", whether it is the PGP Server that presents the TLS certificate or the Load Balancer. So when you build the PGP client, enter this hostname and this will assign " " for the installer package, this is called the "PGPSTAMP", which is the FQDN for the PGP Server. In one example, the Load Balancer FQDN could be named " ". For example, if you have two PGP Servers, one called " " and the other " ", you'll want to use a name that will resolve to the Load Balancer and then Load Balancer will then redirect traffic to one of the two servers in question. If you are using a Load Balancer to route communications to the PGP server, enter the FQDN the Load Balancer will be using. Section 2 of 5: Load Balancers - TLS Passthrough VS TLS Renegotiation, Wildcard Certificate VS Single FQDN Certificate: The Encryption Management Server you are using to create the installer is listed by default. In the Symantec Encryption Server field, type the Encryption Management Server you want the application to interact with.This not typically desired, so checking the box will create the proper managed client. If you choose this option, the user will be in charge of managing their own license number, PGP keys, etc. If this is not checked, it will create a "Standalone/Unmanaged" client that will not communicate with the PGP Server. Reminder: As mentioned above, make sure the Customize check box is selected.In the Platform field, select Mac OS X, Linux 32-Bit, Linux 64-Bit ,Windows 32-bit or Windows 64-bit as appropriate.In the Client field, select Symantec Encryption Desktop.If you wand Standalone, leave the box unchecked, and you will be prompted for the usual standalone setup that requires a license number to be entered This is a critical step if you wish to have your PGP Client managed by the PGP Server. If you do not click the Customize option, then it will download a standalone client, and you will not get the usual enrollment wizard to bind your PGP Client with the PGP server. When you click the "Customize" box, this will create the client that will communicate directly with your own PGP server using a unique FQDN. Important Note: For the PGP Desktop client to be able to enroll and communicate with the PGP Server, the "Customize" box must be checked. The Download Symantec Encryption Clients screen will then be displayed: On this page above, click Download Client button at the bottom.Click Consumers, and then click Groups:.Login to the Encryption Management Server administrative interface.This is the best option to use if Directory Synchronization is being used to enroll clients. The Auto-Detect Policy option means that when the user enrolls with the server, the policy is automatically applied. Section 1 of 5: Creating an Installer with Auto-Detect Policy The PGP Server can allow you to create two client installer types: Auto Detect and Preset Policy-the former being the most widely used and recommended option. You create PGP Desktop client installers with the features and settings that support your organization's security requirements and then deploy those client installers to your end users. The Symantec Encryption Management Server (SEMS/PGP Server) manages all of the Symantec Encryption Desktop (SED/PGP Desktop) clients that are deployed to the environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |