We're trying to load unity enterprise on win2k. We installed exchange 5.5 that ships with the software. However when trying to load the unity piece we get the above message. We can telnet to the server on port 389 so we know that ldap is running. We got ldap enabled on the echange server. we even formatted the server and loaded everything from scratch. We still can't get pass that error message. Can anyone help? firstname.lastname@example.org<br><br>
Windows 2000 is not happy with folks using 389 (it uses that port for something else). Win2K is, in fact, the reason why we had to add that extra dialog to the setup application in the first place. Annoying, but you can get around it pretty easily.
Open the Exchange administration application and head to the Configuration container for the site were installed in. Expand the Servers container and click on the server Unity is installed on. Under the server name youll see the protocols container, click on that and in the right panel youll see an LDAP (Directory) settings option. Double click on that and itll bring up a property dialog. On the General tab, change the Port Number setting to something other than 389. Personally I use 1024 since its safe and easy to remember. Be sure the Use Site Defaults for all properties check box is cleared.
Once youve done this, restart the server and try the install again. This time stick 1024 in there when the Unity setup asks and you should be cool.
If this isnt clear, the README file on the Unity CD talks about this as well I believe.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
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...