The brain trust in our Windows Admins group named our NT domain to match our company name, and now that our company name has changed, we have to migrate thousands of users from one domain to another. The problem is that our AREA LDAP integration is referencing the old domain, so if a user is migrated to the new domain and changes their password, they can no longer get into Remedy (at least, not using LDAP authentication) Is there a way anyone knows to set up multiple AREA LDAP configurations? So that, for example, if the first fails, the second can be used? Or better yet, have the LDAP configuration be specified per user instead of the same for all users? We have ARS v6.3 patch 20, authenticating against our windows 2K domain controllers.
-Aaron * Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> SunCom is the wireless company that's committed to doing things differently. Things we want you to know. This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. This communication may contain material protected by the attorney-client privilege. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
