Exchange 2013 on-prem hybrid to O365

design:
Exchange 2013 deployment on-prem including UM being used for UM for users. Domain and Exchange are set to companyA.net
companyA.com is set up in O365 for email\calendars etc.
ADFS and DirSync already configured to O365.
Available UPN's in AD are already companyA.com and companyA.net.
Plan:
Setup hybrid so some users can have mailboxes on-prem and others on O365.
Have companyA.com be the primary smtp address
Questions:
1) which domain would be used as the autod when running
Set-HybridConfiguration –Domains "companyA.com, companyA.net", "autod:<>"
2) The speech attendant part of UM on prem is a non-negotiable requirement. could the mailboxes be on O365 and still work correctly?
Other considerations:
1) Lync 2013 on-prem is deployed for all features including Enterprise voice. Presence, calendars, and voicemail from exchange required.

Sorry if I am asking a lot of questions.
I am trying to setup test accounts and make sure this is working like we want it to. The production system is 30,000 accounts and I do NOT want to affect any of them until we are ready.
I have the on-prem domain of companyA.net and have setup test.companyA.net as a UPN suffix in AD domains and trusts. ADFS has been setup as well as DirSync (limited to one test OU). I have set up both the companyA.net and test.companyA.net
as additional domains and both show active in Office365 of companyA.com.
I started the hybrid wizard on-prem and got as far as the Domain and token page. Only companyA.net is listed, not test.companyA.net. Again, I ONLY want for now to have test.companyA.net working. Should I be able to proceed or how do I get test.companyA.net
on that list?
Sorry to be skittish, but any really detailed articles (step-by-step is nice) or help on how to get this setup for testing?
I am open to questions and providing what info I can if given how to find it.

Similar Messages

Reading Exchange Online tenant version failed due to an exception when trying to install Exchange 2013 in a hybrid environment.

