Best Practices guide for installing the SEPM 11 RU5 and later using SQL Server 2008 Database

Article:TECH96451  |  Created: 2009-01-29  |  Updated: 2012-12-11  |  Article URL http://www.symantec.com/docs/TECH96451
Article Type
Technical Solution

Product(s)

Environment

Issue



How do I install the Symantec Endpoint Protection Manager (SEPM) 11 RU5 and later on a SQL Server 2008 Database?  


Solution




Note: Installing Symantec Endpoint Protection Manager 11 with a SQL Server 2008 Database is officially supported with Symantec Endpoint Protection Manager 11 RU5 and later.



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

TO INSTALL MICROSOFT SQL SERVER 2008 CLIENT COMPONENTS

  1. Start the Microsoft SQL Server 2008 installation CD and begin the installation process.
  2. In the Installation Definition window, click Client Tools Connectivity and Management Tools Basic.
  3. Complete the installation.



TO CONFIGURE MICROSOFT SQL SERVER 2008 CLIENT COMPONENTS

  1. Click Start> Programs> Microsoft SQL Server 2008> Configuration tools>Sql Server Configuration Manager.
  2. In the Sql Server Configuration Manager, Under SQL Native Client 10.0 Configuration, verify that TCP/IP is an enabled protocol. If it is not an enabled protocol, enable the protocol.
  3. Right-click TCP/IP, and then click Properties.
  4. In the TCP/IP dialog box, in the Default Port box, type the port number that matches the port that is used by the Microsoft SQL Server 2008 instance.
    (The default port is typically 1433. You specify this port number when you create the database)

     
  5. Click OK, and then exit the SQL Server Client Network Utility.



Notes:

  • The Client Tools Connectivity, and Management Tools Basic must be installed on the System where the Symantec Endpoint Protection Manager Console is going to be installed, or the Management Console installation will not install successfully.
  • The Symantec Endpoint Protection Manager Console WILL NOT accept the drive path to any server or network shared drive where the "BCP.EXE" utility is present.
  • On 64-bit installs there are two SQL Native client 10.0 Configurations. Verify that both are enabled.


TO INSTALL THE SYMANTEC ENDPOINT PROTECTION MANAGER

  1. Insert the installation CD, and start the installation.
  2. In the Welcome screen, do one of the following:
    1. If you are installing Symantec Endpoint Protection, click Symantec Endpoint Protection.
    2. If you are installing Symantec Network Access Control, click Symantec Network Access Control.

       
  3. Click Install Symantec Endpoint Protection Manager.
  4. Click through the screens, until the "Destination Folder" screen appears.
  5. In the "Destination Folder", select either 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 screens, until the installation begins.
  8. When the installation finishes and the Installation Wizard Complete screen appears, click Finish

    Note:
    The Server Configuration Wizard screen 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 screen appears automatically.

     

TO CONFIGURE THE SEPM WITH A SQL DATABASE

  1. In the Management Server Configuration Wizard screen, check Install my first site, and then click Next.
  2. In the Server Information screen, 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 screen, in the Site name box, accept or change the default name, and then click Next
  4. In the Encryption Password screen, 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 screen, 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 screen, check Microsoft SQL Server, and then click Next.
  7. In the Define New Database screen, do one of the following:
    • If the database does not exist, check Create a new database (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 screen, type your values for the following boxes, and then click Next:
    • Database Server
      Note: If you created a new instance, the format is <servername_or_IPaddress>\<instance_name>.
    • SQL Port Number
    • Database Name
    • 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 screen, type the same password in the following boxes, and then click Next
    • Password
    • Confirm Password

       
  12. In the Configuration Completed screen, 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

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


References
sqlncli.msi and SQLServer2008_SQLCMD.msi could be downloaded free from

http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en


 



Legacy ID



2009093006181448


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


Terms of use for this information are found in Legal Notices