I am planning to upgrade from Unity 4.2(1) to Unity 5 (Exchange 2007 support is needed). To make the least disruption to our production environment I will be building two separate Unity servers and installing Unity 5 on them.Both will be working at the same time (for transition period) in UM setup. Unity 4 is already working in UM setup.
Now here is my plan:
1. Install Unity 5 using same accounts used when Unity 4 was installed (Dir,MsgStr,Install). These accounts are in AD, so shouldn't be an issue to just reuse them when installing Unity 5
2. Port database from Unity 4 to Unity 5, so Unity 5 has all the config.
3. Create necessary CCM config as far as voicemail ports are concerned (another set of ports). User different VM port DNs, different VM pilot and different VM Profile.
Now, each time I want to migrate user, all I do is change the VM Profile reference under DN to point at new Profile created for Unity 5 in CCM.
Sounds easy, huh? :-)
Have anyone even done this? My concern is so Exchange 2003 environment is not confused by presense of two Unity servers using same AD accounts.
Will Exchange 2003 know to sent notifications to the proper Unity, or will it send them to both and only the one that has the subscriber will act on it? Example being MWI on/off state...