We currently have an Exchange 2010 hybrid install and we have migrated all of our email accounts to Office 365. Now, I want to do an on-premise install of Exchange 2013 to better manage the hybrid setup. When I try to install Exchange 2013 it
asks for my O365 credentials to do a hybrid check but always fails with the above message. I've done quite a bit of searching but haven't come up with anything useful.
Here is what appears in the exchange setup log:
[09/22/2014 15:48:27.0024] [0] Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log for more information.
[09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,
[09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,
[09/22/2014 15:48:27.0147] [0] Session=Tenant Total Cmdlet Time=1.6931035s
[09/22/2014 15:48:27.0148] [0] Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetectionException: Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log
for more information. ---> System.TypeLoadException: Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,

Hi,
I recommend you post this in
office 365 forum also, as they should have more professional knowledge on hybrid deployments
and you may get effective solution timely.
In addition, I found a similar thread for you reference:
http://community.office365.com/en-us/f/156/t/255739.aspx
According to the reply of this thread, if you run the HCW (Hybrid Configuration Wizard) to deploy the Exchange Hybrid environment, there will generate an HCW log
file for this deployment.
Additional troubleshooting information is available in the Update-HybridConfiguration log file located at C:\Program Files\Microsoft\Exchange Server\V1*\Logging\Update-HybridConfiguration\HybridConfiguration****.log
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2013 Office 365 Hybrid Cloud On-Premise Outlook Connection Problem

Hi Everyone,
We are required to migrate FROM the cloud TO an on-premise Exchange 2013 server. We set up a trial of Office365 and linked our test domain to that account. The test domain mimics our current domain, but ends in .net instead of .org.
We set up a test Exchange 2013 server with a few database servers. Internally, we can connect without issue (Outlook). We mapped our test CAS to face the Internet, and can access what we need without issue. We also set up the Hybrid
configuration on both the Exchange 2013 and Office365 servers. We have validated that DirSync works, and migration can occur up to the cloud and back down to the on-premise server.
Now, here is the issue:
We have our DNS records still pointing to Office365, so when we add an Office365 mailbox to Outlook (internal to the network or outside the network) we see absolutely no issues. We migrated a mailbox today to our on-premise server, but upon doing so,
can no longer connect to, or add, that mailbox to Outlook. When we put this integration in to effect for production, we want to be able to migrate mailboxes on-premise from the cloud, and we want to make sure users can still access their mailboxes. This
also goes for distribution groups, conference rooms, etc.
I see that most suggestions say to change your DNS record to point to the on-premise Exchange server, which is great, but after doing so Office365 accounts experience the same issue as above. We NEED to make sure that when we batch migrate, the users
DO NOT lose connectivity to their accounts. We need both Office365 accounts and Exchange on-premise accounts are accessible internally and externally. As an extra tid-bit, we HAVE configured Outlook Anywhere on Exchange 2013, but see no difference.
Any thoughts on this? Office365 and Exchange 2013 see eachother and recognize that the hybrid environment is set up good, but it appears we are missing some configurations. Currently, we have a CNAME record points our autodiscover to autodiscover.outlook.com.
Any help would be MUCH appreciated. Thanks!
Dan

Hi,
Here is an article on Move mailboxes between on-premises and Exchange Online organizations in 2013 hybrid deployments, for your reference:
http://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
I want to make sure OWA works well with the moved mailbox.
To use CNAME based autodiscover method, we need to have all domain names present in a SAN certificate.
With Exchange 2013 CU1, we now have the option of adding multiple SMTP domains to Exchange Federation/Hybrid configuration and we can specify which of these domains should act the "autodiscover" domain.
To configure an SMTP domain as the autodiscover domain, you can run following command:
Set-HybridConfiguration -Domains "domain1.com, domain2.com, domain3.com", "autod:domain.com"
More details, please refer following blogs:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part11.html
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part12.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above links.
Thanks
Mavis Huang
TechNet Community Support

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

Winmail.dat attachments from Exchange 2013 on premi and Hosted Office 365 set up.

Hello TechNet,
I have an on going situation with winmail.dat attachments. I currently have a ticket open with Microsoft, but I want to see if anyone has personal experience with this. Here is the rundown.
We have migrated from an Exchange 2007 server to Exchange 2013 for the migration to Office 365. We also have a hosted Office 365 server with half of our mailboxes in the cloud and half of them on the Exchange 2013 on premise server.
The current settings for TNEFEnabled:
On Premise: False
Hosted: False
Whenever a internal email with a calendar invite(exchange calendar, go to meeting) goes out to any external domain the recipients receive winmail.dat.
When settings for TNEFEnabled On Premise and Hosted are set to true both calendar invites and PDF, Excel attachments etc the recipients receive winmail.dat.
When speaking with Microsoft about this issue. The representative was watching me through a LogMeIn session as I set both TNEFEnabled false on both on Premise and Hosted.
This is really frustrating as many employees depend on this to be fully functional, and to be honest am tired of dealing with this.
I need help.
-Ben

I am having the same issue.
Luckily I have only migrated my own mailbox to office365.
Tried both true and false TNEFEnabled on both onpremise and office365 via powershell and confirmed that both have been applied.
If I send the email as a plain text then the attachment works ok. If I send it as HTML then I get winmail.dat.
The above KB doesnt really help me, sending plain text emails is like going back to the dark ages!
I am sending from outlook to outlook (I send from my external email address, to my work email address and visa-versa)
If someone with an onpremise mailbox sends me an email, the attachment works ok.
If someone sends me an attachment via hotmail, the attachment works ok.
It seems to only effect emails I send to myself through outlook, i am sending it through a POP3 account to our onpremise exchange 2010 which forwards the email to office365

Exchange 2013 Messages Stuck in Queue

Hello,
I have an Exchange 2013 on-prem serer. I'm noticing that certain messages get stuck in the queue. They report back errors of "451 4.4.0 SMTPSEND.SuspiciousRemoteServerError; remote server disconnected abruptly; retry will be delayed".
It seems to be random. I've sent messages to a domain I've seen with messages stuck, and mine work. When I log the send connector it really doesn't show me much. Can anyone give me some leads?
2014-10-13T14:41:42.162Z,Internet Outbound,08D1B4FCB0EBBB8A,10,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,11,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,12,10.10.0.30:19282,152.163.0.67:25,<,250-STARTTLS,
2014-10-13T14:41:42.178Z,Internet Outbound,08D1B4FCB0EBBB8A,13,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.193Z,Internet Outbound,08D1B4FCB0EBBB8A,14,10.10.0.30:19282,152.163.0.67:25,>,STARTTLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,15,10.10.0.30:19282,152.163.0.67:25,<,220 2.0.0 Ready to start TLS,
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,16,10.10.0.30:19282,152.163.0.67:25,*,,Sending certificate
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,17,10.10.0.30:19282,152.163.0.67:25,*,"CN=mail.mydomain.com, OU=Domain Control Validated",Certificate subject
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B2FCB0ENBB8A,18,10.10.0.30:19286,152.163.0.67:25,*,"CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O=""GoDaddy.com, Inc."", L=Scottsdale, S=Arizona,
C=US",Certificate issuer name
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB3A,19,10.10.0.30:19282,152.163.0.67:25,*,0828F6C11RF919,Certificate serial number
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,20,10.10.0.30:19282,152.163.0.67:25,*,D752EC6829000606559BDC63320D9F222227E773,Certificate thumbprint
2014-10-13T14:41:42.209Z,Internet Outbound,08D1B4FCB0EBBB8A,21,10.10.0.30:19282,152.163.0.67:25,*,mail.mydomain.com;www.mail.sigwnet.com;autodiscover.mydomain.com,Certificate alternate names
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EB3B8A,22,10.10.0.30:19282,152.163.0.67:25,*,,Received certificate
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCA0EBBB8A,23,10.10.0.30:19282,152.163.0.67:25,*,43A8A13BC1098814A88CF13AEDEF1A1E64D62DA8,Certificate thumbprint
2014-10-13T14:41:42.240Z,Internet Outbound,08D1B4FCB0EBBB8A,24,10.10.0.30:19282,152.163.0.67:25,>,EHLO mail.mydomain.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBA8A,25,10.10.0.30:19282,152.163.0.67:25,<,250-mtaig-aak04.mx.aol.com,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1A4FCB0EBBB8A,26,10.10.0.30:19282,152.163.0.67:25,<,250 DSN,
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,27,10.10.0.30:19282,152.163.0.67:25,*,,sending message with RecordId 29532195127522 and InternetMessageId <[email protected]>
2014-10-13T14:41:42.474Z,Internet Outbound,08D1B4FCB0EBBB8A,28,10.10.0.30:19282,152.163.0.67:25,>,MAIL FROM:<[email protected]>,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,29,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.0 Ok,
2014-10-13T14:41:42.505Z,Internet Outbound,08D1B4FCB0EBBB8A,30,10.10.0.30:19282,152.163.0.67:25,>,RCPT TO:<[email protected]>,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,31,10.10.0.30:19282,152.163.0.67:25,<,250 2.1.5 Ok,
2014-10-13T14:41:42.552Z,Internet Outbound,08D1B4FCB0EBBB8A,32,10.10.0.30:19282,152.163.0.67:25,>,DATA,
2014-10-13T14:41:42.583Z,Internet Outbound,08D1B4FCB0EBBB8A,33,10.10.0.30:19282,152.163.0.67:25,<,354 End data with <CR><LF>.<CR><LF>,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,34,10.10.0.30:19282,152.163.0.67:25,<,250 2.0.0 Ok: queued as 8A7497000009F,
2014-10-13T14:41:45.688Z,Internet Outbound,08D1B4FCB0EBBB8A,35,10.10.0.30:19282,152.163.0.67:25,>,QUIT,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,36,10.10.0.30:19282,152.163.0.67:25,<,221 2.0.0 Bye,
2014-10-13T14:41:45.719Z,Internet Outbound,08D1B4FCB0EBBB8A,37,10.10.0.30:19282,152.163.0.67:25,-,,Local
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,27,10.10.0.30:19263,74.208.5.21:25,*,,"HandleError has encountered a suspicious connection reset from a remote, non-mailbox transport server (will retry in 00:10:00)."
2014-10-13T14:42:01.132Z,Internet Outbound,08D1B4FCB0EBBB88,28,10.10.0.30:19263,74.208.5.21:25,-,,Remote

Hi rmicha9682,
Agree with Gareth, it seems to be a firewall issue.
I have seen this issue caused by the SMTP Fixup protocol when using TLS encryption.
I recommend you try disabling SMTP Fixup and check if any helps.
The following article for your reference:
http://support.microsoft.com/kb/320027/en-us
Best regards,
Niko Cheng
TechNet Community Support

Some help with migrating exchange 2010 to exchange 2013 + installing another exchange 2010 to be edge-forefront-proxy server

Hi guys (and girls)!
Hear me up. The idea is like this:
A friend of mine has currently Exchange 2010 SP3 in his environment with Forefront Protection installed on it. As we all know Forefront Protection is discontinued in Exchange 2013 environment because Exchange 2013 on-premisses is using integrated tool for
doing that, but a friend of mine would really like to stick with Forefront Protection because it is "much better tool" then integrated stuff in 2013.
Ok, so here's the idea. Exchange 2010 SP3 with Forefront is installed on Phisical machine (so, not virtualized) on 2008 r2 std OS. We decided to move to Exchange 2013 because we wanted to achieve DAG on Exchange 2010 but we realized that is not possible
because 2008 R2 STD OS does not support failover-clustering functionality, but you are able to achieve that on newer OS for example 2012? Ok, so we bought another server, where we are planing to install Vmware Esxi and put two virtual machines on it.
One Will be 2012 r2 STD OS with Exchange 2013 on it, the other Will be 2008 r2 STD with Exchange 2010 Edge role + Forefront on it. We are planing to move Exchange 2010 production server to virtual machine Exchange 2013, and newly virtual machine
with Exchange 2010 edge server will only be "a kind of Proxy server with Forefront functionality". What concers me?
Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
bostjanc

Should we install Exchange 2010 edge transport 1st, or Exchange 2013? I think I have read somewhere after you put Exchange 2013 in production you are "unable" to install any previous Exchange versions is that true?
already answered by PS CL above
One more question about what happens after you install another Exchange 2010 with Edge role in production enviroment? Does installation effects a production enviroment, let's say we do just a clean installation of Exchange + ran updates?
No it does not as long you don't make any changes on send/receive connector and do the EdgeSubscription. As soon as you do the Edge subscription there will be send/receive connector created, so pay attention how to setup the Edge Server.
Which roles do you need to install on Exchange 2010 to achive Edge role? Do you need to have all the roles install for having Edge server (mailbox, hub,cas?).
Just install the Edge Transport Server and make sure you install ADLDS services.
as you have mentioned you are doing to install both Mailbox and Edge server on the same VMware - it is a single point of failure.
Where Technology Meets Talent

Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

Hello guys,
I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
What should I check and configure to make it work?

Hi,
I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact EMC supplier to improve it.
By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2013 UM on-prem-hybrid with Office365

design:
Exchange 2013 deployment on-prem including UM being used for UM for users. Domain and Exchange are set to companyA.net
companyA.com is set up in O365 for email\calendars etc.
ADFS and DirSync already configured to O365.
Available UPN's in AD are already companyA.com and companyA.net.
Plan:
Setup hybrid so some users can have mailboxes on-prem and others on O365.
Have companyA.com be the primary smtp address
Question:
1) The speech attendant part of UM on prem is a non-negotiable requirement. could the mailboxes be on O365 and still work correctly?
Other considerations:
1) Lync 2013 on-prem is deployed for all features including Enterprise voice. Presence, calendars, and voicemail from exchange required.
Need to have the MWI and calendaring\presence work.

1: It should, but first make sure you create the UM Dial Plans other UM properties in Office 365.
Do testing before the move.
I saw one of friend faced issue where as, Voice Mail notification wasn't getting delivered to user Mailbox.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Installing / Upgrading Exchange 2013 to Exchange 2010 with a o365 Hybrid environment

Hi
I am trying to install a new server with Exchange 2013 on an environment with an existing Exchange 2010 Sp3. Reason for that is that I have a o365 hybrid environment and need to disconnect my on-line and on-premise e-mail connection. I want to completely
run all my mailboxes on o365 no-longer dependent on on-premise exchange but the Exchange 2010 doesn't have a functionality to 'dismantle' the hybrid.. we need to have exchange 2013.
When I try to install Exchange 2013 I get an error message that I need to upgrade my o365 tenant. : my o365 tenant version is : AdminDisplayVersion : 0.20 (15.1.49.12) :IsUpgradingOrganisation : False.
Is there a better way of updating my environment.
Regards

Post the error from setup log for more information.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 Hybrid setup & DNS

Greetings! We currently have an Exchange 2010 on prem environment and I have been tasked with getting us into a hybrid state with O365. We already have the tenet portions set up, AD Sync working, etc. My initial thought was to just use
our existing Exchange 2010 servers for the hybrid role, however, upon research it appears that standing up new Exchange 2013 servers specifically as hybrid servers is the suggested route.
My main goal is to do this hybrid deployment with as little impact and change to our environment (and thus user impact) as possible. From what I have read, I will have to change the autodiscover and ews records to point to the new Exchange 2013 servers.
Is it also the case that I will have to redirect OWA to the Exchange 2013 servers? Is there any way to deploy Exchange 2013 hybrid servers in a way that I do not have to change owa, autodiscover, etc?
Thanks in advance!

