Starting with Unity 4.0(1) Exchange 5.5 is not supported for VM only. The reason for this is that Exchange 5.5 is basically a dead product at Microsoft. End of support was extended until Dec 31, 2004 at the last minute only to allow customer to gain support while migrating to Exchange 2000/2003. Since Microsoft isn't maintaining Exchange 5.5 anymore is it not in the best interest of Cisco customer to deploy on it, which is why we don't support it anymore for VM only installations.
We bought VM unity license, customer has a global policy , so far they only maintain and support E55 in their enterprise. We initially proposed e2k solution, at last minute their globle IT turned down this and required E55 integration.
We have no choice. But from installation point, E55 should still be OK as long as it's on a seperate box from Unity in a VM only solution? Right?
Actually it is not OK. While it will technically work Cisco does not want customers deploying VM Unity with Exchange 5.5 since it is rapidly nearing end of support from Microsoft. That isn't code we control and won't be able to help customer with it once it is end of support. As such, it is a requirement that Unity 4.0 and later in a VM configuration use Exchange 2000 or Exchange 2003. Exchange 5.5 for voicemail only is not supported with 4.0.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...