Exchange 2010-2013 co-existence - need for OWA/ActiveSync legacy namespace?

Hi all
Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?
Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user
was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.
So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.
What did I overlook or not understand, or am I making migration more complex than needed?
Thanks for reading and best regards
/Maurice
PS: here were some of my pre-post readings:
Exchange 2003-2013 co-existence, even better
Exchange 2003-2013 co-existence,
Exchange 2010-2013 co-existence slides,
Upgrading ActiveSync to Exchange 2010,

Hi
Is that because External URL on Internet facing CAS servers were set to Blank，and Users are not able to get Updated URL
Please try to Add the External URL and made sure that all the required configurations are set Appropriately.
Also I suggest posting on Exchange ActiveSync Forum as well
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

Similar Messages

  • Problems with archive mailbox in Outlook, with exchange 2010+2013 co-existence

    Hi!
    We have an Exchange 2010 environment plus one Exchange 2013 MBX server meant for archive mailbox purpose. (We are going to upgrade to 2013 but with over 20.000 mailboxes it will take som time. Therefore we need to co-exist with primary mbx on 2010 and archive
    mbx on 2013 for some time.)
    My primary mailbox is on a 2010 MBX server, and I have today given myself an archive mbx on 2013 MBX server.
    When I use OWA, both my primary mailbox and my archive shows up and everything works 100% fine!
    But when I try Outlook 2010 or Outlook 2013, only my primary mailbox works. The archive mailbox shows up, but generates an error when accessing it:
    "The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance"
    Anyone who knows about this issue? Would we nice to know why it works in OWA but not in Outlook.
    Thanks!
    Trond Jenssen

    Hi，
    Please try to recreate a profile to access archieve mailbox.
    If it doesn't make sense, also try Uncheck “Download shared folders” and check it again.
    If you have any feedback on our support, please click
    here
    Wendy Liu
    TechNet Community Support

  • EXchange 2010 & 2013 Co-existence

    Hi,
    I have Exchange 2010 Running currently in 3 Sites. Now I have to introduce Exchange 2013 CU6 on 4th Site (Same Exchange ORg) and migrate all E2k10 Mailboxes to E2k13.
    My Questions is ... What would be the Internal Hostname that I need to mentioned in E2k10 server in Out Look Anywhere ?
    Note: I am using Existing OWA & Autodiscover URL which is running for E2k10 server mai.abc.com & Autodiscover.abc.com .
    On E2k13 I have set External & Internal URL for Outlook anywhere is mail.abc.com .
    I am using E2k10 certificate on E2k13 server as it having same DNS name space mentioned.
    Please suggest !! 
    Amit

    Hi,
    I have Exchange 2010 Running currently in 3 Sites. Now I have to introduce Exchange 2013 CU6 on 4th Site (Same Exchange ORg) and migrate all E2k10 Mailboxes to E2k13.
    My Questions is ... What would be the Internal Hostname that I need to mentioned in E2k10 server in Out Look Anywhere ?
    Note: I am using Existing OWA & Autodiscover URL which is running for E2k10 server mai.abc.com & Autodiscover.abc.com .
    On E2k13 I have set External & Internal URL for Outlook anywhere is mail.abc.com .
    I am using E2k10 certificate on E2k13 server as it having same DNS name space mentioned.
    Please suggest !! 
    Amit
    You wouldn't need to define an internal host. It can be set to the internal FQDN of the 2010 CAS itself. or set to the same as the external hostname if using split DNS.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010/2013 co-existence and Lync integration

    Hello,
    I'm looking at integrating Lync Server 2013 into my lab environment, which consists of a mixed 2010/2013 Exchange environment.
    UM - Exchange 2010
    CAS - Exchange 2013
    MBX - Exchange 2010
    MBX - Exchange 2013
    I've been reading about associating CAS and MBX servers with UM dial plans, when integrating with Lync.
    The Technet articles, and MS Press documentation I've read suggests that
    all CAS and MBX servers need to be associated with the dial plan.
    Does this include the 2010 MBX servers?
    As far as I was aware, in a co-existence environment between 2010/2013 all traffic is proxied to the MBX servers via the CAS 2013 role?
    Does this rule still apply when UM and Lync exist in the environment?
    Also, does the 2010 UM server need to be associated with the Lync UM dial plan, or does the 2013 CAS server handle this traffic as well?
    Thanks
    Matt

    So, just the UM server in 2010 would be associated with the dialplan, you won't even have the option to add a 2010 MBX server.
    The traffic isn't proxied by the 2013 CAS, it's more of a redirect, and yes this happens.  A lot of what will happen under the hood will be somewhat transparent, Lync will determine where it wants to send the UM traffic.  You can
    watch this in the Lync logger by watching SIPStack.
    The 2010 UM server can be associated with the dial plan, but you might not need it unless you're trying to recreate that specifically in your lab.  Exchange 2013 UM can serve mailboxes on an Exchange 2010 server.
    I would suggest just deploying it in your lab and watching what happens, that's half the fun. :)
    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

  • Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

    Hi
    Exchange 2010 users are NOT able to connect to their mailboxes when they go through exchange 2013 OWA address.  We get a message that says following ---> "Something went wrong"
    Following is our URL.  The address is pointing to 2013 CAS loadbalancer VIP.  Outlook anywhere is working fine.  What is going on?
    Important: All my exchange 2010 / 2013 URIs are the same as suggested by Microsoft (Owa, ecp, activesync, ews, autodiscover): --> mail.domain.com/XXX

    Hello Rawa,
    Can you log on Exchange 2010 OWA using its localhost address?
    Please make sure the intenralurl value is set to Exchange 2010’s local host name and set the Externalurl to Null.
    http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
    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

  • Outlook client requirements and Exchange 2010/2013 coexistence

    Good morning!
    A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
    I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
    including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
    Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
    Thanks in advance!

    Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
    http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Missed Call Notification in Exchange 2010/2013 coexistence mode

    Dear all,
    Context:
    Lync 2013 Enterprise Voice, Exchange 2010 and Exchange 2013 in coexistence mode
    Waiting complete migration, some users are always on exchange 2010
    UM role is installed on both exchange server
    The exchange servers UM are attached to only one UM Dial Plan
    Scenario :
    A call to a lync user. The caller hang-up before user announcement
    Problem: Missed call notification doesn't work for user on Exchange 2010 (it's work fine for user on Exchange 2013)
    Voice Messaging works fine
    Troubleshooting / SIP Traces:
    SIP Info is always send to Exchange 2013 even if user is on exchange 2010
    SIP Info sent from Lync FE to Exchange 2013 UM :
    TL_INFO(TF_PROTOCOL) [0]6330.3AE8::02/12/2015-12:25:23.575.015c018e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786->192.168.5.203:5061
    INFO sip:outlook.mydomain.com:5061;ms-fe=exchange2013-UM.mydomain.localdomain;transport=Tls SIP/2.0
    FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;epid=8C75BE2D95;tag=35c2d8a65a
    TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;epid=C4C2F4F6BA;tag=ac126413f
    CSEQ: 43 INFO
    CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
    CONTACT: <sip:LyncFE-2013.mydomain.localdomain;transport=Tls>
    CONTENT-LENGTH: 454
    USER-AGENT: RTCC/5.0.0.0 Inbound Routing (Microsoft Lync Server 2013 5.0.8308.726)
    CONTENT-TYPE: application/ms-rtc-usernotification+xml
    - <UserNotification>
           <User>sip:[email protected]</User>
           <EumProxyAddress>EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain</EumProxyAddress>
           <Time>2015-02-12 12:25:23Z</Time>
           <Template>RtcDefault</Template>
        +  <Event  type="missed">
     </UserNotification>
    ------------EndOfOutgoing SipMessage
    Answer from Exchange 2013 UM
    TL_INFO(TF_PROTOCOL) [1]6330.2DF4::02/12/2015-12:25:23.642.015c2481 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
    <<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786<-192.168.5.203:5061
    SIP/2.0 200 OK
    FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;tag=35c2d8a65a;epid=8C75BE2D95
    TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;tag=ac126413f;epid=C4C2F4F6BA
    CSEQ: 43 INFO
    CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
    VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
    CONTENT-LENGTH: 0
    SUPPORTED: ms-dialog-route-set-update
    SERVER: RTCC/5.0.0.0 MSExchangeUM/15.00.0995.028
    ms-diagnostics-public: 15642;reason="Lync SIP INFO notifications are not supported for legacy users. User: EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain"
    ------------EndOfIncoming SipMessage
    Gerald Cheminant

    Hi,
    This behavior is by design. Exchange 2010 server is not going to accept any SIP messages from Exchange 2013 server because it is not listed as UM IP Gateway. Therefore, even if Exchange 2013 redirected the SIP INFO packet to Exchange 2010, it will fail.
    During migration\coexistance scenario, this feature (Missed call notifications from Lync server) will not work for legacy users whose mailbox is still in Exchange 2010.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Search-Mailbox not attaching the infected emails in target folder and deleting the contents in exchange 2010 & 2013 coexistence

    Dear All,
    I have an issue with deleting circulated spam emails in my environment through search-mailbox
    We have Exchange 2010 & 2013  CU5 environment 
    I followed the search and destroy document for exchange 2010 
    http://windowsitpro.com/exchange-server-2010/search-destroy-email-content-exchange-2010
    Added the user to Discovery Management group
    Created a new role group as below 
    New-RoleGroup "Mailbox Import-Export Management" -Roles "Mailbox Import Export"
    Add-RoleGroupMember "Mailbox Import-Export Management" -Member Administrator
    I ran the below commands
    Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "Administrator" -TargetFolder "Filter" -LogOnly -LogLevel Full
    The above command gets completed successfully and sends the log report  however im unable to see any attachments
    Similarly the deletecontent also gets completed successfully and logs result. But it does not delete the infected emails 
    Search-Mailbox -Identity  "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "administrator" -TargetFolder "filter" -deletecontent -LogLevel Full
    Any idea why it is not fetching the infected emails in zip file and why it is not deleting but it is able to log in the target folder 
    Any help much appreciated
    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)

    Hi All 
    I managed to find the solution. Below command helped me in solving the issue 
    get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -LogOnly -TargetMailbox administrator -TargetFolder filter -LogLevel Full
    get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -TargetMailbox administrator -TargetFolder filter -deletecontent -LogLevel Full
    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)

  • Exchange 2010 - 2013 random auth.owa error

    Hello,
    I have an odd situation where we are preparing 2 exchange 2013 servers to migrate 2010 servers to 
    so currently:
    2x Exchange 2010 (with dag)
    2x Exchange 2013 (with dag).
    Now it's behaving extremely odd when it comes to ECP for the 2013 servers.
    randomly it works and doesn't work.
    i generally try it from localhost on both 2013 servers, and individual server ip's from lets say 4 or 5 places.
    all same login, and admin user is inside mailbox db DAG cluster.
    now the problem:
    it randomly pops up auth.owa error 500 
    when i say random i truly mean random, sometimes everything 100% works, i am able to login 100% from all servers.
    then i check back lets say 2 hours later.. some obtain auth.owa errors while others work.
    What i tried:
    - I rebuild OWA (first with reset, then with remove and re-add method) on both 2013 servers.
    - removed killbit file from 2013's
    - rebuild exchange 2013's (just exchange it self).
    - checked heartbeat monitor boxes and removed the null values.
    It's safe to say i am kind of lost on what to try next. 
    i am also mistefied why it randomly works, i know it's internally loadbalanced, but shutting down 1 of the 2013 servers did not get rid of this strange behavior.
    is it possible that the exchange 2010 servers play a part in this issue?
    Any ideas, any help is very much welcome!.
    Regards,
    Marco
    Key4ce - IT professionals: www.key4ce.eu

    Hi,
    Please check whether the Microsoft Forms Based Authentication service is running on all Exchange servers. 
    Similar thread for your reference:
    https://social.technet.microsoft.com/Forums/exchange/en-US/8cf6886f-a96f-44f1-88ee-bd3a42349fa9/owa-brings-up-logon-screen-but-after-login-gives-http-500-internal-server-error
    Also check the authentication configuration on CAS.
    Get-OwaVirtualDirectory -Server <server name> | fl *auth*
    Set-OwaVirtualDirectory -Identity " server name \owa (Default Web Site)" -FormsAuthentication $true
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 users cant change password in OWA when Cas server is Exchange 2013 cu3

    Running Exchange 2010 and 2013 in mixed mode.  users who is still on Exchange 2010 cant change password in OWA. It worked when it was clean Exchange 2010 installation. Password change is working for users migrated to 2013
    LS

    Hi
    Please follow the below blog which will help you in solving this issue
    http://technet.microsoft.com/en-us/library/bb684904.aspx
    Note: Be careful while modifying the registry settings.
    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.
    Regards,
    Sathish

  • Lync 2010 and Exchange 2007/2013 Co-existence

    Hi,
    I do not work with Exchange, and am only familiar with how Lync 2010 actually interacts with the product.  If today we are working with Exchange 2007, and in the future there are plans to migrate to Exchange 2013, I am assuming there will be some sort
    of co-existence required for a period of time.
    What I am wondering is if anyone has encountered (or is aware of) any issues that may arise as a result of having Lync 2010 deployed in an environment with both of the above versions of Exchange in parallel.
    Would the differences essentially come down to where the user's mailbox was homed?  In other words, would a Lync 2010 user receive the integration features that come with the particular version of Exchange they are homed on?  Or would having both
    versions of Exchange in one environment potentially impact Lync 2010 in some way?
    Thanks so much in advance for any help you can provide, as I have had trouble finding answers so far.

    sorry to reopen the thread...
    Hi all,
    Does anyone know of any update regarding the following link ??
    http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/

  • Outlook 2013/ Exchange 2010 User Mailbox reached Limit and OWA is not reachable

    Hello Folks,I have a strange Outlook/ Exchange problem with one of our Users, interestingly it’s the Boss of our company….The Background:- We have 2 Domains @company-1 or @company-2- We have 1 Exchange 2010 Server Version 14.03.0224.002- Till March of this year our Emails where hosted externally, we used to download the Emails every 2 minutes from POP3 Mailboxes into Exchange- We have 18 Users- So every User had a User account on our Exchange and a Mailbox externally- Now we host our Emails our self via MX and DNS Records(mail.company.cc)- The User kept their Exchange accounts, OWA is now working too So far all works well on my little Server farm.The Catch:Usually our users have only one Email address either @company-1 or @company-2 Except our Boss and one other User, they have an Email address in both Domains They have addresses one...
    This topic first appeared in the Spiceworks Community

    Hi,
    I suggest to repair .ost file to check this issue by the following steps:
    Exit Outlook.
    In Control Panel, click or double-click Mail.
    In the Mail Setup dialog box, click E-mail Accounts.
    Click the Data Files tab, select the Exchange account, and then click
    Open File Location. A file explorer window opens to the location of the data file for the Exchange account. The
    Account Settings and Mail Setup dialog boxes will remain open, behind the file explorer window.
    Close the Account Settings and the Mail Setup dialog boxes, then return to the file explorer window.
    Important: be sure to close these two dialog boxes before you delete the file. If they aren't closed, Windows may display an error message about a conflict.
    In the file explorer window, right-click the Exchange data file and then click
    Delete. The next time you start Outlook, a new .ost file is created for the account.
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Exchange 2010/2013 coexistence published in TMG 2010

    Environment:
    Two Windows 2008 R2, Exchange 2010 SP3 servers, currently holding all mailboxes
    Two Windows 2012 R2, Exchange 2013 SP1 servers, setup in progress
    Two Windows 2008 R2, TMG 2010, V7.0.9193.540 publishing both Exchange 2010 servers.
    Scenario:
    I need to continue having Exchange 2010 setup in TMG as is as the mailbox migration to 2013 will take weeks if not months and I have a project requirement to have Exchange Database Availability Group (DAG) functionality for all mailboxes throughout the project,
    so 4 servers are an absolute must. So I need to add Exchange 2013 in TMG and not just replace the 2010 setup with the 2013 setup and I cannot run one 2010 and one 2013 server. 
    Questions:
    1. I currently only have 2 public IP addresses available to SMTP, mapped to the external interfaces of TMG, to allow my environment to be able receive emails on 4 Exchange servers (two 2010 and two 2013) I need to have 4 public IP addresses, is that correct?
    2. Does anyone have a good general guide/blog for doing this (setting up Exchange 2013 in TMG in a coexistance scenario)? 
    This is nice, but doesn't really approach it from a coexistance scenario:
    http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
    Thanks!

    Hi Trana,
    In TMG you can use single IP address to publish multiple Web address and below are the options which you can explore.
    Hope your OWA ECP etc are Https
    You need a SSL certificate which has all the URL SAN entry of both old and new Exchange server.
    Create a listener and select the IP address (Say public IP address 195.219.x.x)
    Link the SSL certificate
    Public DNS entry
     A record , Single IP
    195.219.x.x 
    Point to           
    Owa1.exchange1.com   - Old Server
    195.219.x.x 
    Point to           
    ECP1.exchange1.com     - Old Server
    195.219.x.x 
    Point to           
    ECP2.exchange2.com      - New Server
    195.219.x.x 
    Point to           
    Owa2.exchange2.com     - New Server
    Create a Web publishing rule as below
    Old server Exchange 1
    Owa1.exchange1.com  
    ECP1.exchange1.com    
    One Web publishing Rule with all the URL added on it and link the Rule with the listener we created
    Point the Web publishing to Exchange1.com server which is old
    New server Exchange 2
     Web publishing Rule with all the URL added on it and link the Rule with the listener we created
    Point the Web publishing to Exchange2.com server which is New
    ECP2.exchange2.com     
    Owa2.exchange2.com    

  • Ports Required to open between Exchange 2010 & 2013

    Hi,
    I have to introduce Exchange 2013 into Exchange 2010 environment that is in same Organization. There are 3 sites connected on which Exchange 2010 installed and 4 site will be Exchange 2013 and then mailbox will migrate to E2k13 servers.
    All 4 sites and connected to MPLS link, please let me know what ports are required to open for Communication between mail flow. 
    From Internet OWA : 443 & 25 is sufficient for Mail flow.
    Amit

    Exchange does not support blocking any ports between individual Exchange Servers as well as Exchange to DC communication, so for internal communication everything has to be opened.  
    If you are just talking client traffic (OWA, ActiveSync, Outlook Anywhere) and smtp mail traffic from external sources, then you should only need 443 (client traffic) and 25 (smtp traffic). 
    https://social.technet.microsoft.com/Forums/en-US/bc21b467-76bb-4c86-b7e1-21daa82cc37a/ports-required-for-exchange-2013-installation?forum=exchangesvrdeploy

  • Exchange 2010 - 2013 Coexistence Issues

    I am migrating from Exchange 2010 to Exchange 2013, the Exchange 2013 is built in a different Geo-location site with its dedicated domain controllers in the new site. I have confirmed the mail flow between Exchange 2010 and 2013 mailboxes. I am able to discover
    Exchange 2010 servers from 2013 environment via Get-ExchangeServer shell command. However, I am not to discover Exchange 2013 servers from 2010 environment. 
    I need to configure Outlook Anywhere and Service Connection Point (Autodiscover) on Exchange 2010 to accept connections from Exchange 2013 servers. 
    Any suggestions would be much appreciated, thanks!

    Hi ,
    Please have a look in to the below mentioned blog after reading that blog i came to know few things .
    I am not sure ,i thought exchange 2013 servers will not be displayed in exchange 2010 management shell.
    Better and advisable method is to configure your exchange 2010 and 2013 servers via EAC or Shell in exchange 2013.
    http://exchangeserverpro.com/exchange-server-2010-2013-migration-managing-co-existence-environment/
    Taken from the above blog :
    You can’t use the Exchange 2010 EMC to manage Exchange 2013 objects and servers. While customers upgrade to Exchange 2013, we encourage them to use the EAC to:
    Manage Exchange 2013 mailboxes, servers, and corresponding services.
    View and update Exchange 2010 mailboxes and properties.
    View and update Exchange 2007 mailboxes and properties.
    We encourage customers to use Exchange 2010 EMC to create Exchange 2010 mailboxes.
    We encourage customers to use Exchange 2007 EMC to create Exchange 2007 mailboxes.
    Customers can continue to perform management tasks using the Exchange Management Shell and script tasks.
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

Maybe you are looking for