Quick Guide to Installing Symantec Endpoint Encryption 7.x in an Active Directory environment.
Last Updated April 01, 2011
**PLEASE NOTE** This document is a simplified version of the Installation instructions contained in Chapters 6 and 2 of the SEE-FD Installation Guide (provided with the software) along with a few tips. The information provided outlines only one way of performing the installation in order to simplify the process as much as possible. This is not the definitive guide. Please consult the SEE Installation guide for more the complete and official installation process.**
Symantec Endpoint Encryption Management Server (SEEMS) 7.x should be installed on a dedicated server running Windows 2003.
**Note: The Symantec Endpoint Encryption Management Server will be referred to as SEEMS in this document.
In order to use Active Directory Synchronization, the SEEMS server must be a member of a domain, and the following accounts (which are required for the installation procedure) must be created in that domain:
A Normal Active Directory User account for SEE clients to connect to IIS - e.g. "seeiis" (no special permissions or group memberships required).
A Domain Administrator*** account for synchronization of data between Active Directory and SEEMS - e.g."seeadsync" (only required if Active Directory synchronization is to be enabled).
An Active Directory Account with at least local administrator privileges on the SEEMS server for the installation of SEEMS. A more limited "Policy Administrator" level account should be considered for increased security. See the Installation Guide for more information on this.
***This account must have domain administrator privileges in the same site and/or domain that the SEE Management Server has been joined to. Note that if your corporate security policy prohibits the use of an administrator account, a non-administrator account can be used, provided that it has been granted read permissions to the Active Directory deleted objects container. See “Extending Domain User Rights with DSACLS” on page 80 of the SEE Installation manual.
MS-SQL Accounts (you will be prompted to create these during the installation of SQL or SQL Express):
Mixed-mode superadmin "sa" account.
SEE db access account -e.g. "seedb", created in the database during installation.
SEEMS server pre-installation requirements. The following components need to be installed in Windows 2003:
Create AD accounts as outlined above. Use complex passwords to avoid password complexity issues.
If using Windows 2003, install asp.net, .NET 2.0 & IIS on the SEEMS server.
Install SQL 2005 Express SP3 (or SQL 7) with Advanced Services (this includes the Management Studio" option):
Add "Management Studio" option (recommended).
Select mixed-mode, define "sa" password, then click through.
Run "SQL Surface Area Connections" from SQL menu.
Go to "Remote Connections" > "Local and Remote Connections".
Select "Using both TCP/IP and named pipes.
Ensure that the SQL Service Logon is set to Local System account
Start > Run > Services.msc.
Right-click on SQL Service, click on properties.
Click on Logon tab.
Ensure Local System Account is selected or select it if it is not.
Install SEE Management Server MSI
Enter "sa" account details.
Enter details for SEE db access account.
Choose to Sync with AD and enter the AD Sync account details.
Enter SEE IIS account details.
Enter IIS http port.
Install Symantec Endpoint Encryption Framework Server installer Package.
Select SQL server instance.
Enter a SEE Management Password. This is a 16-character password internal to SEEMS that must be retained safely.
Install Group Policy Management Console snap-in ("gpmc.msi" available from Microsoft) to allow policy administration from the SEEMS console.
Install SEE Full Disk Server installer package (if using).
Install SEE Removable Storage installer package (if using).
References SEE Installation Manual. Chapter 2.
Imported Document ID: TECH131424
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe