Manage installation packages in the G DATA Administrator

When installation packages are created, the installation file is copied to the directory C:\ProgramData\G Data\AntiVirus ManagementServer\InstallPackages. The same name (per client) is always used for each operating system and the previous file is overwritten.

To avoid having to navigate to this folder after each creation, the link to copy the last created installation package is included in the G DATA Management Server interface. The file can then be conveniently copied to the final storage location. If you need different installation packages (for example for different groups), the file must be copied into your organisational structure before creating the next installation package.

For the creation of installation packages for different tenants, copying is not necessary, as each file contains the unique identifier of the tenant in its name when it is saved.

Do not delete the entries in the installation package list until you are sure that it is no longer needed. Not even if you have already copied the file.

What else is the installation package list under (Organisation → Manage installation packages) needed for?

Each installation package is assigned a package ID that is stored on the client. When a client logs on to G DATA Management Server, a check is made to see whether installation package information is available in the registry and whether this PackageID is contained in the G DATA Management Server database.

Is it present in the list,

  • the client reauthorises itself if authorisation is lost (e.g. when resetting a VM).

  • clients who are registering for the first time can sort themselves directly into the right group or client.