Hybrid Deployment - Migrating from Exchange Online to On-Premise Exchange

Hi,
I'm migrating from Exchange Online to an 2013 On-Premise Exchange.
Hybrid Deployment has been set up and configured successfully.
However, I'm encountering issues while performing a mailbox migration to the on-premise server.
It's has been stuck at validating and reflecting a MigrationTranscientException Error.
Appreciate the valuable advise and suggestions! Thanks!
Cheers!
Joshua
Error message below:
Data migrated:
Migration rate:
Error: MigrationTransientException:
The Mailbox Replication Service could not connect to the remote server because the remote server encountered an internal error. The call to ‎'https://mail.domain.com.sg/EWS/mrsproxy.svc‎' failed. Error details: The content type text/html; charset=utf-8 of
the response message does not match the content type of the binding ‎(application/soap+xml; charset=utf-8)‎. If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: ‎'<!DOCTYPE
html> <html> <head> <title>Runtime Error</title> <meta name="viewport" content="width=device-width" /> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon
} pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable
{ text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error.. --> The content type text/html; charset=utf-8
of the response message does not match the content type of the binding ‎(application/soap+xml; charset=utf-8)‎. If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were:
‎'<!DOCTYPE html> <html> <head> <title>Runtime Error</title> <meta name="viewport" content="width=device-width" /> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon
} pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable
{ text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error. --> The Mailbox Replication Service could
not connect to the remote server because the remote server encountered an internal error. The call to ‎'https://mail.domain.com.sg/EWS/mrsproxy.svc‎' failed. Error details: The content type text/html; charset=utf-8 of the response message does not match the
content type of the binding ‎(application/soap+xml; charset=utf-8)‎. If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: ‎'<!DOCTYPE html> <html> <head>
<title>Runtime Error</title> <meta name="viewport" content="width=device-width" /> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top:
-5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable
{ text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error.. --> The content type text/html; charset=utf-8
of the response message does not match the content type of the binding ‎(application/soap+xml; charset=utf-8)‎. If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were:
‎'<!DOCTYPE html> <html> <head> <title>Runtime Error</title> <meta name="viewport" content="width=device-width" /> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon
} pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable
{ text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error. --> The call to ‎'https://mail.domain.com.sg/EWS/mrsproxy.svc‎'
failed. Error details: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding ‎(application/soap+xml; charset=utf-8)‎. If using a custom encoder, be sure that the IsContentTypeSupported method is
implemented properly. The first 1024 bytes of the response were: ‎'<!DOCTYPE html> <html> <head> <title>Runtime Error</title> <meta name="viewport" content="width=device-width" /> <style> body {font-family:"Verdana";font-weight:normal;font-size:
.7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red
} H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration:
none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width: 440px; o‎'. --> The remote server returned an error:
‎(500)‎ Internal Server Error.. --> The content type text/html; charset=utf-8 of the response message does not match the content type of the binding ‎(application/soap+xml; charset=utf-8)‎. If using a custom encoder, be sure that the IsContentTypeSupported
method is implemented properly. The first 1024 bytes of the response were: ‎'<!DOCTYPE html> <html> <head> <title>Runtime Error</title> <meta name="viewport" content="width=device-width" /> <style>
body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1
{ font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt}
.marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } @media screen and ‎(max-width: 639px)‎ { pre { width:
440px; o‎'. --> The remote server returned an error: ‎(500)‎ Internal Server Error

Hello Joshywahcho ,<o:p></o:p>
First Check is the MRS proxy is enabled or not and restart the Microsoft Exchange Mailbox Replication service and
IIS on Hybrid .<o:p></o:p>
As now Microsoft has change the procedure to roll back the mailbox from O365, please follow the below mention Step<o:p></o:p>
Moved the affected user's mailbox to the Hybrid Server from Office 365 <o:p></o:p>
Connect to Exchange Online using remote PowerShell<o:p></o:p>
Ran the command
$Credentials = Get-Credential<o:p></o:p>
Ran the command
New-MoveRequest -identity <e-mail address of the affected user> -OutBound -RemoteTargetDatabase "Name of the Datbase" -RemoteHostName <Your Host Name> -RemoteCredential $Credentials -TargetDeliveryDomain <Your Target Delivery Domain><o:p></o:p>
Ran the command
Get-MoveRequest -Identity <e-mail address of the user> to check the status of mailbox move<o:p></o:p>
once the mailbox move from Office 365 to Hybrid Server was completed then initiated a Mailbox move from the Hybrid Server to On-premise server <o:p></o:p>
Mailbox was moved successfully from Hybrid Server to the On-premise server .<o:p></o:p>
checked in the On-premise server 2007 and the affected user's mailbox was showing there<o:p></o:p>

Similar Messages

Migrating from SharePoint Online to an In House SharePoint Environment

What will be the method for clients to migrate from SharePoint Online to an In House SharePoint environment if the need arises in the future. I have had clients ask me this and I do not yet have a good answer.

Hi Michael,
Right now, to migrate off of SharePoint Online, it is a manual process. You would need to copy the documents, lists, etc. all manually (suggest creating list templates that contain the data). Third party tools like those offered by Quest, Metalogix, and Casahl also work in this scenario.
However, we realize this is not ideal. We have heard several requests in this area and are now exploring options to provide an automated way to get your data off of SharePoint Online.

Exchange Online mailbox configuration without Exchange Hybrid Configuration wizard.

HI!
We have on premise exchange server 2010 sp2 deployed with domain1.com. We have registered our tenant and verified the ownership of domain1.com on our office365 tenant. We have successfully deployed EOP and configured inbound and outbound connectors
and all the mailflow is working fine. We havenot deployed directory sync server and ADFS for the deployment of EOP. Our Mx is pointed to domain1-com.mail.protection.outlook.com and all the mails are sent and received through EOP. I
want to move a user mailbox such as [email protected] to Exchange Online from on-premise exchange without configuring Dirsync and Exchange Hybrid configuration wizard. I already know the some of the limitations.
If I create a user account [email protected] on the tenant and activate the Exchange License on office365 to create the Mailbox on Exchange online.
I want to know that if I have to create any other send and receive connector or any other configuration either on office365 or exchange online if I cutover one user from our on-premise to exchange online without configuring Exchange Hybrid configuration
wizard on our on premise exchange server??
Will this effect the mailflow between onpremise and exchange online users?
Regards,
Abdullah Salam

It's not clear to me what type of migration you're trying to do. A cutover migration would be an option as long as you understand the limitations of that process. Otherwise are you looking to use a third-party migration tool or some other
mechanism?
The reason you would end up with two mailboxes is if when you assign an Exchange license to a user in the cloud without DirSync, a mailbox is provisioned for that user. You can assign a license after the mailbox is moved assuming you have a mail-enabled
user in the cloud and can do a remote move to it.
Once you manage to get the mailbox to the cloud, now you have to deal with routing which means you'll need a mail-enabled user on-premises for every mailbox in the cloud and will need to have a target address with a coexistence domain such as "@tenant.mail.onmicrosoft.com".
Likewise, Exchange Online will need a mail-enabled user for every on-premises mailbox in order to have a populated GAL and route in that direction.
For security reasons we don't to setup Dirsync and hybrid.
I hear this occasionally and remind organizations that you're putting the actual data (the stuff the credentials protect) in Microsoft's datacenters. If it's a question of trust, cloud services might not be the most appropriate solution for the
organization. The Office 365 Trust Center (http://trust.office365.com/) can provide some insight into the controls that Microsoft has in place to protect your data.
DirSync or the new AADSync can be scoped such that they only sync limited objects. From there, you have the options of Password (Hash) Sync with DirSync (not yet with AADSync) or using AD FS which leaves the authentication with your on-premises
directory.
Joseph Palarchio http://www.itworkedinthelab.com

Exchange Online Protection Standalone for Exchange 2013 On-premise

hello:
I'm about to deploy Exchange server 2013 on-premise for my company and we are going to subscribe EOP standalone. After reading the description from technet
http://technet.microsoft.com/en-us/library/jj723119(v=exchg.150).aspx , I'm confuse about how am I going to manage user.
1. Do I need to have ADFS,DirSync server ready on my local datacenter to synchronize user with EOP?
2. I just need basic spam filtering feature, will EOP work with Exchange 2013 on-premise without having ADFS & DirSync?
Thanks.

If your deployment is not hybrid then you won;t need Dirsync.
http://technet.microsoft.com/en-us/library/jj723153(v=exchg.150).aspx

Can Exchange Online Protection work with Exchange 2010 on-premise

I want to keep my current Exchange 2010 server but switch to Exchange Online Protection for anti-spam.
Is that possible?
Without doing any AD/Azure sync?

Yes to both. With directory synchronization you can have the added benefit of blocking mail to nonexistent recipients.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Migrate from Standard 2003 domain with seperate Exchange 2003 to SBS 2011 - possible? how-to?

Hi there,
I am currently planning on replacing two servers (one server 2003 standard (DC) and one server 2003 standard with exchange 2003) with a single machine running SBS 2011.
I already did several migrations SBS 2003 to SBS 2011, SBS 2008 to SBS 2011 - and I am wondering if the same can be done from 2003 Standard with separate exchange server 2003 to a single SBS 2011. Technically I can see no reason why this shouldn't work -
but so far I have been unsuccessful in finding guidelines or at least some success-stories from other users.
Did anyone do something like that? Any caveats I have to be aware of? Or is it supposed to be flawless as the SBS to SBS migrations I did so far?

Hi,
From the problem description, I understand that you would like to migrate Exchange server 2003 on Windows Server 2003 to SBS 2011.
At first, I would like to clarify one thing. Microsoft doesn’t have the official documentation towards this scenario. And Microsoft doesn’t
recommend dealing with that.
I noticed that there are two servers in your organization. One is Windows server 2003 for DC; the other one is Exchange server 2003. So it can’t
be the same as the documentation (Migrate to Windows Small Business Server 2011 Standard from Windows Small Business Server
2003).
I got your key point that you would like to know the detailed procedures (HOW TO). I suggest that you could visit the
SBSmigration.com to get further information you need. Since it’s not the Microsoft official method,
please do the test before your put it into your production environment.
Regards,
James
James Xiong
TechNet Community Support

[Exchange-Online][EWS][EWS-XML] Exchange server version "V2_22" returned for Office 365 breaks pattern - consequences?

I just notice that talking to Office365 Exchange Web Services at https://outlook.office365.com/ews/exchange.asmx I get this in my SOAP response header:
<Envelope>
<Header>
    <ServerVersionInfo MajorVersion="15" MinorVersion="0" MajorBuildNumber="1049" MinorBuildNumber="23" Version="V2_22"/>
</Header>
This means that the Version 'schema version' property (http://msdn.microsoft.com/en-us/library/exchangewebservices.serverversioninfo.version%28v=exchg.150%29.aspx) now breaks the pattern of versions that we had earlier: Exchange2007, Exchange2007_SP1, Exchange2010,
Exchange2010_SP1, Exchange2010_SP2, Exchange2013
In the schema files I found through Google (searching for <xs:simpleType name="ExchangeVersionType">) I could not find anything later than <xs:enumeration value="Exchange2013"/> (e.g. at http://msdn.microsoft.com/en-us/library/ee237685%28v=exchg.80%29.aspx)
If I do a SOAP request with this "V2_22" string, I still get valid answers.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:mes="http://schemas.microsoft.com/exchange/services/2006/messages">
   <soapenv:Header>
      <typ:RequestServerVersion Version="V2_22"/>
   </soapenv:Header>
But it now looks as if the returned Version is no longer a reliable way to determine the Exchange server version. If V2_22 is not documented anywhere, who says it will not suddenly change to V2_23 tomorrow?
Question: Does this mean I will now have to change my version detection code to look at MajorVersion and then maintain a cross reference between MajorVersion and ExchangeVersionType **myself**? That is horrible: another dependency to maintain
is another potential code break.
As an aside: Note that the "Exchange Server Updates: build numbers and release dates" at http://technet.microsoft.com/en-us/library/hh135098%28v=exchg.150%29.aspx is no longer up to date, it does not mention the 15.0.1049.23 that my XML just returned

What really matters in EWS is the SchemaVersion as that will tell you what operations you can and can't use. From 2010 on you can use AutoDiscover to find what SchemaVersions are supported which is the best way to do version detection. eg
AutodiscoverService adAutoDiscoverService = new AutodiscoverService(ExchangeVersion.Exchange2010);
adAutoDiscoverService.Credentials = ncCred;
adAutoDiscoverService.EnableScpLookup = false;
adAutoDiscoverService.RedirectionUrlValidationCallback = adAutoDiscoCallBack;
adAutoDiscoverService.PreAuthenticate = true;
GetUserSettingsResponse adResponse = adAutoDiscoverService.GetUserSettings("[email protected]", (new UserSettingName[1] { UserSettingName.EwsSupportedSchemas }));
if (adResponse.Settings.Count >= 1)
String schemas = (String)adResponse.Settings[UserSettingName.EwsSupportedSchemas];
I would be careful using the Major build going forward if you have a look at the requests in OWA in Office365 you'll see they are using version 16 in cookies etc
Cheers
Glen

Migrate Sharepoint 2013 from office 365 to on premise

The company management decide to move SharePoint 2013 from Office 365 to on premise. Are there any instructions or step to achieve this, or any recommended third party tools? Thanks
Yee

i think your best bet is 3rd party tool, their are alot of 3rd parties which support this migration. check the below post.
http://social.technet.microsoft.com/Forums/sharepoint/en-US/d348f3a0-345f-4085-b72f-f51a31659485/migrate-from-sharepoint-online-to-on-premise-in-2013?forum=sharepointgeneral
check this blog as well:
http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=369
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Preparing Lab for Exchange hybrid deployment

Dear All,
I would like to practice Exchange 2013 with office 365 lab environment(Hybrid deployment). I need
to prepare this lab setup without having internet connection.
Note :
Please find the below Hyper V servers which i am planning to use for hybrid deployment:
Onpremise servers:
1 Dc
1 Exch 2013
2 Adfs server
2 Adfs Proxy server
1 DRSync server & 1 TMG server
I need to create a Virtual Exchange online office 365 domain to make a hybrid connection with the onpremise servers.
How to acheive this setup.
Kindly Advise
Regards
kamparth

Follow the Exchange server deployment assistant(reference is mentioned above) that is available from Microsoft team and would be an appropriate approach for you.
Meanwhile, you may also walk through this another informative article that covers all the required aspects and provides step-wise instructions to accomplish this job :
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Moreover, if you are still concerned about the data security, you may consider on this automated solution (http://www.exchangemailboxmigration.com/) that could be an appropriate solution to get this
job done in a hassle-free manner without having any interruption.

Exchange 2013 Certificates for Hybrid Deployment Clarification

I have an Exchange 2013 servers (CAS and Mailbox on separate server) which I wanted to setup for Hybrid deployment. I already have a certificate acquired from 3rd party with 3 names (mail, autodiscover and owa). the certificate was installed in the
CAS server. As per the hybrid deployment documentation I need also to install a certificate in the mailbox server, questions:
1. Can I use the same certificate for installation in the mailbox server?
2. Can I also use the same certificate in the Hybrid Configuration wizard for the "certificate to use with securing the hybrid mail transport"?
3. Do I need to include the primary smtp domain (xxxxx.com) in the certificate since current configuration points to the mail.xxx.com as the certificate common name?

Hi,
Here are my answers you can refer to:
1. It depends.
The certificate used for hybrid secure mail transport must be installed on all on-premises Exchange 2013 Mailbox and Client Access servers.
If you're configuring a hybrid deployment in an organization that has Exchange servers deployed in multiple Active Directory forests, you must use a separate third-party CA certificate for each Active Directory forest.
2. Yes. But we recommend that you use a dedicated third-party certificate for any optional AD FS server, another certificate for the Exchange services for your hybrid deployment, and if needed, another certificate on your Exchange servers for other needed
services or features.
3. Yes. Here are the minimum suggested FQDNs that should be included on certificates: domain.com, autodiscover.domain.com, edge.domain.com
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/hh563848(v=exchg.150).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 Hybrid Deployment issues.

Hello.
i have an issue when configuring Exchange hybrid deployment in my environment.
when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
mail will can be sent out and will flow between internal users.
when i check the message trace on 365 the emails were failing with the following error.
Users were also getting a bounce back saying
Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
Any Suggestions on what could be caused
many thanks

Hello.
i have an issue when configuring Exchange hybrid deployment in my environment.
when i complete the Exchange hybrid wizard and OAuth is finished our exchange environment will not receive emails from the "internet" as in senders outside the company.
mail will can be sent out and will flow between internal users.
when i check the message trace on 365 the emails were failing with the following error.
Users were also getting a bounce back saying
Diagnostic-Code: smtp;550 5.4.1 [[email protected]]: Recipient address rejected: Access denied
i wondered if it had anything to do with the MX record on our public DNS, i changed this to the one recommended by O365 domain DNS assistant, but this made no odds,
it looks like it could be a receive connector issue however i am new to exchange so i am still learning.
the only way to fix the issue was to run Remove-Hybridconfiguration on the Exchange 2013 server, when this finished and few moments had passed mail began being received from the internal again.
Any Suggestions on what could be caused
many thanks
Make sure the accepted SMTP domains in the Office 365 EAC are set to Internal Relay rather then Authoritative.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Decommissioning Hybrid Deployment

Hi there,
We are currently running Exchange 2010 and an Exchange 2013 server deployed in a Hybrid set-up with all of our users now migrated to Office 365.
I plan to decommission both Exchange servers but after reading this article: http://blogs.technet.com/b/exchange/archive/2012/12/05/decommissioning-your-exchange-2010-servers-in-a-hybrid-deployment.aspx it recommends keeping one Exchange server on-premise
or it will have 'adverse effects'.
What are these adverse effects and why should I need to keep hosting an on-premise server when it will not be doing anything?
Thanks
Ryan

After speaking with O365 support they have advised that the 'adverse effect' is that you can no longer update certain mail attributes for AD users once the last server has been decommissioned.
For example you would need to use ADSI edit to add a proxy address, which is unsupported.
Decommissioning your Exchange 2010 servers in a Hybrid Deployment
http://blogs.technet.com/b/exchange/archive/2012/12/05/decommissioning-your-exchange-2010-servers-in-a-hybrid-deployment.aspx
Mailbox Management
Organizations that have configured a hybrid deployment for mailbox management and hybrid feature support have also configured Office 365 Active Directory synchronization (DirSync) for user and identity
management. For organizations intending on keeping DirSync in place and continuing to manage user accounts from the on-premises organization, we recommend not removing the last Exchange 2010 server from the on-premises organization.
If the last Exchange server is removed, you cannot make changes to the mailbox object in Exchange Online because the source of authority is defined as on-premises. The
source of authority refers to the location where Active Directory directory service objects, such as users and groups, are mastered (an original source that defines copies of an object) in a hybrid deployment. If you
needed to edit most mailbox settings, you would have to be sure the Active Directory schema was extended on-premises and use unsupported tools such as Active Directory Service Interfaces Editor (ADSI Edit) for common administrative tasks. For example,
adding a proxy address or putting a mailbox on litigation hold when there isn’t an Exchange Management Console (EMC) or Exchange Management Shell (Shell) on-premises becomes difficult and these simple (and other more complex) tasks cannot be done in a supported
way.
Note: A hybrid deployment is not required in order to manage Exchange objects from an on-premises organization. You can effectively manage Exchange objects with an on-premises Exchange server even
if you do not have an organization relationship, Federation Trust, and third-party certificate in place. This Exchange server gives you a supported method for creating and managing your Exchange recipient objects. It is recommended to use Exchange Server 2010
for management tasks since this will give you the option to create objects such as remote mailboxes with the New-RemoteMailbox cmdlet. The server role needed is at least a Client Access Server (CAS) role, for management tools to work properly.

Hybrid Deployment Fails

I have been trying to set up a Exchange 2010 / Office 365 hybrid configuration for a couple of days now. The deployment fails on the configuration of the mail flow. Inbound and outbound mail connectors are created both in the on-premises server and the O365
server.
I have included the full log below.
[8/25/2014 23:25:27] INFO:Opening runspace to http://te-exc/powershell?serializationLevel=Full
[8/25/2014 23:25:28] INFO:Successfully connected to On-Premises
[8/25/2014 23:25:28] INFO:Opening runspace to https://ps.outlook.com/powershell-liveid/powershell.htm?serializationLevel=Full;clientApplication=EMC;ExchClientVer=14.3.123.4
[8/25/2014 23:25:40] INFO:Successfully connected to Tenant
[8/25/2014 23:25:40] INFO:Executing Task: Check Prerequisites
[8/25/2014 23:25:40] INFO:Check Prerequisites state
[8/25/2014 23:25:40] INFO:Running command: Get-AcceptedDomain
[8/25/2014 23:25:40] INFO:Cmdlet: Get-AcceptedDomain --Start Time: 8/25/2014 4:25:40 PM.
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --End Time: 8/25/2014 4:25:42 PM.
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --Processing Time: 1953.1.
[8/25/2014 23:25:42] INFO:Running command: Get-AcceptedDomain
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --Start Time: 8/25/2014 4:25:42 PM.
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --End Time: 8/25/2014 4:25:42 PM.
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --Processing Time: 468.7445.
[8/25/2014 23:25:42] INFO:Running command: Get-AcceptedDomain
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --Start Time: 8/25/2014 4:25:42 PM.
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --End Time: 8/25/2014 4:25:42 PM.
[8/25/2014 23:25:42] INFO:Cmdlet: Get-AcceptedDomain --Processing Time: 78.5231.
[8/25/2014 23:25:42] INFO:Running command: Get-OrganizationRelationship
[8/25/2014 23:25:42] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 8/25/2014 4:25:42 PM.
[8/25/2014 23:25:43] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 8/25/2014 4:25:43 PM.
[8/25/2014 23:25:43] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 46.9032.
[8/25/2014 23:25:43] INFO:Running command: Get-OrganizationRelationship
[8/25/2014 23:25:43] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 8/25/2014 4:25:43 PM.
[8/25/2014 23:25:43] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 8/25/2014 4:25:43 PM.
[8/25/2014 23:25:43] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 374.9928.
[8/25/2014 23:25:43] INFO:Running command: Get-ExchangeServer -Identity 'TE-EXC'
[8/25/2014 23:25:43] INFO:Cmdlet: Get-ExchangeServer --Start Time: 8/25/2014 4:25:43 PM.
[8/25/2014 23:25:43] INFO:Cmdlet: Get-ExchangeServer --End Time: 8/25/2014 4:25:43 PM.
[8/25/2014 23:25:43] INFO:Cmdlet: Get-ExchangeServer --Processing Time: 78.1256.
[8/25/2014 23:25:43] INFO:Running command: Get-WebServicesVirtualDirectory -Server 'TE-EXC'
[8/25/2014 23:25:43] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Start Time: 8/25/2014 4:25:43 PM.
[8/25/2014 23:25:44] INFO:Cmdlet: Get-WebServicesVirtualDirectory --End Time: 8/25/2014 4:25:44 PM.
[8/25/2014 23:25:44] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Processing Time: 1062.4841.
[8/25/2014 23:25:44] INFO:Running command: Get-ExchangeCertificate -Server 'TE-EXC'
[8/25/2014 23:25:44] INFO:Cmdlet: Get-ExchangeCertificate --Start Time: 8/25/2014 4:25:44 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-ExchangeCertificate --End Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-ExchangeCertificate --Processing Time: 749.9927.
[8/25/2014 23:25:45] INFO:Needs Configuration state
[8/25/2014 23:25:45] INFO:Configuration not required
[8/25/2014 23:25:45] INFO:Executing Task: Configure Legacy Exchange Support
[8/25/2014 23:25:45] INFO:Check Prerequisites state
[8/25/2014 23:25:45] INFO:Needs Configuration state
[8/25/2014 23:25:45] INFO:Running command: Get-ExchangeServer
[8/25/2014 23:25:45] INFO:Cmdlet: Get-ExchangeServer --Start Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-ExchangeServer --End Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-ExchangeServer --Processing Time: 93.7467.
[8/25/2014 23:25:45] INFO:Running command: Get-PublicFolderDatabase -Server 'TE-EXC'
[8/25/2014 23:25:45] INFO:Cmdlet: Get-PublicFolderDatabase --Start Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-PublicFolderDatabase --End Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-PublicFolderDatabase --Processing Time: 109.3716.
[8/25/2014 23:25:45] INFO:Configuration state
[8/25/2014 23:25:45] INFO:Calling Install-FreeBusyFolder
[8/25/2014 23:25:45] INFO:Install-FreeBusyFolder completed
[8/25/2014 23:25:45] INFO:Verify Configuration state
[8/25/2014 23:25:45] INFO:Executing Task: Configure Recipient Settings
[8/25/2014 23:25:45] INFO:Check Prerequisites state
[8/25/2014 23:25:45] INFO:Needs Configuration state
[8/25/2014 23:25:45] INFO:Running command: Get-RemoteDomain
[8/25/2014 23:25:45] INFO:Cmdlet: Get-RemoteDomain --Start Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-RemoteDomain --End Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-RemoteDomain --Processing Time: 31.2192.
[8/25/2014 23:25:45] INFO:Running command: Get-EmailAddressPolicy
[8/25/2014 23:25:45] INFO:Cmdlet: Get-EmailAddressPolicy --Start Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-EmailAddressPolicy --End Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-EmailAddressPolicy --Processing Time: 46.8972.
[8/25/2014 23:25:45] INFO:Configuration not required
[8/25/2014 23:25:45] INFO:Executing Task: Creating Organization Relationships.
[8/25/2014 23:25:45] INFO:Check Prerequisites state
[8/25/2014 23:25:45] INFO:Running command: Get-FederationTrust
[8/25/2014 23:25:45] INFO:Cmdlet: Get-FederationTrust --Start Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-FederationTrust --End Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-FederationTrust --Processing Time: 31.2475.
[8/25/2014 23:25:45] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''
[8/25/2014 23:25:45] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:45] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 46.8767.
[8/25/2014 23:25:45] INFO:Getting Value 'DefaultDomain' from '' with 'Get-FederatedOrganizationIdentifier'
[8/25/2014 23:25:45] INFO:Running command: Get-FederatedOrganizationIdentifier
[8/25/2014 23:25:45] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 8/25/2014 4:25:45 PM.
[8/25/2014 23:25:46] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 8/25/2014 4:25:46 PM.
[8/25/2014 23:25:46] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 574.8827.
[8/25/2014 23:25:46] INFO:Needs Configuration state
[8/25/2014 23:25:46] INFO:Configuration state
[8/25/2014 23:25:46] INFO:Running command: Enable-OrganizationCustomization
[8/25/2014 23:25:46] INFO:Cmdlet: Enable-OrganizationCustomization --Start Time: 8/25/2014 4:25:46 PM.
[8/25/2014 23:26:7] INFO:Cmdlet: Enable-OrganizationCustomization --End Time: 8/25/2014 4:26:07 PM.
[8/25/2014 23:26:7] INFO:Cmdlet: Enable-OrganizationCustomization --Processing Time: 21352.4035.
[8/25/2014 23:26:7] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''
[8/25/2014 23:26:7] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 8/25/2014 4:26:07 PM.
[8/25/2014 23:26:18] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 8/25/2014 4:26:18 PM.
[8/25/2014 23:26:18] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 10359.9778.
[8/25/2014 23:26:18] INFO:Running command: Get-FederationTrust -Identity 'Microsoft Federation Gateway'
[8/25/2014 23:26:18] INFO:Cmdlet: Get-FederationTrust --Start Time: 8/25/2014 4:26:18 PM.
[8/25/2014 23:26:18] INFO:Cmdlet: Get-FederationTrust --End Time: 8/25/2014 4:26:18 PM.
[8/25/2014 23:26:18] INFO:Cmdlet: Get-FederationTrust --Processing Time: 62.5539.
[8/25/2014 23:26:18] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''
[8/25/2014 23:26:18] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 8/25/2014 4:26:18 PM.
[8/25/2014 23:26:19] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 8/25/2014 4:26:19 PM.
[8/25/2014 23:26:19] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 1249.9469.
[8/25/2014 23:26:19] INFO:Running command: Get-FederationTrust -Identity 'MicrosoftOnline'
[8/25/2014 23:26:19] INFO:Cmdlet: Get-FederationTrust --Start Time: 8/25/2014 4:26:19 PM.
[8/25/2014 23:26:20] INFO:Cmdlet: Get-FederationTrust --End Time: 8/25/2014 4:26:20 PM.
[8/25/2014 23:26:20] INFO:Cmdlet: Get-FederationTrust --Processing Time: 453.119.
[8/25/2014 23:26:20] INFO:Running command: Get-FederationInformation -DomainName 'x.mail.onmicrosoft.com' -BypassAdditionalDomainValidation 'True'
[8/25/2014 23:26:20] INFO:Cmdlet: Get-FederationInformation --Start Time: 8/25/2014 4:26:20 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: Get-FederationInformation --End Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: Get-FederationInformation --Processing Time: 7109.3829.
[8/25/2014 23:26:27] INFO:Running command: Remove-OrganizationRelationship -Identity 'On Premises to Exchange Online Organization Relationship' -Confirm 'False'
[8/25/2014 23:26:27] INFO:Cmdlet: Remove-OrganizationRelationship --Start Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: Remove-OrganizationRelationship --End Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: Remove-OrganizationRelationship --Processing Time: 93.748.
[8/25/2014 23:26:27] INFO:Running command: New-OrganizationRelationship -Name 'On Premises to Exchange Online Organization Relationship' -TargetApplicationUri 'outlook.com' -TargetAutodiscoverEpr 'https://pod51035.outlook.com/autodiscover/autodiscover.svc/WSSecurity' -Enabled 'True' -DomainNames 'System.String[]'
[8/25/2014 23:26:27] INFO:Cmdlet: New-OrganizationRelationship --Start Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: New-OrganizationRelationship --End Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: New-OrganizationRelationship --Processing Time: 109.3761.
[8/25/2014 23:26:27] INFO:Running command: Get-OrganizationRelationship
[8/25/2014 23:26:27] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:27] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 31.252.
[8/25/2014 23:26:27] INFO:Running command: Get-FederationInformation -DomainName 'te.trybct.com' -BypassAdditionalDomainValidation 'True'
[8/25/2014 23:26:27] INFO:Cmdlet: Get-FederationInformation --Start Time: 8/25/2014 4:26:27 PM.
[8/25/2014 23:26:28] INFO:Cmdlet: Get-FederationInformation --End Time: 8/25/2014 4:26:28 PM.
[8/25/2014 23:26:28] INFO:Cmdlet: Get-FederationInformation --Processing Time: 1374.9915.
[8/25/2014 23:26:28] INFO:Running command: Remove-OrganizationRelationship -Identity 'Exchange Online to on premises Organization Relationship' -Confirm 'False'
[8/25/2014 23:26:28] INFO:Cmdlet: Remove-OrganizationRelationship --Start Time: 8/25/2014 4:26:28 PM.
[8/25/2014 23:26:29] INFO:Cmdlet: Remove-OrganizationRelationship --End Time: 8/25/2014 4:26:29 PM.
[8/25/2014 23:26:29] INFO:Cmdlet: Remove-OrganizationRelationship --Processing Time: 1234.3802.
[8/25/2014 23:26:29] INFO:Running command: New-OrganizationRelationship -Name 'Exchange Online to on premises Organization Relationship' -TargetApplicationUri 'FYDIBOHF25SPDLT.te.trybct.com' -TargetAutodiscoverEpr 'https://te.trybct.com/autodiscover/autodiscover.svc/WSSecurity' -Enabled 'True' -DomainNames 'System.String[]'
[8/25/2014 23:26:29] INFO:Cmdlet: New-OrganizationRelationship --Start Time: 8/25/2014 4:26:29 PM.
[8/25/2014 23:26:30] INFO:Cmdlet: New-OrganizationRelationship --End Time: 8/25/2014 4:26:30 PM.
[8/25/2014 23:26:30] INFO:Cmdlet: New-OrganizationRelationship --Processing Time: 984.373.
[8/25/2014 23:26:30] INFO:Running command: Get-OrganizationRelationship
[8/25/2014 23:26:30] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 8/25/2014 4:26:30 PM.
[8/25/2014 23:26:31] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 8/25/2014 4:26:31 PM.
[8/25/2014 23:26:31] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 468.7504.
[8/25/2014 23:26:31] INFO:Verify Configuration state
[8/25/2014 23:26:31] INFO:Running command: Get-FederationTrust
[8/25/2014 23:26:31] INFO:Cmdlet: Get-FederationTrust --Start Time: 8/25/2014 4:26:31 PM.
[8/25/2014 23:26:31] INFO:Cmdlet: Get-FederationTrust --End Time: 8/25/2014 4:26:31 PM.
[8/25/2014 23:26:31] INFO:Cmdlet: Get-FederationTrust --Processing Time: 46.8759.
[8/25/2014 23:26:31] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''
[8/25/2014 23:26:31] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 8/25/2014 4:26:31 PM.
[8/25/2014 23:26:31] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 8/25/2014 4:26:31 PM.
[8/25/2014 23:26:31] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 31.2538.
[8/25/2014 23:26:31] INFO:Getting Value 'DefaultDomain' from '' with 'Get-FederatedOrganizationIdentifier'
[8/25/2014 23:26:31] INFO:Running command: Get-FederatedOrganizationIdentifier
[8/25/2014 23:26:31] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 8/25/2014 4:26:31 PM.
[8/25/2014 23:26:32] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 8/25/2014 4:26:32 PM.
[8/25/2014 23:26:32] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 580.8766.
[8/25/2014 23:26:32] INFO:Executing Task: Configuring organization relationship settings.
[8/25/2014 23:26:32] INFO:Check Prerequisites state
[8/25/2014 23:26:32] INFO:Running command: Get-FederatedOrganizationIdentifier -IncludeExtendedDomainInfo ''
[8/25/2014 23:26:32] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Start Time: 8/25/2014 4:26:32 PM.
[8/25/2014 23:26:32] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --End Time: 8/25/2014 4:26:32 PM.
[8/25/2014 23:26:32] INFO:Cmdlet: Get-FederatedOrganizationIdentifier --Processing Time: 578.1212.
[8/25/2014 23:26:32] INFO:Needs Configuration state
[8/25/2014 23:26:32] INFO:Configuration state
[8/25/2014 23:26:32] INFO:Running command: Get-WebServicesVirtualDirectory -Server 'TE-EXC'
[8/25/2014 23:26:32] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Start Time: 8/25/2014 4:26:32 PM.
[8/25/2014 23:26:33] INFO:Cmdlet: Get-WebServicesVirtualDirectory --End Time: 8/25/2014 4:26:33 PM.
[8/25/2014 23:26:33] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Processing Time: 1062.5009.
[8/25/2014 23:26:33] INFO:Running command: Set-WebServicesVirtualDirectory -Identity 'TE-EXC\EWS (Default Web Site)' -MRSProxyEnabled 'True'
[8/25/2014 23:26:33] INFO:Cmdlet: Set-WebServicesVirtualDirectory --Start Time: 8/25/2014 4:26:33 PM.
[8/25/2014 23:26:36] INFO:Cmdlet: Set-WebServicesVirtualDirectory --End Time: 8/25/2014 4:26:36 PM.
[8/25/2014 23:26:36] INFO:Cmdlet: Set-WebServicesVirtualDirectory --Processing Time: 2749.9991.
[8/25/2014 23:26:36] INFO:Running command: Set-OrganizationRelationship -MailboxMoveEnabled 'True' -FreeBusyAccessEnabled 'True' -FreeBusyAccessLevel 'LimitedDetails' -ArchiveAccessEnabled 'True' -MailTipsAccessEnabled 'True' -MailTipsAccessLevel 'All' -DeliveryReportEnabled 'True' -TargetOwaURL 'http://outlook.com/owa/x.onmicrosoft.com' -Identity 'On Premises to Exchange Online Organization Relationship'
[8/25/2014 23:26:36] INFO:Cmdlet: Set-OrganizationRelationship --Start Time: 8/25/2014 4:26:36 PM.
[8/25/2014 23:26:36] INFO:Cmdlet: Set-OrganizationRelationship --End Time: 8/25/2014 4:26:36 PM.
[8/25/2014 23:26:36] INFO:Cmdlet: Set-OrganizationRelationship --Processing Time: 62.4992.
[8/25/2014 23:26:36] INFO:Running command: Get-OrganizationRelationship
[8/25/2014 23:26:36] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 8/25/2014 4:26:36 PM.
[8/25/2014 23:26:36] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 8/25/2014 4:26:36 PM.
[8/25/2014 23:26:36] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 31.2534.
[8/25/2014 23:26:36] INFO:Running command: Set-OrganizationRelationship -FreeBusyAccessEnabled 'True' -FreeBusyAccessLevel 'LimitedDetails' -MailTipsAccessEnabled 'True' -MailTipsAccessLevel 'All' -DeliveryReportEnabled 'True' -Identity 'Exchange Online to on premises Organization Relationship'
[8/25/2014 23:26:36] INFO:Cmdlet: Set-OrganizationRelationship --Start Time: 8/25/2014 4:26:36 PM.
[8/25/2014 23:26:37] INFO:Cmdlet: Set-OrganizationRelationship --End Time: 8/25/2014 4:26:37 PM.
[8/25/2014 23:26:37] INFO:Cmdlet: Set-OrganizationRelationship --Processing Time: 593.7489.
[8/25/2014 23:26:37] INFO:Running command: Get-OrganizationRelationship
[8/25/2014 23:26:37] INFO:Cmdlet: Get-OrganizationRelationship --Start Time: 8/25/2014 4:26:37 PM.
[8/25/2014 23:26:38] INFO:Cmdlet: Get-OrganizationRelationship --End Time: 8/25/2014 4:26:38 PM.
[8/25/2014 23:26:38] INFO:Cmdlet: Get-OrganizationRelationship --Processing Time: 890.625.
[8/25/2014 23:26:38] INFO:Running command: Get-AvailabilityAddressSpace
[8/25/2014 23:26:38] INFO:Cmdlet: Get-AvailabilityAddressSpace --Start Time: 8/25/2014 4:26:38 PM.
[8/25/2014 23:26:38] INFO:Cmdlet: Get-AvailabilityAddressSpace --End Time: 8/25/2014 4:26:38 PM.
[8/25/2014 23:26:38] INFO:Cmdlet: Get-AvailabilityAddressSpace --Processing Time: 31.2458.
[8/25/2014 23:26:38] INFO:Running command: Get-WebServicesVirtualDirectory -Server 'TE-EXC'
[8/25/2014 23:26:38] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Start Time: 8/25/2014 4:26:38 PM.
[8/25/2014 23:26:39] INFO:Cmdlet: Get-WebServicesVirtualDirectory --End Time: 8/25/2014 4:26:39 PM.
[8/25/2014 23:26:39] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Processing Time: 1062.4996.
[8/25/2014 23:26:39] INFO:Verify Configuration state
[8/25/2014 23:26:39] INFO:Executing Task: Configure Mail Flow
[8/25/2014 23:26:39] INFO:Check Prerequisites state
[8/25/2014 23:26:39] INFO:Running command: Get-HybridMailflowDatacenterIPs
[8/25/2014 23:26:39] INFO:Cmdlet: Get-HybridMailflowDatacenterIPs --Start Time: 8/25/2014 4:26:39 PM.
[8/25/2014 23:26:43] INFO:Cmdlet: Get-HybridMailflowDatacenterIPs --End Time: 8/25/2014 4:26:43 PM.
[8/25/2014 23:26:43] INFO:Cmdlet: Get-HybridMailflowDatacenterIPs --Processing Time: 4056.2607.
[8/25/2014 23:26:43] INFO:Running command: Get-ExchangeCertificate -Thumbprint '868584A2D4A8F99C70D3A899FABE3915267A12F0' -Server 'TE-EXC'
[8/25/2014 23:26:43] INFO:Cmdlet: Get-ExchangeCertificate --Start Time: 8/25/2014 4:26:43 PM.
[8/25/2014 23:26:43] INFO:Cmdlet: Get-ExchangeCertificate --End Time: 8/25/2014 4:26:43 PM.
[8/25/2014 23:26:43] INFO:Cmdlet: Get-ExchangeCertificate --Processing Time: 703.1244.
[8/25/2014 23:26:43] INFO:Needs Configuration state
[8/25/2014 23:26:43] INFO:Running command: Get-SendConnector
[8/25/2014 23:26:43] INFO:Cmdlet: Get-SendConnector --Start Time: 8/25/2014 4:26:43 PM.
[8/25/2014 23:26:43] INFO:Cmdlet: Get-SendConnector --End Time: 8/25/2014 4:26:43 PM.
[8/25/2014 23:26:43] INFO:Cmdlet: Get-SendConnector --Processing Time: 46.8753.
[8/25/2014 23:26:44] INFO:Running command: Get-ReceiveConnector -Server 'TE-EXC'
[8/25/2014 23:26:44] INFO:Cmdlet: Get-ReceiveConnector --Start Time: 8/25/2014 4:26:44 PM.
[8/25/2014 23:26:44] INFO:Cmdlet: Get-ReceiveConnector --End Time: 8/25/2014 4:26:44 PM.
[8/25/2014 23:26:44] INFO:Cmdlet: Get-ReceiveConnector --Processing Time: 93.7516.
[8/25/2014 23:26:44] INFO:Running command: Get-RemoteDomain
[8/25/2014 23:26:44] INFO:Cmdlet: Get-RemoteDomain --Start Time: 8/25/2014 4:26:44 PM.
[8/25/2014 23:26:44] INFO:Cmdlet: Get-RemoteDomain --End Time: 8/25/2014 4:26:44 PM.
[8/25/2014 23:26:44] INFO:Cmdlet: Get-RemoteDomain --Processing Time: 46.8719.
[8/25/2014 23:26:44] INFO:Running command: Get-RemoteDomain
[8/25/2014 23:26:44] INFO:Cmdlet: Get-RemoteDomain --Start Time: 8/25/2014 4:26:44 PM.
[8/25/2014 23:26:44] INFO:Cmdlet: Get-RemoteDomain --End Time: 8/25/2014 4:26:44 PM.
[8/25/2014 23:26:44] INFO:Cmdlet: Get-RemoteDomain --Processing Time: 499.9994.
[8/25/2014 23:26:44] INFO:Running command: Get-HybridMailflow
[8/25/2014 23:26:44] INFO:Cmdlet: Get-HybridMailflow --Start Time: 8/25/2014 4:26:44 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: Get-HybridMailflow --End Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: Get-HybridMailflow --Processing Time: 656.2517.
[8/25/2014 23:26:45] INFO:Configuration state
[8/25/2014 23:26:45] INFO:Running command: Get-SendConnector
[8/25/2014 23:26:45] INFO:Cmdlet: Get-SendConnector --Start Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: Get-SendConnector --End Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: Get-SendConnector --Processing Time: 46.8793.
[8/25/2014 23:26:45] INFO:Running command: New-SendConnector -Name 'Outbound to Office 365' -AddressSpaces 'System.String[]' -SourceTransportServers 'System.String[]' -Fqdn 'te.trybct.com' -RequireTLS 'True' -TLSAuthLevel 'DomainValidation' -TLSDomain 'outlook.com' -ErrorPolicies 'DowngradeAuthFailures'
[8/25/2014 23:26:45] INFO:Cmdlet: New-SendConnector --Start Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: New-SendConnector --End Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: New-SendConnector --Processing Time: 218.7463.
[8/25/2014 23:26:45] INFO:Running command: Get-ReceiveConnector -Server 'TE-EXC'
[8/25/2014 23:26:45] INFO:Cmdlet: Get-ReceiveConnector --Start Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: Get-ReceiveConnector --End Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:45] INFO:Cmdlet: Get-ReceiveConnector --Processing Time: 93.7522.
[8/25/2014 23:26:45] INFO:Running command: New-ReceiveConnector -Server 'TE-EXC' -Name 'Inbound from Office 365' -RequireTLS 'True' -PermissionGroups 'AnonymousUsers' -Fqdn 'te.trybct.com' -TLSDomainCapabilities 'outlook.com:AcceptOorgProtocol' -Bindings 'System.String[]' -RemoteIPRanges 'System.String[]' -AuthMechanism 'Tls'
[8/25/2014 23:26:45] INFO:Cmdlet: New-ReceiveConnector --Start Time: 8/25/2014 4:26:45 PM.
[8/25/2014 23:26:46] INFO:Cmdlet: New-ReceiveConnector --End Time: 8/25/2014 4:26:46 PM.
[8/25/2014 23:26:46] INFO:Cmdlet: New-ReceiveConnector --Processing Time: 562.5053.
[8/25/2014 23:26:46] INFO:Running command: Set-HybridMailflow -SecureMailEnabled 'True' -CentralizedTransportEnabled 'False' -OnPremisesFQDN 'te.trybct.com' -CertificateSubject 'te.trybct.com' -InboundIPs 'System.String[]' -OutboundDomains 'System.String[]'
[8/25/2014 23:26:46] INFO:Cmdlet: Set-HybridMailflow --Start Time: 8/25/2014 4:26:46 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Set-HybridMailflow --End Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Set-HybridMailflow --Processing Time: 4371.1325.
[8/25/2014 23:26:50] INFO:Verify Configuration state
[8/25/2014 23:26:50] INFO:Running command: Get-SendConnector
[8/25/2014 23:26:50] INFO:Cmdlet: Get-SendConnector --Start Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Get-SendConnector --End Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Get-SendConnector --Processing Time: 46.8812.
[8/25/2014 23:26:50] INFO:Running command: Get-ReceiveConnector -Server 'TE-EXC'
[8/25/2014 23:26:50] INFO:Cmdlet: Get-ReceiveConnector --Start Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Get-ReceiveConnector --End Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Get-ReceiveConnector --Processing Time: 124.9969.
[8/25/2014 23:26:50] INFO:Running command: Get-RemoteDomain
[8/25/2014 23:26:50] INFO:Cmdlet: Get-RemoteDomain --Start Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Get-RemoteDomain --End Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:50] INFO:Cmdlet: Get-RemoteDomain --Processing Time: 46.8765.
[8/25/2014 23:26:50] INFO:Running command: Get-RemoteDomain
[8/25/2014 23:26:50] INFO:Cmdlet: Get-RemoteDomain --Start Time: 8/25/2014 4:26:50 PM.
[8/25/2014 23:26:51] INFO:Cmdlet: Get-RemoteDomain --End Time: 8/25/2014 4:26:51 PM.
[8/25/2014 23:26:51] INFO:Cmdlet: Get-RemoteDomain --Processing Time: 343.7434.
[8/25/2014 23:26:51] INFO:Running command: Get-HybridMailflow
[8/25/2014 23:26:51] INFO:Cmdlet: Get-HybridMailflow --Start Time: 8/25/2014 4:26:51 PM.
[8/25/2014 23:26:52] INFO:Cmdlet: Get-HybridMailflow --End Time: 8/25/2014 4:26:52 PM.
[8/25/2014 23:26:52] INFO:Cmdlet: Get-HybridMailflow --Processing Time: 843.7522.
[8/25/2014 23:26:52] INFO:Disconnected from On-Premises session
[8/25/2014 23:26:52] INFO:Disconnected from Tenant session
[8/25/2014 23:26:52] ERROR:Updating hybrid configuration failed with error 'Subtask ValidateConfiguration execution failed: Configure Mail Flow
at Microsoft.Exchange.Management.Hybrid.Engine.ExecuteTask(ITask taskBase, ITaskContext taskContext)
Additional troubleshooting information is available in the Update-HybridConfiguration log file located at C:\Program Files\Microsoft\Exchange Server\V14\Logging\Update-HybridConfiguration\HybridConfiguration_8_25_2014_23_25_27_635446059279694192.log.

Hi,
The above issue occurs if hybrid mail flow connectors already exist in the on-premises environment and in Exchange Online. You need to remove the hybrid mail flow connectors from on-premises environment and from Exchange Online at first. And then continue
the Hybrid Configuration Wizard again.
For more information, please refer to the above kb Amit provided.
Hope this can be helpful.
Best regards,
Amy Wang
TechNet Community Support

Lync 2013 On Premises integration with Exchange Online Unified Messaging

I am working on deploying Lync 2013 Server on premises and integrating it with Exchange Online. We do not use Exchange on premises.
My question is how to integrate with Unified Messaging specifically. Other functions like Calendar, call logs seem to be working fine.
There are many guides online on how to do this, and I have read many and attempted to follow with no luck. All seem to assume that UM has already been deployed on prem which I don't have. Is this possible to integrate Lync with Exchange Online without having
and Exchange deployment on premises first.
Another source of confusion is the Office Voice Access number and how Lync clients dial voicemail. Where does this go if somebody dials internally (from Lync) and externally (from PSTN)? Exchange online or Lync on prem? And if Lync, then my guess would be
Lync forwards on to Exchange Online UM somehow. Do I have to purchase a number from somewhere because of it being on 365 or can I use a spare DID?
From my tests so far, when I call voicemail as any user, it seems to dial that same user and then the call fails.
Hopefully someone can shed some light on this for me.

You can integrate Exchange UM with Lync Server 2013.
Please check the deployment process at http://technet.microsoft.com/en-us/library/gg398968.aspx
Lisa Zheng
TechNet Community Support

Getting EOP to send mail to On premises Exchange 2013

one of may clients has Office 365 Enterprise E1 for Nonprofits and on premise exchange 2013 server which I'm trying to implement the EOP service.
but i cannot get the exchange online outbound connector to forward on the emails to the on premise server.
i have active directory sync working.
i.e when i add a new user on premises it creates it online.
could anybody let me know how to get this service to work.
what i would like is
1 mx record to point to eop service and collect and filter email.
(which i have done by adding mx records as per dns instructions. checks show as fine.but changed back to on premises server because emails where only staying in online inbox. the on premises domain name has been setup within office 365 as default domain and
in accepted domains within exchange online.both exchange online and on premises default domain name our the same.)
2 filter mail to be forwarded to correct mail box to on premises server.
( which i have setup outbound connector with exchange online to point to our on premises exchange server but does not receive any emails they are received in office 365 online mailbox and not forwarded on)
3 on premises server to forward mail to EOP service
( which i have done by creating inbound connector in exchange online and adding it as smart host to on premises outbound connector and appears to be working fine.)
am i missing something?
any help would be gratefully appreciated
Many Thanks
Stephen
1 first server (AD,AD CS,DC,Dhcp,dns servers and Hyper V)
setup physical server with windows server 2012 r2 standard Essentials Experience Role installed and hyper v role
2nd server server (exchange 2013)
VM with windows server 2012 r2 with exchange server 2013 installed and all updates done including exchange cu1 update.

Matthew thank you your reply but No it is set for Authoritative. would this be the problem.
many thanks
Stephen

Hybrid Deployment - Migrating from Exchange Online to On-Premise Exchange

Similar Messages

Maybe you are looking for