The file config.xml
This article gives you an overview of the variable configuration settings for the G DATA Management Server
The configuration file config.xml contains all modifiable environment parameters of the G DATA Management Server. These are loaded when the service is started, so the 'G DATA Management Server' service must always be restarted after changes have been made to the file. Only then will the new parameters be used.
The file is located in the G DATA Management Server program directory (default):
C:\Programme (x86)\G Data\G DATA AntiVirus ManagementServer
When saving the Config.xml file, make sure that the file is saved with an .xml extension. (When "Save as" is used, the default setting of the text editor is ".txt". This has the consequence that .txt is still appended to the name entered. To avoid this, change the setting to "All files").
The structure of the file "Config.xml" will be familiar to administrators who have already edited configuration files in XML style. The file defines different setting groups and lists settings in this group with the tag pair <setting></setting>. Each setting has a name, a type and a value, which are defined as attributes in the <setting> tag. The values are typically integers, boolean values (true/false), strings or TimeSpan values. The table in this section lists the name of the setting and the associated possible values. The setting name should never be edited. Only the value is changed to the desired setting.
The different settings of Config.xml are grouped by theme. The different groups and their most important settings are listed below.
Example
<?xml version="1.0" encoding="utf-8"?>
<config>
<group name="Database">
<setting name="DbServer" type="string" value=".\GDATA2014" />
...
</group>
</config>
Database: <group name="Database">
Configuration of the ManagementServer database.
These settings should be configured via the GData.Business.Server.Config.exe file: Create database and assign to the G DATA Management Server
Setting | Default | Description |
---|---|---|
DbServer |
.\GDATA2014 |
The instance of the database. |
Database |
GData_AntiVirus_MMS |
The name of the database. |
DbUser |
<empty> |
The username of the database. |
DbPassword |
<empty> |
The password of the database. |
UseSQLWindowsAuth |
True |
The authentication type. |
DBConvertTimeout |
300 |
Timeout time of the conversion in minutes. |
AllowSecondaryConvert |
False |
Second conversion attempt allowed Yes/No |
Example
<group name="Database">
<setting name="DbServer" type="string" value=".\GDATA2014" />
<setting name="Database" type="string" value="GData_AntiVirus_MMS" />
<setting name="DbUser" type="string" value="" />
<setting name="DbPassword" type="string" value="" />
<setting name="UseSQLWindowsAuth" type="bool" value="True" />
<!--Timeout in minutes !-->
<setting name="DBConvertTimeout" type="int" value="300" />
<setting name="AllowSecondaryConvert" type="bool" value="False" />
</group>
Culture: <group name="Culture">
Region specific settings.
Setting | Default | Description |
---|---|---|
EmailCodePage |
<empty> |
Code page for outgoing emails. If no code page is defined here, UTF-8 is used. |
Example
<group name="Culture">
<setting name="Ui" type="string" value="de" />
<setting name="Language" type="string" value="GER" />
<setting name="Email" type="string" value="ambulanz_csr_ger@gdata.de" />
<setting name="EmailCodePage" type="string" value="" />
</group>
Peer-to-Peer <group name="P2P">
Settings for peer-to-peer update distribution.
By default, peer-to-peer update distribution is set up in such a way that the G DATA Management Server suggests the most suitable machines (e.g. in terms of network load and update duration) for each client to load updates peer-to-peer. In some special cases, it may be necessary to change the criteria of the G DATA Management Server in order to achieve an optimal result.
In the table below you will find an overview of the variable parameters. Before changing these values, "DoNotConsiderP2PConfigToDB" must first be deleted from the registry from the key
HKEY_LOCAL_MACHINE\Software\Wow6432Node\G DATA\AVK ManagementServer
when using a 32-bit system, the key is located under
|
If the key is still present when the G DATA Management Server service is restarted, the changed values will not be read in.
Setting | Default | Description |
---|---|---|
P2PMaxNumberOfHops |
1 |
Maximum number of hops between two clients so that they are considered to be in each other’s neighbourhood. |
P2PConnectRetries |
3 |
Maximum number of connection retries before a client forwards a connection request to another peer. |
P2PClientMaxServedPeers |
5 |
Maximum number of clients simultaneously served by a peer. |
P2PClientAbandonedConnectionThresholdMin |
1 |
Maximum period of inactivity before a connection is considered dropped (on the client side). |
P2PConsiderClientsOnBattery |
False |
Clients running on battery power are excluded as a source of updates. |
P2PConsiderClientsLastAccess |
True |
While determining a client as a source for an update, the last access of the client is taken into account. |
P2PConsiderClientsSubnet |
False |
Clients are in the neighbourhood of another if both are from the same subnet. |
P2PConsiderClientsDomain |
True |
Clients are in each other’s neighbourhood if they are both in the same domain. |
P2PConsiderClientsDHCP |
False |
Clients are in each other’s neighbourhood if both obtain their dynamic IP addresses from the same DHCP server. |
P2PConsiderClientsGateway |
False |
Clients are in each other’s neighbourhood if they both use the same default gateway. |
P2PMmsMaxServedPeers |
50 |
Maximum number of simultaneous client connections served by the ManagementServer (connections used to download a signature/programme update). |
P2PMmsAbandonedConnectionThresholdMin |
1 |
Maximum period of inactivity before a connection is considered dropped (on the ManagementServer side). |
P2PDisablePGMUpdateDistribution |
False |
Enables or disables peer-to-peer distribution of programme file updates. (If disabled, only signature updates are distributed peer-to-peer). |
Example
<group name="P2P">
<setting name="P2PMaxNumberOfHops" type="int" value="1" />
<setting name="P2PConnectRetries" type="int" value="3" />
<setting name="P2PClientMaxServedPeers" type="int" value="5" />
<setting name="P2PClientAbandonedConnectionThresholdMin" type="int" value="1" />
<setting name="P2PConsiderClientsOnBattery" type="bool" value="False" />
<setting name="P2PConsiderClientsLastAccess" type="bool" value="True" />
<setting name="P2PConsiderClientsSubnet" type="bool" value="False" />
<setting name="P2PConsiderClientsDomain" type="bool" value="True" />
<setting name="P2PConsiderClientsDHCP" type="bool" value="False" />
<setting name="P2PConsiderClientsGateway" type="bool" value="False" />
<setting name="P2PMmsMaxServedPeers" type="int" value="50" />
<setting name="P2PMmsAbandonedConnectionThresholdMin" type="int" value="1" />
<setting name="P2PDisablePGMUpdateDistribution" type="bool" value="False" />
</group>
Gradual programme update <group name="Culture">
Settings for gradual update distribution.
Many parts of the calculation can be perfectly adapted to the respective circumstances in each company network. For various settings, default values have been defined for the first six stages. If more stages are used, additional values can be added to the configuration file. If there are more levels than values for a particular setting, the next values are extrapolated from the range (estimated from existing values, for a more detailed explanation see Wikipedia: Extrapolation).
Setting | Default | Description |
---|---|---|
SPUEnable |
3 |
Bitmask for two settings in the Updates > Staged Deployment window of G DATA Administrator: Automatically stage program updates (1) and Automatically assign clients for the first stage (2). |
SPUStopAbsolute |
5,15,20,30,40,50 |
The number of faulty clients per stage at which the staged software distribution should be stopped (absolute number). Used if less than SPUStopPromille. |
SPUStopPromille |
25,75,100,150,200,250 |
The number of faulty clients per stage at which staged software distribution should be stopped (per thousand). Used if smaller than SPUStopAbsolute. |
SPUStepsAbsolute |
20,60,120,300,500,1000 |
Currently not in use. |
SPUStepsTimespan |
3.00:00:00 (3 Tage) |
dd.hh:mm:ss. Time period until the next stage is released. Corresponds to the 'Release next group after' setting in G DATA Administrator. |
SPUZombieTimespan |
14.00:00:00 (14 Tage) |
dd.hh:mm:ss. Clients that have not connected to the ManagementServer in a certain period of time are not counted in the mathematical calculation that governs the staged software distribution. |
SPUFirstStepLimit |
5,20 |
Minimum and maximum number of clients to be included in the first stage. |
SPUTotalSteps |
3 |
Number of stages. Corresponds to the setting Number of groups in G DATA Administrator. |
SPUSyncTimespan |
00:30:00 (30 Minuten) |
dd.hh:mm:ss. Synchronisation of the status of the staged software distribution between clients, subnet servers and ManagementServer. |
SPUMinClients |
10 |
Minimum number of clients on the network required for staged software distribution to start. |
Example
<group name="Programupdate">
<setting name="SPUEnable" type="int" value="3" />
<setting name="SPUStopAbsolute" type="string" value="5,15,20,30,40,50" />
<setting name="SPUStopPromille" type="string" value="25,75,100,150,200,250" />
<setting name="SPUStepsAbsolute" type="string" value="20,60,120,300,500,1000" />
<setting name="SPUStepsPromille" type="string" value="100,300,600,1500,2500,5000" />
<setting name="SPUStepsTimespan" type="TimeSpan" value="3.00:00:00" />
<setting name="SPUZombieTimespan" type="TimeSpan" value="14.00:00:00" />
<setting name="SPUFirstStepLimit" type="string" value="5,20" />
<setting name="SPUTotalSteps" type="int" value="3" />
<setting name="SPUSyncTimespan" type="TimeSpan" value="00:30:00" />
<setting name="SPUReportTimespan" type="TimeSpan" value="01:00:00" />
<setting name="SPUMinClients" type="int" value="10" />
<setting name="UseTelBeta" type="bool" value="False" />
</group>
Used folders <group name="Folder">
Here you will find all variable directories used by G DATA Management Server.
Some directories cannot be easily changed without adjusting any existing registry keys that may be related to the changed path.
Setting | Default | Description |
---|---|---|
LogFileFolder |
C:\ProgramData\G DATA\AntiVirus ManagementServer\Log |
G DATA Management Server log files. |
QuarantineFolder |
C:\ProgramData\G DATA\AntiVirus ManagementServer\Quarantine |
All files that have been quarantined by the clients and transferred to the ManagementServer are located here. |
UpdateDistributionFolder |
C:\ProgramData\G DATA\AntiVirus ManagementServer\Updates |
Virus signature and program file updates are placed here when they are downloaded. This value is synchronised with the IUpdateCfg.xml file every time the ManagementServer is started. The folder can be moved with these instructions. |
InternetUpdatePgmFolder |
C:\Program Files (x86)\G Data\G DATA AntiVirus ManagementServer |
The folder where the Internet update component (IUpdate.exe) is stored by default. This value should not be changed. |
BackupFolders |
C:\ProgramData\G DATA\AntiVirus ManagementServer\Backup |
Default path for backups. Ignored if paths for server backups have been defined in the G DATA Administrator. |
DBBackupFolder |
<empty> |
The last used database backup folder in GdmmsConfig.exe. The folder setting should only be changed via the GdmmsConfig.exe user interface. |
AdvancedReportingFolder |
AdvancedReporting |
Folder specification for advanced reporting. |
PatchFilesFolder |
C:\ProgramData\G DATA\AntiVirus ManagementServer\Patches |
This is where the PatchManager files are stored. |
LinuxRepoFolder |
C:\ProgramData\G DATA\AntiVirus ManagementServer\LinuxRepo |
Linux repositories downloaded from G DATA Management Server are stored here. |
InstallPackagesFolder |
C:\ProgramData\G DATA\AntiVirus ManagementServer\InstallPackages |
Client installation packages are stored in this folder when created via G DATA Administrator. |
Example
<group name="Folder">
<setting name="LogFileFolder" type="string" value="C:\ProgramData\G DATA\AntiVirus ManagementServer\Log" />
<setting name="QuarantineFolder" type="string" value="C:\ProgramData\G DATA\AntiVirus ManagementServer\Quarantine" />
<setting name="UpdateDistributionFolder" type="string" value="C:\ProgramData\G DATA\AntiVirus ManagementServer\Updates" />
<setting name="InternetUpdatePgmFolder" type="string" value="C:\Program Files (x86)\G Data\G DATA AntiVirus ManagementServer" />
<setting name="BackupFolder" type="string" value="C:\ProgramData\G DATA\AntiVirus ManagementServer\Backup" />
<setting name="DBBackupFolder" type="string" value="" />
<setting name="AdvancedReportingFolder" type="string" value="AdvancedReporting" />
<setting name="PatchFilesFolder" type="string" value="C:\ProgramData\G DATA\AntiVirus ManagementServer\Patches" />
<setting name="LinuxRepoFolder" type="string" value="C:\ProgramData\G DATA\AntiVirus ManagementServer\LinuxRepo" />
<setting name="InstallPackagesFolder" type="string" value="C:\ProgramData\G DATA\AntiVirus ManagementServer\InstallPackages" />
</group>
Server type <group name="Server">
These settings determine whether the ManagementServer runs as a main, secondary or subnet server.
The parameters "MainMms", "SubnetMms" and "IsSecondaryMMS" can be configured. The following specifications are possible:
-
If IsSecondaryMMS contains <True> as a value, the G DATA Management Server service runs as a Secondary Sever.
-
If IsSecondaryMMS contains <False> as value and SubnetMms is not empty, then the G DATA Management Server service runs as a subnet server.
-
For all other combinations, G DATA Management Server runs as Main Server
Example
<group name="Server">
<setting name="MainMms" type="string" value="MEINSERVER" />
<setting name="SubnetMms" type="string" value="" />
<setting name="IsSecondaryMMS" type="bool" value="False" />
</group>
Patch management <group name="Patch">
PatchManager settings.
Setting | Default | Description |
---|---|---|
CopyPatchesFromOldPatchFolder |
True |
Copies existing patches downloaded with an older G DATA Management Server to the current location. |
UpdateClientPatchServerLog |
0 |
Bitmask for the type of Patch Management Log entries displayed under Server > Infrastructure Logs in G DATA Administrator: None (0); Software detection jobs (1); Software distribution jobs (2). |
UpdateClientPatchStateIntervalMinutes |
1 |
Number of minutes PatchManagement communicates its patch status to G DATA Management Server. |
AutoPatchJobsBatchSizeDaily |
5000 |
Number of automatic patch jobs that can exist simultaneously in one day. |
AutoPatchJobsRetryDays |
7 |
Number of days after which a new patch attempt is made by automatic patch jobs. |
AutoPatchJobsBatchSizeNightly |
10000 |
Number of automatic patch jobs that can exist simultaneously at night. |
ImportTaskAndPolicyPatches |
False |
Please do not change. |
Example
<group name="Patch">
<setting name="CopyPatchesFromOldPatchFolder" type="bool" value="True" />
<setting name="UpdateClientPatchServerLog" type="int" value="0" />
<setting name="UpdateClientPatchStateIntervalMinutes" type="int" value="1" />
<setting name="AutoPatchJobsBatchSizeDaily" type="int" value="5000" />
<setting name="AutoPatchJobsRetryDays" type="int" value="7" />
<setting name="AutoPatchJobsBatchSizeNightly" type="int" value="10000" />
<setting name="ImportTaskAndPolicyPatches" type="bool" value="False" />
</group>
Network <group name="Network">
Network parameter settings.
Setting | Default | Description |
---|---|---|
DisableActiveDirectorySearch |
False |
Disable Active Directory synchronisation. |
IPv6Mode |
0 |
Determines whether the IPV& mode of the G DATA Management Server is on or off: 0=off 1=on. |
ListenIPAddress |
<empty> |
Alternative IP address of the G DATA Management Server. |
AdminPort |
0 |
Port for TCP communication with the G DATA Administrator. Any port number can be entered. The value 0 sets the port to 7182. After changing the value for AdminPort in this file, the server must be used in the servername:port format when logging in to G DATA Administrator. |
TestLinks |
False |
G DATA Internal. Please do not change. |
ClientHttpPort |
80 |
Port for TCP communication. Any port number can be entered. |
ClientHttpsPort |
443 |
Port for TCP communication. Any port number can be entered when changing according to our instructions (Attention: Linux and Mac clients must then also be adjusted). You can get detailed instructions here: Configure HTTPS Port of the G DATA Management Servers. |
MaxHttpIdleTimeSeconds |
0 |
Maximum duration between request and response for which the socket remains open. Should only be changed in problem cases in consultation with G DATA Business Support. |
MinClientHandshakeVersion |
1 |
G DATA Internal. Please do not change. |
ClientHandshakeTimeoutSeconds |
5 |
Timeout for the handshake between G DATA Security Client and G DATA Management Server. Should only be changed in problem cases in consultation with G DATA Business Support. |
HttpWebApiTimeoutSeconds |
300 |
Timeout for HTTP requests. Should only be changed in problem cases in consultation with G DATA Business Support. |
HttpsWebApiTimeoutSeconds |
300 |
Timeout for HTTPS requests. Should only be changed in problem cases in consultation with G DATA Business Support. |
Example
<group name="Network">
<setting name="DisableActiveDirectorySearch" type="bool" value="False" />
<setting name="IPv6Mode" type="int" value="0" />
<setting name="ListenIPAddress" type="string" value="" />
<setting name="AdminPort" type="int" value="0" />
<setting name="TestLinks" type="bool" value="False" />
<setting name="ClientHttpPort" type="int" value="80" />
<setting name="ClientHttpsPort" type="int" value="443" />
<setting name="MaxHttpIdleTimeSeconds" type="int" value="0" />
<setting name="MinClientHandshakeVersion" type="int" value="1" />
<setting name="ClientHandshakeTimeoutSeconds" type="int" value="5" />
<setting name="HttpWebApiTimeoutSeconds" type="int" value="300" />
<setting name="HttpsWebApiTimeoutSeconds" type="int" value="300" />
</group>
General settings <group name="General">
This area also contains other general settings.
Setting | Default | Description |
---|---|---|
MaxUpdateThreads |
1000 |
Not used currently. |
MaxSubnetUpdateThreads |
100 |
The maximum number of subnet servers that can simultaneously connect to the ManagementServer for update or synchronisation. |
PerformStartupDBCheckAndRepair |
True |
Removes unnecessary database entries when starting the "ManagementServer" service. |
DisplayLicenseLimit |
True |
The number of permissible licences and the licence expiry date are displayed in the Licence Overview module. |
MaxParallelClientInstallation |
5 |
The maximum number of clients that can be installed simultaneously via remote access. Large numbers can lead to network overload. Minimum 5, maximum 1000. |
SyncReportDays |
90 |
Maximum age (in days) of reports synchronised between the ManagementServer and the SubnetServer. |
SyncNumberOfRowsPerBatch |
200 |
Number of database rows per batch to be synchronised between the ManagementServer and the Subnet-Server (affects performance and should not be less than 100). |
SoftwareInventoryEnabled |
True |
Synchronisation of client software inventory data from the subnet server to the main ManagementServer. If a very large number of subnet servers are used, this could affect network performance. The function can be disabled. |
QueryPageSize |
10000 |
Performance when querying large databases. A high number increases the initial waiting time but decreases the total waiting time. Decreasing the number will decrease the initial wait time but increase the total wait time. |
GCLargeObjectHeapCompactionDailyHour |
5 |
Not used currently. |
CheckFeatureLanguageCode |
True |
G DATA internal. Please do not change. |
ShowLastActiveUser |
True |
Sets whether to display the last active user on the client in G DATA Administrator. |
MinFullBackupsToKeep |
3 |
Sets how many backups are to be kept. |
EnableDatabaseWriteCache |
True |
Optimisation for insertion into large tables. Please do not change. |
PercentageThresholdFreeSpace |
10 |
Specifies the percentage of remaining hard disk space from which an alarm message should be sent when the hard disk threatens to fill up (from version 15.2 onwards). |
Example
<group name="General">
<setting name="MaxUpdateThreads" type="int" value="1000" />
<setting name="MaxSubnetUpdateThreads" type="int" value="100" />
<setting name="PerformStartupDBCheckAndRepair" type="bool" value="True" />
<setting name="DisplayLicenseLimit" type="bool" value="True" />
<setting name="MaxParallelClientInstallation" type="int" value="5" />
<setting name="SyncReportDays" type="int" value="90" />
<setting name="SyncNumberOfRowsPerBatch" type="int" value="200" />
<setting name="SoftwareInventoryEnabled" type="bool" value="True" />
<setting name="QueryPageSize" type="int" value="10000" />
<setting name="GCLargeObjectHeapCompactionDailyHour" type="int" value="5" />
<setting name="CheckFeatureLanguageCode" type="bool" value="True" />
<setting name="ShowLastActiveUser" type="bool" value="True" />
<setting name="MinFullBackupsToKeep" type="int" value="3" />
<setting name="EnableDatabaseWriteCache" type="bool" value="True" />
<setting name="PercentageThresholdFreeSpace" type="int" value="10" />
</group>