Hi Joe,
Based on my knowledge, we didn't need to install Exchange 2013 to perform routing.
We can just deploy an Exchange 2010-based Hybrid Deployments.
Please make sure the Exchange 2010 upgrade to SP3.
More details to see:
Hybrid Deployments
https://technet.microsoft.com/en-us/library/gg577584(v=exchg.141).aspx
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

FIM Outlook add-in w/ Exchange 2010 hybrid to O365

We have a hybrid Exchange environment with Office365. I started noticing the "approve/deny" buttons provided by the Outlook FIM plugin no longer worked. The error shown is "This request cannot be approved or rejected because it
was received from an unauthenticated sender."
What I figured out was my mailbox is in the cloud but the FIM service's mailbox is on-prem, so technically they are from different Exchange orgs and hence the sender is no longer validated since its like an external sender.
Has this scenario been seen by anyone else or addressed already by MS teams? Is there any way to relax the security on the FIM plugin itself to not do this check as a workaround? I checked through some reg keys and unfortunately didn't find any
setting saying "VerifySender=NO"

This issue is resolved, and may not have been an unexpected behavior afterall. After a full directory sync between the on-prem AD and O365, the addresses in the GAL appears normal and no longer showed the smtp address in brackets like it does for external
senders.
there may have just been an inconsistency in the x500 / exchange addresses in the objects, so after a full sync cycle, its been fine, so this scenario should work no problem for others.

