Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 16953

Office 365 Hybrid Configuration

$
0
0

On-premise we have exchange 2010 & 2013 coexsistance with each having there own separate FQDN. I have now been instructed to move the students to office 365 while keeping the staff on-premise for now.

 

Currently exchange 2010 still has almost all the users with about a half dozen people migrated to 2013. All email flows outbound out of the 2013 servers to the internet... All server that need a certificate has the same 3rd party multi certificate installed.

 

I have configured exchange 2010 as the hybrid server and I was able to migrate a test account to office 365 which will/does have the same FQDN as the on-premise exchange 2010. I can get the test account to send to a yahoo.com account but I cannot get it to send internally and when I send to it from an account internally I get a NDR very soon saying DNS is in a loop. I recalled seing something similiar when confguring the original setup and I believe it is because all the outbound is going through the exchange 2013 servers.

 

I tried to update the 2013 servers to act as the hybrid servers but I get some generic error early in the configuration stating:

Updating hybrid configuration failed with error ‎'Subtask Configure execution failed: Upgrading hybrid configuration from Exchange 2010... Object reference not set to an instance of an object. at Microsoft.Exchange.Management.Hybrid.UpgradeConfigurationFrom14Task.UpgradeFopeConnectors‎(ITaskContext taskContext)‎   at Microsoft.Exchange.Management.Hybrid.UpgradeConfigurationFrom14Task.Configure‎(ITaskContext taskContext)‎   at Microsoft.Exchange.Management.Hybrid.Engine.ExecuteSubStep‎(String subStepName, ITaskContext taskContext, ITask task, Func`3 substep, Func`4 createException, Boolean throwOnFalse)‎

 

Our incoming MX record points to our barracuda spam & virus firewall for both FQDN domains...

Both domains test fine using the MS autodiscover check etc..

Disync running just fine!

 

Questions:

Anyone have an idea what the error is?

Where should I be running the hybrid server from, 2010 or 2013?

Should I just open a case with MS?

 

Thanks in advace,

 

Steve

 


Viewing all articles
Browse latest Browse all 16953

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>