Mark Minasi's Tech Forum
Register Calendar Latest Topics Chat
 
 
 


Reply
  Author   Comment  
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #1 
When I attempt to install Exchange 2016 CU3 in an existing Exchange 2010 SP3 RU15 hybrid environment (Office 365 - Exchange Online), I encounter the following error message:

"If you continue to see this this message then it indicates that either the XML file specified is corrupt, or you are attempting to upgrade your on-premises Exchange installation to a build that isn't compatible with the Exchange version of your Office 365 tenant. Your Office 365 tenant must be upgraded to a compatible version of Exchange before upgrading your on-premises Exchange installation."

This happens when I run setup /PrepareAD.

It has to do with the /MyTenantOrganizationConfig parameter that apparently specifies details about your Office 365 tenant.

I've regenerated the xml file 3 times and still encounter the error.

I've asked for assistance on the Technet forum but we're going round in circles:

https://social.technet.microsoft.com/Forums/exchange/en-US/d574ae01-b0fe-48aa-9f10-93c8fb9bbf07/mytenantorganizationconfig-error-still?forum=Exch2016GD

Has anyone else encountered this type of problem in a hybrid environment?

I imagine this scenario would be fairly common in hybrid environments: Exchange 2010 and Office 365, then migrating onsite Exchange to 2016.
0
Wobble_Wibble

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 45
Reply with quote  #2 
Sorry not seen it yet. Only as far as 2010 or 2013 on Hybrid configuration.

My spell checker is in serious need of a kicking.

__________________
Press any key....
Yes, any key....
OK, try the space bar.
0
Severin

Still Checking the Forum Out
Registered:
Posts: 1
Reply with quote  #3 

Hi there

I have the same problem. I successfully upgraded a 2010 to 2016 cu2... but now i'm stuck on another upgradde from 2010 to 2016 cu3.

Had you any success to resolve the issue? I will try with cu2 today...

BR

Severin

0
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #4 
No solution yet. Still working on this with someone on the MS Technet Exchange forum.

So you can confirm this works with CU2?

I might try that myself then, since my testing with Exchange 2016 has been delayed a good month now (because of CU3?).
0
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #5 
A solution was proposed in TechNet discussion referenced above. Have yet to attempt this, hopefully will do so in the next few days.
0
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #6 
It failed with the suggestion made in the Technet forum and it failed with CU2. Same error.
0
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #7 
This was resolved. Solution in the TechNet link posted earlier.
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 751
Reply with quote  #8 
Thanks for posting.
__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
DM-AVAL

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 69
Reply with quote  #9 

You're welcome.

As I proceed with my testing, we'll see if the solution doesn't break something else... [biggrin]

0
Previous Topic | Next Topic
Print
Reply

Quick Navigation: