The current talk around CRM at the moment is all about the Spring Wave AKA the CRM 2016 Update 1. Unlike Dynamics CRM 2015 Update 1, released at the same time last year, On-Premise customers can also take advantage of the latest update now by downloading Service Pack 1. Now it’s worth pointing out that some features, such as Guided Help and Field Service Management, are not made available to On-Premise customers at this time. Nevertheless, I think it’s a really positive step forward that On-Premise customers get most, if not all, of the latest updates as part of the Spring Wave, at the same time as Online customers. I’ve already talked previously about some of the great things to expect as part of the Spring Wave, so I would strongly recommend that organisations look at scheduling in their on-premise upgrade sooner rather than later. The main reason is the simplicity involved behind the actual upgrade process, which is the focus for this week’s blog post:

How to Download Service Pack 1

If you have enrolled your Dynamics CRM installation into Windows Update, then currently SP1 does not appear when your run Check for Updates on your CRM Server (this will change starting from Q3, according this knowledgebase article). Therefore, you will need to download the update manually via the following link:

There are a number of install files available as part of the update. On first glance, it can be difficult to determine which update file relates to which component of your CRM installation, so I have provided a summary of this below:

CRM2016-Client-KB3154952-ENU-Amd64.exe – Outlook Client (64 Bit)
CRM2016-Client-KB3154952-ENU-I386.exe – Outlook Client (32 Bit)
CRM2016-Mui-KB3154952-ENU-Amd64.exe – Outlook Client (64 Bit) Language Pack – English
CRM2016-Mui-KB3154952-ENU-I386.exe – Outlook Client (32 Bit) Language Pack – English
CRM2016-Router-KB3154952-ENU-Amd64.exe –  Email Router (64 Bit)
CRM2016-Router-KB3154952-ENU-I386.exe – Email Router (32 Bit)
CRM2016-Server-KB3154952-ENU-Amd64.exe – Server Update
CRM2016-Srs-KB3154952-ENU-Amd64.exe – Reporting Extensions

There is also a final file – CRM2016-Tools-KB3154952-ENU-amd64.exe – which I believe may be some kind of utility to perform database upgrades. I have been unable to get this working successfully on my end and, from the looks it, the server update performs the database upgrade as part of the update. If anyone knows what this is for and how it works, let me know in the comments below.

Installing the Update

The update is really simple – this is backed up by the fact that it can be completed in as little as 6 button presses!

After running the self-extracting installer, you will be greeted with the first screen of the setup process:


As is always the case, accept the license agreement:


Then, confirm that you are ready to begin the installation:


The installation process shouldn’t take long (about 10 -15 minutes when I performed it). Once complete, you’ll then be able to view the installation log file and specify whether or not you want to restart the server immediately:



As part of the update, your organisations and databases will be automatically updated to the latest version. So, no need to manually perform this yourself after the update.

Reporting Extensions Update

The only thing to point out with this is that this will need to be installed on the same machine as your CRM’s SSRS instance. Depending on your On-Premise deployment, your SSRS instance may be installed on a different server. The actual process of installing the update is identical to the above. Fortunately, however, a server reboot is not required 🙂

Outlook Client Update

Updating the Outlook client is also very similar and straightforward. Any existing connections will still work after the update. You will also need to install the update(s) for any currently installed language pack(s) immediately after this update is complete. In most cases, this will just be the one update for your CRM organization’s base language. Depending on the size and complexity of your CRM deployment, you may need to plan carefully to ensure a successful roll-out; you may be happy to note that the existing CRM client should still work with a 8.1 CRM instance, so you can always choose to defer this part of the update entirely.

The Testing Conundrum

As with any application update, it is always prudent to ensure that you have performed some kind of testing. This can be invaluable in identifying issues that can then be resolved in good time, without causing disruption to colleagues/end-users of the application.

The difficulty in this particular case is that the update appears to automatically update all organizations on a CRM instance in one fell swoop. So you cannot, for example, setup a copy of your primary CRM instance that you can perform a test upgrade on. You would therefore have to deploy an entirely separate CRM instance which you can perform the necessary testing on. You can use a trial key to cover the initial licensing hurdle, but you will still need to allocate hardware and put time aside to get your temporary testing environment setup.

