Skip to main content


This section allows you to define communication and update settings for target endpoints assigned with relay role.


This module is available for:

  • Windows for workstations

  • Windows for servers

  • Linux

The settings are organized into the following sections:


The Communication tab contains proxy preferences for the communication between relay endpoints and the GravityZone components.

If needed, you can configure independently the communication between target relay endpoints and Bitdefender Bitdefender Cloud Services / GravityZone, using the following settings:

  • Keep installation settings - to use the same proxy settings defined with the installation package.

  • Use proxy defined in the General section - to use the proxy settings defined in the current policy, under General > Settings section.

  • Do not use - when the target endpoints do not communicate with the specific Bitdefender components via proxy.


This section allows you to define the update settings for target endpoints with relay role:

  • Under Update section, you can configure the following settings:

    • The time interval when the relay endpoints check for updates.

    • The folder located on the relay endpoint where product and signature updates are downloaded and also mirrored. If you want to define a specific download folder, enter its full path in the corresponding field.


      It is recommended to define a dedicated folder for product and signature updates. Avoid choosing a folder containing system or personal files.

      This Download folder is also where the Patch caching data is stored.

  • The default update location for relay agents is You can specify other update locations by entering the IP or the local hostname of one or several relay machines in your network, then configure their priority using the up and down buttons displayed on mouse-over. If the first update location is unavailable, the next one is used and so on.


    Update locations and are used as a fallback.

    To define a custom update location:

    1. Enable the Define custom update locations option.

    2. Enter the address of the new update server in the Add location field.

      Use one of these syntaxes:

      • update_server_ip:port

      • update_server_name:port

      The default port is 7074.

    3. If the relay endpoint communicates with the local update server through a proxy server, select Use Proxy. The proxy settings defined in the General > Settings section will be taken into account.

    4. Click the add_inline.png Add button at the right side of the table.

    5. Use the up-arrow.png Up / down-arrow.png Down arrows in the Action column to set priority of defined update locations. If the first update location is not available, the next one is taken into account, and so on.

    To remove a location from the list, click the corresponding delete_inline.png Delete button.

    Although you can remove the default update location, this is not recommended.