Call Manager on W2K Domain ??

[BartKile]

We are a new CallManager 3.3/Unity 4.0 Installation - Exchange 2000 Integration.
Our Cisco Vendor tells me that the Call Manager Server should not be a part of our existing W2K Active Directory Domain.
Any comments on putting it on the domain?

 

[talbotpat]

It is recommended NOT to place CallManager servers into a domain, rather to leave them in a workgroup. In the past, (3.2/3.3) upgrades would not start successfully if the CallManager server was a member of a domain. This would necessitate a Spirian backup and rebuild of the CallManager server if the box was a publisher server. If the server was a subscriber, then all that would be needed would be to reinstall CallManager and link to the existing publication on the publisher CallManager server. Do not place the CallManager(s) into a domain. You'll be glad you didn't. ;-)

Pat

 

[lui3]

exposures to viruses etc. not to mention you do not want to be sharing files from CCM with domain users. you want it as isolated as possible. very little user access to disrupt its call handling.

 

[simonxts]

You can have the Callmanager use the AD in the Domain using the directory plugin. This way your users authenticate to the AD rather than to the local DC LDAP directory on the Callmanager.

 

[commsguy]

i put call manager's in the domain with no problem.....

just remove them when upgrading, and things are fine.

commsguy

http://www.convetech.com

 

[scaine]

Commsguy is correct - our pilot tests used the Call Managers in the domain and they worked fine.

Since then, we've changed that policy and run our live environment with CM in a workgroup.

Question you have to ask is "Why put them in the Domain?". What would it give you that you'd risk going against best recommendation for? Leave em in a workgroup unless you have a compelling reason not to.

 

[talbotpat]

My earlier comments were related to the CM being a domain *controller*. Like commsguy, we have seen and placed CM's into the domain and haven't seen any significant issues. However, the recommendation from TAC is not to place the CM's into domains, but have them exist in a workgroup, so that is our first preference and strong recommendation to clients unless they have a compelling reason to put them into a domain. So far, I haven't had anyone come up with a very compelling reason to do so.