![]() ![]() LegacyExchangeDN ß the key of this article!.(with some other helpful info!) Source Preparation So…here is one method to collect the Exchange Legacy DN before migration and three ways to correct it after migration. For our Microsoft 365 tenant migration customers, you are not likely reading this as we do this entire process by default! The good news for Quadrotech’s Office 365 reporting customers is we collect this for you. You can fix this as they come in by just taking the Exchange Legacy DN from the NDR, but that won’t scale. You need to collect the Exchange Legacy DN from the source before the move to make it easier. So the bad news is that if you are here right now, it can be hard to fix this. The business result is people going to the wrong place at the wrong time, confused users, and frantic emails saying, “DELETE THE BAD INVITE NOW!!” How To Add X500 Email Addresses The result is that if someone updates a calendar invite after it has been moved to another environment, the internal attendees will get a nasty undeliverable (NDR). Because of this, internal recipients are actually stored in content, like calendar invites. ![]() What exactly is the problem?īack before Exchange was integrated into Active Directory, Exchange used the Legacy Exchange DN for internal recipients. ![]() This stems back to the very early days of Exchange. When moving from one environment to another, calendars can be a major challenge. Regardless of Exchange Version, including Exchange 2010, Exchange 2013, Exchange 2016, or Exchange Online in Office 365, this trick still applies today. The X500 email address, or the X500 Proxy Address, is one of the most important “tricks” of the data migration trade. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |