Office 2010 vs. 2013 - migrating from XP to W7

I have a client with >200 PCs, and about 50 already run W7 with Office 2010. The remaining 150+ XP PCs are currently being migrated to W7, and the client wants to stay with Office 2010, as they have already purchased 50 or so licenses for their existing
W7 PCs.
I am finding Office 2010 licenses harder and harder to find, and much more expensive since Office 2013 was released. The client also has plans to add 50+ PCs during Q4 2014 when a new location is opened. I am hesitant to proceed with their direction,
if 2010 licenses become no longer available. I know that MS has discontinued sales, and vendors will only be allowed to continue to sell 2010 until their inventory is depleted. My client is aware of this, but they do not want to standardize on 2013 because
they feel they would then have wasted their money buying the roughly 50 copies of 2010. And they do not want a mishmosh of 2010/2013 in their company, they want to be all on the same version.
Any advice?I do not want to move them away from Office (to openoffice, Corel, or worse!) but if I can't get them standardized on 2010 they may be forced to move to another platform or worse decide to find a new IT consultant. They understand this is not
my fault per se, but they blame me for not anticipating this during the last few years when I recommended Office 2010 for their new W7 PCs. No good deed goes unpunished as they say.

Hi
Since it is hard to purchase Office 2010, you can take Office 2013 and downgrade to Office 2010.
However downgrade rights are only available for volume licenses.
Check the following article:
http://www.microsoft.com/licensing/about-licensing/briefs/downgrade-rights.aspx
Tylor Wang
TechNet Community Support

