Customer has 4 Unity servers at different locations, all running Unity 4.0(5). Each Unity server has its own Partner Exch2K3 server, local to itself. All servers are in one common AD environment, and are setup for Unified Messaging.
We enabled Digital Networking on all the servers recently, and things seem to function mostly, but we have an issues we can't resolve.
On one of the servers, the other 3 Unity servers in the network do not show under "Network->Dialing Domains->Profie->Pilot Numbers for Cross-Server Login, Transfer, and Live Reply". On the other 3 servers, the box at that location shows the other 3 Unity servers in the domain. This seems to be a synchronziation or replication issue, but can't quit pinpoint the cause of it. The server has been rebooted, but that didn't seem to fix it.
All 4 servers are in the same Dialing domain. Interestingly, on the server that is out-of-synch, the dialing domain didn't show up in the drop-down list. I had to manually enter it in the text box below that. After the Dialing Domain was established, 2 of the servers were able to see the domain, but this last server didn't. That's why I entered it manually, but it still seems to be out of synch with the rest of the servers.
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.