AADS and Anti Virus software

Results

Generic Advice

• Turn Off / Disable settings related to  "Heuristic", or "PUA (potential unwanted software)"

Heuristic / PUA does result in false positives, and results in disabling and deleting AADS program files (and other files, like Windows Executables...)

Which AV software to use...

Should it be needed to select or to change the AV software, possible AV-TEST GmbH might be usefull for reviewing and selecting AV software.

How we test AADS and Anti Virus software

• Install default Windows
• Install the Anti Virus Software
• Change settings in the Anti Virus Software if such is required. What we change from the default, is documented in this FAQ. 
• Run the test in an AADS Farm and do lots of remote desktop sessions

• Application Control is used:

• The $desktop and $aad Windows Menu do make sure that Windows, Explorer, the Taskbar, etc, are all loaded and running as if it is default Windows.
• The $aad Apply Relaxed Control is something an Administrator would not apply to users; it lifts off the protection as offered by AADS Application Control. It is applied here because the test should not somehow limit Windows and the Anti Virus software. The point of this FAQ is to let Windows and the Anti Virus software do what is wants to do, and document its behaviour in this FAQ.
• The Logoff Delay is a special CMD-file, that makes sure that the user is logged off after a short time. The test we do here is to let users do logon's and logoff's for several days, and see how the Anti Virus software handles this.
• The Notepad application is always good to use when testing; for notes. Also if the user has only 1 Visible Application , being the Logoff Delay, then the user will not get to see a full desktop, but only this 1 Application will be started and shown on the desktop of the user. By giving the users also Notepad, the user has 2 Visible Applications.

• Logoff Delay:

• The tool aadscommandlinetool is described here, and can be downloaded from our website.

aadscommandlinetool.exe /sleep 600 120
aadscommandlinetool.exe /logoffme

• The clients are Linux clients, running rdesktop. Each client is running its own version of the following script; each client has its own username and password in the bash-script:

#!/bin/bash
while true
do
rdesktop -a 24 -g 800x600 -u domain001 -p ****** -d ipc 192.168.200.60
sleep 300s
done

The bash-script running on each client cooperates with the logoff.cmd.

• The bash-script does a logon,
• With a bit of random time the cmd-script logoff.cmd does the logoff,
• The bash-script waits 300 seconds and does again a login.

and this keeps on running "forever". Roughly every 5 a 10 minutes the user does a logon, desktop is created, and the user does a logoff.