ActiveSync in Exchange 2007 and 2013 Coexistence

Hi,
I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
autodiscover works well for users on both 2007 and 2013
I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
I have A records configured for both names on my public DNS and internal DNS
THE ISSUES
testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
Existing users on exch2007 can no longer receive mails on their mobile devices
URLs
Exchange 2007
Exchange 2013
Internal owa
mydomain.com/owa
mail.mydomain/owa
External owa
legacy.mydomain.com/owa
mail.mydomain.com/owa
AutoDiscover
mail.mydomain.com
mail.mydomain.com
EWS
legacy.mydomain.com
mail.mydomain.com
ECP
mail.mydomain.com
Internal ActiveSync
legacy.mydomain.com
mail.mydomain.com
External ActiveSync
$null
mail.mydomain.com
OutlookAnywhere
legacy.mydomain.com
mail.mydomain.com
I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
Any help on this would be much appreciated ..
Richard ..
..forever is just a minute away*

You don't need to use a legacy URL for ActiveSync in Exchange 2013.  It will proxy ActiveSync for Exchange 2007 just fine.  In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition.  I recommend
you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

  • Exchange 2007 and 2013 coexistence

    Hi,
    we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server)  i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
    I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
    Thanks

    Hello,
    Please check your DNS configuration and ISA/TMG rules.
    We recommend you use TMG or UAG.
    You can refer to the "TMG rules" section in the following article:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Cara Chen
    TechNet Community Support

  • GAL and Free Busy Information during Exchange 2007 and 2013 coexistence

    Hello Everyone,
    I am finishing up an Exchange 2013 migration from 2007.  I am currently still in coexistence and had some questions around the Global Address List and Free Busy Information.
    How to I tell if my clients are pulling address book information from my Exchange 2013 or 2007 Global Address List?  I don't want to remove the 2007 system if the clients are pulling from it.  All mailboxes are moved to Exchange 2013.
    How do I make sure my clients are pulling the Fee Busy Information from Exchange 2013 or 2007?  If I remove my 2007 servers will my clients lose Free Busy Information?
    How do I tell what Exchange version my clients are getting this information from?
    Thanks for any assistance!
    Ian...

    Hello,
    Free/busy information are retrieved from user’s mailbox by EWS service.
    GAL(I think you may refer to OAB), we can use the following command to get it’s generated server:
    Get-OfflineAddressBook |FL
    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

  • Free/Busy not working Exchange 2007 and 2013 co-existence

    Hi,
    I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
    works correctly, but between Exchange 2007 and 2013 it's not working.
    I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
    The internal and the external URLs are set to https://legacy.mydomain.com/....
    What am I missing?
    Thanks & Kind Regards,
    Jürgen

    Hi,
    According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
    1. Does the issue happen to all users or specific users?
    2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
    3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
    create a new Outlook profile
    to have a try.
    4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
    Virtual directories settings in Exchange 2007:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
    Certificate and Virtual directories settings in Exchange 2013:
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
    5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
    If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

    Hi
    We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
    I'm now testing with a few test users I've migrated from 2007 to 2013.
    Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
    Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
    When I start Outlook, I get the error Unable to open the default mail folders
    When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
    When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action" 
    Thanks for any help you could provide
    Martin

    Changed the
    ExternalClientAuthenticationMethod  for the 2007 server.
    Output for  Get-OutlookAnywhere | fl *method*
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
    asking for credentials.
    If I dig further and try to manually configure server settings:
    If I specify the Exchange 2013 server and try a 'Check
    Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
    If I specify the Exchange 2007 server and try a 'Check
    Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
    Any other thoughts on this issue?
    Thanks,
    Martin

  • Exchange 2010 and 2013 coexistence Internal and external URL

    Hi all,
    been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
    Still i dont get any smarter.
    Here is scenario:
    Exchange 2010
    Cas1
    Cas2
    Mailbox1
    Mailbox2
    Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
    Exchange 2013
    CAS+Mailbox
    Cas+Mailbox
    DNS
    mail.exchange.com pointing to VIP (kemp loadbalancer)
    Autodiscover ( pointed to same vip ,kemp load balancer)
    Outlook anywhere on all servers (2010 and 2013)
    Internal ( pointing to VIP on Kemp)
    External ( pointing to external IP,then it passes firewall that again passes to kemp)
    Problem we are having is when migrating users from Exchange 2010 - 2013.
    Users using Outlook 2010
    restart of outlook and mail  works fine.
    OWA works fine
    Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
    Users using Outlook 2013
    Outlook in disconnected status,only fix is to create new profile.
    OWA works fine
    Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
    Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
    Where is the config wrong?
    Thanks!
    Please 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. Thank you! Off2work

    Hi Martina,
    did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
    Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
    Tried repair Outlook profile,no og.Only fix is to setup New account.
    Any more tips?
    thanks!
    Please 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. Thank you! Off2work

  • Exchange 2007 and 2013 Co-existnec - ActiveSync Issue

    Hi
    We have introduced Exchange 2013 servers in our existing Exchange 2007 environment. We have a customized Exchange 2007 ActiveSync setup i:e we created a custom separate website in IIS for ActiveSync to serve the ActiveSync devices. After the introduction
    of Exchange 2013 CAS servers, when we installed the new certificate on them and configured the virtual directory with ActiveSync URLs, the Exchange 2013 servers seems to be receiving Activesync requests but they can't just proxy it to Exchange 2007 for some
    reason. following Warning is logged on Exchange 2013 servers:
    [Eas] Marking ClientAccess 2010 server MIA-EXCAS01.utg.uvn.net (https://mia-excas01.utg.uvn.net/Microsoft-Server-ActiveSync) as unhealthy due to exception: System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
    at System.Net.HttpWebRequest.GetResponse()
    at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
    We still need to install new Certificate on the Exchange 2007 servers. Wondering what could be the issue here, can Exchange 2013 proxy the connection to Exchange 2007 on a custom website ? or it looks for one under Default Website?
    Can the absence of new certificate (meaning certificate mismatch) lead to this issue?
    Thanks
    Taranjeet Singh 
    zamn

    Actually 2013 can proxy ActiveSync to 2007
    Please follow this.
    1. Set AutodiscoverInternalURL using this command for every CAS server
    Set-ClientAccessserver -identity -CAS1 -AutodiscoverInternalURI
    https://mail.yourcompany.com/autodiscover/autodiscover.xml (for FQDN , using your CAS NLB name if exist)
    2. Set OWA virtualdirectoy (2013) via EAC
    Internal URL : https://mail.yourcompany.com/owa External URL : https://mail.yourcompany.com/owa
    3. Set ECP virtualdirectory (2013) via EAC
    Internal URL : https://mail.yourcompany.com/ecp External URL : https://mail.yourcompany.com/ecp
    4. Set OAB virtualdirectory (2013) via EAC
    Internal URL : https://mail.yourcompany.com/OAB External URL :
    https://mail.yourcompany.com/OAB
    5. Set EWS virtualdirectory (2013) via EAC
    Internal URL : https://mail.yourcompany.com/EWS/Exchange.asmx External URL :
    https://mail.yourcompany.com/EWS/Exchange.asmx
    6. Set ActiveSync virtualdirectory (2013) viaEAC
    Internal URL : https://mail.yourcompany.com/Microsoft-Active-Sync
    External URL : https://mail.yourcompany.com/Microsoft-Active-Sync
    For 2007
    1. Set AutodiscoverInternalURL using this command for every CAS server
    Set-ClientAccessserver -identity -CAS1 -AutodiscoverInternalURI
    https://mail.yourcompany.com/autodiscover/autodiscover.xml (for FQDN , using your CAS NLB name)
    2. Create DNS record
    legacy.yourcompany.com = your CAS2007 NLB (if exist)
    3. Set OWA virtualdirectory (2007) via EMC
    External URL = https://legacy.yourcompany.com/owa
    4. Set ActiveSync (2007) via EMC
    Internal URL = https://serverFQDN/Microsoft-Active-Sync   <<<< Using for proxy
    External URL =
    https://legacy.yourcompany.com/Microsoft-Active-Sync <<<< Using for redirect
    5. OAB via EMC
    External URL = https://legacy.yourcompany.com/OAB
    6. EWS via Exchange shell
    External URL = https://legacy.yourcompany.com/EWS/Exchange.asmx
    FYI

  • Coexistence with Exchange 2007 and 2013

    Hi everyone ,
    i migrated this week to exchange 2013 in coexistence with exchange 2007 ,,,, is it normal that i cannot create anymore a mailbox on the exchange 2007 server even with the console (ecp) in 2013 ?? 
    thanks

    Provided an answer on your other thread
    https://social.technet.microsoft.com/Forums/en-US/393a2406-5202-4d21-9583-2e4beed574be/create-mailbox-on-2007?forum=exchangesvrgeneral
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • Exchange 2007 and 2013 coexistent

    Hi
    Ive installed exchange 2013 in my domain where exchange 2007 is installed. The servers can see each other and mailbox migration works.
    The problems im having is with owa, outlook and activesync. When going (internally) to exchange2013/owa site and login in with a user thats on 2007 i have to log in twice, once on each owa site. I belive that the same will happen with activesync and thus
    not work?
    the users ive move to exchange 2013 are getting promted to type in user and pass every time!
    my setup is exchange 2007 sp3 ru11 and exchange 2013 without any cu
    thanks for the help

    The most common problem that I have seen has caused by having the wrong authentication methods configured for Outlook Anywhere on both the new and legacy server. You might want to start a new thread for that problem.
    Martina Miskovic

  • Exchange 2007 and 2013 coexistance Problem

    We are in the process to migrate our current Exchange 2007 to Exchange 2013.
    Our environment is as follows:
    HT01= Hub CAS Server (Exchange 2007)
    MB1, MB2 = Mailbox CCR Cluster (Exchange 2007)
    CAS1= CAS Server (Exchange 2013)
    MBNew1, MBNew2 = Mailbox Servers (Exchange 2013)
    Emails for users that are on Exchange 2007 can send and receive external emails. But they cannot send emails to users that are on Exchange 2013.
    Users on Exchange 2013 can send/receive externally, send to Exchange 2007 users, but cannot receive emails from Exchange 2007 Users.

    Are you getting any NDR? Post it.
    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 2007 to 2013 coexistence Legacy access

    I’ve successfully installed Exchange 2013 CU1 (in a cloned environment so I’m no harm done
    J) and most thinks seems to work but OWA and Active Sync on EX2007 mailboxes give me some headache.
    I’ve created a legacy.company.com DNS record, reconfigured the virtual directories on EX2007 and set OWA to FBA/basic.
    OWA IS redirected to EX2007 legacy URL but authentication is not being passed through and you have to enter username password again at the EX2007 OWA site. Active Sync (tested on Iphone) works but you have to enter password at every sync.
    What could I be missing?
    /Søren Emig

    Fiona,
    Reading through the first technet link, it makes it seem as though redirection should happen silently and the FBA should be passed to the CAS2007 server seemlessly.  
    CAS2007 will consume that hidden form's data, authenticate the user and:
    Retrieve and render the user's mailbox data from the Exchange 2007 mailbox server and provide the data view back to the user.  The response will contain an FBA cookie for the legacy namespace, and from that point on all user activity within the session
    will go to legacy CAS only.
    Or proxy the request to the Exchange 2003 mailbox server and provide the data view back to the user.  The response will contain an FBA cookie for the legacy namespace, and from that point on all user activity within the session will go to legacy CAS
    only.
    That sounds like the OWA page should render without the user logging in a second time.  Also, if you look at the docs for Exchange 2010, the scenario is the same. http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    CAS-01 will look for an Exchange 2007 ExternalURL property
    that has an ExternalAuthenticationMethods setting
    that's identical to theInternalAuthenticationMethods setting
    on the Exchange 2010 Client Access server. If the settings match, CAS-01 will redirect to this external URL. If source and target CAS have Forms Based Authentication (FBA) enabled, the source CAS issues a hidden form back to the browser that contains the user’s
    credentials and FBA settings, along with the redirect URL. This is transparent to the user.
    Now if the SSO code for Exchange 2013 is not ready, that is another matter.  But there is no documentation that I could find explicitly stating this.

  • Autodiscover Exchange Server 2007 and 2013 Coexistence

    Hello
    We are having some issues where some users are not being notified when their mailbox is being migrated to E2013.
    Before 2013, we never had a load balanced solution for CAS in Exchange Server 2007 or a single name space.
    Below is our current config
    AutoDiscoverServiceCN          : Server2K7CASpd
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2k7CASdr
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {USChicago, UKLondon, SGSingapore}
    AutoDiscoverServiceCN          : Server2013CASPD01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASPD02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR02
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    AutoDiscoverServiceCN          : Server2013CASDR01
    AutoDiscoverServiceClassName   : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
    AutoDiscoverServiceGuid        : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope          : {UKLondon}
    I believe that we should change the AutoDiscoverServiceInternalUri on the two 2007 CAS to ALSO be the same as our 2013 CAS.
    We know that when Outlook is opened, Autodiscover will respond with any of the 6 available CAS, and we think that those Outlook clients that are misconfigured, are those that are not getting notified when their Mailbox is moved to E2013.
    Thanks

    We are also getting inconsistent results using the Test-OutlookWebServices PS
    Test 1
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 76 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 558 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.domain.local/EWS/Exchange.asmx. The elapsed time
              was 46 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1013
    Type    : Error
    Message : When contacting https://mail.domain.local/Rpc received the error The remote server returned an error: (404) Not
              Found.
    Id      : 1017
    Type    : Error
    Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.domain.local/Rpc. The elapsed time was 93
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.
    Id      : 1021
    Type    : Information
    Message : The following web services generated errors.
                  Contacting server in EXPR
              Please use the prior output to diagnose and correct the errors.
    Test 2
    Test-OutlookWebServices -Identity [email protected] | fl
    Id      : 1003
    Type    : Information
    Message : About to test AutoDiscover with the e-mail address [email protected].
    Id      : 1006
    Type    : Information
    Message : The Autodiscover service was contacted at https://legacy.Domain.local/Autodiscover/Autodiscover.xml.
    Id      : 1016
    Type    : Success
    Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 46 milliseconds.
    Id      : 1015
    Type    : Success
    Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
              time was 0 milliseconds.
    Id      : 1014
    Type    : Success
    Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.Domain.local/UnifiedMessaging/Service.asmx.
              The elapsed time was 15 milliseconds.
    Id      : 1016
    Type    : Success
    Message : [EXPR]-Successfully contacted the AS service at https://legacy.Domain.local/EWS/Exchange.asmx. The elapsed time
              was 78 milliseconds.
    Id      : 1015
    Type    : Information
    Message : [EXPR]-The OAB is not configured for this user.
    Id      : 1014
    Type    : Information
    Message : [EXPR]-The UM is not configured for this user.
    Id      : 1017
    Type    : Success
    Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://legacy.Domain.local/Rpc. The elapsed time was 187
              milliseconds.
    Id      : 1006
    Type    : Success
    Message : The Autodiscover service was tested successfully.

  • OWA Coexistence 2007 and 2013

    Hi
    We are currently coexisting exchange 2007 and 2013 servers. Everything works fine, except OWA from the external.
    Our domain is limocar.int. 
    Exchange 2007: exch2007
    Exchange 2013: exch2013
    On our internal DNS server, I've created legacy.limocar.int pointing to exch2007's IP address.
    Exch2013 internal OWA: https://exch2013.limocar.int/owa
    Exch2013 external OWA: https://mail.ourcompany.com/owa (where "ourcompany" is our company name) 
    EXCH2007 internal OWA was set to $NULL
    EXCH2007 external OWA: https://legacy.limocar.int/owa
    From the outside, I can log any 2013 users. But when I try to log a 2007 user, it changes the browser url to legacy.limocar.int, which indeed gives an error "The page cannot be displayed"
    What am I doing wrong? instead of using legacy.limocar.int, should I use legacy.ourcompany.com? If so I will ask our public DNS to create legacy.ourcompany.com
    Thanks for your help,
    Martin

    The legacy namespace is used not only for OWA.
    As Krishna mentioned, all OWA users will hit the Exchange 2013 OWA URL (ex. OWA.yourcompany.com). The Exchange 2013 will check where the user mailbox resides and if it is an Exchange 2007 MBX, it will use the legacy URL that is configured in Exchange 2007
    (ex. legacy.yourcompany.com) and silently redirect the clients to it.
    The reason you need to seriously consider using the same external and internal URL (***.youcompany.com) and avoid using internal FQDN or NetBIOS names is the so called BR v1:
    ===================================================
    Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, Version 1.0
    BR 1.0 - Adopted by CA/Browser Forum (includes over 30 CA members and major browser vendors: Microsoft, Apple, Mozilla, Google, Opera)
    Effective as of July 1, 2012
    • CA SHALL NOT issue a certificate with an Expiry Date later than 1 November 2015 with a SAN or Subject Common Name field containing a Reserved IP Address or Internal Server Name.
    • Effective 1 October 2016, CAs SHALL revoke all unexpired Certificates whose SAN or Subject Common Name field contains a Reserved IP Address or Internal Server Name.
    ===================================================

  • Autodiscover service overlap between Exchnage 2007 and 2013 mailboxes

    Hi,<o:p></o:p>
    I have Exchange 2007 Legacy environment and owa/rpc/activesync/autodiscover configured with DNS name owa.domain.com.<o:p></o:p>
    I have installed Exchange 2013 and owa/rpc/activesync/autodiscover configured with DNS name mobile.domain.com.<o:p></o:p>
    Its a requirement to retain different URL for Exchange 2007 and 2013.<o:p></o:p>
    Now...Exchange 2007 users RPC over http is broken because their outlook rpc setting is automatically getting configured to mobile.domain.com which belongs to Exchange 2013.<o:p></o:p>
    I know I have thought about updating the hostfile for Exchange 2007 clients to achieve this.Without changing the URL and
    retaining the existing DNS names, can we prevent RPC over https outlook setting changes for Exchange 2007 users alone?

    Hi,
    You can deploy localxml for Exchange 2007 user:
    http://support.microsoft.com/kb/2212902/en-gb
    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

  • Lync 2010 and 2013 coexistence - DNS

    Hi all,
    we are planning to upgrade from Lync server 2010 to 2013.During this mode,what is best to do regarding DNS?
    Should we just keep existing ones and let Lync server proxy users, or do we need to point dns (internal and external) to the new 2013 server?
    Like in Exchange 2010 and 2013 coexistence we had to point all dns to 2013 server,or users wont be proxied.
    These are the DNS:
    lyncdiscoverinternal
    meet,dialin,admin
    _sipinternaltls._tcp.domain.com
    _sipfederationtls._tcp
    sip.domain.com
    Other DNS i might forgot?
    thanks!
    Please 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. Thank you! Off2work

    If you don't want to cut everyone over at once, you'll need different FQDNs for external web services between the pools, because mobility and meetings will use them both, regardless of where lyncdiscover and meet point. 
    If you want to keep the same name, that's fine, but you'll have to cut over in one big shot.
    Also, pick a different name for the internal vs external web services.  Mobility uses the external name, even when connecting on internal WiFi, so you'll want to redirect requests on port 443 to port 4443 for that and make it available internally. 
    If you have the same name for the internal web services, then internal requests will also use that path, which can cause issues or at the least route through a reverse proxy for no good reason.
    Correct about pool FQDN being unique, also internal and external web service FQDNs unless you move everyone in one shot and don't care.
    Everything else is pretty much a repoint when you're ready situation.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Maybe you are looking for