Forum Discussion
decommision resource forest and install Exchange 2016 in account domain with existing hybrid
Thanks Dominik. Although I have null experience in this, this is also what I thought would be the best approach. But unfortunately, the customer has already setup a hybrid with Ex2010 in their Resource domain, setup Azure AD Connect in the Account forest and migrated already users to EOL.
So, we need to do in this config, like described:
- Ex2010 in resource forest, Azure AD Connect in Account forest, Hybrid on Ex 2010 and already users migrated to EOL.
So the question, what global steps do I take to decommission the Resource forest? Thanks for helping me in advance!
The problem is that you should have been provisioned the migrated users to the Exchange 2016 resource forest prior migrate it to Exchange Online. You can't to this for Exchange Online mailboxes anymore.
1. Export all attributes from the Exchange Online migrated users from your on-premises Active Directory in the Exchange 2010 resource forest.
2. Migrate Cross-Premise to Exchange 2016.
3. Import the Exchange attributes in the new Exchange 2016 user account (except those which were moved with prepare moverequest, like homemdb, exchangeversion, etc.)
4. Stop AAD Connect.
5. Decomission hybrid: https://technet.microsoft.com/library/dn931280(v=exchg.150).aspx
5. Run AAD Connect in the new Forest
6. Set up hybrid
But this is not a overall supported solution, just my personal experience. And, of course, it is a very low level list which tasks must be performed.