GData

• GData works OK on AADServer while using default GData configuration settings.
• Tested on Windows 11 x64 (Test date Dec 2021)

Older versions and tests with GData:

The GData option "Behaviour monitor" needs to be disabled to avoid problems.

• Tested on Windows 10 x64 build 17751 (Test date Oct 2018)
• Tested on Windows 7 x64 SP1 (Test date Sep 2017)
• Tested on Windows 7 x64 SP1 with all updates (Test date Apr 2016)

Tested on Windows 11 x64 (Test date Dec 2021)

The GData installation as we have done for this test is as follows:

• We did only install the "Anti Virus".

• The configuration of GData is default. We have not changed any setting within GData.

Everything worked OK. We have not encountered any issue while running the tests:

• Install Windows 11 x64.
• Update Windows until there are no more updates available.
• Install GData.
• Install AADS Demo Enterprise for Windows 10/11 x64, latest AADS build.
• Apply AADS Optimize .
• Run 3 clients that do login, and logout every 5 a 10 minutes.

Windows 10 x64 build 17751 (Test date Oct 2018)

The GData installation is almost default, except for the "Behaviour Monitoring":

The option "Behavior Monitor" results in false positives , and in disabling and deleting of AADS program files.

Once  "Behaviour Monitoring" is disabled, GDATA runs OK on our AADServer for several days.

Windows 7 x64 SP1 (Test date Sep 2017)

The GData installation is almost default, except for the Real Time Protection:

The option "Behavior Monitor" results in false positives , and in disabling and deleting of AADS program files.

Windows 7 x64 SP1 with all updates (Test date Apr 2016)

The GData installation is almost default, except for the Real Time Protection:

The option "Behaviour monitor" is disabled. This option expects apparently that Windows is single Logon, single Session, single User, single Desktop, and causes to much trouble.

When this option is enabled, and AADS tries to create and run multiple sessions, the following popups might appear:

If an AADS program is "stopped", then AADServer can not create multiple desktops.....
If an AADS program is "moved to quarantine", AADServer stops working correctly....

• AADServer needs to be re-installed.

It is possible to select "Allow Always":

but for reasons unknown to us, it did still happen that AADS files where removed, rendering the AADServer to stop working properly. Also, this popup might be shown to users who do not have enough Administrator Rights to disable this unwanted GData decision.
Possible this did happen because,

• AADServer is updated with the latest build and because of that AADS exe-files are changed, or
• GData updates itself, or
• some bug in GData.

Although one can expect that GData has only good intentions with the option "Behavior Monitoring", we choose to disable this option, such to make sure that the AADServer keeps on running properly.

When the option "Behavior Monitoring" is disabled, the result might be that GData keeps on showing "annoying popups" to all logged-in users, every time an user does a logon. The checkbox "don't show again" did not work for us. We have unfortunately not found an option somewhere in GData for permanently disabling all popups to the users.

GData Firewall

Because GData takes over the Windows Firewall, it is required to enter rules such that the Users can connect to the AADServer:

• Select Firewall, Status.

• Create a "New" Rule:

• Select Advanced Rule Set Editor

• Create a Rule Set with the name AADS
• Create a Rule that allows TCP inbound / outbound on port 3389.

• When AADS is used in a Farm, create a second Rule that allows UDP inbound / outbound on port 3390.