Exchange Online (O365) and Exchange 2013 On-Premise, Public Folder issues?

Hello,
I have recently migrated from Exchange 2010 to Exchange 2013 on premise (decommissioned the old server) and migrated my public folders to the new mailbox architecture found in Exchange 2013.
We are also hybrid setup with Office 365 and Exchange Online (AD FS and Password Sync). For our on-premise Exchange we use Split DNS.
What I am trying to do now is give my Exchange Online users the ability to see our on-premise public folder infrastructure however I am not having any luck in getting this to work.
On premise I have the "PublicFolderMaster" mailbox which is the Primary Public Folder Mailbox, and PublicFolderMailbox1 which is the secondary mailbox (where all the public folder data is).
How do I configure my Exchange Online to allow the users to see on-premise public folders? I tried..
Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PublicFolderMaster,PublicFolderMailbox1
In my O365 user's Outlook I see Public Folders, but when I try to expand it I get an error saying unavailable...
What am I doing wrong?

Or must I follow all these steps in addition to the last step above?
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx

Exchange 2013 Hybrid Configuration Wizard OAuth error

Hi,
We are facing following error when we run OAuth configuration after complete the Hybrid Configuration Wizard.
Error:
ScenarioFailureException
Message:
Exchange OAuth authentication couldn‎'t find any accepted domains in your on-premises organization.
Verify you‎'ve configured at least one on-premises accepted domain.
Location:
   at Microsoft.Online.CSE.HRC.Activities.OAuthActivities.GetCertificateActivity.Run‎()‎
   at Microsoft.Online.CSE.HRC.Workflow.Activity.WorkflowBaseActivity.Launch‎()‎
   at Microsoft.Online.CSE.HRC.Workflow.Runtime.WorkflowActivityHelper.Execute‎(ActivityContext context, Boolean launch)‎
   at System.Activities.NativeActivity.InternalExecute‎(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)‎
   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody‎(ActivityExecutor executor, BookmarkManager bookmarkManager,
Location resultLocation)‎
Environment:
2x Exchange 2013 CU6 (DAG+one ClientAccess)
Directory Sync Server
No ADFS server since we don't need single sign on
Office 365 E3 Tenant
We have tried manually setup the OAuth configuration according to the below TechNet article but failed when running the ExportAuthCert.ps1
script file. It couldn't match the certificate thumbprint with the location "Cert:\LocalMachine\My"
http://technet.microsoft.com/en-us/library/dn594521%28v=exchg.150%29.aspx
Please help!
Thanks in Advance
Roshan

We have the exact same Issue, tried the exact same setup and NO JOY!! - any resolution yet?
Also found this article:
http://consulting.risualblogs.com/blog/2014/09/10/exchange-2013-cu6-hybrid-users-with-o365-unable-to-query-freebusy-for-on-premises-users/comment-page-1/#comment-5192
..... but did not fix the free/busy
Best Regards,
Francois

Hybrid Exchange 2013 rather then 2010

Hi.
On a lots of blogs i find that the costumer will have advantages to upgrade the hybrid server (On-Prem) from Exchange 2010 to 2013. Witch advantages is there? I can see that the
EAC and the Portal merges better, but is it any other god reasons?
Rinken

Hi,
Both on-premises Exchange 2013 and Office 365 have their own pros and cons. You can refer to the following article for more details about comparing Office 365 pros and cons with Exchange 2013.
http://searchexchange.techtarget.com/tip/Comparing-Office-365-pros-and-cons-with-Exchange-2013-hybrid-setups
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software
or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
More information about Exchange Server 2013 Hybrid Deployments:
http://technet.microsoft.com/en-GB/library/jj200581(v=exchg.150).aspx
Hope this is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2013 on-prem hybrid to O365

Similar Messages

Maybe you are looking for