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
-
Allow remote connection on your SQL Server instance.
-
On the server hosting the database, open Microsoft SQL Server Management
Studio and connect to the database server used by Security Center.
-
In the Microsoft SQL Server Management Studio window,
right-click the database server name (
) in the Object Explorer,
and click Properties.
-
In the Server Properties window, click
Connections.
-
Under the Remote server connections section, click the
Allow remote connections to this server option.
-
Click OK and close Microsoft SQL Server Management
Studio.
-
Enable the TCP/IP protocol on your SQL Server instance.
-
On the server hosting the database, open SQL Server Configuration
Manager.
-
Expand the SQL Server Network Configuration section, and
select the protocols for your database server instance (for example,
Protocols for SQLEXPRESS).
-
Right-click the TCP/IP protocol and set its status to
Enabled.
IMPORTANT: We strongly recommend using TCP/IP, even though the Named Pipes
protocol is supported. You don't have to enable both protocols.
-
Close SQL Server Configuration Manager.
-
Ensure the SQL Server Browser service is properly configured to
make the instance visible on the network.
-
On the server hosting the database, open Microsoft Management Console
Services (
services.msc).
-
Right-click the SQL Server Browser service, and click
Properties.
-
On the General page, from the Startup
type list, select Automatic.
-
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.
-
Restart your SQL Server instance to enable the settings you’ve changed.
-
On the server hosting the database, open Microsoft Management Console
Services (
services.msc).
-
Right-click the SQL Server instance service, such as
SQL Server
(SQLEXPRESS), and click Restart.
-
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.
-
On the server hosting the role, open Microsoft Management Console Services
(
services.msc).
-
Right-click the Genetec Server service, and click
Properties.
-
On the Log on page, select the This
account option, and type an administrator Account
name and Password.
-
Click .
-
Repeat these steps on every server that’s hosting a Security Center role that must
connect to the remote database server.
-
From the Config Tool homepage, open the System task and click the
Roles view.
-
Select the role and click the Resources view.
-
In the Database server field, enter the path to the remote
database.
For example:
DB_SERVER.GENETEC.COM\SQLEXPRESS