• Status: Solved
  • Priority: Low
  • Security: Public
  • Views: 30
  • Last Modified:

MS Exchange X500

I have two forests both with exchange 2013 servers. We will call them EX1 and Ex2. I will be creating new AD accounts and associated mailboxes for users moving from EX1 to EX2. These accounts will obviously be empty when users first login. In order to ensure these users get their old email I will simply export their email from EX1 to PST and then import it into their associated mailboxes in EX2. I will also repoint the domain name pointing to EX1 to EX2 and create email alias to ensure they still receive any email sent to their old address. - Hope you're still following!

My question is after the migration if users hit the reply button to any of their old email will this cause an issue as I recall some problem previously with X500 addresses, thanks.
0
Sid_F
Asked:
Sid_F
  • 4
  • 3
1 Solution
 
MaheshArchitectCommented:
Correct
you will face NDR issue as legacyexchangedn value will remain missing at target
to avoid this situation, you need to properly migrate those mailboxes by provisioning source users to target
3rd party tools are also available
OR
you may use exchange native scripts and ADMT for same
The process is bot complex
i suggest you open GIGs for same
0
 
MaheshArchitectCommented:
In short, you need to migrate source accounts to target and do not not create new accounts
0
 
Sid_FAuthor Commented:
New accounts must be created as they are two entirely different forests. Surely X500 addresses can be created in the new environment.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Sid_FAuthor Commented:
Thinking about this a little more

1) John is a user in the old company. I am switching off the entire network in the old company and giving everyone new accounts and email in the new companies exchange.

2) John now has a completely new email in the new company. To allow for customers to still reach John I repoint his old domain to the new companies exchange and setup secondary SMTP address to match his old address.

3) I also export his email out of the old exchange server to PST and import it into his mailbox on the new exchange server.

Will I still have NDR issues? If so this would in theory mean I would need two exchangeLegacyDN's entries? Server is 2013
0
 
MaheshArchitectCommented:
No you cannot create x500 addresses manually, you need to copy it from source

The scenario you mentioned last will work great

you will not face problem if user 1st time send email to john old email address as it don't have cached copy of his email address which ultimately points to old exchange server

You may face problem when user have cached copy of John's email ID, in that case if user types his old email address manually, then it will not use cached copy
The ideal solution to avoid such issues is to copy John's old ID legacy exchange DN value and copy it to his new account as X500 address
0
 
Sid_FAuthor Commented:
Is this only an issue for people who send email using an auto complete file? so if my users delete their auto complete file or setup a new outlook profile then the legacy DN's are not required?

I have tested this with two mailboxes and it would appear they are not affected because there is no historic NK2 file. Hopefully someone can confirm.
0
 
MaheshArchitectCommented:
Yes, that is absolutely correct
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now