Can Unity 188.8.131.52 and Unity 3.x coexist in the same Exchange site? We are running Exchange 55 SP4 and Unity 184.108.40.206 on two Unity servers attached to and want to upgrade one of the Unity servers to 3.x. The 2 switches are NEC Neax 2400 with serial integration.<br><br>
be aware, however, that users on the 2.4.6 system wont be able to send messages by name/id to users on the 3.x system and vice versa... they wont appear in each others directories over the phone.
Short story is there's no networking capabilities between 2.x and 3.x systems in this case (you can use blind addressing and internet subscribers etc... if you really need to but this is somewhat ugly from an admin standpoint).
The coexistence will be transitory and lost of networking is ok. We have two physical switch locations, each with their own Unity 2.4.6 server. For testing and eval purposes we want to build Unity 3.x into the production site and move in batches, IT then followed by everyone else. So we will have 3 Unity servers, two 2.4.6 and one 3.x. Then decomission the Unity 2.4.6 and then move on to the other switch location and replace its server. Do you see any problems with this scenario?
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.