We have a customer running Unity 4.2 in two separate servers one for VM (all in one box) and another for UM with typical setup mail server off the box.
Now they want to upgrade Exchange to 2007 and put both VM and UM users on same box with mixed licensing. I know we have to upgrade Unity to 5.x to support Ex2k7 but what should we do to add those VM only users on the same box?
1. Does Unity support mixed VM/UM licensing with Exchg 2007?
2. Do we need a Exchange 2003 mail store just for VM only users?
3. Can we use the same exchange 2007 server withe separate OU for VM users.
4.If we have to add a separate exchange 2003 server for VM users, can this be installed on the Unity server itself or do we need a separate exchg2003 mail store server?
Yes, mixed UM/VMO is offered. The licensing isn't dependent upon the Exchange version.
Here is a good white paper that should answer all/most of your questions regarding mixed mode and the migration process. It suggests that different mail stores be created on the Exchange server to house the VMO users.
Mixed mode doesn't require a specific Exchange version. Exchange 2007 is supported with Unity 5, therefore will work when integrated with Unity 5. The UM/VM is all a matter of how AD accounts and mailboxes are organized which all comes into play with the Unity licensing as explained in that document.
You could just put the VMO users on the same Exchange 2007 server if you wanted. These users however obviously wouldn't have access to voice mail via their Outlook client or the View Mail plug-in available to them like the Unified subscribers would.
If we use Exchg2007 for all VMO and UM users what about the exchange licensing for VMO users? They have to buy more Exchange 2007 user license or ??? becuase MSFT put more restrictions on licensing now.
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.