Forum Discussion
Deleted
Aug 14, 2017decommision resource forest and install Exchange 2016 in account domain with existing hybrid
Following situation at a customer:
- Account and Resource forest
- Office 365 tenant
- Azure AD Connect machine running in Account forest, syncing both directories
- ADFS in Account forest
- Exchange 2010 in Resource forest with Hybrid setup
What we want:
- decommision resource forest/domain and Exhange 2010
- install Exchange 2016 in account forest
- make 2016 the hybrid
I was wondering which steps we had to take. We are now already migrating user to Exchange Online. For a new user we create a user with Linked Mailbox in Resource domain. We ADMT it to the Account forest, we trigger ADSync. A mailuser is made in Office 365 and we iniate a mailbox move.
Then in the resource forest we have a Mail Contact in Ex2010 and a disabled account in AD.
1- How can we get rid off these migrated users?
2- When can we install 2016 in the account forest, can it do any harm when we install it next to Ex 2010 which is in the other forest(ofcourse we have a trust)
3- How to move on from here?
Thanks for your support!
(sorry, I also posted this by accident in the Office 365 community. I realized later it should be here?)
- Admin001315Copper ContributorGood evening, Good morning Guys!
Glad I found this post. Now, I have the same scenario and the final goal is also same - to have Exchange 2016 in Account forest and decom Resource forest. The only thing is my client doesn't want to keep Exchange mailbox role, he just wants Exchange Management tools in Account forest as the only need isto manage the recipients and create remote mailboxes. There is no dependency of Autodiscover, smtp relay, and Hybrid (freebisy sharing etc). Can I continue with installing the Exch management tools alone without the Exchange server, or do I need ome Exchange server before installing the tools on another machine? I didn't get an exact answer on this so please share your opinions. - Deleted
Olaf Duits wrote:
Following situation at a customer:
- Account and Resource forest
- Office 365 tenant
- Azure AD Connect machine running in Account forest, syncing both directories
- ADFS in Account forest
- Exchange 2010 in Resource forest with Hybrid setup
What we want:
- decommision resource forest/domain and Exhange 2010
- install Exchange 2016 in account forest
- make 2016 the hybrid
I was wondering which steps we had to take. We are now already migrating user to Exchange Online. For a new user we create a user with Linked Mailbox in Resource domain. We ADMT it to the Account forest, we trigger ADSync. A mailuser is made in Office 365 and we iniate a mailbox move.
Then in the resource forest we have a Mail Contact in Ex2010 and a disabled account in AD.
1- How can we get rid off these migrated users?
2- When can we install 2016 in the account forest, can it do any harm when we install it next to Ex 2010 which is in the other forest(ofcourse we have a trust)
3- How to move on from here?
Thanks for your support!
(sorry, I also posted this by accident in the Office 365 community. I realized later it should be here?)
Olaf Duits, we too have the same requirement and same current setup as described by you. Did you manage to decommission exchange in resource forest and install in account forest ? If so, please provide the steps you followed to complete this. - Richard InnesBrass ContributorGood luck.
- Deleted
One more thing. All the preps are done and I am about to install Exchange 2016 on this machine now. Just to be cautious; are there any things that might influence the current Ex2010/EOL Hybrid environment or traffic? Just to be sure I have retrieved the current autodiscover settings and created a little script to re-set the autodiscover settings back to their original values, just in case they might be adjusted.
Thanks again!
Olaf
Be sure to establish mail flow in your new environment prior decomissiong Exchange 2010 hybrid. Or queue the mails from on-premises <-> EXO during the time you configure the new hybrid organization.
- Dominik
Hi Olaf,
Based on my expierience doing a lot of account/resource forest migrations when hybrid is already in place: Do first the consolidation within your forests and then go hybrid to your tenant before moving any users to Exchange Online.
Another possible solution is to migrate all users to Exchange Online, decomissioning Exchange 2010 and configure Exchange 2016 for hybrid and offboard users if necessary.
The problem with already migrated users from Exchange 2010 to Office 365: you "must" normallly use Prepare-MoveRequest prior migration users to Exchange Online to create a MEU object in the new Exchange 2016 forest. It is not supported to write Exchange attributes with ADSIEDIT or other tools without using Exchange.
If you setup the Exchange 2016 hybrid environment, your already migrated users will be a "RemoteMailbox, Privisioned". Your currently migrated mailboxes from Exchange 2010 are "RemoteMailbox, Migrated". And, if you want to offboard users during "reversy hybrid" you have to export the MailboxGUID from the Exchange Online mailboxes to your on-premise MEU object.
Long speak short: firest consolidate your on-premise Forests with a cross-forest migration and then go hybrid to your tenant. This is the "supported" and easiest kind of migration. Of course, you can copy all Exchange attributes with PowerShell or FIM (except some attributes like HomeMDB, ExchangeVersion, etc.) after your hybrid switch to the Exchange 2016 forest, but this requires a lot of planning and some other tools for the attribute flow between the forests.
Cheers,
Dominik
- Deleted
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.