SQL Server Connection
The first task is to connect the GateKeeper Hub (on-premise version only) server application to an SQL Server to create and manage a database to be used by the Hub. GateKeeper Hub requires an SQL database to store data regarding users, computers, logs, etc. This database is part of an SQL Server instance that is running on your network. The SQL Server can be running locally on this computer, or any other computer on your network. All the data is stored on your network and not shared with anyone else.
Click Settings () to bring up three options:
Create a new database for Hub (create new SQL database)
Edit existing connection (edit SQL connection)
Update connected database (synchronize existing SQL database)
Create New SQL Database
Clicking on the button to create a new database will bring up a sidebar with options to log in to an SQL Server and create a new user and database for the GateKeeper Hub to utilize. A new database must be created the first time the GateKeeper Hub is installed. You will need the instance name of the SQL Server and administrative rights to create databases in the SQL Server instance. While creating the new database, a new GateKeeper Hub user is also added to the SQL Server with ownership rights to the newly created database.
Enter the location of the SQL Server. If the SQL Server is on the same machine as the Hub, then the SQL Server address will be in the following form:
Typical instance names for SQL Servers are SQLEXPRESS or MSSQLSERVER.
If the SQL Server is on a different computer on the network, then the SQL Server address will be of the form:
The SQL Server will have to be configured to communicate over Internet Protocol (IP). Typical port number for the SQL Server is 1433, and the instance name is whatever the SQL instance you want to connect to. For example, the SQL address can be written as:
Next, you will select the authentication mode to log on to the SQL Server. This login account must have privileges to create new users and databases in the SQL Server instance.
Select Windows Authentication, from the Authentication Type drop down menu, if your credentials have access to create a database on the SQL Server. If not, select SQL Server Authentication to sign in with credentials that have access to create a database and enter a login username and password.
The next step is to create the GateKeeper Hub database. Default values for the database name, database user, and database password are auto filled. These can be changed as required. Once the values are filled in, click on Create Database to create the new user and database.
Once the database has been successfully created, a notification will confirm it and the sidebar will show the database and user created for use with GateKeeper Hub.
Edit Existing SQL Server Connection
A SQL Server database connected to the GateKeeper Hub database can be changed at any time. You can edit the SQL connection information using the Edit existing connection (edit SQL Server) option. This is useful if there are multiple GateKeeper Hub databases on the network, and you want to switch the Hub server from one to another. This is also useful if the SQL Server user assigned to GateKeeper Hub has to be changed. This may occur if the database administrator has changed the password for the GateKeeper database user. If the GateKeeper database user has changed, then the Hub will no longer be able to communicate with the SQL Server and must be updated by editing the SQL Server connection.
The currently connected SQL Server and database will be displayed when the side panel is first opened. Click Edit to make changes to the SQL connection.
Once you have updated the various fields, click Save Changes to save your edits. This will then verify all changes including the connection to the SQL Server, validity of the database, accessibility by the user, and the tables inside the database. If everything is verified, then the new settings will be saved, and the GateKeeper Hub website will be restarted.
Additionally, there’s a button to ensure that the SQL Server has mixed mode authentication enabled. Clicking on the Enable Mixed Mode Authentication button will enable SQL authentication on the SQL Server if it was not already enabled. This is important because the GateKeeper Hub server can only use SQL Authentication to access the SQL Server.
Synchronize on-premise GateKeeper Database
Whenever a new instance of the GateKeeper Hub is installed, it modifies the tables in the GateKeeper database associated with the Hub to ensure that all database changes are incorporated properly. In order to make sure that the database has been successfully updated, a backup button to synchronize all tables in the GateKeeper database is provided. Click this button to run an SQL script to update the tables in the GateKeeper database as needed.
For any additional questions or concerns regarding proximity login, computer locking, credential management, or compliance, please contact GateKeeper Enterprise support using the Support Ticket form on https://gkaccess.com/support/ or email firstname.lastname@example.org.
GK application setup; gk application set up; hub manager applications; How to setup the GateKeeper Enterprise database in the SQL Server; How to set up database in the SQL Server for GateKeeper; How to set up GateKeeper Enterprise database in the SQL Server; How to set up GateKeeper Enterprise database in the SQL Server; Setting up the GateKeeper Enterprise database in the SQL Server; How to set up the Enterprise database in the SQL Server for GateKeeper; How to set up database SQL Server for GateKeeper; How to set up the database in the SQL Server for database; on-premise gatekeeper setup; set up gatekeeper onpremise; is gatekeeper on-premise software?;
Please sign in to leave a comment.