Jeff,<br><br>I have a customer that would like a Unity Demo, but currently has about 7 Exchange servers running in production mode with Service Pack 3 installed. Unity 2.4.6 requires Exchange 5.5 with Service Pack 4. I have heard several anecdotal stories about registry problems during the install when mixing Exchange systems in the same site/organization. Can you add any input and/or assurances.<br><br><br>
Hey Nick... since you guys figured out all kinds of good stuff on this one, I'm going to shamelessly drop your findings out here!
Technically Unity only cares about the SP on the local Exchange server but MS reccomends that all SPs in the site match. Before this morning I didn't think it was that big a deal since I know some sites are in this config... looks like you guys ran into some pain. Short story, MS isn't kidding.... it's a good idea to be at SP4 across the boards.
Here's the info that was passed to me this monring:
================================= We brought up Exchange 5.5 on the Unity server and joined it to the existing site. We then upgraded the Unity server to SP4 (left primary server at SP3). Here are some of the problems we had with the main Exchange server (even after we took the Unity Exchange server offline):
Basically some of the directory versions of the proxy generators did not match the actual dynamic link library (DLL) file versions. The directory versions were listed as SP4 versions while the actual DLLs on the box were SP3 versions. (note that we had never applied SP4 to this box).
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.