Connecting roles to remote database servers - Security Center 5.10

If a role database is hosted on a different server than the role, you must configure the remote database server (SQL Server) to accept connection requests from the role.

1. For SQL Server 2014 and earlier, allow remote connection on your SQL Server instance.
   1. On the server hosting the database, open Microsoft SQL Server Management Studio and connect to the database server used by Security Center.
   2. In the Microsoft SQL Server Management Studio window, right-click the database server name () in the Object Explorer, and select Properties.
   3. In the Server Properties window, select the Connections page.
   4. Under the section Remote server connections, select the option Allow remote connections to this server.
   5. Click OK and close Microsoft SQL Server Management Studio.
2. Enable Named Pipes and TCP/IP protocols on your SQL Server instance.
   1. On the server hosting the database, open SQL Server Configuration Manager.
   2. Expand the SQL Server Network Configuration section, and select the protocols for your database server instance (for example, Protocols for SQLEXPRESS).
   3. Right-click the Named Pipes and TCP/IP protocols, and set their status to Enabled.
      
   4. Close SQL Server Configuration Manager.
3. Make sure your SQL Server instance is visible from other computers on your network.
   1. On the server hosting the database, open Microsoft Management Console Services (services.msc).
   2. Start the service named SQL Server Browser.
   3. Right click the SQL Server Broswer service, and click Properties.
   4. In the General tab, from the Startup type drop-down list, select Automatic.
      The SQL Server instance is now available from the Database server drop-down list of any role Resources tab in Config Tool.
4. Restart your SQL Server instance to enable the settings you have changed.
   1. On the server hosting the database, open Microsoft Management Console Services (services.msc).
   2. Right-click the SQL Server instance service, such as SQL Server (SQLEXPRESS), and click Restart.
5. On every server that hosts your Security Center roles, change the logon user of the Genetec Server service to a Windows administrator account that also has the permissions to access the SQL Server instance you just modified.
   The Windows administrator account is usually a domain account used to connect to all servers.
   1. On the server hosting the role, open Microsoft Management Console Services (services.msc).
   2. Right-click the Genetec Server service, and click Properties.
   3. In the Log on tab, select the This account option, and type an administrator Account name and Password.
   4. Click Apply > OK.
   5. Repeat these steps on every server that is hosting a Security Center role that will connect to the remote database server.
6. Select the role in Config Tool > Resources tab, and modify the database path to point to the remote database.
   For example: DB_SERVER.GENETEC.COM\SQLEXPRESS

   NOTE: If required, specify a port as follows: <hostname>,<port>\<sql_instance>