Exchange 2007/2010/2013 UM coexistence

We currently have an Exchange 2007/2010 environment in production along with Lync 2010 (UM provided).
I have installed a number of Exchange 2013 server and will be migrating ( over a LONG time ) to the new system.
In the meantime, I need to have all services co-existent across all three Exchange versions.
It looks like I have everything workign now except UM for Lync 2010.
I tried adding the Exchange 2013 server into the existing 2007/2010 dial plan and am having issues.
Here is what i did.
EAC
- Installed certificate on all Exchange 2013 servers
- Enabled Unified Messaging on all the servers
- Select server
- Set TLS
- Associated 2007/2010 Dial Plan
- Set UM service on certificate on all servers
- Restarted UM service
- Did the above for all MB and CAS servers
- Wait about an hour
Lync fails to send calls to voice mail, giving me events 45024 and 44022 on the Lync FE stating that Lync could not connect to the Exch MB servers and the attempt to connect to UM failed.
Any suggestions?
Do I need to rerun the following ?
- Exchucutl.ps1
- Ocsumutil.exe
Thanks!
Tom

When I go into the Exchange EAC Unified messaing / UM IP Gateway screen I see the Um IP Gateways configured in the legacy Exchange systems and had hoped that these existing gateway definitions would suffice.
Does exchucutil.ps1 need to run from a 2013 Exch server to initialize these gateways in Exch 2013?
On my fist attempt, VM was failing for my 2007/2010 users. I had not even started to test with a 2013 user. I successfully backed out by dis-associating the dial plan in the Exchange EAC console from all the Exch 2013 servers.
If I run exchucutil.ps1, try again, and it fails, what is my backout plan? Do I need to rerun exchucutil.ps1 on a legacy Exchange system? or will merely dis-associateing the diual plan in Exchange 2013 again suffice.
Thanks Tom
After typing this, I realize that this is probably more of an Exchange question so I posted the question there. I apologize now for any cross posting misbehavour.
Posted to -
http://social.technet.microsoft.com/Forums/exchange/en-US/6fbfad13-3480-46c6-804d-3757110e61c7/exchange-um-coexistence-exch-20072010-and-exch-2013?forum=exchangesvrunifiedmessaging

