Maintain sites and services domain controller topology

A common issue customers come across is Centrify binding to the wrong Domain Controllers.  For example, all the users in the US may be authenticating to a domain controller that is not geographically desirable.  In most instances, this occurs because the AD Sites and Services definition does not include the subnets of the UNIX/Linux systems or is not updated on a consistent basis. 

A process should be defined where the UNIX/Linux networking teams regularly interact with the AD team to assure subnets are added and removed from AD Sites and Services accordingly.