G DATA Support - FAQ
Support Code: 21008

How to allow the ManagementServer or secondary server to be contacted via its IP address or FQDN by the Security Clients

This article will help you to configure the Security Clients to contact the ManagementServer or secondary server via its IP address or Fully Qualified Domain Name (FQDN) instead of its hostname.

By default the Security Client contacts the server via its hostname. This requires Domain Name Resolution to work between the client and the server.

However, clients can be configured to use the IP address or Fully Qualified Domain Name (FQDN) of the server instead.

The procedure is different (and easier) if the client has not yet been installed, but can also be done post-installation.

To learn how to configure it on a client already installed, consult the following article:

How to change locally the ManagementServer or subnet server assigned to a Security Client

 

To configure it on clients which have yet to be installed, proceed as follows:

Step 1. On the machine which hosts the SQL server used by the G DATA ManagementServer, open a command prompt as Administrator.

Step 2. Type in the following command:

sqlcmd.exe -S SQL_Server_Name -E -d Database_Name -Q"INSERT INTO Server (Parameter, Value0) VALUES ('ServerNamesForAgents', 'New_Name')"


Where:

SQL_Server_Name is the name of the server which hosts the database of G DATA.

If you have installed the default SQL Server 2014 Express on the same machine as the ManagementServer, then this name should be “.\GDATA2014”.


Database_Name is the name of the database of G DATA.

If you have installed the default SQL Server 2014 Express on the same machine as the ManagementServer, then this name should be “Gdata_AntiVirus_MMS”.


You can find both the SQL Server Name and the Database Name by opening the utility called “GdmmsConfig.exe” located in the installation folder of the ManagementServer, which is by default:

C:\Program Files (x86)\G DATA\G DATA AntiVirus ManagementServer

Value0 is for the ManagementServer. If you wish to change the name of the secondary server instead, change this to Value1.

 

New_Name is the new name which will be used by the clients to communicate with the server. This can be the server’s IP address or FQDN.

e.g.: sqlcmd.exe -S .\GDATA2014-E -d Gdata_AntiVirus_MMS -Q"INSERT INTO Server (Parameter, Value0) VALUES ('ServerNamesForAgents', '192.168.1.37')"

Step 3. If the command has been successfully executed, you will see the following message:

(1 rows affected)

Step 4. From now on, any client installed remotely from G DATA Administrator or locally with an installation package will start communicating with the server via the new name.

Keep in mind that for the local installation, you will have to create a new installation package for this change to apply.

 

An important point to note is that the above mentioned command will only work once on any ManagementServer. If you want to change the name of the ManagementServer later on, you will have to use another command, which is as follows:

sqlcmd.exe -S SQL_Server_Name -E -d Database_Name -Q "UPDATE server SET Value0 = 'New_Name' WHERE Parameter = 'ServerNamesForAgents'"

 

As mentioned above, to change the name of the subnet server instead, replace Value0 by Value1.

Last change:
10/27/2016

Operating system:
 Windows

Products:
 Endpoint Protection Business
 Managed Endpoint Security
 AntiVirus Business
 Client Security Business