Given that this release is not a “major” release of the application, I would argue softly that you can probably throw caution to the wind and perform the update with a minimal amount of testing, particularly if your CRM instance has not been significantly customised/extended. There does not appear to be anything majorly changed under the hood of CRM for this release that could cause problems (unlike the 2015 Spring Wave release for CRM Online). In order to best inform your decision on this, you should consider the following factors:

  • Are you able to schedule your CRM update over a weekend or extended out of hours slot, and have resources in place to perform any post-update testing? If the answer is yes, then you may be able to get away with not performing any pre-update testing.
  • What is the maximum amount of time your CRM instance can be taken down for during normal working hours?
  • Does your CRM utilise the Email Router, CRM for Outlook and/or multiple language packs? If yes, then performing upgrade testing of these components may be beneficial.
  • Does your business have a spare Windows Server instance that can be used for a test upgrade, without incurring additional cost to the business? If yes, then a major impediment has been eliminated, meaning that you should look at performing a test update.

Has anyone performed an On-Premise upgrade to SP1 yet? Let me know your experience and comments below!

8 thoughts on “Installing Dynamics CRM 2016 SP1 (On-Premise)

  1. Pingback: Form Scripting, Interactive Service Hub and Other Considerations - Microsoft Dynamics CRM Community

  2. Martin Franz on 21st July 2016 at 7:46 am said:

    we already performed the upgrade to service pack 1. It is a bit strange, when checking the version of an organisation, which was already created before the update (i.e. our PROD system), we see ( (DB So the database version was NOT upgraded. Organisations created after the upgrade have db version 8.1.
    We don’t know, if this is a bug or feature. At least, we cannot apply solutions created for 8.1 on this organisation. Does anybody have the same issues?

    Besides that: after the upgrade, the application did pass all regression tests without any new problems, something we did not expect, as we have a lot of customizations – not all conforming to standard. We have some issues with a sporadical internal error. At least, the error does not affect the process, simply clicking solves the issue.

    Best regards, Martin

    • The CRM Chap on 21st July 2016 at 7:10 pm said:

      Hi Martin,

      Thanks for sharing your experiences. Did you have any joy figuring out how to use the CRM2016-Tools-KB3154952-ENU-amd64.exe file, as I believe this may facilitate the database upgrade for organisations? It looks to contain some kind of command line executable, but unfortunately no instructions on how to use 🙁

      Glad to hear that the update did not cause you any major issues, from what I’ve seen there is nothing big in there a la 2015 Update 1, so hopefully your experience will give others confidence to update as well.



      • Martin Franz on 22nd July 2016 at 9:23 am said:

        Hi Joe,
        thanks for the hint about the command line tool – I will give that a try (fortunatelly I still have some test/development system which were created with 8.0 and updated to 8.1 having the same crm/db version mismatch).

        Some more issues (positives as well as negatives) after the upgrade:
        Web API – when using v8.1 in the url – works now more as documented. We have transformed some REST queries into Web API, tests were promising, will put that to production soon.
        Web API with FetchXML is a bit a pain. Paging works different than with “normal” queries. And, we have troubles with the paging cookie. I will investigate that in more detail soon. At least, paging also works without the paging cookie…as there is a performance implication according to documentation, we will wait until we solved it, before we use that in production.
        We could track down the “Internal error, send it to Microsoft” to a non-standard modification. We removed that modification; at least the last (production) day we did not get that error. Details: we changed the HTML tab order to have the cursor jump from left2right (heck, why can’t that be done in standard!?).
        Also positiv: we nearly always got an “Internal error, send to MS” in the development environment, when adding entities to a solution. This seems to be solved.

        My recommendation is: if you plan to upgrade an existing 8.0 installation, first check, if you also get that crm/db mismatch. Maybe there is some documentation about how to upgrade the database version, or maybe only we are experiencing that.


  3. Joao Paulo Mendes Proença Norte on 23rd September 2016 at 1:12 pm said:

    In balanced environment is required to run the setup upgrade in both CRM machines?

    • The CRM Chap on 23rd September 2016 at 7:41 pm said:

      Hi Joao,

      By balanced environment, I am assuming you mean a multiple-server deployment? When applying the update myself, I applied the update against a CRM instance where all roles were installed on the same server. I would imagine that on a multiple-server deployment then yes, you would need to run this on all machines that contain an installed server role. If anyone out there is able to confirm or deny this, that would be a big help!



  4. Got an unusual error when going into System Settings: More info at this link:

    • The CRM Chap on 24th September 2016 at 7:04 am said:

      Hi Chris,

      Have you tried the steps Andrii has outlined in his reply post to see if that resolves the issue? Also, have you restarted your CRM, SQL/SSRS etc. servers since applying the update?



Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Post navigation