How-to


Changelog


Troubleshooting


Privacy policy for enterprise solutions



Page tree
Skip to end of metadata
Go to start of metadata
Module Updates

All clients have their own local copy of the virus signature database, so that virus protection is also guaranteed when no connection to the G DATA ManagementServer or the Internet is available. Updating virus signatures (as well as program files) on clients takes place in two steps, which can both be automated. In the first step, the latest files from the G DATA update server are downloaded to the G DATA ManagementServer. The Updates module lets you configure this process. Subsequent distribution of the updates to the clients can be configured under Client settings > GeneralUpdates.

Updates - Signature updates

On the Signature updates panel, you can configure the process of downloading signature updates from the G DATA update server to G DATA ManagementServer.

The following information and settings are available under Status:

  • Version engine A: The current version of the virus signatures for engine A on G DATA ManagementServer.
  • Version engine B: The current version of the virus signatures for engine B on G DATA ManagementServer.
  • Last execution: Timestamp for the last execution of the virus signature update process.
  • Status: The status of the virus signature update process.
  • Update status: Update the Status field.
  • Run update now: Carry out an immediate update of the virus signature database on G DATA ManagementServer.

Under Automatic updates, the virus signature update can be scheduled. To do this, check the box next to Run update periodically and specify when and with what cycle the update is to be carried out. To enable automatic updating, your G DATA ManagementServer must be connected to the Internet and you must have entered the user name and password that you have received upon registration under Updates > Access data and settings. If the server connects to the Internet via a proxy server, your proxy credentials must also be entered there.

Updates can be distributed centrally (from the ManagementServer or subnet server to clients) or, if you activate Peer to Peer update distribution, decentralised (allowing already updated clients to distribute updates to other clients). Be sure to check the port requirements for this option.

Updates - Program updates

In the Program Updates section, you configure the download of client program files from the G DATA update server to ManagementServer. Program file updates should be installed automatically so that all clients can use the full scope of G DATA CyberDefense products.


The following information and settings are displayed under Program Files (Client):

  • Current version: The current version of the client program files stored on the ManagementServer.
  • Last run: The last run of the update process.
  • Status: The status of the update process.
  • Update Status: Updates the status.
  • Start update now: Starts an immediate update of the client program files on G DATA ManagementServer.

In the Automatic updates section, you can schedule the update of client program files. The settings are identical to those under Signature updates.

G DATA ManagementServer itself can only be updated via a Start menu item. To do this, call up the Internet Update entry in the G DATA ManagementServer program group in the Start menu.


Program file updates are not issued every hour, so the update interval can be set to a daily or weekly request. Scheduling program file updates is also recommended for servers that are not permanently connected to the Internet. The Internet connection option will only perform an update if G DATA ManagementServer detects that the server has an Internet connection. The only reason not to have program files updated automatically by G DATA ManagementServer is if the Internet connection is not always available. To prevent files from being automatically distributed to clients, appropriate configurations are required in the Client Settings module.

A program update can also be started manually on the client. Proceed as follows:

Clients > Clients > Overview > search/filter desired clients in the list > right click on the clients > Update program files now


Program file updates always require a reboot of the client computer.



MailSecurity for Exchange

As with G DATA Security Client, MailSecurity for Exchange performs an automatic upgrade when a new version is available on ManagementServer. To ensure that the latest version of the Exchange plug-in is used, the Internet Update tool of ManagementServer has the Update program files (client) feature. If the Exchange plug-in updates its program files automatically according to the configuration, this will be done the next time it connects to the ManagementServer. Alternatively, an upgrade can be performed manually using G DATA Administrator.

Updates - Staged distribution

In the Staged distribution area, you can specify whether to apply program updates to all clients simultaneously or in stages. A staged distribution reduces the server and network load that occurs during a program update.

If you choose staged distribution, you can specify whether the distribution is automatic or you can specify yourself which clients are to receive program updates first, which clients come after, and the extent to which the distribution is subdivided into different distribution stages.

The first level always includes five clients.

If you do not want to use staged distribution, it is possible to disable the automatic program update option within G DATA Administrator and then distribute it via the context menu on a group or individual basis.


To do this, select the desired client or client group. Right-click to open the menu. Click on Update program files automatically to remove the check mark and thus disable the automatic program updates.


Alternatively, you can also make the settings via the client settings General under Updates.

Updated client software may need to be tested to ensure compatibility with all client configurations on the network. Although minor version changes usually have no side effects, a staged rollout is recommended. Staged distribution can be enabled in the Updates module. Only when the program file has been successfully updated on the clients of one stage, it will be installed on the clients of the next stage.

The number of stages can be defined manually. The larger the network, the more stages are recommended to ensure a smooth installation. It is also possible to configure after how many days the next stage is updated. With the default value of three days, clients can be checked for problems to stop the distribution of a particular update if serious problems occur. The staged distribution settings can be changed by editing the Config.xml configuration file.

Program file updates always require a reboot of the client computer.

For some client roles, this must be carefully planned so that the computer is not restarted during an important task. In these cases, the Restart after update setting controls client behavior. The end user can be notified that their computer needs to be restarted. This restart can be forced or a report can be generated in the Security Events section so that the administrator can manually intervene and restart the computer at a later time.

Updates - Access data and settings

With your online registration you received access data for updating the virus databases and program files. Enter these under User name and Password. Select the nearest Region to ensure optimal speed when downloading updates.

The Version check (enabled by default) should always be switched on because it improves update speed. If, however, problems arise with virus signature databases, switch off the version check. During the next update, the integrity of all virus signature database files will be checked and files will be redownloaded if necessary.

Proxy settings opens a window in which proxy server credentials can be entered. You should only enter these if an update cannot be executed without a proxy server.

G DATA software can use the Internet Explorer proxy connection data (from version 4). First configure Internet Explorer and check whether the test page of our update server is accessible: https://dlarray-europ-pool-1.gdatasecurity.de/api/status. In the Proxy settings window, switch off the option Use
proxy server. Under User account, enter the account for which you have configured Internet Explorer (the account with which you have logged in to your computer).

Updates - Signature rollback

In rare cases, a virus signature update can lead to a false alarm or similar problems. It can make sense to block the latest virus signature update and use a previous one instead. Under Rollbacks you can indicate how many of the virus signature updates you would like to hold as a reserve for engine rollbacks. The default value here is the last five signature updates for each engine.

Should the latest update for one of the engines result in problems, the network administrator can block it for a certain time interval and distribute a prior signature update to the clients and subnet servers.

On clients that are not connected to G DATA ManagementServer (e.g. notebooks used in business travel), no rollbacks can be carried out. A block of new updates from the server to the client cannot be retracted without contacting G DATA ManagementServer.

With the affected engine selected in the Engine dropdown list, its most recent engine updates are listed under Blocked updates. Select the update(s) that should be blocked and click OK. Those updates will no longer be distributed, and clients that have previously received them will be rolled back to the most recent non-blocked update (when they connect to the ManagementServer). Optionally, new updates can be included in the block: tick Block new updates until and select a date.

  • No labels