Adding LegacyExchangeDN to another mailbox
Hi We have a mailbox - help@domain.com that has a LegacyExchangeDN (LED) of X. The ID of this mailbox is MBX1. There is another mailbox that we want to start using (MBX2) for this purpose - support@domain.com. It has an LED of Y. We'll be disconnecting MBX1 in Exchange and then deleting after 14 days. We'll also be adding help@domain.com as a secondary email address on to the MBX2 properties. But for internal mails, which use the LED value, we want to make sure there are no outages. Does anyone know the best way to add the LED of MBX1 to MBX2? Is this carried out in Exchange or AD? Applies to Exchange 2007 SP2.
February 15th, 2011 3:04pm

On Tue, 15 Feb 2011 19:55:28 +0000, Smith1974 wrote: >Hi We have a mailbox - help@domain.com that has a LegacyExchangeDN (LED) of X. The ID of this mailbox is MBX1. There is another mailbox that we want to start using (MBX2) for this purpose - support@domain.com. It has an LED of Y. We'll be disconnecting MBX1 in Exchange and then deleting after 14 days. We'll also be adding help@domain.com as a secondary email address on to the MBX2 properties. But for internal mails, which use the LED value, we want to make sure there are no outages. Does anyone know the best way to add the LED of MBX1 to MBX2? Is this carried out in Exchange or AD? Applies to Exchange 2007 SP2. Add the legacyExchangeDN value of MBX1 as a custom X500 address type on MBX2. Use the EMC to do this -- AFTER you extract the legacyExchangeDN value from MBX1 and then disable the MBX1 mailbox. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2011 3:10pm

What order should do I this all in? I was thinking: 1. Make a note of MBX1's LED (X) 2. Disconnect MBX1 3. Right after disconnection, add X as an X500 address to MBX2 How does that sound?
February 15th, 2011 3:19pm

On Tue, 15 Feb 2011 20:10:28 +0000, Smith1974 wrote: >What order should do I this all in? I was thinking: > >1. Make a note of MBX1's LED (X) 2. Disconnect MBX1 3. Right after disconnection, add X as an X500 address to MBX2 > >How does that sound? Yes. You'll still have a window where the values won't be correct as the AD replicates the changes. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2011 3:44pm

Great, thank you. Question - in the plan above, both MBX1 and MBX2 have the same LED. Although MBX1 is disconnected, will this make a difference? If a user sent a mail to the LED of X, which is present on both (disconnected) MBX1 and MBX2, is there the change that Exchange would issue a failure report? Or does it never try and route messages to disconnected mailboxes? I am thinking whether we should remove the LED value of X from MBX1 before adding to MBX2? In terms of the window you mention, I guess whenever we make the change we'd be wise to force AD replication?
February 15th, 2011 3:51pm

On Tue, 15 Feb 2011 20:42:30 +0000, Smith1974 wrote: >Question - in the plan above, both MBX1 and MBX2 have the same LED. Nope. Not gonna happen. The same address can't be assigned to two mailboxes. When you disable (what you called "disconnect") MBX1 it loses the legacyExchangeDN property. >Although MBX1 is disconnected, will this make a difference? If a user sent a mail to the LED of X, which is present on both (disconnected) MBX1 and MBX2, is there the change that Exchange would issue a failure report? Or does it never try and route messages to disconnected mailboxes? > >I am thinking whether we should remove the LED value of X from MBX1 before adding to MBX2? Yes. Of course. But that happens when you disable the mailbox. >In terms of the window you mention, I guess whenever we make the change we'd be wise to force AD replication? Or just do the changes when the sender's inactive. I don't know the complexity of your AD topology. Within an AD site it should all be over in 5 minutes. Between AD sites replication happens every 15 minutes. The KCC (or whatever they're calling it these days) usually figures out a good way of getting the changes between sites -- unless you've set up your own site links. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2011 5:33pm

>When you disable (what you called "disconnect") MBX1 it loses the >legacyExchangeDN property. Sorry, getting my terminology wrong :) Ok, so as soon as I disable a mailbox, the LED is lost from it? What's the reason for this - because the LED is an AD attribute and when you disable a mailbox you are disconnecting it from the associated AD account? In which case, let me give an unrelated scenario. MBX3 (mbx3@domain.com) has an LED of Z. I then disable that mailbox and try and send a mail to it from my Outlook using a cached entry (so that it's using the LED)...what sort of NDR would I get, an error saying that mbx3@domain.com is no longer a valid address, or seeing as the LED has been removed, a message saying that there is no such LED? Thanks for all your help, very interesting topic I think.
February 15th, 2011 5:41pm

On Tue, 15 Feb 2011 22:33:34 +0000, Smith1974 wrote: >>When you disable (what you called "disconnect") MBX1 it loses the >>legacyExchangeDN property. >Sorry, getting my terminology wrong :) Ok, so as soon as I disable a mailbox, the LED is lost from it? Yes. >What's the reason for this - because the LED is an AD attribute and when you disable a mailbox you are disconnecting it from the associated AD account? No, it's becasue there's no longer any need to keep it. >In which case, let me give an unrelated scenario. MBX3 (mbx3@domain.com) has an LED of Z. I then disable that mailbox and try and send a mail to it from my Outlook using a cached entry (so that it's using the LED)...what sort of NDR would I get, an error saying that mbx3@domain.com is no longer a valid address, or seeing as the LED has been removed, a message saying that there is no such LED? Thanks for all your help, very interesting topic I think. You would get a NDR where the error was an unknown recipient, and the reason would be ExRecipientUnknown. If you sent the e-mail using a SMTP address you'd get a similar error, but it'd be just RecipientUnknown. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2011 8:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics