Exchange 2013/2010 - Co-Existence, URLs.

Hey Team,
I am sure this is well documented and i for some reason cant seem to get good solid answer. But here is my questions. what are the correct URL settings for (OWA, ActiveSync, EWS) etc for Exchange 2013/2010 in a coexistence scenario?
1) All servers in the same ad site
2) mail. autodiscover, pointed to the 2013 server
3) 2013 server is internet connected.
Am i supposed to clear all the 2010 URLs?, Just the external ones? Use a separate namespace?
Thanks,
Robert
Robert

This is well documented in the below post, I would recommend you check it:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
In Exchange 2010/2013 coexistence scenario, CAS 2013 will proxy all connections to Exchange 2010.
How CAS2013 Picks a Target Legacy Exchange Server
It’s important to understand that when CAS2013 proxies to a legacy Exchange Client Access server, it constructs a URL based on the server FQDN, not a load balanced namespace or the InternalURL value.
When a CAS2013 starts up, it connects to Active Directory and enumerates a topology map to understand all the Client Access servers that exist within the environment. Every 50 seconds, CAS2013 will send a lightweight request to each
protocol end point to all the Client Access servers in the topology map; these requests have a user agent string of HttpProxy.ClientAccessServer2010Ping
Mohammad Saeed Abdelaziz | MCSE 2003 | MCTS: Lync, OCS, Exchange2007 | CCNP | UC Voice Specialist http://lyncrocks.wordpress.com/

