Endpoint Encryption

I was able to install the SEE Management Server v 11.0.0 on a server 2008 R2 box with Microsoft SQL 2012, but when I try to activate the management server I recieve the following error.

"Unable to connect to Symantec Encryption Management Server. Either the server is not running or the server hostname/IP is invalid."

Any help is apprecited

Please provide a few more specifics.  When you say "Activating" the management server, do you mean you are trying to create client packages?

What specific version of MSSQL is in use?  MSSQL Express, Express w/Advanced Services, Standard, Datacenter, or something else?  64- or 32-bit?

I am using MSSQL 2012 standard. 64 bit

When you launch the SEE Management Server Configuration Manager there is a tab labeled SEMS Config on the far right. There is a check box to "Activate Symantec Encryption Management Server" I enter the host IP user name and password and get the error that "SEMS Configuration is unable to connect... etc"

Ah, ok.  That is to connect the SEE Management Server to the Symantec Encryption Management Server, formerly known as the PGP Universal Server.  It is for customers who are using both the SEE and PGP products, and allows the PGP server to sync recovery tokens to the SEE server.  It is not a normal setup.

Do you have a Symantec Encryption Management Server in use in addition to the Symantec Endpoint Encryption Management Server?

The rebranding of PGP products into something with a very similar naming convention can cause some confusion.  We see a lot of similar questions in support.

Ahhh ok that makes sense. I do not have an endpoint management server but it may be something I will have in the future. Is there a seperate installer for the management console? The only application i see in the Symantec Endpoint Encryption directory is the SEEMS configuration manager.

I found the Management installer package agent.msi within the archive. just needed someone to clear that question up for me. Thanks agian for your help!

The Symantec Endpoint Encryption Manager attempts to pin to the start menu instead of adding it to the directory.  They are currently evaluating this, as it is not intuitive, and they may resolve it in a future version.