Lync Online vs Exchange 2013 On Premise

We have Lync 2013 Online and Exchange 2013 SP1/Outlook 2013 SP1 on premise. All work well with RPC over HTTP.
We are trying to get MAPI over HTTP (Outlook 2013 SP1 / Exchange 2013 SP1). But it seems that the MAPI over HTTP no longer respects the Internet Explorer Bypass Proxy List. Therefore the Outlook client tries to connect to the on-premise
Exchange Server CAS via the proxy server. Outlook 2013 Connection status shows DISCONNECTED and AUTHN FAILED.
To reconnect Outlook we can either;
1. Turn off the Proxy Server in IE (Outlook then connects but we cannot browse the web).
2. Remove the Microsoft Online Services assistant (again Outlook then connects, but Lync does not).
To troubleshoot this we've used the Process Monitor and can see Outlook actively reading the registry key (HKCU\software\microsoft\windows\currentversion\internet settings\proxyoverride). Problem is it doesn't appear to use them.
Has anyone else seen this behaviour with MAPI over HTTP and the Online Services Sign In Assistant (MSOIDCLI)?

This is a known issue with MAPI/HTTP at this moment. Outlook Team is investigating it for a root cause & possible fix. No ETA is available at this time. I will update this post when we have an update.
Issue: If an Outlook 2013 SP1+ user has 'Bypass proxy server for local addresses' setting enabled in Internet Explorer (Internet Options | Connections | LAN Settings), then Outlook does not connect over MAPI/HTTP to a mailbox on Exchange
2013 SP1+ server. This issue does not happen connecting over RPC/HTTP in the same setup.
I see another known issue mentioned here thus wanted to quickly confirm that as well. Another known issue with MAPI/HTTP is as described below. This issue has been fixed and fix is planned to be deployed in Office 365/Exchange Online soon & is currently
planned to be included with E2013 SP1 CU6 (tentative).
Issue: User1 has full access to User2’s mailbox, User2 also has an Archive mailbox. Using Outlook 2013 SP1+ User1 connects over MAPI/HTTP to Exchange 2013 SP1+. User2’s Primary mailbox is then accessible to User1 in his Outlook thru Auto-mapping,
but User1 cannot see User2’s Archive mailbox. If User1 connects over RPC/HTTP, he does not see this issue.
Sr. Program Manager, Product Quality, Exchange Client Access Server

Similar Messages

Exchange 2013 on-premises doesn't see Exchange Online profile pictures

Hello!
We are on an hybrid deployment with some users on Exchange 2013 on-premises and others on Exchange Online (Office 365 E3 plan). We have enabled photo sync (PhotosEnabled attribute) in the organization relationship, both on-premises and online, but while
Exchange Online users can see all profile pictures, Exchange on-premises can see only on-premises pictures.
It also looks like that online users can see only a low resolution version of on-premises users' pictures.
Do you have any idea how to troubleshoot or fix this, please?
Thanks!

... but Exchange Online doesn't copy his his-res photo to online AD. This would explain why on-premises users cannot see online photos, but vice versa works...
Hi,
Generally, if you upload a hi-res photo in Exchange Online, Exchange will automatically create a 48 pixel by 48 pixel version of that photo and update the user's thumbnailPhoto attribute. Note, however, that the reverse is not true: if
you manually update the thumbnailPhoto attribute in Active Directory, the photo in the user's Exchange 2013 mailbox will not automatically be updated.
Therefore, the user photo would be read by the following method in order:
1. The higher-resolution photo which is cached to 648 pixels by 648 pixels in Exchange Online\2013 used for Lync 2013.
2. The higher-resolution photo which is cached to 96 pixels by 96 pixels in Exchange Online\2013 used for OWA, Outlook and Lync 2013.
3. The low-resolution photo which is stored in the user’s ThumbnailPhoto attribute in Active Directory.
In your scenario, please upload a higher-resolution photo in OWA (Settings > Options > account > Edit information > photo > change) for a test Exchange Online user, wait for the photo updates in Exchange and AD. Then check whether this photo
can be viewed by other Exchange Online users and Exchange 2013 users.
Regards,
Winnie Liang
TechNet Community Support

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 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

Exchange online and Exchange 2010 on-premise calendar availability

I am running a hybrid exchange 2010 on-premise and online exchange environment. The online exchange users cannot see calendar availability of anybody on premise. The on-premise users can see the online exchange availability. I can see the
calendar if the calendar is shared, but trying to setup a meeting or calendar appointment still shows the unavailable through all days.
All of the users are using office 365 for outlook on premise and exchange online. If it is only working one way, could it be an autodiscover issue where it is not configured correctly on our on-premise exchange 2010 or online exchange? Which
side would be causing the issue?

I have done a little more research and ran the following in powershell:
[PS] C:\Windows\system32>Get-FederationInformation -domainname weiman.com
RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
TargetApplicationUri : outlook.com
DomainNames           : {Weiman.onmicrosoft.com, weiman.com, Weiman.mail.onmicrosoft.com}
TargetAutodiscoverEpr : https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
TokenIssuerUris       : {urn:federation:MicrosoftOnline}
IsValid               : True
[PS] C:\Windows\system32>Get-OrganizationRelationship | FL
RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
DomainNames           : {herbertstanley.com, weiman.com, Weiman.mail.onmicrosoft.com}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : True
DeliveryReportEnabled : True
MailTipsAccessEnabled : True
MailTipsAccessLevel   : All
MailTipsAccessScope   :
TargetApplicationUri : outlook.com
TargetSharingEpr      :
TargetOwaURL          : http://outlook.com/owa/herbertstanley.com
TargetAutodiscoverEpr : https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled : True
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : On Premises to Exchange Online Organization Relationship
DistinguishedName     : CN=On Premises to Exchange Online Organization Relationship,CN=Federation,CN=WEIMAN,CN=Microsof
                        t Exchange,CN=Services,CN=Configuration,DC=herbertstanley,DC=com
Identity              : On Premises to Exchange Online Organization Relationship
Guid                  : 26b4ec5d-fe93-473e-b451-1f9aa2e94ebb
ObjectCategory        : herbertstanley.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 1/13/2014 1:25:54 PM
WhenCreated           : 12/17/2013 1:04:32 PM
WhenChangedUTC        : 1/13/2014 7:25:54 PM
WhenCreatedUTC        : 12/17/2013 7:04:32 PM
OrganizationId        :
OriginatingServer     : gemini.herbertstanley.com
IsValid               : True
I am not sure why we have that value for the OriginatingServer. That server is a backup domain controller, not the server that houses the on-premise exchange.
I then ran the set-OrganizationRelationship and get the below error.
[PS] C:\Windows\system32>Set-OrganizationRelationship -Identity weiman.mail.onmicrosoft.com -targetapplicationUri outloo
k.com -TargetAutodiscoverEpr https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
The operation couldn't be performed because object 'weiman.mail.onmicrosoft.com' couldn't be found on 'gemini.herbertst
anley.com'.
    + CategoryInfo          : NotSpecified: (0:Int32) [Set-OrganizationRelationship], ManagementObjectNotFoundExceptio
   n
    + FullyQualifiedErrorId : F2215CB2,Microsoft.Exchange.Management.SystemConfigurationTasks.SetOrganizationRelations
   hip
How do I change the originating server to be my exchange server?

Cutover Migration to Exchange 2013 On-premises

I have two clients who will be merging their on-prem Exchange
organizations. Different forests. I've done many cutover migrations to
Office 365 for other clients so I'm familiar with the process. My
question is: Is it possible to do an O365-style cutover migration (create migration endpoint, cutover batch, etc.) from
an on-prem Exchange 2010 server to an on-prem Exchange 2013 server using
the same steps?
Thanks in advance for any input.
Steve

Hi,
Based on my knowledge, the Cutover Migration is used for migration to Exchange online. There is no related document about
Cutover Migration from Exchange 2010 to Exchange 2013.
To perform Exchange 2010 corss-forest migration to Exchange 2013, you need to use Active Directory Migration Tool (ADMT) migrate user accounts.
Here is a related blog which may help you. (Even though this article is for Exchange 2010 corss-forest migration, it's also applies to cross-forest migration from Exchange 2010 to Exchange 2013.)
http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2013 on-premises pricing

Hello,
I'm looking for prices of Exchange 2013. I have one server + 20 users. I suposed need one server licence + 20 CALs, but I'm not sure about prices of CAL, if I look for on the internet I can find several prices, since 3 $ to 90$. We only needs a simple
licence for mail, contact and calendar, but a permantly licence.
When I will know the right price I will compare with Online solution.
Thanks in advance.
jspt

I would suggest you to call Microsoft Licensing for accurate information. And they will be able to give you an estimate based on your requirement.
http://www.microsoft.com/licensing/
Blog |
Get Your Exchange Powershell Tip of the Day from here

Lync 2010 with Exchange 2013 UM

Hi,
I am currently in the early stages of a large migration from Exchange 2010 to Exchange 2013. We have moved some test user mailboxes over to Exchange 2013 however have stumbled at the UM integration.
We have 2 x CAS and 3 x Mailbox servers with Lync 2010.
When a user diverts his/her calls to VM, the calls just cuts off and we get "Unable to establish a connection. No connection could be made because the target machine actively refused it 1.1.1.2:5061.
We get this message for all 3 Mailbox servers that it attempts to route the call too. Mailboxes servers listen on 5063 for TLS in Exchange 2013 and these cannot be changed. So what is going wrong with my setup?
Only the CAS are members of the DialPlan (we have tried putting the mailboxes servers in the dial plan with no avail).
Shouldn't the CAS servers redirect Lync to the Mailbox servers on 5063 instead of 5061? Why is Lync trying to connect on 5061 (I know why, but how do I stop it!)
Many Thanks,
Eddie

In my case it were Active Directory attributes of object
CN=MCA1,CN=Servers,CN=Exchange AdmGr...DC=local,DC=com
The attributes
msExchUM* weren't configured at all, despite being set by GUI and PShell. I had to set them manually through ADSIedit.msc and UM began to work after restarting Lync Server.
I need to investigate further why they aren't set.

Imceainvalid on sent emails - Outlook 2013 and Exchange 2013 on premise

Hi All
I have a customer that has had a ongoing issue for some time now and I have had no luck in resolving it. I can see the exact same issues highlighted by other people but generally this relates to older office version and/or older exchange.
Issue: Error after sending email:
IMCEAINVALID -
Remote Server returned '550
5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP
address (IMCEAINVALID-)'
[email protected]
Cause:
If you check the properties of the To/CC addresses (only the display name is filled out as the email address, the email address field itself and "type" are not filled (does not always occur and not for ALL
recipients of email)
Checks:
There are no local contacts for these email addresses in outlook. The auto complete cache has also been cleared. Running exchange in cached mode is not an available option due to the setup.
Email details:
These emails are generated by third party software however not the same software. This is occurring on emails generated into the outlook client by software Rosetta as well as by Mimecast plugin to download archivedemails(then reply to all). This is also
an intermittent issue and does not occur every time with all the emails.
Search:
All searches I have done seem to mainly point to the auto complete option in outlook but this is not the cause of this in my scenario. There was also a known issue in Office 2007 I believe with a office update to resolve, but this is Outlook 2013.
Any assistance would be appreciated.

Hi,
If you just create an email directly from Outlook, has this issue occurred ever?
You can also start Outlook in Safe Mode and then use the 3rd-party software to send some test emails, check if the problem persists.
To start Outlook in Safe Mode:
Press Win + R, type "outlook.exe /safe" in the blank box, press Enter.
In Outlook Safe Mode, all add-ins will be disabled. If there's no problem in Outlook Safe Mode, disable the suspicious add-ins to verify which one caused the problem.
Since the issue is intermittent, you may need to test for a period.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

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

Setting up Push Notification from on premise exchange 2013

We have been trying to get push notifications to work with the OWA for IPhone/Ipad app using the information provided in the below TechNet article. We have an exchange 2013 on premise installation and going by the info in the article, are attempting to create
a relationship with the office 365 servers. We already have our domain configured in office 365. When we attempt to create the New-Authserver, we receive the following error.
New-AuthServer MicrosoftSts -AuthMetadataUrl https://accounts.accesscontrol.windows.net/metadata/json/1/?realm=DOMIAN
Cannot acquire auth metadata document from 'https://accounts.accesscontrol.windows.net/metadata/json/1/?realm=DOMAIN.
Error: An exception occurred during a WebClient request..
    + CategoryInfo          : ResourceUnavailable: (:) [New-AuthServer], AuthMetadataClientException
    + FullyQualifiedErrorId : [Server=MAIL SERVER,RequestId=9dd5e9ff-71cc-455f-9efb-5bb98c2d1f83,TimeStamp=5/13/2014 9:1
   3:13 PM] [FailureCategory=Cmdlet-AuthMetadataClientException] DEDA18E3,Microsoft.Exchange.Management.SystemConfigu
rationTasks.NewAuthServer
    + PSComputerName        : CAS server
http://technet.microsoft.com/en-us/library/dn511017(v=exchg.150).aspx
The Oauth certificate was successfully created and exported to the various mail servers. Does anyone have any ideas and what the issue could be?
Thank
Jorge

you may find posting in the Lion Server forum to be more helpful.

Cisco IronPort with On Premise Exchange 2013

Hello All
The company I work for is in the process of starting an on premise Exchange 2007 to Exchange 2013 migration.
Most of the issues I don't think I'll have an issue with; however, where I am not finding much info is in regards to other companies using Cisco IronPort with Exchange 2013.
SO, I have two questions within this topic...
One, is anyone using Cisco IronPort with Exchange 2013 (on premise) out here?
Two, my manager is very controlling. I am the Exchange Admin; however, anything having to do with this IronPort thing with regards to Exchange HE has to do it. So, if anyone is familiar with this IronPort thing... How much work on the IronPort is going
to have to be done during this migration to keep things going?

It shouldn't be any different with Exchange 2013 than it is with Exchange 2007.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 mailbox migration from third party cloud to on premises

Hi,
we are currently utilizing a third party exchange 2013 cloud service to host user's mailboxes ( intermedia), now we implemented an exchange 2013 on-premises environment in Hyper V infrastructure and want to plan migration of mailboxes and related configuration.
cloud and on-premises environment have same SMTP domain ( Eg: XYZ.ORG) and currently an additional Temporary SMTP domain ( XYZ.CO ) used to test the external mailflow of on-premises since xyz.org is registered with cloud.
we need to migrate all mailboxes to on premises and enable XYZ.ORG for on-premises.
Pls suggest the prerequisites,steps, best practices for migration
Thanks in advance.

Hi Sumesh,
1. Please make sure your mails are flowing correctly using XYZ.CO domain. Hope you have XYZ.ORG also created in Exchange.
2. Hope you already created the users in your Exchange2013 server and distribution groups for current users
3. You plan a weekend for changing your MX records.
4. Change MX and A records to a lower TTL days before the migration to decrease DNS update time on migration day
5. Export Hosted Exchange data for each user to PST files using the PST capture tool and move your PSTs to a centralized location.
6. Change MX and A records to point to on-premises Exchange 2013
7. Import Hosted Exchange data from PST files into the new Exchange profiles
Please check these as well
http://community.office365.com/en-us/b/office_365_community_blog/archive/2011/08/15/exchange-hybrid-configuration-tips-moving-cloud-based-mailboxes-to-the-on-premises-organization.aspx
http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/microsoft-pst-capture-tool-part1.html
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Migrate Office 365 To On-Premise Exchange 2013

hello
My client attempts to migrate the mailboxes hosted from Office 365 to Exchange 2013 on-premise hosted in the client's company.
However, despite all attempts , it appears that no procedure works correctly. All's time , something wrong appears Inside the process.
Indeed, on Office 365 we don't see the servers in our on-premise exchange 2013.
the Exchange Hybrid are set correctly and to exchange 2013 migration attempts to run Office 365. (MRS proxy select)
All servers are in the same Update. My client can't update with the last CU6 all server and want to stay with the CU3
Thanks for your read and for your help
Best regard
Alexis

Bonjour,
J'ai deja réalisé ce type de mission, si celle-ci est tout à fait possible en utilisant uniquement les outils intégrés à Exchange, elle nécessite beaucoup de préparation, notament en terme d'AD, et selon la configuration dans laquelle vous êtes, peut etre
*non* transparente pour vos utilisateurs.
" My client can't update with the last CU6 all server and want to stay with the CU3"
C'est par contre un point plus que géneant, le CU3 n'est plus supporté par MS, la compatibilité avec O365 n'est donc pas garantie.
Si vous souhaitez un echange plus sérieux sur ce sujet, vous pouvez me contacter.
Bruce Jourdain de Coutance - Consultant MVP Exchange http://blog.brucejdc.fr

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Lync Online vs Exchange 2013 On Premise

Similar Messages

Maybe you are looking for