Forum Discussion
decommision 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 - Ex...
Good luck.
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
Thanks. I sure will. Just for now, the basis installation, so prior to run the setup.exe now, I was wondering if anything else can be 'broken'. I can't think of any, since these are two complete different forests (they do have a trust of course).
Configure mailflow, new hybrid etc. will be done later.
An issue I encountered was the following. I ran the setup to install Ex2016 and also added the /OrganizatioName qualifier to it with the name of the company. Now the setup fails with the error that this Organization already exists! I didn't expect this, since this is a different forest. Before I remove the /OrganizationName qualifier, can I ignore this error? How can it 'see' the existing Exchange organization in the other forest?
