Best Practices guide for Installing the Symantec Endpoint Protection Manager with a SQL Server 2005 Database

Article:TECH104405  |  Created: 2008-01-14  |  Updated: 2010-08-13  |  Article URL http://www.symantec.com/docs/TECH104405
Article Type
Technical Solution


Environment

Issue



How do I install the Symantec Endpoint Protection Manager (SEPM) on a SQL Server 2005 Database?

OR

What are the Best Practices to install the Symantec Endpoint Protection Manager (SEPM) on a SQL Server 2005 Database?

 


Solution




To install the Symantec Endpoint Protection Manager (SEPM) on a SQL Server 2005 Database, follow the given steps:

A. INSTALL MICROSOFT SQL SERVER 2005 CLIENT COMPONENTS
1. Start the Microsoft SQL Server 2005 installation CD and begin the installation process.
2. In the Start window, click Server components, tools, Books Online, and samples.
3. Continue the installation until you are prompted to select the components to install.
4. In the Components to Install dialog box, click Advanced.
5. In the left pane, click and expand Client Components.
6. Click Client Component features Connectivity Components and Management Tools, so they both show Will be installed on local hard drive.
7. Click Next and Complete the installation.


B. CONFIGURE MICROSOFT SQL SERVER 2005 CLIENT COMPONENTS
1. Click Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager.
2. Under SQL Native Client Configuration, click Client Protocols, right-click TCP/IP, and then click Properties.
3. In the Default Port box, type the port number that matches the port that is used by the Microsoft SQL Server 2005 instance.

Note: The default port is typically 1433. You specify this port number when you create the database.

4. Click Apply > OK.
 

  • An important point to note here is that the SQL Server Client Tools have to be installed on the System where the Symantec Endpoint Protection Manager Console is going to be installed, both locally and remotely, else the Management Console Installation will not complete.
  • Additionally, the Symantec Endpoint Protection Manager Console WILL NOT accept the drive path to any server / network shared drive where the BCP.EXE utility is present.


C. INSTALL THE SYMANTEC ENDPOINT PROTECTION MANAGER
1. Insert the installation CD, and start the installation.
2. In the Welcome panel, do one of the following:
 

  • In you are installing Symantec Endpoint Protection, click Symantec Endpoint Protection.
  • If you are installing Symantec Network Access Control, click Symantec Network Access Control.


3. In the next panel, click Install Symantec Endpoint Protection Manager.
4. Click through the panels, until the Destination Folder panel appears.
5. In the Destination Folder panel, accept or change the default installation directory.
6. Do one of the following:
 

  • To configure the Symantec Endpoint Protection Manager IIS Web as the only Web server on this computer, check Create a custom Web site, and then click Next.
  • To let the Symantec Endpoint Protection Manager IIS Web server run with other Web on this computer, check Use the default Web site, and then click Next


7. Click through the panels, until the installation begins.
8. When the installation finishes and the Installation Wizard Complete panel appears, click Finish

Note: The Server Configuration Wizard panel can take up to 15 seconds to appear. If you are prompted to restart the computer, restart the computer.
When you log on, the Server Configuration Wizard panel appears automatically.


D. TO CONFIGURE THE SEPM WITH A SQL DATABASE
1. In the Management Server Configuration Wizard panel, check Install my first site, and then click Next.
2. In the Server Information panel, accept or change the default values for the following boxes, and then click Next:
 

  • Server Name
  • Server Port
  • Server Data Folder


3. In the Site Information panel, in the Site name box, accept or change the default name, and then click Next
4. In the Encryption Password panel, in the Encryption Password boxes, type a password, and then click Next. Document this password and put it in a safe.
Note: You cannot change or recover the password after you create the database. You must also enter this password for disaster recovery purposes if you do not have a backed up database to restore.

5. In the Secure Communications panel, do one of the following:
 

  • To secure communications with digital certificates, click Yes, and then click Next.
  • To not secure communications with digital certificates, click No, and then click Next


6. In the Database Server Choice panel, check Microsoft SQL Server, and then click Next.
7. In the Define New Database panel, do one of the following:
 

  • If the database does not exist, check Create a new database (Highly Recommended).
  • If the database does exist, check Use an existing database.
     

Note: An existing database must define file groups PRIMARY, FG_CONTENT, FG_LOGINFO, FG_RPTINFO, and FG_INDEX. The user account for database access must have privileges db_ddladmin, db_datareader, and db_datawriter. If these requirements are not met, your installation fails. A best practice is to define a new database.

8. Click Next.
9. In the Microsoft SQL Server Information panel, type your values for the following boxes, and then click Next:
 

  • Database Server
    Note: If you created a new instance, the format is <Server Name>\<Instance Name>.
  • SQL Port Number
  • Database Name

(do not create a name that begins with a number)

  • User
  • Password
  • SQL Client folder
  • DBA user
  • DBA password
  • Database Data folder


10. In the Warning dialog prompt, read and understand the warning information about clear text communications, and then click OK.
11. In the Set Console Password panel, type the same password in the following boxes, and then click Next
 

  • Password
  • Confirm Password


12. In the Configuration Completed panel, do one of the following:
 

  • To deploy client software with the Migration and Deployment Wizard, click Yes.
  • To log on to the Symantec Endpoint Protection Manager Console first, and then deploy client software, click No


Now, you have successfully installed the Symantec Endpoint Protection Manager (SEPM) on a SQL Server 2005 Database.


References
sqlncli.msi and SQLServer2005_SQLCMD.msi can be downloaded free from www.microsoft.com/downloads



Technical Information
When trying to create a database that uses numbers in the name first (1234SEP) you will receive the error message failed to connect to the database . The install will fail.


 



Legacy ID



2008031504445748


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


Terms of use for this information are found in Legal Notices