RE: [ActiveDir] OT? - LEGACY EXCHANGE DN

[Brown, Bill [contractor]]

Title: Message

Nice reply Al – however I do not believe that the legacyExchangeDN of the first administrative group has anything to do with the legacyExchangeDN of a newly created user in AD.  Well, maybe I am missing something here.  I do not intend on “mucking about” with the attributes for anything other than the users that need correction.  Additionally, I question the fact about the ADC being the mechanism involved with the setting.  The reason I state that is because I created a new user in AD in the domain that handles the E55 server and then a mailbox for the user.  Guess what?  ADSI Edit shows the legacyExchangeDN attribute correctly for that user and that information was populated via the ADC.  Finally, I believe that there can be a delivery issue involved when the user legacyExchangeDN does not match up with what E55 “sees” in the DS attribute OBJ-DIST-NAME…   R/Bill   -----Original Message----- From: Mulnick, Al [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 1:32 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] OT? - LEGACY EXCHANGE DN   http://support.microsoft.com/default.aspx?scid=kb;EN-US;q273863 is the description of how to do this.  However, I should caution you that mucking about with the legacyExchangeDN attribute is not a good idea.  Getting your users to live with it now is a better approach.  They will be living with it going forward since Exchange GAL in Exchange 200x doesn't care about containers.  You could also create ABV's to mimic this, but again, I don't recommend spending much time on the legacy system.   At some point, you're going to have to work with these users to make the change.  If they cannot make that change, there might be a reason to use the GAL views in Exchange 200x and it's best to know that early.    Finally, keep in mind that the ADC is the mechanism involved in this setting.  To move them between 5.5 containers is not as simple as changing the legacyExchangeDN since 5.x didn't understand or allow movement between containers; it requires the Microsoft shuffle (copy, delete, create) on the 5.5 side + replication times.  In other words, there's a lot of moving parts to make this scenario work.   Luck! :)   Al -----Original Message----- From: Brown, Bill [contractor] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 12:16 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT? - LEGACY EXCHANGE DN Al,   The immediate thing that comes to mind is that in our mixed mode environment [that we will have to live with for a while yet...] is that in the E55 sites the GAL lists these folks as being in the Recipients container (ou) where they are really in a different departmental container (ou).  Believe it or not - we have users that insist on going to a container listing in the GAL and picking their send to addresses!  Short of that - I am sure there are other issues.  Lastly, if MS put the attribute into AD - I think the attribute should represent the user exactly and this is not the case.   R/Bill   -----Original Message----- From: Mulnick, Al [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 10:59 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] OT? - LEGACY EXCHANGE DN   Plenty, but I have a question first.  Why are you wanting to change it?  What benefit is there if you change it? -----Original Message----- From: Brown, Bill [contractor] [mailto:[EMAIL PROTECTED] Sent: Thursday, October 16, 2003 10:01 AM To: ActiveDirList Subject: [ActiveDir] OT? - LEGACY EXCHANGE DN To All, When I create a user in AD the legacyExchangeDN attribute is always set to cn=Recipients no matter what ou the user was created under.  Using ADSI Edit to change the value to reflect the correct setting fails as the value is immediately changed back.  Does anyone have any thoughts on this??? R/Bill