I am trying to install sql server 2016 using this cookbook.symantec endpoint protection is installed on my server. Learn more about SQL Server 2016 data processing and privacy controls, please see the Privacy Statement. 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.
![]()
.Site name.Server name.Port numbersYou should contact your network administrator before you make changes to the default Symantec Endpoint Protection Manager port configurations.The location of the Symantec Endpoint Protection Manager server data folderIf there is not enough available free space on the drive on which Symantec Endpoint Protection Manager is installed, relocate the server data folder to an alternate drive.On the database selection screen, click Microsoft SQL Server database and then click Next.You can select the embedded database with a custom configuration. However, this step assumes that you select the SQL Server database.Check with your SQL database administrator to confirm whether or not the automatic database maintenance tasks should be enabled.Symantec recommends that you host SQL Server and Symantec Endpoint Protection Manager on separate physical servers.For information on supported versions of Microsoft SQL Server, see the.Click Create a new database, and then click Next.
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. Table: Required SQL Server configuration settingsConfiguration settingInstallation requirementInstance nameDo 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 configurationMixed mode or Windows Authentication modeSee.sa passwordSet this password when you set Mixed Mode authentication.Enabled protocolTCP/IPIP addresses for TCP/IPEnable IP1 and IP2TCP/IP port numbers for IP1, IP2, and IPALLSet 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 connectionsMust 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.displays the settings that you might need to know before you begin the installation process.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. NMSSQLData.If you install to a named instance on SQL Server 2008, the instance name is appended to MSSQL10.
For example, MSSQL10. Instance nameMSSQLData.If you install to a named instance on SQL Server 2008 R2, the instance name is appended to MSSQL1050.
For example, MSSQL1050. Instance nameMSSQLData.If you install to a named instance on SQL Server 2012, the instance name is appended to MSSQL11. For example, MSSQL11. Instance nameMSSQLData.If you install to a named instance on SQL Server 2014, the instance name is appended to MSSQL12. For example, MSSQL12. Instance nameMSSQLData.If you install to a named instance on SQL Server 2016, the instance name is appended to MSSQL13.
![]()
For example, MSSQL13. Instance nameMSSQLData.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |