I am planning the following Unity v5 deployment:
Message Store (Exchange 2k3) hosted on Secondary Unity server
Primary & Secondary Unity servers in different Locations with a WAN between them.
SQL Server 2k on both Unity Servers.
The WAN connectivity passes all the criteria for redundancy, latency, distance etc.
My concern is over the Active Directory configuration. The system requirements document on CCO states the following:
â¢ For the Active Directory domain, you must use one of the following configurations:
- Both Cisco Unity servers are member servers in the same Active Directory domain.
- The secondary server is a domain controller and the primary server is a member server in the
secondary server domain.
â¢ When servers are installed in different locations, each location must have a domain controller/global
I will not be making these servers members of an already existing Domain hence would be looking to make the Secondary server the DC. However, what happens to the Primary as the requirement is that it should have access to a DC/GC server itself as it is in a separate location ?
The Unity Install guide provides detail as to how to create the Active Directory DC using the "dcpromo" application on the Secondary server. Do I also run this on the Primary as well ?
Basically the details of AD config and requirements are confusing in the documentation I have seen and nothing seems to give specific detail to the deployment I am looking to do.
My Customer does not want the Unity servers in the same Data Centre hence why I am faced with this issue.
Also, the Unity servers need access to DNS as part of the dcpromo process. Is this simply a case of activating the DNS service (Dynamic DNS ?)on each server ?
I hope someone can provide some clarity as I am going around in cricles with this !!
Matt, that is correct, just make sure that you create AD sites so Primary Unity uses the local DC as primary and remote DC as failover, the same applies to DNS. The Primary server will be the DC/GC and will be promoted as the first DC on the domain, the second server will be another DC for the same domain. That way, DC updates will be faster (BTW, You can also promote the second server as a GC).
In regards to TAC support, if you have redundant links on the WAN with different providers, you do not need the DC/GC/DNS on the primary site, just on the secondary since the only issue that we could have will be to loose connectivity which is almost impossible if the WAN connection is fully redundant.
Any of the scenarios that we have previously discussed are supported as long as we have Gb links and less than 10ms delay, this only applies to Unity 5.X/7.X.
Have a nice day!!!