MM R3.1: private vs corporate Windows domain

[seezer]

Greetings,

I've done several installs in the past in which MM resided in its own private domain. Now, I'm paying more attention to these choices and trying to determine difference between joining a private Windows domain vs corporate Windows domain.

The concept and planning guide indicates that the key difference between the private and corporate domain is how subscribers and administrators authenticate to the voice mail domain. Is this correct?

If the corporate LAN interfaces reside in the customer's data network, does the MM have to join the corporate domain? Will client applications such as the Outlook client work properly if the MM is in a private domain? Benefits to private domain vs corporate domain?

Regards,

Seezer

 

[KenMeans]

Well I find that putting it in it's own domain makes it easer to install and maintain. If you join the Corp Domain then you are at the mercy of the IT Dept and the policies that thy have set for the domain. And if they have not set the user up right then the install can go bust as well.

All of the plugin's will still work fine in both cases.



Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[seezer]

Thanks for clarifying that Ken.

Regards,

Seezer

 

[pabxdude]

to add to ken's post:

i tried my first copr domain install. all worked 100% until the IT dept applied there corporate policies to my accounts and computers.

after that - nothing worked.

rebuilt as private domain and no issues.

 

[seezer]

Thanks pabxdude. Sounds like the private domain is the way to go unless otherwise requested by the customer. I certainly do not want to rebuild the servers after they are cutover.

Regards,

Seezer