Connecting roles to remote database servers - 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. - Security Center 5.14 - Administrator guides - Videos

Security Center Administrator Guide 5.14

Product
Security Center
Content type
Guides > Administrator guides
Version
5.14
Release
5.14
ft:locale
en-US
Last updated
2026-07-13

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.

Before you begin

  • Add a firewall rule to allow sqlbrowser.exe (SQL Server Browser) to use UDP port 1434. This enables clients to discover the port numbers for named instances of SQL Server that are using dynamic ports.
  • Add a firewall rule for sqlservr.exe (Microsoft SQL Server) to allow remote applications to connect to the SQL Server database engine. This ensures inbound traffic on named instance ports reaches the database.
  • Configure DNS to ensure consistent and reliable resolution of all server names.
For more information, see Add a program exception for the SQL Server executable from Microsoft.

What you should know

You must ensure that roles can connect to remote database servers for the following scenarios:

Procedure

  1. 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 click Properties.
    3. In the Server Properties window, click Connections.
    4. Under the Remote server connections section, click the Allow remote connections to this server option.
    5. Click OK and close Microsoft SQL Server Management Studio.
  2. Enable the TCP/IP protocol 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 TCP/IP protocol and set its status to Enabled.
      The SQL Server Configuration Manager window, with Protocols for SQLEXPRESS selected.
      IMPORTANT: We strongly recommend using TCP/IP, even though the Named Pipes protocol is supported. You don't have to enable both protocols.
    4. Close SQL Server Configuration Manager.
  3. Ensure the SQL Server Browser service is properly configured to make the instance visible on the network.
    1. On the server hosting the database, open Microsoft Management Console Services (services.msc).
    2. Right-click the SQL Server Browser service, and click Properties.
    3. On the General page, from the Startup type list, select Automatic.
    4. Start the SQL Server Browser service.
    The SQL Server instance is now available from the Database server list of any role's Resources page in Config Tool.
  4. Restart your SQL Server instance to enable the settings you’ve 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 hosting Security Center roles that need to connect remotely to the SQL server, 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 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. On the Log on page, 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’s hosting a Security Center role that must connect to the remote database server.
  6. From the Config Tool homepage, open the System task and click the Roles view.
  7. Select the role and click the Resources view.
  8. In the Database server field, enter the path to the remote database.
    For example: DB_SERVER.GENETEC.COM\SQLEXPRESS

Example

Watch this video to learn more. Click the Captions icon (CC) to turn on video captions in one of the available languages.