The "High Road"??? Which road is that? I like to take the road less and most traveled myself... Which do you prefer?
-----Original Message----- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Monday, July 01, 2002 1:11 AM To: MS-Exchange Admin Issues Subject: RE: Changing legacyExchangeDN on a user account Take the high road, David, and don't validate those kind of posts by responding. :o) -----Original Message----- From: David N. Precht [mailto:[EMAIL PROTECTED]] Sent: Sunday, June 30, 2002 2:21 PM To: MS-Exchange Admin Issues Subject: RE: Changing legacyExchangeDN on a user account Very funny -----Original Message----- From: Andy David [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 6:54 PM To: MS-Exchange Admin Issues Subject: RE: Changing legacyExchangeDN on a user account Dont forget to type "unsubscribe" in the message body before you do that. -----Original Message----- From: Precht, David N. [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 5:27 PM To: MS-Exchange Admin Issues Subject: RE: Changing legacyExchangeDN on a user account I was just about to hit send..... -----Original Message----- From: John Weber [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 17:22 To: MS-Exchange Admin Issues Subject: RE: Changing legacyExchangeDN on a user account XADM: Move Mailbox Informational Messages List the legacyExchangeDN Attribute of Source and Destination Information Store (Q264391) ... XADM: Move Mailbox Informational Messages List the legacyExchangeDN Attribute of Source and Destination Information Store. XADM: Move Mailbox ... XADM: How to Change the legacyExchangeDN Attribute in Native Mode with ADSI Edit (Q273863) If the legacyExchangeDN attribute of your original administrative group contains an OU value of anything except First Administrative Group, you must change the legacyExchangeDN values of several system objects on your recovery server before restored XADM: Cannot Publish Outlook Free and Busy Information Because Mailbox Reconnect Forces legacyExchangeDN Delimeters to Uppercase Letters (Q288564) ... Publish Outlook Free and Busy Information Because Mailbox Reconnect Forces legacyExchangeDN Delimeters to Uppercase Letters. XADM: Cannot Publish Outlook Free and ... XADM: You Cannot Generate an Offline Address List and an Event ID 9126 Error Message Is Logged (Q318237) ... find details, address, or display templates because of an incorrect legacyExchangeDN value. During an unsuccessful installation of or removal of Exchange ... XADM: Minimum Permissions Necessary to Perform Exchange 2000 Server-related Tasks (Q316792) ... attributes on the user object: autoReplyMessage adminDisplayName dLMemDefault homeMDB homeMTA legacyExchangeDN mail mailNickname mAPIRecipient mDBUseDefaults msExchADCGlobalNames msExchControllingZone msExchFBURL msExchHideFromAddressLists msExchHomeServerName msExchMailboxGuid ... XADM: How to Enable Disabled Accounts That the ADC Creates (Q316047) ... to match the mailbox with already has mail attributes. The legacyExchangeDN attribute of the user also does not match the Exchange ... XADM: InterOrg Replication Utility Does Not Replicate Free-and-Busy Information (Q316022) ... be identical. In addition, either the ExchangeDN attribute or the legacyExchangeDN attribute of the free-and-busy user must exist, and it must ... XADM: Mailboxes Do Not Replicate from Active Directory to Exchange Server 5.5 (Q313212) ... CN=,OU=,DC=,DC=com because it does not have a legacyExchangeDN for the site it belongs in.( Connection Agreement'' #1288) This ... XADM: ADClean Sets "msExchMasterAccountSID" Attribute on Enabled Users (Q309222) ... attempts to convert a Microsoft Windows NT Security Identifier( SID) to a legacyExchangeDN. Only disabled users should have the msExchMasterAccountSID attribute set. This ... XADM: Workarounds for Problems with Mbconn.exe (Q301585) This article describes workarounds for the following known problems in Mbconn version 6.0.4417: Mbconn sets uppercase legacyExchangeDN delimiters, which causes Outlook clients to be unable to publish their free/busy information. Mbconn suddenly quits HOWTO: Programmatically Create Offline Address Books in Exchange 2000 (Q300123) ... the first" SetInfo" call when you are creating the object): legacyExchangeDN- A single-valued distinguished name attribute that stores the legacyExchangeDN of the ... XADM: Mail to Offline Address Book Users Is Returned with a Non-Delivery Report (Q297471) ... again.< server.domain.com #5.1.0> This issue can occur if the user 's legacyExchangeDN attribute is stored in all uppercase letters in Active Directory ... XADM: Requirements for Disabling the Recipient Update Service (Q296479) ... set the following attributes on all mail-enabled or mailbox-enabled objects: legacyExchangeDN proxyAddresses textEncodedORAddress mail mailNickname displayName The following is a brief explanation ... XADM: Windows 2000 Contacts and Users (Q233209) ... displayName: jdoe; 1> mail: [EMAIL PROTECTED]; 1> givenName: John; 1> instanceType: 4; 1> lastLogoff: 0; 1> lastLogon: 0; 1> legacyExchangeDN: /o=or1/ou=first administrative group/cn=Recipients/cn=jdoe; 1> logonCount ... XADM: How to Prevent Tombstones from Deleting Exchange Server 5.5 Mailboxes (Q288569) ... folder, they delete Exchange Server 5.5 mailboxes that match the legacyExchangeDN attribute of the tombstone. Before you configure the ADC Connection ... XADM: Error Message Updating Free and Busy Data in Exchange 2000 Server (Q286783) ... are not valid. This issue can occur if the user 's legacyExchangeDN attribute 's delimiters in Active Directory are either stored in all ... XCLN: How to Retrieve Last Logon Time of Exchange Users Using Extended MAPI (Q259570) ... Exchange Server 5.5 computer or the legacy Exchange Server DN( legacyExchangeDN) of an Exchange 2000 Server computer. The DN is then ... XADM: Creating Recipient Policies Based on Administrative Group (Q252395) ... Group you want to sort. The base query is (&(mail=*)(legacyExchangeDN=/o=/ou=/*)) Where /o= is your organization, and /ou= is the Administration ... XADM: How the Recipient Update Service Applies System Policies (Q253838) ... so on) needs to have at least these attributes: mailNickname, legacyExchangeDN, and displayName. Without the mailNickname attribute, an object is not ... XADM: Public Folder Connection Agreements (Q264889) In Microsoft Exchange Server 5.5, public folders are represented in two places: in the information store (hierarchy, [ACLs], and data content), and in the directory service. The directory representation is used mainly for revealing the public folders XGEN: Exchange 2000 Release Notes, Part II (Q277845) This article is part two of a two-part article that contains the Release Notes for Microsoft Exchange 2000 Server. To see part one, click the article number below to view the article in the Microsoft Knowledge Base: Q277844 XGEN: Exchange 2000 XADM: Non-Delivery Report Sending from Exchange Server 5.5 to Exchange 2000 Because of Active Directory Connector Replication (Q295377) ... the Active Directory Connector( ADC) replicates the Connection Agreement, the LegacyExchangeDN attribute of the Exchange 2000 account must match the OBJ-DIST-NAME ... XADM: Active Directory Connector Replicates Organizational Unit Subcontainers to Exchange Server 5.5 (Q313218) ... the ADC to create the mailbox objects based on the LegacyExchangeDN attribute. This prevents the Connection Agreement from replicating the organizational ... XGEN: How to Configure a Two-Way Recipient Connection Agreement for Exchange Server 5.5 Users (Q296260) This article describes how to create a two-way Recipient Connection Agreement to replicate an Exchange Server 5.5 directory to a Windows 2000 domain. XCCC: Direct Booking Does Not Work When Free and Busy Information is Unavailable (Q305390) ... Publish Outlook Free and Busy Information Because Mailbox Reconnect Forces legacyExchangeDN Delimeters to Uppercase Letters Q278305 XADM: Exchange 2000 Server Users ... John Weber Consultant Centerlogic 503-262-0490 x203 -----Original Message----- From: Miller Bonnie L. [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 12:36 To: MS-Exchange Admin Issues Subject: RE: Changing legacyExchangeDN on a user account John--you wouldn't happen to have a KB article covering that, would you? I'm going to go ahead and change it first on a test account just be safe, but was just wondering about the history of this value. Our previous EX5.5 admin had mentioned a value that was the unique identifier in 5.5 databases which was the name--was this that value? They used to have to export mail, delete, and recreate accounts in Exchange rather than renaming them due to this problem, reconnecting the new mailbox to the renamed NT4 account. When moving to E2k with AD, I'm assuming that the unique ID is now tied to the user SID and that even if this was the old unique ID for 5.5 that it would be okay to change. Anyone know if this is correct? -Bonnie -----Original Message----- From: John Weber [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 12:25 PM To: MS-Exchange Admin Issues Subject: RE: Changing legacyExchangeDN on a user account And it is, in fact, the recommended, and maybe only, method to use to change that attribute. Ex5.5 - E2K migrations needed this fix on sp0 installs. John Weber Consultant Centerlogic 503-262-0490 x203 -----Original Message----- From: Miller Bonnie L. [mailto:[EMAIL PROTECTED]] Sent: Friday, June 28, 2002 10:56 To: MS-Exchange Admin Issues Subject: Changing legacyExchangeDN on a user account Is it safe to use ADSI Edit to change the legacyExchangeDN attribute of a user account in E2k SP2 Native Mode running on Win2k SP2+SRP1 Native Mode AD? Thanks for any ideas, Bonnie List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm ------------------------------------------------------------------------ ------ The information contained in this email message is privileged and confidential information intended only for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copy of this message is strictly prohibited. If you have received this email in error, please immediately notify Veronis Suhler Stevenson by telephone (212)935-4990, fax (212)381-8168, or email ([EMAIL PROTECTED]) and delete the message. Thank you. ======================================================================== ====== List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