Similar Messages

  • Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

    Greetings!  I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
    I am running into some odd behavior.  Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I  receive errors.  OWA works just fine for these Exchange
    2010 mailboxes, it is just Outlook that has the problem.  This is what I am running into:
    1. Outlook uses autodiscover to locate server settings.  It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
    2. It then gives me the settings box for Exchange server and Mailbox.  This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role).  If I then change the server to the Exchange 2010 CAS server,
    and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
    3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
    I've been doing as much research on this as I can.  I've tried disabling IPv6 to no avail.  It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards. 
    Any suggestions?  Thanks in advance!

    Hi,
    Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
    You can use your original SSL Cert for your new Ex 2013 environment.
    In dns you want two host A records: mail.domain.com and autodiscover.domain.com
    On your 2013 set your internal and external virtual directories to mail.domain.com
    leave autodiscover and Powershell alone.
    Also set the autodiscover URI to your Certificate name ie. mail.domain.com
    Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
    Thanks.  I wanted to give some additional info before I run any commands.  I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP.  I have a 3 entries for mail.domain, for DNS round robin; basically
    it is listed 3 times for the IP of each of my Exchange 2013 servers.  Does any of this sound problematic?

  • User calendar sharing problem on Exchange 2013 & 2010 co-existence

    Recently, I am trying to upgrade my site to Exchange 2013 from 2010.  Most of the functions are work without problem except 2013 mailbox user try to access the sharing calendar on Exchange 2010 mailbox server.
    e.g. User A is exchange 2010 mailbox user
    user create a calendar 'testing' and sharing with user B
    who is exchange 2013 mailbox user when user B try to add the calendar in OWA, user B get
    'The action couldn't be completed.
    An error occurred and your request couldn't be completed.  If the problem continuesm contact your helpdesk with this HTTP Status code: 500.'
    Actually, the error is 'The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.'
    But there are no problem if user A sharing his own calendar.  User B could add it without problem.

    user B can access the calendar from outlook ? if its still not working from outlook please try to repair outlook profile and check
    Regards
    John
    Thanks for your reply.  However, user B could not add the calendar in OWA 2013.  I think, it doesn't related to outlook profile.

  • Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

    Hi,
    Here is our current scenario;
    Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
    Exchange 2003 - exch1.domain.lan
    Exchange 2010 (SP3) - exch2.domain.lan (local domain name)  /  mail.domain.com.au (external domain name)
    ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
    services to be the external domain name and am running split DNS.
    The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
    I need to repurpose the first Exchange 2010 server once it's removed.
    My high level questions are;
    1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
    2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
    OR does it matter which way I do it?
    I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
    organisation.
    1) Do I configure CAS to be externally facing right from the get go or do I do that later?
    2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
    In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
    names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
    OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
    Any guidance on the above is helpful.
    Thanks.
    Steve

    Hi Steve I will try my best to answer each of these 
    My high level questions are;
    1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
    2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
    OR does it matter which way I do it?
    doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
    to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure. 
    I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
    1) Do I configure CAS to be externally facing right from the get go or do I do that later?
    Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
    2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
    Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
    In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
    names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
    You  can always export the certificate and then import it to the newly installed Exchange 2010.
    OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
    You will only need to setup the CAS array if you are going to use both the server which can be done later.
    Hope that help
    Where Technology Meets Talent

  • Exchange 2003-2010 co-existence environment

    i have exchange 2003 -2010 co-existence environment .
    Everything works fine accept below;weird issue,i tried to re-create routing group connector but issue is same.
    My issue is very simple,The mail flow as below:
    exchange 2003 to outside............
    exchange 2010 to outside ...........works
    exchange 2010 to 2003 ...............works
    exchange 2003 to 2010................is not 

    Hi Huzefa,
    Can you try creating a new bidirectional RGConnector and check?
    New-RoutingGroupConnector -Name "NameOfRG" -SourceTransportServers "Ex2010.contoso.com" -TargetTransportServers "Ex2003.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true
    http://technet.microsoft.com/en-us/library/aa997292(v=exchg.141).aspx
    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.

  • 2013/2010 Co-existence - why outlookanywhere is compulsory ?

    Hi all
    i have been doing several exchange migrations from 2003 /2007 to 2010 and i am inteeding to do my first migration from 2010 to 2013.
    in my orga 2010 we do not use outlook anywhere.
    seems to be easy but i dont get something :
    why should i enable OA on my 2010 cas in order to migrate to 2013? obviously, i m aware of since Ex2013 all traffic goes to RPC/HTTP (rpc/tcp = mapi /rcp no longer exist)
    but during the Co-Existence period,
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array, right ?
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2013, they will connect to the Exchange 2013 MBX through the cas2013, right ?
    But what if we won't intend to use OA on Ex2013 either  ? ( i mean
    leave the external hostname entry blank)
    we dont have to enable OA on ex2010 as mentioned everywhere ?
    i suppose everythin gonne be ok ?
    thanks a lot
    Regards

    you are right but look :
    in place 2010
    outlook connectivity internal (rpc/tcp)
    -outlook.company.com=> casarray
    outlook connectivty external
    - none (vpn require)
    OWA, EWS, ASync.... internal and external
    - mail.company.com
    Co-existence 2010/2013
    outlook connectivity internal (rpc/http)
    -mail.company.com
    outlook connectivity external (rpc/http)
    - not set...
    but as you said it will be routable. so CAS2013 will receive some rpc/http(s) requests but wont be able to proxy to cas2010 because AO anywhere wont be enable on existing 2010 orga ?
    only maiboxes already moved to exchange2013 will be able to connect from outside with AO on 2013.
    so if i conclude, the only reason to enable AO on 2010 orga during a co-existence with 2013 its just to proxy AO request from outside to exchange2010.
    But if mailbox are still on ex2010, if a internal client attempt to connect we wont care about outlook anywhere. just connect with casarray just like before co-existence ?????
    i hope i made myslef clear
    Correct. If you don't enable OA on the 2010 CAS, then any OA connections from the 2013 CAS will fail.
    You can verify this with
    https://testconnectivity.microsoft.com/
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 / 2010 coexistence with different public domains

    Currently in my organization
    1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
    1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
    1x Exchange 2010 Standard w/SP3 - Mailbox
    In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
    miles away. We have no IT staff in any of our field locations.
    We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
    domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
    domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
    domain.local - Our internal Active Directory domain.
    We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
    severely underutilized.
    Goals for the Exchange migration
    My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
    final topology is:
    2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
    2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
    1x VM with Exchange 2013 Standard w/SP1 - Client Access
    1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
    I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
    We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
    until Exchange 2013 SP3 is released.
    Deployment Plan
    Install Exchange 2013 on new VMs.
    Create CAS Array object.
    Configure Exchange 2013 to publish under the new namespace.
    Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
    Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
    Unknowns
    My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
    since we'll be using the new domain for each mailbox we move.
    My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

    Hi,
    From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013. 
    About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
    About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
    About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
    Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
    Checklist: Upgrade from Exchange 2010
    Install Exchange 2013 in an Existing Exchange 2010 Organization
    Upgrade from Exchange 2010 to Exchange 2013
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 & 2010 coexist problem. Authentication Credentials Prompt in Outlook

    Hello Forum
    We have two Exchange servers coexisting together. A new 2013 and a old 2010.
    Everything was setup with the help of the Exchange Deployment Assistant.
    I have had alot of trouble with Outlook 2013 Prompting for credentials on Exchange 2013 Mailboxes. None of the 2010 Mailboxes expericence this popup.
    I solved most of the popup issues with this by changing the ExternalClientAuthenticationMethod to ntlm.(from negotiate)
    http://blog.gothamtg.com/2013/10/15/users-constantly-prompted-for-credentials-after-being-migrated-to-exchange-2013/
    and installing this update for Outlook:
    http://support2.microsoft.com/kb/2899504/en-us
    Now 2013 Mailboxes Work without any anoying popups. Except when they try to open another users mailbox that is located on the old 2010 server or a shared 2010 calander.
    The connection to Exchange 2010 is working if I input the users password, but should it not work without this popup too?
    This connections name acording to Outlook is called: Exchange-Mail RPC/HTTP (remote [NTLM])
    We use the same domain for external and internal autodiscover connections.
    Test Exchange Connectivity Analyzer shows everything ok.
    If i run
    get-outlookanywhere | fl *external*
    (2013 server)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    (2010 server)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    ExternalClientsRequireSsl          : True  
    Only one thing I am wondering here is. If I change my old 2010 Auth Method to NTLM if that will break anything i OWA and so on.
    What do you Guys have setup in your environments and can you point me towards any troubleshooting?
    Thanks!

    For us, the changes made in IIS are permanent, there quite possibly is a powershell way of doing it but I am still getting to grips with PS myself so I don't know.
    I wont plagiarise others work but these two links here give a good explanation between Basic and NTLM. personally, I have always used basic because I always seem to get problems with NTLM, though one time it did work as expected but I forgot what I did to
    get it working now.
    https://social.technet.microsoft.com/Forums/exchange/en-US/92178beb-3310-4363-8848-d022a6e2a77f/basic-vs-ntlm-authentication-outlook-anywhere
    http://www.sysadminlab.net/exchange/outlook-anywhere-basic-vs-ntlm-authentication-explained  

  • 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/2010 coexistence DAG functionality?

    Hi, so this is a bit of a silly question. But I need to make sure I understood the situation correctly.
    I currently have an Exchange 2010 DAG with 2 servers and I am mid way through (In the Exchange Server Deployment Assistant) introducing my first Exchange 2013 server.
    The plan is to make the new 2013 server the active DAG member one of the old 2010 servers the passive member for a short term until that 2010 server is rebuilt to 2013, but that's not going to work is it? Once I migrate a 2010 user to a 2013 database, that
    user only exists in 2013, right?
    Theres no way of adding a 2013 database into a 2010 DAG, so that if the 2013 server is down, the 2010 server will become active?
    Thanks

    No, there is not.  You will build a new Exchange 2013 DAG and move mailboxes from Exchange 2010 to Exchange 2013 mailbox databases.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Missing ECP directory in Exchange 2013/2010

    Hi Folks,
    I have an exchange 2013 and 2010 server running in a domain.
    I was trying to log into the Exchange Admin Centre on Exchange 2013. After typing the credentials the page just refreshed and set the prompt back in the password field.
    Doing a Get-ECPVirtualDirectory results in the message "An IIS directory entry couldn't be created. The error message is Access is denied", Category Info: Not Installed (myserver\ecp (Default Web Site):ADObjectId). FSComputername:(name of exchange
    2010 server).
    I am unable to either create or remove the ECP directory (although it claims one exists).  Opening the exchange management console on my 2010 server shows OWA is set up, but the ECP entry is blank.
    If I try and login to OWA I get the login screen, but after entering credentials I just get HTTP 400 bad request.
    In IIS on my 2013 server, there is an ecp directory with just a web.config and auth directory under the default website, there is also an ecp directory (containing contents) under the 'Exchange Back End' site.
    Does anyone know how to go about re-creating the ECP directory etc.
    Regards
    Andy

    Hi Andy
    Ensure that Microsoft Exchange Security Groups and Exchange Trusted Subsystem group should be a  member of the local admins and restart the server
    Steps:
     Launch IIS Manager Navigate to -> Web Sites -> Default Web Site Right Click on Default Web Site and choose Permissions Add Exchange Trusted Subsystem and grant Full Control Restart IIS Restart the server
    If none of the above works then try the following
    First remove the affected one 
    Get-ECPVirtualDirectory | Remove-ECpvirtualDirectory
    Then create a new one by following below 
    http://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
    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)

  • OWA SSO issues in Exchange 2013 - 2007 co-existence

    This may not be possible. For a multitude of reasons the client needs OWA authentication of Windows Integrated and Basic. As a result I''ve got a double prompt for users still on 2007 for OWA externally.
    Do you have to use Forms Based Authentication to get SSO to work? Is it possible to enable FBA as well as basic and Windows auth?

    FBA is required on the source and destination, yes. You would need to enable that and not use Basic or Windows Auth.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox is located within the local AD site on an Exchange 2007 Mailbox server.
    CAS2013 will initiate a single sign-on silent redirect (assumes FBA is enabled on source and target) to
    legacy.contoso.com. CAS2007 will then facilitate the request and retrieve the necessary data from the Exchange 2007 Mailbox server.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 2007 co-existence Outlook Anywhere issues

    Sorted out all other issues (apart from a SSO issue- another thread) . Activesync, autodiscover etc all working- but Outlook Anywhere does not work for Exchange 2007 external mailboxes. It does work for 2013 mailboxes internally and externally-
    and 2007 mailboxes internally.
    Exchange 2013 SP1. Exchange 2007 Sp3 RU10. Legacy namespace is in use and on certificate. Outlook Anywhere IIS Authentication is set to Basic and NTLM on both 2007 and 2013 servers.  Outlook Anywhere external client authentication is set to Basic.
    Any sugestions what to look at next?

    Tony,
    I apologize for the stupid question, but was Outlook Anywhere working on Exchange 2007 before you started the upgrade?
    When you open command prompt on Exchange 2007 and ping the Exchange 2007 internal FQDN or NetBIOS name, do you get an IPv4 address or you get the IPv6 one?
    Step by Step Screencasts and Video Tutorials

  • Exchange 2013 / 2010 / 2007 - Public Folders

    I have read that legacy public folders and 2013 public folders canot co-exist.
    If I have legacy public folders A, B and C, does this mean...
     that if I migrate folder A to 2013, i cannot maintain a replica on legacy systems, but folders B and C are still accessible
    ..or..
     If I migrate folder A to 2013, I must migrate folders B and C also.
    If I am need to import folder D, from an external Exchange 2013 installation, into my legacy public folder system, is it possible to migrate folder D out of the external 2130 environment into my legacy public folder environment? If so, is there any extra functionality
    2013 PF has that the users will lose if the folders are down graded to legacy?
    Thanks!
    Tom

    Hi,
    User mailboxes on Exchange 2013 servers can connect to legacy public folders, but legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 server.
    Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously.
    Before you migrate public folders, you need to migrate mailboxes to Exchange 2013 first.
    Please refer to the following article.
    http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx
    Besides, here is a related thread for your reference.
    http://social.technet.microsoft.com/Forums/office/en-US/7603f02e-beb4-4c3d-8cb9-613ad806766b/public-folder-migration-from-multiple-exchange-2007-to-exchange-2013?forum=exchangesvrsharingcollab
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2003 - 2010 Co-existence Migration Autodiscover & OAB Issue

    Hi,
    I am in the middle of a Ex2003 to Ex2010 Migration initially through co-existence. Everything has been working perfectly for the last couple of months.
    The first Ex2010 server I installed (EX01.domain.local) was just a temporary server that hosted a handful of users that were imported from another company.
    I have since installed a second Ex2010 server (EX02.domain.local), which will be the permanent 2010 server. The end result will be 1 Ex2010 server only, after I have migrated everyone off EX01 and the 2003 server.
    EX01 and EX02 both have the Mailbox, CAS, & HT roles installed.
    I created the mailbox and Public Folder databases on EX02. I have assigned the Public Folder database to the mailbox database.
    I added EX02 as a Source Server within Hub Transport.
    I've exported the UC/SAN certificate from EX01 and imported it into EX02 and assigned the SMTP, IIS, POP & IMAP services to it.
    I setup the legacy URL for OWA.
    I changed the relevant settings on EX02, eg OWA, ECP, ActiveSync, OAB, AutoDiscoverServiceInternalUri etc to be external domain name that is listed on the certificate, eg mail.domain.com.au. (The SSL certificate is through GoDaddy and they do not allow you
    to put any internal domain names on the certificate).
    So before I installed the second Ex2010 server, everything was working correctly.
    After I installed the second Ex2010 server and performed the steps above, I have noticed a couple of things;
    1) The Autodiscovery test within Outlook works for mailboxes that have been migrated to either of the Ex2010 servers, but fails for mailboxes that are still on the Ex2003 server. It finds the correct URL, https://mail.domain.com.au/Autodiscover/Autodiscover.xml,
    and brings back an HTTP status of 200. However, it says it then fails with (0x800C8203). I tested with Outlook 2003 and 2010. They both fail.
    2) OAB fails to download for clients whose mailbox is still on the Ex2003 server. It fails with (0x8004010F - The operation failed. An object cannot be found). It works for clients with mailboxes on either of the 2010 servers.
    I'm going around in circles reading numerous articles on trying to fix autodiscover. Using Microsoft's MRCA site, autodiscovery works externally for clients on the Ex2010 servers, but not on the 2003 servers, (which I thought was how it worked anyway as
    autodiscovery doesn't work on Ex2003).
    Is this the same for internal users. I'm not sure if I'm chasing my tail by trying to fix something that doesn't need fixing, but obviously the OAB should work.
    Any suggestions are grateful.
    Thanks.
    Steve

    Output from get-webservicesvirtualdirectory | fl
    RunspaceId                      
    : 12158f4a-101e-45c7-b35a-02c6b5652e41
    CertificateAuthentication       :
    InternalNLBBypassUrl            
    : https://ex01.domain.local/ews/exchange.asmx
    GzipLevel                      
    : High
    MRSProxyEnabled                
    : False
    MRSProxyMaxConnections         : 100
    Name                            
    : EWS (Default Web Site)
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    LiveIdSpNegoAuthentication     : False
    WSSecurityAuthentication        
    : True
    LiveIdBasicAuthentication       : False
    BasicAuthentication            
    : True
    DigestAuthentication            
    : False
    WindowsAuthentication          
    : True
    MetabasePath                    
    : IIS://EX01.domain.local/W3SVC/1/ROOT/EWS
    Path                            
    : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
    ExtendedProtectionTokenChecking : None
    ExtendedProtectionFlags        
    ExtendedProtectionSPNList       : {}
    Server                          
    : EX01
    InternalUrl                    
    : https://mail.domain.com.au/ews/exchange.asmx
    ExternalUrl                    
    : https://mail.domain.com.au/EWS/Exchange.asmx
    AdminDisplayName                
    ExchangeVersion                
    : 0.10 (14.0.100.0)
    DistinguishedName              
    : CN=EWS (DefaultWebSite), CN=HTTP, CN=Protocols, CN=EX01, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Administrative Groups,CN=CompanyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Identity                        
    : EX01\EWS (Default Web Site)
    Guid                            
    : fd59fcca-87aa-4c7c-87d9-6ddeef4ca9e9
    ObjectCategory                  
    : next.lan/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
    ObjectClass                    
    : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
    WhenChanged                    
    : 28/03/2014 11:25:50 AM
    WhenCreated                    
    : 29/12/2013 9:42:33 AM
    WhenChangedUTC                  
    : 28/03/2014 12:25:50 AM
    WhenCreatedUTC                  
    : 28/12/2013 10:42:33 PM
    OrganizationId                  
    OriginatingServer              
    : DC2.domain.local
    IsValid                        
    : True
    RunspaceId                      
    : 12158f4a-101e-45c7-b35a-02c6b5652e41
    CertificateAuthentication       :
    InternalNLBBypassUrl            
    : https://ex02.domain.local/ews/exchange.asmx
    GzipLevel                      
    : High
    MRSProxyEnabled                
    : False
    MRSProxyMaxConnections         : 100
    Name                            
    : EWS (Default Web Site)
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    LiveIdSpNegoAuthentication     : False
    WSSecurityAuthentication        
    : True
    LiveIdBasicAuthentication       : False
    BasicAuthentication            
    : True
    DigestAuthentication            
    : False
    WindowsAuthentication          
    : True
    MetabasePath                    
    : IIS://EX02.domain.local/W3SVC/1/ROOT/EWS
    Path                            
    : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
    ExtendedProtectionTokenChecking : None
    ExtendedProtectionFlags        
    ExtendedProtectionSPNList       : {}
    Server                          
    : EX02
    InternalUrl                    
    : https://mail.domain.com.au/EWS/Exchange.asmx
    ExternalUrl                    
    : https://mail.domain.com.au/ews/exchange.asmx
    AdminDisplayName                
    ExchangeVersion                
    : 0.10 (14.0.100.0)
    DistinguishedName              
    : CN=EWS (Default Web Site), CN=HTTP, CN=Protocols, CN=EX02, CN=Servers, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Administrative Groups,CN=CompanyA,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Identity                        
    : EX02\EWS (Default Web Site)
    Guid                            
    : e592adcd-18c2-4c4b-bd89-fca95e9e9622
    ObjectCategory                  
    : next.lan/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
    ObjectClass                    
    : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
    WhenChanged                    
    : 28/03/2014 10:50:54 AM
    WhenCreated                    
    : 27/03/2014 10:34:27 AM
    WhenChangedUTC                  
    : 27/03/2014 11:50:54 PM
    WhenCreatedUTC                  
    : 26/03/2014 11:34:27 PM
    OrganizationId                  
    OriginatingServer              
    : DC2.domain.local
    IsValid                        
    : True

Maybe you are looking for