locked
Upgade a multi-tenant CRM 2013 on premise system RRS feed

  • Question

  • Hi

    Can someone please advise as to how to upgrade a three server CRM 2013 instance? Am I right in thinking that you start with an upgrade on the first server and then have to run the software again on the other two servers? Do you need to detach on any of the machines first and reimport?

    Thanks

    Saturday, February 7, 2015 6:50 PM

Answers

  • Your steps above are as I'd do, except for Rickard's point that it would be better (maybe necessary, I can't remember) to reinstall the CRM Reporting Services component. This would give these steps:

    • Snapshot all VMs
    • Backup config and org databases
    • Disable load balancing
    • Uninstall CRM Reporting Services component
    • Upgrade server1
    • Upgrade server2 - yes, this just updates the crm files on the server
    • Install CRM 2015 CRM Reporting Services component
    • Reenable load balancing
    • Test and confirm

    The Crm 2013 Outlook client can work with Crm 2015 Server, though I'd suggest you upgrade it as well. You can upgrade the client either before or after upgrading the server


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    • Marked as answer by sjb500 Tuesday, February 10, 2015 10:27 AM
    Tuesday, February 10, 2015 10:25 AM
    Moderator

All replies

  • Hi,

    it looks like you are considering inplace upgrade. Based on my experience this is not the best way to go. I would suggest to install CRM 2015 in new envrinoment in the final setup and then importing the CRM 2013 database into this environment.

    Michal

    Saturday, February 7, 2015 9:43 PM
  • Thanks for the response. But really? So our current three farm 2013 solution would need to be replicated entirely as 2015 with all the work that that entails setting up boxes, opening ports, establishing ADFS trust, generating urls, importing & upgrading dbs, migrating users Outlook clients etc etc. I can't see that being viewed particularly favourably. Is there really no approved upgrade path for a standard multi-tenant soln. I can see us instead deciding to jump ship and move to Salesforce!
    Monday, February 9, 2015 7:27 AM
  • You can upgrade in-place. The main reason for upgrading to a new environment is that it gives a quicker rollback process in the event of problems. However, providing you've done a full test upgrade (doing this for one server is probably sufficient, as this will include the database upgrade) in advance, you should be confident that the upgrade will work without problems.

    You do need to run the upgrade on each of the servers. What server roles do you have on each server ?

    • If you have multiple front-end servers that are load balanced, it would be best to turn off access to the load balanced URL during the upgrade
    • If the servers have separate roles, then you don't to detach any (and it is simpler if you don't)

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Monday, February 9, 2015 3:55 PM
    Moderator
  • Hi and thanks for the response. Great, so it sounds possible to upgrade a multi-tenant in-place. I have already tested the upgrade on a copy of the org on a separate box and all seemed well. Would you be able to confirm or otherwise modify what I think are my steps for a successful upgrade?

    1. Snapshot all VMs
    2. Backup config and org databases
    3. Disable load balancing
    4. Upgrade server1
    5. Upgrade server2 (will this do anything given that the db was already upgraded in step 4?) - I guess, if nothing, this just updates the crm files on the server?
    6. Upgrade report server - does this need to be done?
    7. Reenable load balancing
    8. Test and confirm

    Does the outlook client also need upgrading or otherwise changing?

    Thanks again

    Tuesday, February 10, 2015 9:09 AM
  • I think you should start with uninstalling the reporting services component (not the reporting services server but the CRM component).

    I did an in-place upgrade of CRM4->2011 and I didn't turn off any load balancing, unsure if that was pure luck or not, but it worked. The backing up of everything is of course the first step.

    For some weird reason an in-place upgrade was so much quicker than a migration upgrade for that system which ran for 9 hours and then crashed. With the in-place it was completed in less than 4h IIRC.

    One thing you should make sure you do on a load balanced system is to have everything in the database if you don't have it already.

    Regards


    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se
    My Blog: http://rickardnorstrom.blogspot.se

    Tuesday, February 10, 2015 9:33 AM
  • Your steps above are as I'd do, except for Rickard's point that it would be better (maybe necessary, I can't remember) to reinstall the CRM Reporting Services component. This would give these steps:

    • Snapshot all VMs
    • Backup config and org databases
    • Disable load balancing
    • Uninstall CRM Reporting Services component
    • Upgrade server1
    • Upgrade server2 - yes, this just updates the crm files on the server
    • Install CRM 2015 CRM Reporting Services component
    • Reenable load balancing
    • Test and confirm

    The Crm 2013 Outlook client can work with Crm 2015 Server, though I'd suggest you upgrade it as well. You can upgrade the client either before or after upgrading the server


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    • Marked as answer by sjb500 Tuesday, February 10, 2015 10:27 AM
    Tuesday, February 10, 2015 10:25 AM
    Moderator
  • Thanks all for help and advice - much appreciated.
    Tuesday, February 10, 2015 10:27 AM