It isn't required for the CallManagers to be in a domain, even if you have the directory integrated with your Active Directory domain. It is supported for them to join your domain. Joining them to a domain has no operational impact, but you should follow procedures carefully when performing upgrades, as some upgrades require you to dis-join the domain temporarily.
You cannot, however, make them domain controllers. This stops you from upgrading them or applying service packs, as doing this requires you to be logged in as local Administrator, which you cannot do on a domain controller.
Take extra care if you integrate with Active Directory and apply group policies to the CallManager server computer accounts. Some items, like password lockout settings, can get you into trouble. You will have no end of trouble repairing your cluster if your SQL service accounts get locked out, and this WILL happen during upgrades.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...