It's invaluable for these situations. In this case, you could look at changing the partner exchange server, seperating Unity and Exchange, and replacing or convertin a Cisco Unity server or failover servers.
One of the Unity servers ver 4.2.1 is already running on windows 2003. I need to upgrade this server to Unity 5.0.1(same hardware) and since its already running windows 2003, all I have to do is upgrade the Unity software version to 5.0.1, however, I need to add a 2nd Unity as failover also needs to be running 5.0.1. My question is
Should I do the failover configuration while still running 4.2.1 in order to minimized downtime (since one unity is down the other is still running)
then upgrade both Unity to version 5 one at a time, or just upgrade the 1st Unity 4.2.1 to version 5.0.1 then configured/add the failover Unity to the cluster, however i feel More downtime is required with this last option
If you are staying in VMO, it's pretty easy to just create an entire new domain for this.
Create your domain
Install Unity 4.x, Exchange etc.
The Dirt restore will re-create the Exchange and AD accounts for you, restore the Unity DB, etc.
Once it's all working on the new hardware, etc, then proceed with the inplace upgrade to Unity 5.x.
Messing around with FSMO, Exchange , etc is really not necessary. Unless you have some complelling reason to keep the VMO domain running or for something else? I typically look at VMO domains for Unity as "short life" domains. They are only built to run Unity VMO and nothing more. If you are installing a new VMO server and upgrading all this stuff, it's much easier to create new in my opinion. Nobody likes decommisioning Exchange, FSMO roles and all the fun MSFT stuff that goes along with it.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...