Endpoint Encryption

I need to install multiple Endpoint Encryption Management servers for redundancy and the documentation that I've found says you must install only one primary and the rest as secondary servers.

Can you install the additional Endpoint Encryption Management servers using the same database as the primary (shared DB like Endpoint Protection) or do they have to have a separate database for each install  (not stated in any docs I've found)?

What version are you running?  As far as the documentation goes, there is no mention of SEE MS clustering anymore in the v11.* documentation.

Even the older SEE8.* documentation, only mentions it in passing as using Windows NLB (see page 114 of the Install Guide):

http://www.symantec.com/docs/DOC5560

Thanks for the response, Symantec Endpoint Encryption is v11.0.1 MP1 (the latest as far as I know).

I know there is very little reference to any kind of redundancy/failover, just thought there may be a solution or something that I was missing. Endpoint Protection has a specific setup for this to provide failover/load balancing and was hoping that Endpoint Encryption would be similar.

So what is the recommended solution, just run one server and have good backups?

Hi Techsup99,

We can configure NLB on Symantec Endpoint Encryption Servers, below are the step for the same

What you need : -

1. One SQL server with management studio installed
2. Have two Domain admin account which we will use to point to the database by primary and secondary server
3. Install primary SEE server point to the same database and then install the secondary respectively.

How to setup : -

1. Install primary SEE server and point to local or remote SQL
2. Make sure that you have a Domain Admin account which has proper rights over the SEEMSDB
3. Install the secondary SEE server and point to the same SQL instance and to the SEEMSDB
4. Make sure to have another SQL account for this server and has the proper rights for the secondary SEE server

Once you have client package created, you will be able to see this client on both the server, when you pull reports.