Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Upgrade to V9 and Windows Server 2016

  • 1.  Upgrade to V9 and Windows Server 2016

    Posted Dec 06, 2018 07:37 AM

    after Microsoft finally released some Updates for CRM On-Prem we are currently trying these updates out.
    Installing Update 2.3 wasn't a problem but my colleague encounterd quite a few issues with the v9 Update.
    Because our Servers are running on Windows Server 2012 R2 the first thing was that we needed a windows Server Upgrade.
    So we tried that but then the problems began: All Website Settings from IIS were gone and we don't really know how to restore them.
    We tried a few things but nothing did really help yet.

    After googling for a little bit I also saw that during the installation (we didn't do it but our Network team colleagues) that there is a message which says that an upgrade to Windows Server 2016 is not recommended and a clean Install should be done instead.
    But how should we do that exactly? Set up new servers, install CRM there and then import the Org Databases?

    So my question is, did someone try to upgrade a CRM Application Server to Windows Server 2016 and did it work?
    Also did someone do the upgrade to v9 already and has some input on that?


    Florian Ehemann
    CRM Developer
    Arthrex GmbH
    Academy - Online Interactive Learning from Experts

  • 2.  RE: Upgrade to V9 and Windows Server 2016

    Posted Dec 10, 2018 08:49 AM
    We haven't yet performed the upgrade, but I already talked about it with my colleague before.
    They would Setup new Servers with SQL2016 and then do a fresh install of CRM and afterwards do a data Migration.
    Afterwards all IP-related functions have to be changed too, to reflect the new IP-addresses (e.g. CRM-URL).

    For the data Migration we would also get the help of an external Company.

    Johannes .


    Academy - Online Interactive Learning from Experts

  • 3.  RE: Upgrade to V9 and Windows Server 2016

    Posted Dec 11, 2018 10:55 AM
    I would absolutely recommend setting up a new 2016 server, doing an install fresh, and then importing the organization.  (Though that doesn't import every single setting, since some are stored in the main database as opposed to the org one...but it does bring in the vast majority.)

    However, there is currently a major bug where V8 organizations cannot be imported into v9 without an unsupported workaround.  A bunch of us have tickets in with MS on it and it's being worked on, but there's no resolution yet.  Note - as far as I've heard, this is a 100% blocking issue.  I haven't heard of a single person being able to do it without the workaround.

    That being said, we did the workaround solely for a test environment (it involves copying in an older version of a patch file from the preview release), and after that it did seem to go well and we've noticed very few issues in the uograded org.  So once they fix the bug that's definitely the way to go.

    Allison Walters
    IT Coordinator
    Centre for Affordable Water and Sanitation Technology
    Calgary AB

    Academy - Online Interactive Learning from Experts

If you've found this thread useful, dive deeper into User Group community content by role