Exchange 2013 Hybrid with O365 - migrated user causes admin restart prompt for multiple other users

Greetings! We are in the process of doing some testing and migration in a hybrid deployment with Office365 and Exchange on premise.
I just completed a migration for an on-premise user. We have, so far, migrated 3 users in the IT department as initial testing. The first two migrations were very cut and dry. The third migration; as soon as I finalized the batch, multiple
people on our team received messages about having to restart Outlook. These were users that had not been migrated and were not part of any migration batch, but were members of the same department. I am trying to understand, under what circumstance
could a migration of a user cause other users who are still on premise to receive the "admin made changes" prompt in Outlook.
Thanks in advance.

Hi Joe,
Could you share the migration batch? Note, please hide if there are any sensitive information like domain name and server name.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

Exchange 2013/2010 Co-existance Outlook Users Always Prompted for Password

Hello,
We are in the process of attempting to migrate to Exchange 2013, but during the migration time, we need to coexist with the two versions. Our outlook clients are a mix of Office 2007, 2010, and 2013. When a user is migrated from 2010 to 2013,
they start getting prompted for their password in Outlook every few minutes. They can click cancel and continue working, but they continue to get prompts for their password. If they click the update folder button in outlook, it updates fine, and
the password prompt goes away for awhile.
Most topics on this state that this is caused by a certificate issue. We have an internally deployed CA, with the Root certificate trusted by all clients. The exchange 2013 server has a certificate that was created by this CA.
I believe that this is caused by OAB (address book) still being hosted on the Exchange 2010 server (with a self signed cert), that is causing the connection to fail. Is there anyway to test this without breaking outlook connections for the users that
are on Exchange 2010? Or is there any other reason that this would occur?
Thanks for any assistance.

Sorry for taking so long to reply, other items came up that rank higher then this migration.
I ran the Test-OutlookWebServices CMD and got this result:
[PS] C:\Windows\system32> Test-OutlookWebServices
Source                              ServiceEndpoint
Scenario                       Result Latency
(MS)
EXCHANGE13.company.local           exchange10.company.local           Autodiscover: Outlook Provider Failure     229
EXCHANGE13.company.local
Exchange Web Services          Skipped       0
EXCHANGE13.company.local
Availability Service           Skipped       0
EXCHANGE13.company.local
Offline Address Book           Skipped       0
I
am currently thinking that this may be the error. Is there a way to
change the first failing result to the hostname of the
exchange13.company.local without breaking the current settings for the
exchange10.company.local autodiscover?

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

Default frontend receive connector settings exchange 2013 hybrid edition?

Hi,
I am busy setting up a hybrid environment with exchange 2007 , exchange 2013 hybrid edition and office 365.
When installing exchange 2013 it creates a default frontend receive connector, on the security tab anonymous user is also selected.
Should i leave it this way?
At the moment the mx record is pointing to the exchange 2007, in the future i will change the mx record to the exchange cloud.
I can telnet and mail to the exchange 2013 server, but there is no spam protection, do i need the anonymous user if i am not intended to use this for the mx record, i suppose office 365 is going to use this connector.
(ps: still have to run the hybrid configuration wizard, waiting for dns ownership txt record)

Hi Steven,
Just as Ed said, the connector restrict access via IP address. We can also create another ones.
If you worry about the spam, I suggest enabling the Anti-Spam function on MBX server.
More details in the following articles:
Spam Protection
http://technet.microsoft.com/en-us/library/jj218660(v=exchg.150).aspx
Enable Anti-Spam Functionality on Mailbox Servers
http://technet.microsoft.com/en-us/library/bb201691(v=exchg.150).aspx
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 CU6 with DAG - ECP Delete does not go to soft-delete state, retention policy ignored

I am not sure if this is a BUG or this is as intended. Typically if a mailbox is 'deleted' from the EAC or ECP console the user account is disabled and the mailbox is marked for removal (soft-delete) until the retention policy expires the item (default
30 days). However we deleted a mailbox and the mailbox was purged immediately as well as the user was moved to the hidden recycle bin in Active Directory.
We replicated this issue twice in a DAG environment, we do not have this issue in a non-DAG environment.
Question: Other than restoring from the backup, is there a way to recover the mailbox?
Thank You,
-Jake
Jacob Evans Jake of All Trades

Hi,
I tested in my lab, Exchange 2013 CU1 with DAG deployed, if I deleted a mailbox from EAC, then it would be a disconnected mailbox and the associated Active Directory user account was also deleted. I could find it under the Disconnected Mailbox.
Was the mailbox logged ever?
If you delete a mailbox that you never log in, it won't show as disconnected mailbox.
And for the question :"Question: Other than restoring from the backup, is there a way to recover the mailbox?", I'm afraid you have to recover from backup.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 Hybrid Deployment, on-premise to multiple Office 365 tenants

Hello, we are in the early stages of planning an Exchange 2013 hybrid deployment for a federation of education organisations.
We are planning to use a single on-premise Exchange organisation for staff mailboxes across all member organisations, each member already has it's own Office 365 tenancy for students, which we would like to maintain if possible.
My question is, is it possible (and supported) for an Exchange hybrid deployment with a single on-premise organisation with multiple Office 365 tenants, my understanding is that only a 1:1 deployment is supported, can somebody confirm or clarify this ?
Thanks

I think if you have different AD sites then you can install the DirSync or ADFS for each of them and have one way replication. I 'd aks this question to Office365 Forum and support.
Where Technology Meets Talent

How to configure Exchange 2013 OWA with Single Sign On

Hi All ,
How to configure Exchange 2013 OWA with Single Sign On ?
Thanks .

Hi,
From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
Exchange 2013 OWA Single Sign on with Exchange 2010
https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
If that is not your case, please feel free to tell me.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013: Problem with Default Global Address List after migration

I just completed a migration from Exchange 2007 to Exchange 2013. The 2007 box has been decommissioned just last week. I have been seeing weird issues with our offline addressbook and global address list, since the migration, but always thought
it was related to Ex2007. Well the issues still exist and here's what i've found so far:
1. If any user goes to Schedule Appointment in Outlook, and they click the Rooms button (on the Scheduling Assistant page), we get a LONG wait (about 5 mins or more) and then an error that says: "The operation could not be completed because
an offline address book is not available. Download a copy of the offline address book." When i click OK, the address book is up, with the "All Rooms" list showing blank (we have 3 rooms in Exchange currently).
2. Now if I go to the Address Book in Outlook it opens to the GAL and it's up to date... I can also force an update to the offline address book after adding a new group or entry, so i know offline address books are being updated properly and
working. HOWEVER, if i go to any of the other address lists (besides Contacts and GAL) under All Address Lists (All Contacts, All Groups, All Rooms, All Users and Public Folders) I get the same error given above: "The operation could not be
completed because an offline address book is not available. Download a copy of the offline address book."
3. I went to the Exchange 2013 EAC and went to Organization -> Address Lists. Everything under here said 'NO' under the Up-to-Date column. When i looked at the properties on each list, and clicked save, I had to update to the new version.
After doing this, the Up-to-Date column said 'YES'. I could do all lists EXCEPT for the GAL. It still says 'NO'
4. The last thing i did was set my Outlook to NOT be in cached mode. This should give me a direct connection to the GAL and all lists, if I'm not mistaken... So when i do this, I cannot even open see the GAL. The ONLY option in the
Address Book that comes up is Contacts (which are my personal ones).
5. I just now ran Get-GlobalAddressList | fl in powershell on the Ex2013 server. I see some things that make me wonder... First; nothing in the RecipientFilter field, however, there is something in the LdapRecipientFilter field.
Second; the RecipientFilterType field says "Legacy". and Third; the RecipientFilterApplied field says "False".
Didn't know what these should all be, but it appears maybe this is the cause of all my issues?? Can someone help me out here.. even if i have to recreate a new GAL, i'm fine with that, I just don't know all the steps to do so. I just need it
to work!
Thanks
Jeff
-Jeff

