A customer of mine has a POV installation of Unity because they are a Notes shop so they originally did not want the Unity server integrated into their environment. The Unity server is 2.4.6 on W2K in its own Active Directory enabled domain. Quick Question: Can a trust relationship be used to pass their login credentials (to their existing NT 4.0 domain) with the appropriate acls of course on the W2K domain so that they don't have to login twice when trying to open Active Assistant?<br><br>Thanks for your help<br><br>
Ok I think I understand what you want to do, but let me recap. You have NT accounts created in the Unity servers domain and separate NT account created in their main domain where users are authenticating, right? It sounds like the Unity server is an island install where were in our own domain and our own Exchange org/site, right? Im assuming you created these voice mail users on Unity via the SA and we turned around and created Exchange accounts and local NT accounts for them on our box.
If thats the case, a trust relationship alone isnt going to do it for you. Even if the NT login name and password are the same in both domains, NT Challenge and Response isnt going to work for you here each NT account has a SID associated with it and when an account hits our web server we pass that SID through and look to see if theres an Exchange account that matches that NT account thats also a subscriber. Since these users will be coming from another domain with different NT account, the SID will not match anything in our Exchange server.
What youd need to do is create a trust such that the Unity domain trusts your main domain. Then you need to rip through in Exchange and associated each mailbox with its corresponding NT account in the main domain (they will be associated with accounts in the Unity domain already). Once you do that they should be able to hit the AA page without being asked to authenticate again.
If I totally missed your pitch, let me know and Ill take another swing.
You understood it perfectly; that was exactly what I figured I needed to do, but I wanted to make sure there wasn't anything above setting up the Trust and associating the Exchange Account (I didn't write that originally, but nonetheless thought about that)with the login on their other NT domain. Thanks as always. I will get them all set up.
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.