Similar Messages

  • Maximum number of user mailboxes supported by single Exchange Database in 2007 / 2010 & 2013 ?

    What is the Maximum number of user mailboxes supported by single Exchange Database  in 2007 / 2010 & 2013 ?
    Aditya Mediratta

    Agree with Keith, there is no MB # limit, however there are practical concerns such as DB size and how that effects recoverability as well as performance.   In terms of extremes we had one major educational customer that had 35K Mailboxes in
    a single database so you can utilize a ridiculous # of mailboxes in a DB if desired.  IMO you are better off to keep the # of mailboxes to a reasonable level, i.e. no more than 250-500 mailboxes per DB
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Configuring Message Clasifications Exchange 2010 - Outlook 2007/2010/2013

    Hi
    I created Message Classification as described in:
    http://technet.microsoft.com/en-us/library/bb123498(v=exchg.141).aspx
    New-MessageClassification ....
    New MessageClassification is visible in OWA.
    I stared deploy Message Classifications for Outlook 2007 using this
    http://technet.microsoft.com/en-us/library/aa998271(v=exchg.141).aspx
    Of course there is small bug: "AdminClassificationPath"="c:\\Classifications.xml" but is should be
    "AdminClassificationPath"="c:\Classifications.xml"
    After set up it doesn't work. The same for Outlook 2010 and 2013?
    Does anybody deploy Message Classifications for Outlook 2007 or 2010 or 2013 with success?
    I use Exchange 2010 SP3 with all RU and Outlook 2007, 2010, 2013 with all updates.
    Kind Regards Tomasz

    Hi,
    How do you know this is an old reoccurring message? Based on the content or time?
    Since the MailboxAutoReplyConfiguration is correct, I suspect the issue can occur by certain client machine. At this stage, I suggest you disable OOF and re-enable
    OOF on the problematic machine. If the issue persists, please refer to the following article to clean the problematic client’s Outlook rules. (run Outlook.exe /cleanrules in Run console.)
    http://www.tech-recipes.com/rx/2161/outlook_2007_clean_up_command_line_switches/
    Thanks.
    Novak Wu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    [email protected]  
    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 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

  • 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."

  • Legacy Namespace for Exchange 2007 to 2013 co-existence

    We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
    are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
    need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
    I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
    Thanks in advance for your help.

    In coexistence with exchange 2013 and legacy version the request happens in 2 types.
    For Exchange 2010 –
    Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
    For Exchange 2007 –
    Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
    Certificates:
    All the required SAN entries for UM,webservices and activesync should be created.
    Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
    Exchange 2013 only then owa redirection will work.
    You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
    Existence.
    Following change needs to be done in Firewall
    External OWA URL should be directed to exchange 2013 Internet Facing CAS.
    External EWS URL should be directed to  exchange 2013 Internet Facing CAS.
    External Autodiscover URL should should be directed to  Exchange 2013 CAS.
    External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
    External UMvirtualDirectory should be directed to  Exchange 2013 CAS.
    Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
    a mailbox on Exchange 2007.
    External and Internal DNS settings
    Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
    exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
    Example:
    Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
    Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
    facing exchange 2013 CAS FQDN
    Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
    Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
    address
    The internal DNS records should point to the internal host name and IP address of your Exchange
    2013 Client Access server
    Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
    Authentication Settings:
    This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
    Set the owa virtual directory authentication only to  Basic in exchange 2007.
    In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
    Things to check:
    If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
    Virtual Directories doesn’t have it configured.
    If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
    For further references you can refer my article below
    http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
    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)

  • Issue moving remote user from exchange 2007 to 2013

    have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
    during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.  
    outlook was working connecting to both servers, and OWA was working on both servers.
    couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
    but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
    if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
    when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
    could this have caused my outlook connectivity issue?
    I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    any suggestions?

    I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
    Hi,
    Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
    According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
    Please try to logon OWA to check whether this user works.
    If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
    Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
    Please try to run Outlook under safe mode to avoid AVs and add-ins.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Outlook 2011 for Mac with Microsoft Exchange 2007/2010

    Hi,
    For already a fews days I am troubleshooting a Mac Outlook 2011 <> Exchange sync issue. I've got exact the same symptoms in two totally different environments. 
    - Environment one:
    Exchange 2007 SP3 RU 14 (8.3.379.2)
    Outlook 2011 14.4.7
    - Environment two:
    Exchange 2010 SP1 RU 8 (14.1.438.0)
    Outlook 2011 14.4.7
    Problem:
    Autodiscover and EWS synchronisation test from Microsoft Exchange Connectivity Analyzer is succesfull. Configuring an new (Exchange) e-mail account with Outlook2007/2010/2013 fully based on autodiscover works with no errors. 
    Configure Outlook 2011 based on autodiscover when connected to the internal LAN works. Configure Outlook 2011 based on autodiscover or by hand doesn't work from WAN. 
    I am unable to synchronize Outlook 2011 with Exchange when WAN connected (No error in logging). I am able to synchronize OS X Mail (Default OSX Mail client) with the same Exchange server.
    Conclusion: the autodiscover function that Outlook 2011 uses does not work from WAN, the autodiscover function that Outlook 2007/2010/2013 and Exchange Connectivity Analyzer is using does work from WAN. Do I need to configure something special for synchronization
    with Outlook 2011 other than explained above when working from WAN?
    When testing EWS with 3th party tooling(EWS Editor) and Exchange Connectivity Analyzer everything is working as it should be. (all mailbox data is shown). If you need any more information about the context I am happy to provide.
    Regards,
    Mikkie van Falier

    Hey hpujary.
    Welcome to the BlackBerry Support Community Forums.
    At this time, only contacts can be synchronized with BlackBerry Link software and a BlackBerry 10 Smartphones. The functionality to provide more options for PIM synchronization may be added in the future. I cannot say for certain that the issue outlined in KB27248 is resolved for BlackBerry 10 Smartphones as the functionality does not exist to confirm.
    Cheers.
    -Sawks
    Come follow your BlackBerry Technical Team on Twitter !@BlackBerryHelp
    Be sure to click Like! for those who have helped you.
    Click Accept as Solution for posts that have solved your issue(s)

  • 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

  • Can only access emails through OWA after migration from exchange 2007 to 2013

    can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
    needed RCA ... plz help..

    Hi,
    From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
    In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • How to migrate from exchange 2007 to 2013 step by step tutorials please

    Hi
    I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
    We have 800 mailbox in total
    Our domain controllers are
     Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
    I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
    Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
    I currently only have 1 exchange server 2007, with all the roles on the one server.  I would like to keep that same as
    well with exchange 2013.
    Thanks

    Exchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
    You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
    migration task in more secure way.

  • Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

    I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
    two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
    Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
    Data migrated:                        
    Migration rate:                        
    Error:                        
    MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
    context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server
    FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824        
    Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288  
    StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]   
    Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
    Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624   
    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856   
    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
    prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
    15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115   
    Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970  
    StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
    All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
    The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
    The Source Server is Running Exchange 2007.
    I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
    I would appreciate any help you can give me!
    Thanks,
    Jon

    Any update if you have resolved the issue.
    Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

  • Setup first Exchange 2013 with mixed mode exchange 2007/2010

    my company has exchange 2007 hub and edge and exchange 2010. I'm planning to retire all exchange 2007 first follow migrate to exchange 2013. so I have few questions as below ?
    1. Do I need to unsubscribe hub 2007 from edge first before uninstall ? Currently we have 2 hubs (2007 and 2010). How can I remove hub 2007 from exchange edge server 2007 ?
    2. let say once my landscape just have exchange 2010, is it installing our first exchange 2013 will impact our mail flow ? my understand there is NO impact until we switch over 'mail IP' to CAS 2013. am I correct ?
    3. what is minimum requirement for co-exist with exchange 2013 for exchange 2010 ? is it enough with SP3 or I need to apply SP3 RU5 ? in deployment assistant, the requirement is SP3 RU5 but most article i read just mention SP3.
    thx.

    1.  I would remove the edge subscription for sure.  Then it isn't strictly necessary to uninstall Exchange Edge if you're just going to flatten the box anyway because that server isn't in Active Directory except through the Edge Subscription process. 
    I'm not sure what you're asking about "NO impact".
    2.  The coexistence requirements are clearly documented in TechNet.  I'll leave it to you to search it since you can do that just as well as I can.  That said, I would recommend that you go ahead and install the latest rollup on all your servers
    first.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Lync2013 EWS URLs for Exchange 2007/2010 Coexistence

    Hi
    Last weekend we deployed and activated our new Exchange 2010 CAS. The 'old' Exchange 2007 CAS is still there, using the legacy URL method, since mailboxes are mostly still located on 2007 Mailbox servers.
    In other words, clients connect to the Exchange web-services on the 2010 CAS, and depending on where their mailbox is located (2007 or 2010 Mailbox-server) they either stay with the 2010 CAS or get re-directed to the 2007 CAS (legacy.company.com)
    Internal and External URL's are the same, for both the primary and the legacy URL's. All is well, no issues with Outlook clients or OWA, EWS, Activesync.
    Enter Lync 2013.
    Since the change this weekend, we're getting Outlook/Exchange Integration errors. Checking the Lync Configuration Information (CTRL-Click system tray icon), I can see the EWS Internal/External URL's being used by the client. These URL's point to the 2010 CAS.
    So why the error ?
    Does the 2010 CAS re-direct Lync clients to the legacy URL, just like it does with OWA/Outlook clients ?
    Does it even have to, to supply EWS data for mailboxes on 2007 servers ?
    Can I change the EWS URL's, and have them point to the legacy URL, but only for Lync clients ? (and change it back later)
    Already checked a mailbox on Exchange 2010, it's Lync user does not get the integration error. So the problem is definitely related to mailboxes on 2007, that need the old CAS server during coexistence. Also, before the CAS 2007 server worked fine, providing
    EWS to Lync clients.
    Eventually, the plan is to move the mailboxes from 2007 to 2010, but this error puts pressure on that plan. It will take at least 2 or 3 weeks, during which time clients continue to get the error until they are moved.
    I'm kinda stuck here.

    Lync uses DNS to find autodiscover to obtain EWS URL.
    Which server did the DNS record Autodiscover point to?
    You can run the command Get-AutodiscoverVirtualDirectory to get the EWS internal URL and external URL on the server the Autodiscover pointing to.
    2010 CAS can’t redirect Lync client to the legacy URL.
    Lisa Zheng
    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

Maybe you are looking for