Hi,
In my opinion, it is better to confirm whether the GAL is good, first.
How about the GAL working in OWA?
If GAL working well in OWA, it seems the issue on the Outlook Client or Connectivity side.
Please trying to run Outlook on the safe mode to avoid some AVs, add-ins and firewall for testing.
Please follow the steps as below to narrow down the OAB issue.
Following are the locations that .lzx files in CAS server and BMX server:
CAS:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB
MBX:
C:\Program Files\Micorosft\Exchange Server\V15\ExchangeOAB
Please verify whether the .lzx files update to the latest.
1. If the .lzx files in MBX server not update to the latest.
It should be an issue on the OAB generation side.
2. If the .lzx files in MBX server is latest, but CAS server not.
It should be a distribution issue.
1) Please run Get-OabVirtualDirectory command in EMS to verify whether at least one OAB VD exist in the org. If not, please create a new one.
2) Please make sure whether any setup for Web Distribution. Selecting the “Enabling an Offline Address Book for Web Distribution” checkbox.
3) Please force restart File Distribution services to distribute OAB files manually.
3. If the .lzx files in MBX server and CAS server are all update to the latest.
It should be the connectivity between CAS server and Client issue.
1)Please verify the network.
2)Please check DNS, MX, etc. configuration.
3)Please run “Test E-mail AutoConfiguration” to check the AutoDiscover details.
   Please make sure the OAB URLs are correct.
   If the OAB URLs are incorrect, please using following command to re-set them:
   Set-OABVirtualDirectory -Identity "ServerFQDN\OAB (Default Web Site)" -ExternalUrl
https://www.contoso.com/OAB -InternalUrl
https://mail.contoso.com/OAB
4)Please checking the App log and finding solutions from Microsoft Technet articles or KB, according to the Event ID.
5)If it still not working after performing the methods above unfortunately, please trying to re-build OAB Virtual Directory.
   Article for reference:
   Remove, Re-Create, and Reconnect an Offline Address Book Virtual Directory
http://technet.microsoft.com/en-us/library/bb123595(v=exchg.141).aspx
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment

hi,
I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot.
I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?
Thanks

Hi Muhammad
Can you please give few more information about your environment so that people around here can help you out
I have existing Exchange Server 2010 Hybrid Deployment - Do you have Exchange 2010 and Office 365 in a
hybrid setup now ?
Are you trying to upgrade your on premise Exchange 2010 servers to Exchange 2013 ?
Or Are you trying to migrate your on premise Exchange 2010 to a different forest to Exchange 2013 ?
You can try the below suggestions-
I would better suggest you to follow Microsoft Exchange Server Deployment Assistant - http://technet.microsoft.com/en-us/office/dn756393.aspx
Also i would recommend you to check the prerequisites for hybrid deployment with office 365
http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Cheers !!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Can't install Exchange 2013 after previous uninstall (insufficient user privileges with the same user)

I have installed Exchange 2013 on Windows Server 2012, which ist a member of a Windows Server 2012 R2 Domain. All prerequisites and AD modifications were successfully completed and I could install Exchange 2013. Unfortunately I made a mistake with
the target directory and had to uninstal Exchange 2013. If I start the Setup again, it fails in prerequisite check - the current user should not be a member of Enterprise and Schema admin Group, but it's the same user, which comleted the previous Installation
of Exchange 2013! Do you have any idea how to solve this Problem - I'm running out of ideas.

Inhave tried to run setup /PrepareSchema again and get the following error in exchange setup log:
[03.07.2014 19:25:53.0305] [0] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
[03.07.2014 19:25:53.0337] [0] Validating options for the 0 requested roles
[03.07.2014 19:25:53.0383] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
[03.07.2014 19:25:53.0399] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
After removing all Exchange Parts by ADUC (advanced View) and ADSI Edit (Services) I'm able to install Exchnge 2013 again - the uninstall procedure seems not to work in a clean manner.

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.

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

Exchange 2013 coexistence with 2010

