For 2 reasons we do recommend not to use Bitdefender on an AADServer:
The Bitdefender Firewall does somehow disables / prevents the AADServer to be part of a Domain. When attempting to join the Domain, the result is error code 1355.
We have not been able to find a setting in Bitdefender such to make Domain Joining possible, except for the setting to disable the Bitdefender Firewall. Once the Bitdefender Firewall is disabled, Domain Joining works as usual and OK.
Bitdefender continuously disables AADS files and settings. The accompanying Event Text from Bitdefender contains the phrase "potentially", implying that not really a problem is detected, but despite that Bitdefender does disable the AADS software:
We have not been able to find settings within Bitdefender such that it would accept AADS files and settings.
There are some settings within Bitdefender that might give the Administrator the impression (illusion...) that settings are possible such that Bitdefender would be OK with AADS Files and settings:
but none of these settings did prohibit Bitdefender from disabling AADS files and settings.
The unavoidable conclusion is therefore that Bitdefender Internet Security 2016 might be a good product for a single user, single desktop, single login, single session Windows PC, but it can not be used on a multi user, multi desktop, multi login, multi session AADServer.
Copyright 2012-2017 AADS WorldWide LTD. AADS Terminal Server | Application Server | Remote Desktop solutions | Firewall