OnPremise archive mailbox not showing for Office 365 users
Hello everyone, We encounter an issue with hybrid configuration, here are some details : - Exchange 2010 SP3 - ~15 users migrated to Exchange Online Situation : - User "Tom" has his mailbox on Exchange Online, with an E3 licence, arcihve mailbox enabled - User "Bob" has his mailbox on Premise (Exchange 2010) - User "Mike" has his mailbox on Premise (Exchange 2010), archive mailbox enabled - User "Tom" has full access delegation on "Mike" mailbox - User "Tom" can see and have access to "Mike" mailbox - User "Tom" can't see "Mike" archive mailbox - User "Tom" can see and access his own archive mailbox - User "Bob" has full access delegation on "Mike" mailbox - User "Bob" can see and have access to "Mike" mailbox and archive mailbox To sum up : - An Office 365 user with full access delegation on an On Premise mailbox (with archive mailbox enable) can't see nor have access to this archive mailbox. Any help would be much appreciated. Cheers, MaxNew Exchange Server installation for Hybrid Configuration
Hi Team. I have a Exchange Server on premise with hybrid configuration Exchange Online. I need installation Exchange Server 2016 and seize Exchange Server 2013. Perform new hybrid configuration with Exchange Online. For Exchange Server 2016 I can use the procedure of this URL to get KEY and activate the server? Hybrid Configuration Wizard and licensing of your on-premises server used for hybrid https://techcommunity.microsoft.com/t5/exchange-team-blog/hybrid-configuration-wizard-and-licensing-of-your-on-premises/ba-p/608106Hybrid Autodiscover Fails,RedirectAddr (same value as RemoteRoutingAddress) Must Be Same as O365 UPN
Thank you for taking the time to read this. I've been banging my head on why this must be or I've got something wrong with my hybrid configuration. I have a Full Hybrid environment setup between on-prem Ex2013 and O365 and it works great except the autodiscover part. user@DOMAIN.com is the default SMTP address of this local domain user whose RemoteRoutingAddress is user@DOMAIN.mail.onmicrosoft.com. Autodiscover is pointed to on-prem Ex2013 because that's what you're supposed to do until all mailboxes are off of the on-prem Ex2013. Outlook finds the autodiscover.xml correctly but the RedirectAddr value that Ex2013 returns is the RemoteRoutingAddress value instead of the Default SMTP Address value for this user so unless the Office 365 UPN for this mailbox matches the RemoteRoutingAddress, Outlook fails to complete setup. How can I make Ex2013 return the Default SMTP address as the RedirectAddr value in the autodiscover response instead of the RemoteRoutingAddress of a user?Configuring your Exchange hybrid deployment, in a nutshell
This less than 5-min video provides key information on how to setup an Exchange Hybrid Deployment. In addition, the articles below contain updates on topics covered by this video, along with their main takeaways, in bold. Subtitles in brazilian portuguese (my native language) are also available, which can be enabled/disabled from the built-in YouTube player. Enjoy!!! Hybrid deployment best practices "Should we have a hybrid specific URL? - We have seen deployments where a decision is made to keep the existing Mail.Contoso.com and Autodiscover.Contoso.com pointing to a bank of Exchange 2010 servers and have a new hybrid URL, such as hybrid.Contoso.com, pointing to a couple of Exchange 2013 servers. This is an example of an environment that did not introduce Exchange 2013 in a recommended way. "Some might ask: “Can I keep just my hybrid server up to date?” The answer: there is no such thing as a “hybrid server” (meaning that companies shouldn't add Exchange servers exclusively for hybrid, unless the sizing says it differently). What this question is really asking is: “Can I just update the server were I plan to run the Hybrid Configuration Wizard (HCW) from?” The answer to that is “No.”" Hybrid deployment prerequisites "Before you create and configure a hybrid deployment using the Hybrid Configuration wizard, your existing on-premises Exchange organization needs to meet certain requirements. If you don't meet these requirements, you won't be able to complete the steps within the Hybrid Configuration wizard and you won't be able to configure a hybrid deployment between your on-premises Exchange organization and Exchange Online." Exchange Queue & A: Handling hybrid environments "With older hybrid servers—that is, hybrid servers running Exchange 2010—you need to create an Autodiscover record in DNS for all SMTP domains. Also, the SAN certificate has to include all used autodiscover DNS records in the SAN list. With the Autodiscover domain feature, you have the option of setting one of your SMTP domains as the Autodiscover domain. This is indeed a great new feature of Exchange Server 2013." Introducing the Microsoft Office 365 Hybrid Configuration Wizard "This article tells you what’s new and shows you how to run the wizard. We also explain the various issues that have been addressed with the new Wizard, and touch on some of the telemetry we pull with every run of the wizard." Hybrid Configuration wizard "This topic gives you an overview of the Exchange hybrid deployment configuration process, hybrid deployment features and options available to you, and the Hybrid Configuration Engine, which executes the core actions necessary for both configuring and updating a hybrid deployment." Exchange Hybrid Product Key Distribution Add multiple domains to Office 365 *** UPDATE on 10/17/2017: Added a note to the top of this post to make it clear that there's actually not such a thing as hybrid servers. Thanks so much Tiago Souza for the feedback!
Acquisition migration into existing hybrid tenant
Hi, have a unique scenario and seeing if i can do the work without leveraging a tools based migration. Here is my scenario Company A is in a hybrid configuration with Exchange on prem and office 365 Company B was acquired and is fully exchange 2010 on prem there is already a plan under way to do an AD migration of the user objects. The forest will go away once the consolidation is done Is there a way where i can do remote mailbox moves from the source envrioment without attaching AAD connect to that envrioment? I envision a scneario such as the following 1) configure enough of the hybrid envrioment in company b to enable a remote mailbox move to Office 365 (making the routing addresses, migration endpoint, accepted domains etc.) 2) leverage AD migration tools to sync the necessary exchange AD data to the source forest to create the concept of a on prem mailbox in Office 365 (and groups etc.) 3) perform a remote mailbox move of the mailbox data 4) finalize the migration 5) sync the updated mailbox attributes to Company A's forest so that it is seen as a remote mailbox on both sides 6) user's outlook client would get the redirect from on prem to o365 and not require a redownload fo the OST as the mailbox GUID is the same. it's a very large environment (4000 users, 20TB of data) so i'd like to avoid going tools based if at all possible.
