About SQL Server configuration settings

If you install
Symantec Endpoint Protection Manager
with a SQL Server database, there are specific configuration requirements for SQL Server.
Before you create the database, Symantec recommends that you install a new instance of SQL Server that conforms to Symantec installation and configuration requirements. You can install a database in an existing instance, but the instance must be configured properly or your database installation fails. For example, if you select a case-sensitive SQL collation, your installation fails.
To maximize the security posture of remote SQL Server communications, place both servers in the same secure subnet.
Required SQL Server configuration settings
Configuration setting
Installation requirement
Instance name
Do not use the default instance name. Create a name such as SEPM.
By default, a database named Sem5 is created in the SQL Server instance when you install
Symantec Endpoint Protection Manager
. The default name is supported, but can cause confusion if you install multiple instances on one computer.
Authentication configuration
Mixed mode or Windows Authentication mode
sa password
Set this password when you set Mixed Mode authentication.
Enabled protocol
TCP/IP
IP addresses for TCP/IP
Enable IP1 and IP2
TCP/IP port numbers for IP1, IP2, and IPALL
Set TCP Dynamic Ports to blank, and specify a TCP port number. The default port is typically 1433. You specify this port number when you create the database.
The
Symantec Endpoint Protection Manager
database does not support dynamic ports.
Remote connections
Must be enabled. TCP/IP protocol must also be specified.
If your database is located on a remote server, you must also install SQL Server client components on the computer that runs
Symantec Endpoint Protection Manager
. SQL Server client components include
BCP.EXE
. The version number of the SQL Server client components should be the same as the version number of SQL Server that you use. Refer to your SQL Server documentation for installation instructions.
During the
Symantec Endpoint Protection Manager
database configuration phase of the installation, you select and enter various database values. Understand the decisions you must make to correctly configure the database.
The following table displays the settings that you might need to know before you begin the installation process.
SQL Server database settings
Setting
Default
Description
Server name
local host name
Name of the computer that runs
Symantec Endpoint Protection Manager
.
Server data folder
SEPM_Install
\data
Folder in which the
Symantec Endpoint Protection Manager
places data files including backups, replication, and other
Symantec Endpoint Protection Manager
files. The installer creates this folder if it does not exist.
The default value for
SEPM_Install
is C:\Program Files (x86)\Symantec\
Symantec Endpoint Protection Manager
.
For 32-bit systems (12.1.x only), it is C:\Program Files\Symantec\
Symantec Endpoint Protection Manager
.
Encryption password
None
The password that encrypts communication between
Symantec Endpoint Protection Manager
and clients. The password can be from 6-32 alphanumeric characters and is required.
Document this password and put it in a secure location. 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.
Database server
local host name
Name of the computer where SQL Server is installed, and the optional instance name. If the database server was installed with the default instance, which is no name, type either
host name
or the host's
IP address
. If the database server was installed with a named instance, type either
host name
\
instance_name
or
IP address
\
instance_name
. The use of
host name
only works with properly configured DNS.
If you install to a remote database server, you must first install the SQL Server client components on the computer that runs
Symantec Endpoint Protection Manager
.
SQL Server Port
1433
The port that is used to send and receive traffic to the SQL Server.
The use of port 0 is not supported. Port 0 specifies a random, negotiated port.
Database Name
sem5
Name of the database that is created.
Database user name
sem5
Name of the database user account that is created. The user account has a standard role with read and write access. The name can be a combination of alphanumeric values and the special characters
~ # % _ + = | : .
. The special characters
` ! @ ' $ ^ & * ( ) - { } [ ] " \ / < ; > , ?
are not allowed. The following names are also not allowed: sysadmin, server admin, setupadmin, securityadmin, processadmin, dbcreator, diskadmin, bulkadmin.
Database password
None
The password that is associated with the database user account. The name can be a combination of alphanumeric values and the special characters
~ # % _ + = | : . /
. The special characters
! @ * ( ) { } [ ] ; , ?
are not allowed.
SQL Server native client folder
SQL Server 2005 (12.1.x):
Install directory
\90\Tools\Binn
SQL Server 2008:
Install directory
\100\Tools\Binn
SQL Server 2012:
Install directory
\110\Tools\Binn
SQL Server 2014 / 2016 / 2017 / 2019:
Install directory
\Client SDK\ODBC\110\Tools\Binn
Location of the local SQL native client directory that contains bcp.exe.
The installation paths that are shown represent the default paths for Microsoft SQL Server.
Install directory
represents the installation drive and directory for Microsoft SQL Server.
To install the SQL Server native client, see the Microsoft TechNet page appropriate for your version of SQL Server:
Server user name
None
Name of the database server administrator account, which is typically sa.
Server password
None
The password that is associated with the database server administrator account, which is typically sa.
Database data folder
Automatically detected after you click
Default
.
SQL Server 2005 (12.1.x):
Install directory
\MSSQL.1\MSSQL\Data
SQL Server 2008:
Install directory
\MSSQL10.MSSQLSERVER\MSSQL\Data
SQL Server 2008 R2:
Install directory
\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQL Server 2012:
Install directory
\MSSQL11.MSSQLSERVER\MSSQL\Data
SQL Server 2014:
Install directory
\MSSQL12.MSSQLSERVER\MSSQL\Data
SQL Server 2016:
Install directory
\MSSQL13.MSSQLSERVER\MSSQL\Data
SQL Server 2017:
Install directory
\MSSQL14.MSSQLSERVER\MSSQL\Data
SQL Server 2019:
Install directory
\MSSQL15.MSSQLSERVER\MSSQL\Data
Location of the SQL Server data folder. If you install to a remote server, the volume identifier must match the identifier on the remote server.
The installation paths shown represent the default paths for Microsoft SQL Server.
  • If you install to a named instance on SQL Server 2005, the instance name is appended to MSSQL with a dot numeric identifier. For example, \MSSQL.
    n
    \MSSQL\Data
  • If you install to a named instance on SQL Server 2008, the instance name is appended to MSSQL10. For example, \MSSQL10.
    instance name
    \MSSQL\Data
  • If you install to a named instance on SQL Server 2008 R2, the instance name is appended to MSSQL10_50. For example, \MSSQL10_50.
    instance name
    \MSSQL\Data
  • If you install to a named instance on SQL Server 2012, the instance name is appended to MSSQL11. For example, \MSSQL11.
    instance name
    \MSSQL\Data
  • If you install to a named instance on SQL Server 2014, the instance name is appended to MSSQL12. For example, \MSSQL12.
    instance name
    \MSSQL\Data
  • If you install to a named instance on SQL Server 2016, the instance name is appended to MSSQL13. For example, \MSSQL13.
    instance name
    \MSSQL\Data
  • If you install to a named instance on SQL Server 2017, the instance name is appended to MSSQL14. For example, \MSSQL12.
    instance name
    \MSSQL\Data
  • If you install to a named instance on SQL Server 2019, the instance name is appended to MSSQL15. For example, \MSSQL13.
    instance name
    \MSSQL\Data
Clicking
Default
displays the correct installation folder if you entered the database server and instance name correctly. If you click
Default
and the correct installation folder does not appear, your database creation fails.