Who all has had problems with 2013 proxing requests to 2010? I tried a migration and couldn't even get OWA to proxy or redirect. I was receiving errors like this:
Autodiscover would fail for 2010 users but fine for 2013 users:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms
and
Created a new user on 2010 and login to OWA does this:
Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
I've tried it multiple ways and I've actually done this migration before. Either way this was the same AD site, and I checked/tried the following:
Checked AD Replication and it was fine
Exchange 2013 was at SP1
Exchange 2010 was at SP3 Rollup 6
Exchange 2010 was a single server with CAS/HUB/Mailbox
Exchange 2010 was not using a CAS Array
Exchange 2013 had two mailbox servers in a DAG and one CAS server
I've tried both setting all external URL's on 2010 to https://legacy.domain.com/* and also not setting External URL's. Neither fixed the issue
https://legacy.domain.com/autodiscover/autodiscover.xml worked fine (600 invalid request response) and https://owa.domain.com/autodiscover/autodiscover.xml worked fine too (2013) but Test Connectivity and Outlook didn't work
I checked for bad HTTP Redirections on new and old servers and made sure there were no HTTP redirections added
Would really love some input to see what I did wrong. Thank you!

Thanks for responding!
The internal URL's for 2010 I set to https://legacy.domain.com/*. So the OWA internal URL is https://legacy.domain.com/owa. The external URL was set to the same and I also tried not settings the external URL at all.
Just FYI.. legacy.domain.com pointed to the internal IP when using internal DNS servers and legacy.domain.com pointed to the external IP when external which all went to the 2010 server
The detailed error from ExRCA is listed above. It failed autodiscovered and wouldn't continue. The thing is autodiscover seemed to work fine going to 2010 and to 2013 but it failed when it tried to proxy to 2010. So if a mailbox was on 2013 then ExRCA was
fine. If I opened a url to https://legacy.domain.com/autodiscover/autodiscover.xml and logged in I got the XML 600 error like I should. This is what autodiscover said:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms

OWA problem Exchange 2013 coexistence with 2010

Hi all,
I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
to access OWA with a mailbox that is still on 2010 it fails with the following error:
something went wrong
A problem occurred while you were trying to use your mailbox.
X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
X-OWA-Version: 15.0.913.21
X-FEServer: <name of 2013 server>
X-BEServer: <name of 2013 server>
Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
Any help is greatly appreciated!
Best regards
Daniel

Hi,
How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 Hybrid and Rightfax

We are in the process of planning our migration to Office 365, and one of the things we currently use in our Exchange 2010 on prem solution is Rightfax for direct faxing inbound/outbound. The plan is to roll out exchange 2013 in hybrid mode, and I
am wondering what i need to do so that faxing continues to work?
Since we will be running a hybrid, is it as simple as installing the rightfax service on the exchange server, or do I need to plan for some kind of cloud access, similar to how they borked up exchange UM integration (requires a session border controller,
rather than routing through exchange on premises box).

Hi,
According to the description, following is my understanding:
1. You want to migrate to Office 365 from Exchange server 2010.
2. Exchange server 2010 host the Rightfax, now.
3. You want to install a new Exchange server 2013 on-premise. Let the Exchange server 2013 on-premise host the Rightfax.
4. Exchange server 2013 on-premise and Office 365 Hybrid Deployment.
Please correct me if there is any misunderstanding.
If all of above is right, I find some resource relate on Hybrid Deployment with Exchange 2013 on-premises and Office 365.
Exchange Server 2013 Hybrid Deployments
http://technet.microsoft.com/en-us/library/jj200581(v=exchg.150).aspx
Note: If you want to move mailboxes from your on-premises organization to the Exchange Online organization, and those mailboxes are configured for UM, you should configure UM in your hybrid deployment prior to moving those mailboxes.
If you move mailboxes before you configure UM in your hybrid deployment, those mailboxes will no longer have access to UM functionality.
About the Rightfax, I find this from Microsoft resource:
OpenText RightFax version 10
http://pinpoint.microsoft.com/en-us/applications/opentext-rightfax-version-10-12884918124
However it works with
Hyper-V, Microsoft Exchange Server 2010, Microsoft Office 365, Microsoft SharePoint Server 2010, Windows Server 2008 R2.
I'm not quite familiar with it. We can also contact to Rightfax Support to double confirm this.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange 2013 Hybrid with O365 - migrated user causes admin restart prompt for multiple other users

Similar Messages

Maybe you are looking for