Crossforest Migration Autodiscover and Outlook profile config

I am working on Exchange 2010 Cross-forest migration project and as far as to my knowledge the normal behavior for autodiscover and outlook configuration is as following:

1- Once we finish migrating user to the target forest, Autodiscover works only if the UPN domain is added to the user's proxy address list, or if SCP is exported and imported to target AD.

2- Outlook will require user to create new profile after user is migrated. what I mean by this is that user can't close and open outlook to find it working with the new configuration (New Target Forest server) ?

Is there anything that can change this behavior where user can still use their old outlook profile without taking any action .. just as if it's a normal intra-forest migration?
LVL 24
Mohammed HamadaSenior IT ConsultantAsked:
Who is Participating?
Mohammed HamadaSenior IT ConsultantAuthor Commented:
To answer my own question here's how we got it to work.

In order for outlook to work for the user without creating new profile or affecting end user's work I did the following:

1- First use Prepare-moverequest to create the User on Target forest.

2- Use ADMT to copy this user's SID from Source forest.

3- New-Moverequest and migrate the user to target forest.

The User gets a warning that Admin did something and needs to restart his/her outlook. as soon as the user restart his/her outlook they'll get prompted for credentials and after they write their target forest credentials they'll log in flawlessly.

This has been tested and working, We were doing this the other way around which was apparently not working we first were using ADMT, then use Prepare-Moverequest ..etc

Hope this helps anyone who is doing something similar
timgreen7077Exchange EngineerCommented:
As long as the email address associated with the mailbox is the same and resolvable via autodiscover after the migration outlook should automatically update and allow the user to continue with the same outlook profile. Once they open outlook it generally prompts them to restart outlook because a change has been made and once the close and re-open outlook it generally will use the same profile successfully.
Mohammed HamadaSenior IT ConsultantAuthor Commented:
The config I have is as following

Source Domain:  with Exchange 2010 SP3
Target Domain: With Exchange 2010 SP3

User is migrated via ADMT with SID history ..etc, User profile and computer is also migrated without an issue.
When opening old outlook it doesn't connect. so we create a new profile and autodiscover configures the users mail on the target domain

User Before Mailbox Migration has:
Computer Object:

User After Mailbox Migration has
UPN:    #User's Account changed from name.surname to ID (Number)
PrimarySMTP :
Computer Object:

So in this scenario it works fine for us, but the argument is that there's a way (Even with changing the UPN from name.lastname to Number) still user can open their old outlook profile and work on it .
Mohammed HamadaSenior IT ConsultantAuthor Commented:
Solved it on my own
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.

All Courses

From novice to tech pro — start learning today.