Similar Messages

  • Lync 2013 migration from Lync 2010

    Hi All,
    I have a problem after I've successfully migrated our Lync environment from Lync 2010 (what was migrated from OCS 2008 R2) to Lync 2013.
    When I would like to delete the old Lync 2010 Front End server from the topology I cannot do that, because there are some TrustedApplicationPool registered to that. And I cannot delete this unused TrustedApplicationPools, because I got the following error:
    "Remove-CsTrustedApplicationPool : Cannot remove legacy trusted application pool. Use the legacy tools to remove the pool, then run Merge-CsTopology."
    I've tried that many ways, I've tried the merging etc. but it was unsuccessful. Has anybody any idea, step-by-step or something what can helpful to me?
    Many thanks,
    Tamás Dobos

    Hi,
    Did you check this step by step migration lync 2010 to 2013
    http://www.oiboran.com/?p=1073
    To remove Trusted application pools
    Get-CSTrustedApplicationPool
    Remove-CSTrustedApplicationPool -Identity nameofthepool 
    Removing Lync 2010
    http://terenceluk.blogspot.nl/2012/12/removing-lync-server-2010-standard.html
    Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

  • 2010 to 2013 migration. Can't connect OWA to 2013 server unless 2010 server is on line

    I am migrating an SBS 2011 Exchange server (2010) to Exchange 2013 on a W2012 Server (not a DC). I completed the install and moved one user's mailbox to the 2013 server. All users can process their email via OWA and Outlook. But, if the SBS 2011 server is
    disconnected, the migrated user cannot log on via OWA and I can't log in to administrator ecp. They just time out. I know the mailbox is migrated because if I disconnect the 2013 server and OWA into the SBS 2011 server it gets an error saying the mailbox server
    is unavailable. I must have missed a step in the migration. Can someone please point me at some documentation for completing the migration. 
    Thank,
    Lou
    Louyo

    Hi,
    Please have a look in the similar threads.
    https://social.technet.microsoft.com/Forums/office/en-US/5990037a-8b3f-4abe-8589-22032171adc6/exchange-2013-2013-coexistence-owa-rendering-on-2010-cas-for-2013-mailbox?forum=exchangesvrclients
    https://social.technet.microsoft.com/Forums/office/en-US/bc8628e6-a0c5-4fd8-95c1-36ee5a644847/owa-still-lands-at-exchange-2010-for-users-migrated-from-exchange-2010-to-2013?forum=exchangesvrclients
    https://support2.microsoft.com/kb/2931385?wa=wsignin1.0
    Note : Just ensure the active directory replication is working properly in your exchange environment .
    Regards
    S.Nithyanandham
    Thanks & Regards S.Nithyanandham

  • Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

    I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
    as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
    Symptoms:
    Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
    from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
    URL to connect to my proxy server for Exchange: webmail.domain.com
    Connect using SSL only: Checked
    Only connect to proxy servers that have this principal name in their certificates: Unchecked
    On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
    On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
    After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
    first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
    Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
    Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
    domain: blank
    username: their AD username
    server: webmail.domain.com
    After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
    begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
    for mobile users in the same way that it's been working for us with Exchange 2010?
    Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

    Hi,
    Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
    Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
    fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
    Please restart the following Exchange service to have a try:
    Microsoft Exchange RPC Client Access
    Microsoft Exchange Mailbox Replication
    Restart IIS service by running IISReset in a Command Prompt window.
    Then check whether the Outlook client can connect to Exchange 2013 or not.
    As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
    https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
    Regards,
    Winnie Liang
    TechNet Community Support

  • Lync 2010 to 2013 Migration DB issue, central management database.

    Hello ,
    During Lync 2010 to 2013 migration , on my back end database for Lync 2013 I previously created there data base instances on my lync 2013 BE , (RTC,MON, ARC) THERE DIFFERENT ISTNACE using sql server enterprise 2012 .
    Now I want to finish the migration by moving the central management server to the lync server 2013.
    my question now I tried to create a new DB instance and I face some issue related  the space on the server .
    can I use any of the existing isnatce which I created before for the (RTC,MON, ARC) or can I sue the default instance which is created by default with sql 2012 server installation .to install the central management database.
    do I need a spate instance ? for the new central management store on my lync server 2013
    Thanks
    MK

    Hello
    After I run the command
     Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn hq-lync2013-be.MYDOMAIN -SqlInstanceName RTC.
    -Then
    Enable-CsTopology
    -Then
    Move-CsManagementServer .
    And now after the move when I check the logs :
    WARNING: The move completed successfully but the following additional steps are required:
      Run local setup on the following computers to remove Central Management services that are no longer defined in the topology:
        - HQ-LYNC-FE-01.MYDOMAIN
    WARNING: "Move-CsManagementServer" processing has completed with warnings. "2" warnings were recorded during this run.
    WARNING: Detailed results can be found at
    "C:\Users\MYUSER\AppData\Local\Temp\2\Move-CsManagementServer-0d4806f4-554d-497d-a0dc-0fc98a6e076d.html".
    THESE AR ETEH TWO WARININGS :
    Warning: Failed to cleanup file store for the new Central Management Server. Error The directory is not empty.
    Warning: The move completed successfully but the following additional steps are required:
    Run local setup on the following computers to remove Central Management services that are no longer defined in the topology:
    - HQ-LYNC-FE-01.MYDOMAIN.
    I Run the local setup on both the FE2013 AND FE2010.
    now when I run the command :
    Get-CsManagementStoreReplicationStatus
    UpToDate           : False    (I shutdown this server )
    ReplicaFqdn        : HQ-EDGE01.mydomain
    LastStatusReport   :
    LastUpdateCreation : 3/16/2015 1:52:45 PM
    ProductVersion     :
    UpToDate           : False
    ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
    LastStatusReport   :
    LastUpdateCreation : 3/16/2015 1:52:45 PM
    ProductVersion     :
    UpToDate           : False
    ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
    LastStatusReport   :
    LastUpdateCreation : 3/16/2015 1:52:45 PM
    ProductVersion     :
    UpToDate           : False
    ReplicaFqdn        : HQ-LYNC-MA-01.mydomain
    LastStatusReport   :
    LastUpdateCreation : 3/16/2015 1:52:45 PM
    ProductVersion     :
    NOW THEER IS REPLICATION ISSUE ?
    I notice that service on my lync 2010 SOME OF THEM ARE STOPPED :
    FILE TRANSFER AGENT , MASTER REPLICATORE AGENT , CALL PARK SERVICE (ALL ON LYNC 2010)
    ALL SERVICE ON 2013 FE IS OK AND RUNNING..
    I notice this error in my lync server 2013 vents .
    I host the shared file on my lync server 2010 mediation server
    Microsoft Lync Server 2013, Master Replicator Agent service encountered an error while accessing a file share and will continuously attempt to access this file share until this issue is resolved. While this condition persists, replication to replica machines
    might not occur.
    IO failure occurred for Path=\\HQ-LYNC-MA-01.mydomain\LYNCSHARE\1-CentralMgmt-1\CMSFileStore\xds-master\working\replication\tmp. Exception=Access to the path '\\HQ-LYNC-MA-01.mydomain\LYNCSHARE\1-CentralMgmt-1' is denied..
    Cause: Possible issues with file share permissions. This can occur if the computer hosting the file share has outdated cached credentials for the computer that is trying to access the file share.
    Resolution:
    For details about how to resolve file share permission issues, see the product documentation.
    SO ANY ADVICE ?
    Regards
    MK

  • Problem opening documents from SharePoint (2013) libraries with Office 2010 and 2013 components installed

    Hi
    I've been encountering the problem of Office files failing to open from SharePoint 2013 libraries with the prefix of 'ms-excel:ofv|u|' etc. in the url. Following the
    helpful questions and answers in the forum, I've identified the likely cause as the fact that my main Office installation is 2010, but I also have installed OneDrive for Business 2013 (which I need in order to sync document libraries with my local drive).
    The solution I've seen suggested elsewhere of deactivating the SharePoint integration of Office 2013 components fails for two reasons: there is no way (or at least, I can't find one) of deactivating SharePoint integration probably because, deactivating
    SharePoint integration would likely stop the syncing of libraries/folders.
    One thing that I have noticed in my case that I've not seen mentioned elsewhere is that if I right-click a document and select 'open in new tab/window' the required
    document opens directly in the relevant office package. I don't know if this is a useful observation, but it seems to be new information.
    My question is, is there a way I can continue to sync libraries and open Office documents directly in Office 2010? My thoughts are possible changes to registry settings
    (which I can do, but don't know enough to find the correct ones myself) or (re)installation of software in some appropriate order to leave the correct settings.
    I have 'repaired' my Office 2010 installation without any observed affect on behavior.
    Thanks
    Ray
    (I've just seen a suggestion that Office 2010 SP2 may fix this issue. I've requested to test this, but whilst this may fix my problem, rolling it out to
    other users may be more problematic. In the meantime, other suggestions of solutions are welcome)

    Hi,
    According to your description, it is a good way to do a test about office 2010 SP2, here is an article about this issue- limitations of using the OneDrive for Business sync app with Office 2010 applications , it may help you.
    http://office.microsoft.com/en-us/sharepoint-help/solve-problems-youre-having-with-the-onedrive-for-business-sync-app-HA104047973.aspx
    Paul Shui
    Microsoft Online Community Support
    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

  • Going from Office 2010 to 2013 and Back to 2010 I lost My Outlook Search

    Hello--
    We are doing some beta testing and I had to install Office 2013 from 2010. I finished the testing and went back to 2010.
    Now, when I do a Windows search, my Outlook email is not included in the search results. This is a major loss to my productivity. I believe I read that Outlook email is not included in the Windows search with 2013, so that's probably why I lost it.
    Can you tell me how I can include Outlook email in my Windows searches again? I searched for solutions online and all I got were questions.
    Thanks!
    Stephen
    Stephen Davis

    Hi,
    Sorry for not having resolved this issue so far. We can try to uninstall Office 2010 first, then delete the following registry keys from the location:
    Win + R, type "regedit"(without quotes) then press Enter.
    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps
    carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry,
    http://windows.microsoft.com/en-US/windows7/Back-up-the-registry
    HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook
    HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\15.0\Outlook
    HKEY_LOCAL_MACHINE\Software\Microsoft\Office\Outlook
    Once the keys are deleted restart the computer, then re-install Office 2010 to check the result.
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here
    That fixed it. After I did the steps you indicated, I went back to the Indexing options and made sure the Office14 folder was included.
    Thansk
    Stephen Davis

  • OWA still lands at Exchange 2010 for users migrated from Exchange 2010 to 2013

    I never had any issues with OWA redirection for a few users that I migrated from Exchange 2010-2013 initially. For users that I am migrating in the past few days, the OWA 2013 is landing on Exchange 2010 despite the mailbox being successfully migrated to
    Exchange 2013.
    Troubleshooting:
    1. I have restarted the IIS Services
    2. I have restarted MSExchangeOWAAppPool.
    3. I have also checked the homeMDB attribute of the 2013 migrated user with the Exchange 2013 database.
    I would really appreciate if anyone could share their experiences on similar issues.

    I have checked it, the migration status is completed. In regard to the namespaces, both CAS 2010 and 2013 are set to mail.domain.com; CAS 2013 is the internet facing. I have also checked the internal access for OWA, it's the same scenario. Migrating them
    back to 2010 and 2013 won't resolve the issue in my case, because the issue persists for every new user that I am migrating.
    I recently found the following when I login with a user who is not effected and then logout:
    1. Login in back with the affected user without closing the browser or clearing the cache, it lands at CAS 2013 OWA.
    2. However, I get the below listed error message when I logout. 
    Your request couldn't be completed.
    Click here to continue working.
    This may have occurred for security reasons or because your session timed out.

  • Exchange 2013 Migration from 2010 Test (Shared split DNS)

    Hi
    Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13
    and EXC10 ip adresses (Round Robin).
    I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
    get:
    A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
    Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?

    You should never use the server name in any of the URLs.  You should use either a CNAME or a load-balanced VIP with a generic name like mail.company.com or webmail.company.com.  Then you just point this name to the new server.  If
    you're currently using a server name, it's about time to change that first before trying to switch to Exchange 2013.
    Curently im using a generic name, mail.test.com. But that's just a normal A record on the internal DNS. So i cannot use that on both?

  • Journaling mailbox - Exchange 2013 Migrations from 2010

    hi guys
    i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
    and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
    move old one at the end .
    my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ?? 
    thank you
    Indunil

    Hi,
    Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
    And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
    So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Infopath forms 2010 to 2013 migration issue

    I need to migrate InfoPath forms 2010 to SP 2013. Now in 2010 InfoPath forms are connected to data connection library & having classic authentication. Since SP 2013 doesn't support classic authentication what are the issues should come to handle? What
    should be correct strategy & steps for this migration?

    Hi Sunil
    Sharepoint 2013 will support the Classic mode authintication but while creating any new webapplication using sharepoint central administration you can only used claim based authintication
    Check the below link for step by step approcah about infopath
    http://technet.microsoft.com/en-in/library/cc262263(v=office.14).aspx
    You can alos check this link
    Claims-based authentication is an essential component to enable the advanced functionality of SharePoint 2013. To move classic-mode web applications from SharePoint 2010 Products to SharePoint 2013, you can convert them to claims-based web applications within
    SharePoint 2010 Products, and then migrate them to SharePoint 2013. The procedures in this article illustrate various supported scenarios.
    The Windows PowerShell Convert-SPWebApplication cmdlet in SharePoint 2013 converts classic-mode web applications to claims-based web applications.
    http://technet.microsoft.com/en-us/library/gg251985(v=office.15).aspx
    http://blogs.technet.com/b/rajbugga/archive/2013/08/07/infopath-over-claims-authentication-sharepoint-2010-amp-2013.aspx
    Please mark the Answer and Vote me if you think that it will you to resolved your issue
    did you missed to give any link here:
    "You can alos check this link" ?
    Also, Can you plz tell how to manage data connections in case of infopath migration?
    Your answer is overall good.

  • Upgraded MS Office 2010 to 2013, how do I get the pdf menu option in Word, Excel, etc - Using Acrobat X

    Hi
    Have just upgraded from MS Office 2010 to Office 2013.
    Have lost the menu option "Acrobat" for creating pdfs (using Acrobat X).
    How to I get it back?
    Cheers

    uninstall acrobat, clean (Download Adobe Reader and Acrobat Cleaner Tool - Adobe Labs) and reinstall acrobat.

  • Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    Exchange 2010 has 2 databases:
    1. Database with users mailboxes;    Journaling YES: Journal account.
    2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
    Exchange 2013 has 1 database:
    1. Database with moved users mailboxes;    Journaling YES: Journal account.
    I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
    I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
    I'd like:
    * to understand technically what happened,
    * to avoid unnecessary growth of Journal Database.
    I'd like not to switch off journaling for all users during mailbox move.
    best regards Janusz Such

    Hello Winnie,
    your understanding is not correct:
    I move mailboxes from first DATABASE which is journaled;
    second database is dedicated solely for Journal user's mailbox and is not touched now.
    Thank you for PS commands; I'll use them...
    best regards Janusz Such
    Hi Janusz,
    Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
    My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
    Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
    Journal rule instead of database journal as a workaround.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 to 2013 Migration Question

    Hi Folks,
    This is where I'm at: We have 2 Exchange 2010 servers (both multi role) and I was given 4 VM's for exchange 2013.  I just completed installing Exchange on the four 2013 VM's (2 dedicated CAS and 2 dedicated MBX) and applied SP1.  I documented all
    of the 2010 server config info (i.e. all the URL's for the namespaces, etc).  We have a hardware NLB and a MacAfee host in the DMZ where all inbound/outbound email routes to check for AV/Spam.  My question is, what are my next steps that
    take place so that I'm truly in co-existence mode?  I'm assuming I want to make the 2013 servers primary now so that all mail routes to/from them and all client connections are made to them?  Could someone point me in the right direction maybe
    to an article on what my next steps are?  I want to get everything cut over while in co-existence so that I can start moving mailboxes.  Thanks a lot ! 

    Exchange Server Deployment Assistant is good starting point:
    http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-AAAAAAAAQAAAAAEAAAAAAA%7e%7e
    Upgrade from Exchange 2010 to Exchange 2013:
    http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    http://msexchangeguru.com/2013/05/10/exchange2013-migration/
    http://www.petenetlive.com/KB/Article/0000788.htm
    Below is high level migration plan:
    1. Update active directory schema for exchange 2010 sp3.
    2. Install Exchange 2010 SP3 and rollup updates on existing servers.
    3. Update active directory schema for exchange 2013 CU3.
    4. Install and configure new Exchange 2013 CU3 servers.
    5. Install public SSL Certificate.
    6. Configure Web URL's for Exchange 2013 servers.
    7. Configuration Hardware Load Balancer for:
    a) High availability of Client Access roles.
    b) Reverse Proxy for outlook web app.
    8. Create mailbox databases and configure database copies for the corresponding DAG.
    9. Test High Availability environment.
    10. Test mail flow  to & from internet/internally for all locations.
    11. Test BlackBerry device connectivity with Exchange 2013 environment (if nay)
    12. Test migrate mailbox from Exchange 2010 to Exchange 2013.
    13. Test Outlook & OWA connectivity for migrated test mailbox.
    14. Validate new Exchange 2013 environment.
    15. Pilot mailboxes migration from Exchange 2010 to Exchange 2013.
    16. Migrate mailboxes from Exchange 2010 to Exchange 2013.
    17. Migrate Public Folders from Exchange 2010 to Exchange 2013
    18. Dismount & stop Exchange 2010 services on all servers for few days before decommissioning of Exchange 2010 servers.
    19. Decommission Exchange 2010 servers gracefully.
    If this will help then please mark it as answer...thanks
    Best of luck!
    Liaqat

  • Issue sending bulk email after Exchange 2010 to 2013 migration

    Hi!
    I have an issue with some reporting software sending bulk emails after our Exchange 2013 migration. 
    I can see the connections in the firewall and I can see the first connections under the protocol logs in the Exchange servers. What happens is that after ~10 emails, within the same amount of seconds from what I can tell, the mail flow just stops to the
    Exchange server. I cant seem to find an error message anywhere within the Exchange logs and I've tried updating the receive connector with higher timeouts / Connection limits but the users still cant send all the invoices etc right away. 
    We have multiple applications / receive connectors with this issue and the users did not report any issues with Exchange 2010 so I am assuming that this issue did not exist there. 
    We're running two multi-role (CAS/MB) Exchange 2013 servers in a DAG. Exchange 2010 is not fully decommissioned yet but all links and users are moved to 2013.
    Any help is much appreciated!

    Hi ,
    To avoid the issues when relaying the emails from application server through exchange then we need concentrate on the below mentioned parameters on the receive connectors in exchange 2013 cas servers and also we need to set the parameter value as per your
    environment requirement.
    Please check the below mentioned values on the dedicated receive connectors in exchange 2013 cas server to relay emails from the application server
    Parameters :
    ConnectionInactivityTimeout
    ConnectionTimeout
    MaxInboundConnection
    MaxInboundConnectionPercentagePerSource
    MaxInboundConnectionPerSource
    MaxRecipientsPerMessage
    MessageRateLimit
    Note : In case if none of the above changes help you then the final option would be to enable the protocol logging on the receive connector utilized by the application server to relay emails via exchange server and with the help of the logs we can can came
    to know that why the connections from the application server to exchange server is disconnecting after some emails has send.
    Thanks & Regards S.Nithyanandham
    Here are the relevant values for the receive connector, doublechecked and it's the same on both DAG members;
    ConnectionTimeout                       : 00:20:00
    ConnectionInactivityTimeout             : 00:05:00
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : Unlimited
    MaxInboundConnectionPercentagePerSource : 100
    MaxRecipientsPerMessage                 : 200
    MessageRateLimit                    
    : Unlimited
    Adding logs for one big connection spike from the customer. About 50 inbound connections to the Exchange servers . 
    SMTP Receive;
    2015-01-26T18:02:46.991Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,0,DAG member 01:587,Customer IP:60262,+,,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,1,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,2,DAG member 01:587,Customer IP:60262,>,"220 DAG member 01 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,3,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,4,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,5,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,6,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,7,DAG member 01:587,Customer IP:60262,>,250-DSN,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,8,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,9,DAG member 01:587,Customer IP:60262,>,250-STARTTLS,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,10,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,11,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,12,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
    2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,13,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,14,DAG member 01:587,Customer IP:60262,<,STARTTLS,
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,15,DAG member 01:587,Customer IP:60262,>,220 2.0.0 SMTP server ready,
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,16,DAG member 01:587,Customer IP:60262,*,,Sending certificate
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,17,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate subject
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,18,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate issuer name
    2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,21,DAG member 01:587,Customer IP:60262,*,server;DAG member 01,Certificate alternate names
    2015-01-26T18:02:47.053Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,22,DAG member 01:587,Customer IP:60262,*,,TLS negotiation succeeded
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,23,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,24,DAG member 01:587,Customer IP:60262,*,,Client certificate chain validation status: 'EmptyCertificate'
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,25,DAG member 01:587,Customer IP:60262,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,26,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,27,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,28,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,29,DAG member 01:587,Customer IP:60262,>,250-DSN,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,30,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,31,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,32,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,33,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
    2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,34,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
    2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,35,DAG member 01:587,Customer IP:60262,<,AUTH LOGIN,
    2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,36,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
    2015-01-26T18:02:47.100Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,37,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
    2015-01-26T18:02:47.131Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,38,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnyRecCustomer IPient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
    2015-01-26T18:02:47.147Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,39,DAG member 01:587,Customer IP:60262,*,[email protected],authenticated
    2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,40,DAG member 01:587,Customer IP:60262,*,,Proxy session was successfully set up. Session [email protected] will now be proxied
    2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,41,DAG member 01:587,Customer IP:60262,>,235 2.7.0 Authentication successful,
    2015-01-26T18:02:47.819Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,42,DAG member 01:587,Customer IP:60262,-,,Local
    SMTP Send
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,0,,DAG member 02:465,*,,attempting to connect. Client proxy session for [email protected]
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,1,DAG member 01:57446,DAG member 02:465,+,,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,2,DAG member 01:57446,DAG member 02:465,<,"220 DAG member 02 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,3,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,4,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,5,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,6,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,7,DAG member 01:57446,DAG member 02:465,<,250-DSN,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,8,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,9,DAG member 01:57446,DAG member 02:465,<,250-STARTTLS,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,10,DAG member 01:57446,DAG member 02:465,<,250-X-ANONYMOUSTLS,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,11,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,12,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS GSSAPI NTLM,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,13,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,14,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,15,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,16,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,17,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,18,DAG member 01:57446,DAG member 02:465,<,250 XSHADOWREQUEST,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,19,DAG member 01:57446,DAG member 02:465,>,X-ANONYMOUSTLS,
    2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,20,DAG member 01:57446,DAG member 02:465,<,220 2.0.0 SMTP server ready,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,21,DAG member 01:57446,DAG member 02:465,*,,Received certificate
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,23,DAG member 01:57446,DAG member 02:465,*,,Proxy target certificate
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,24,DAG member 01:57446,DAG member 02:465,*,"CN=*.email.com, OU=IT, O=X, L=X, S=X, C=SE",Certificate subject
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,25,DAG member 01:57446,DAG member 02:465,*,"CN=DigiCert High Assurance CA-3, OU=www.digicert.com, O=DigiCert Inc, C=US",Certificate issuer name
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,28,DAG member 01:57446,DAG member 02:465,*,*.email.com;email.com,Certificate alternate names
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,29,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,30,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,31,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,32,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,33,DAG member 01:57446,DAG member 02:465,<,250-DSN,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,34,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,35,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM LOGIN,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,36,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS EXCHANGEAUTH GSSAPI NTLM,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,37,DAG member 01:57446,DAG member 02:465,<,250-X-EXCHANGEAUTH SHA256,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,38,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,39,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,40,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,41,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,42,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,43,DAG member 01:57446,DAG member 02:465,<,250-XSHADOWREQUEST,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,44,DAG member 01:57446,DAG member 02:465,<,250-XPROXY,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,45,DAG member 01:57446,DAG member 02:465,<,250-XPROXYFROM,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,46,DAG member 01:57446,DAG member 02:465,<,250-X-MESSAGECONTEXT ADRC-2.1.0.0 EPROP-1.2.0.0,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,47,DAG member 01:57446,DAG member 02:465,<,250 XSYSPROBE,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,48,DAG member 01:57446,DAG member 02:465,>,X-EXPS EXCHANGEAUTH SHA256 ,
    2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,49,DAG member 01:57446,DAG member 02:465,>,<Binary Data>,
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,50,DAG member 01:57446,DAG member 02:465,<,235 <authentication information>,
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,51,DAG member 01:57446,DAG member 02:465,>,XPROXY SID=08D2051B7AE3DA8E IP=Customer IP PORT=60262 DOMAIN=customerdomain.com CAPABILITIES=0 
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,52,DAG member 01:57446,DAG member 02:465,<,250 XProxy accepted and authenticated,
    2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,53,DAG member 01:57446,DAG member 02:465,*,,Proxy session successfully set up for [email protected]. Inbound session will now be blindly proxied
    2015-01-26T18:02:47.819Z,Client Proxy Send Connector,08D2051B7AE3DA8F,54,DAG member 01:57446,DAG member 02:465,-,,Remote
    Nothing after these logs indicating any type of issue with the receive connector. Tried to make the logs as anonymous as possible. Hope they still make sense.
    Note; Database was active on DAG member 02 but all incoming traffic on port 587 was directed to DAG member 01.

