I read the following on a cisco page "It is recommended to keep all your Cisco CallManager servers in Windows workgroups rather than Active Directory domains."
I believe that I have seen this documented elsewhere, but I cannot remember every seeing a reasoning behind this. Can anyone tell me why Cisco recommends to leave yourr callmanagers in workgroups instead for on their own domain?
I don't see why you should have to dis-join the domain to run updates. I know that Cisco requires you to do this, but here must be more reasoning behind why cisco recommends to put your call managers in a workgroup. Thanks for the answer.
I think Cisco should address this... It is a real pain to have CCMs in a workgroup when things like BAT and the Realtime Monitor tool will not MLA for authinication. This required I create local account for my administrators to use BAT...
I was once told by a TAC engineer that the main reason was because of Viruses etc. If the server is part of a domain and the vius exists in a domain authenticated user session it could spread to the CCM servers. This was back in the 3.0 days when there were no supported ANti-Virus products for CCM too.
It also makes it easier to troubleshoot weird problems without having to worry about group policy inheritance.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.