Currently when administrating AD based logins you need to add both a AD server in the settings and configure a AD server for each AD group and AD user - this would be much more userfriendly if it was one setting that was used across those items.
When changing the domain controller to a new server (we assume that AD domains are extremely rarely renamed), changing this requires changing the server name on each object for users, groups and the server settings - bare in mind that it's each user that have logged on VisualCron through their AD group membership and not just specific AD users added in VisualCron as AD login users. It also doesn't make sense that AD servers being changed on users granted access through a AD group membership.

The current design scales terribly when using AD servernames instead of domain and is error prone due to the number of objects need to be updated.