Maybe you are looking for

  • Music skips and stops and starts

    Hello, we have just got a nano to replace a 3rd gen iPod. I have around 50 gigs of music on a lacie USB drive, and the music plays flawlessly from here in iTunes. However once imported into the nano, there is distortion, jumps and clicks in the music

  • How can I sync my documents on my devices if I have two different Apple IDs

    I would like to be able to sync my Pages documents on all my devices.  However, one of my devices uses a different Apple ID (my work one).  Is there any way to get Pages to sync the documents created with the first ID onto the device with the second

  • Xsl:output function fully implemented in XSL-processor?

    I'm using XSL-processor as contained in the XML-parser version 2.0.2 in C. When changing the referring DTD of an incoming XML-message with following XSL-stylesheet <xsl:output method="xml"/> <xsl:output ommit-xml-declaration="no"/> <xsl:output standa

  • Manufacturer Part cycle AMPL Error

    Hi Gurus, I am testing the MPN cycle where My internal  material number is A00001 (2 MP material A00001_1 , A00001_2 with mat type HERS ) I am buying this from vendor 100328 (ac group 0001) where there are 2 source of the material  manufacturer 10069

  • Satellite A200 13M - black screen and will not switch off

    Hello I hve just purchased a *Satellite A200 13M*. At first power on, Windows Vista seemed to be correctly installed and internet connection (wifi) was working. The Norton programme was updated, and I was able to download and install OpenOffice. Howe