Category: Miscellaneous

  • When will my cloud get updated? CRM Online and Update Rollup status

    The benefits of running your Dynamics CRM application in Microsoft’s cloud is that you don’t have to worry about installing update rollups to your server, since MS takes care of all that maintenance. The downside is that you can’t be sure when exactly the updates take place. As we’re coming closer to the expected release date of Dynamics CRM R8, it’s a good time to reflect on the past update schedules of CRM Online.

    As of mid-June, CRM Online organizations are still running only the Update Rollup 5 version (at least on the EMEA CRM4 data center), while on-premises environments may already be running Update Rollup 8. No matter if you use an existing environment or sign up for a new trial organization, the version you get is 5.0.9688.1561. This corresponds to roughly the build number of on-premises UR5, which is 5.0.9688.1533, whereas Update Rollup 6 is 5.0.9690.1992 already. How can you check the version of your CRM Online application? Simple: on the browser client just click File – Help – About Microsoft Dynamics CRM. You’ll see version from the top of the pop-up screen.

    So, where do I go to translate those ten digits into a human readable version name? For the list of detailed build numbers, related KB articles and other information, be sure to bookmark this page on the Dynamics CRM In The Field blog: Microsoft Dynamics CRM 4.0 and 2011 Update Rollup Release Dates, Build Numbers, and Collateral. That page is being updated as new rollups are released and it also has in the past contained projected release dates of upcoming updates as well. Has, since at the time of writing it no longer does. Also note that the CRM Online build numbers and release schedules can and will differ from on-premises, as we’ve already seen.

    How to check the Update Rollup version on CRM Online

    Back when Update Rollup 7 was released on March 22nd, the accompanying post on the CRM Team blog promised the CRM Online Datacenter update schedule to “Mid to Late April, 2012”. This was also the information on the related article KB 2600643, but things have changed since then, as now all the post UR5 KB articles read:

    For online customers Infrastructure improvements are being made to CRM Online. Because of this, update rollups will not be applied to servers until the improvements are complete. Through the System Notifications page for the system maintenance window, you will be notified of when your organization will be updated to the new infrastructure. The latest updates will be applied at that time. 

    It’s no secret that Microsoft is working on bringing the Dynamics CRM Online and Office 365 clouds onto a single platform and unifying many of the surrounding components, such as subscription management or user authentication. This has apparently caused the planned schedules of Update Rollups to CRM Online get changed from those earlier communicated. When UR5, also known as the Q4 2011 Service Update, was released, it was deployed first to CRM Online environments before becoming available for on-premises and hosted environments. Since then we’ve seen UR6, UR7 and UR8 all get released to the on-premises environments first, with CRM Online remaining in the “UR5+” status for quite some time. Note that the builds are not exactly the same and there are likely to be differences in what the terminology means for different platforms. For example, UR6 brought support for SQL Server 2012, but we’ve already heard Microsoft say that CRM Online was running on SQL 2012 long before that.

    What the current status of updates to the Microsoft hosted cloud means that CRM Online customers are not yet able to leverage enhancements brought in UR6-8, such as the read-optimized forms introduced in Update Rollup 7. Also any server side bugfixes and functional changes beyond UR5 must be assumed to be lacking from CRM Online organizations, although we can’t know for sure what may have been applied as hotfixes. For example, problems with connections not merging when deactivating duplicate records was fixed in UR7.

    On the client side things are a bit different, since all the Update Rollups are rolling onto CRM Outlook clients through Microsoft Update. There is no longer a separate client version for Online and on-premises, so everybody gets the same hotfixes. Even though Microsoft recommends that the client and server Update Rollup versions should be kept close to one another, they don’t need to be identical. Here’s what it says on the CRM In The Field blog:

    The general rule of thumb is to try to keep the versions in sync as much as possible. However, it is permissible (though not recommended as a long-term solution) to run mismatched Update Rollup versions on Outlook client and server, as Microsoft does do some testing of such combinations.

    So, since the CRM Online version difference is obviously well known by MS, the UR combinations shouldn’t be an issue for Outlook users who’ve deployed the latest Microsoft Update packages. Even if you’re using the offline database in your CRM Outlook client, I assume compatibility between the CRM Online database has been taken into consideration. Of course in the field of IT, you should never assume anything, rather you should test any Update Rollups in a dedicated test environment, but smaller CRM customers may not always have that luxury. Which gets us to the following rule of thumb: don’t ever be the first one deploy the latest Update Rollup once it’s released. Wait a few weeks and check out the CRM forums and blog posts to read about the experiences other users have with the latest update, only then decide to deploy the update onto production devices (first onto your own test servers and clients, if you have them available). The Dynamics CRM community tends to be quite effective in reporting new issues that arise with UR’s, so leverage the wisdom of the crowd and save yourself from some unpleasant surprises.

    The big question that many people are searching for an answer to is: when exactly will Dynamics CRM R8 / Update Rollup 9 / Q2 2012 Service Update be released? (In case that previous terminology trio made no sense to you, be sure to read my explanation of the “Dynamics CRM update & version madness”.) I wish we knew, but in reality only Microsoft has that information and it hasn’t been publicly communicated. We’ve got less than two weeks to go on the Q2 of 2012, which makes it a tight schedule to keep if also Online organizations would need to be updated in addition to releasing the on-premises bits. We need to remember that R8 is a very significant update due to the added cross browser support, which will surely keep many CRM developers busy with fixing legacy scripts, so any issues that the R8 beta program may have revealed certainly need to be thoroughly investigated and I’m glad if Microsoft is taking extra time to get the whole CRM Anywhere experience right with UR9.

    Status update 2012-06-20: As reported on XRM Services blog, the US data center CRM Online organizations were updated to 5.0.9690.2174 on June 19th, which translates to Update Rollup 7+ but still a bit below the Update Rollup 8 available for on-premises environments. A similar update has been scheduled to take place on EMEA data centers one week later, on June 26th. Since it’s quite unlikely that there would be several maintenance breaks on consecutive weeks, this appears to indicate that at least for CRM Online customers the long awaited R8 release, also known as Microsoft Dynamics CRM Q2 2012 Service Update, appears to be delayed from the original schedule and now seems to become “Q3 2012 Service Update”. It is of course still possible that the on-premises bits for Update Rollup 9 will be released before the end of June.

    Status update 2012-07-04: It’s Q3 now and we know for sure that the release of R8 has been delayed from Q2 2012. The service break for CRM Online on June 26th in EMEA didn’t actually bring any updates to the CRM application, but now there’s another maintenance break scheduled for July 11th. Since the US data center went from UR5+ to UR7+ in the previous round, this may just be EMEA catching up on the delayed Update Rollups.  I’ll update the post again as we see the results or hear announcements from Microsoft so watch this space.

    Status update 2012-07-07: Finally we have a release date of July 19th for CRM Online. However, the “CRM Anywhere” functionality has been dropped from the update and will not arrive until six months later in Q4 2012. Read my analysis on the announcements from this blog post.

  • Dynamics CRM update & version madness explained

    Things used to be simple back in 2005 when I started working with Microsoft Dynamics CRM (known as only Microsoft CRM back then). You pretty much knew that there would be a version update every 2-3 years. In between, there would be a number of hotfixes created to address software bugs, which were packaged as “Update Rollups”. CRM 3.0 received in total three such packages. CRM 4.0 things kicked up a notch as we started getting these Update Rollups (UR) based on a regular schedule, one update every 2 months (until they were put on hold after UR21). CRM 2011 adopted the same UR release schedule, but in addition to that, Microsoft announced that they would adopt a new agile release model.

    Exactly one year after the announcement we find ourselves in situation that may seem quite confusing to the casual observer. There are new releases in the horizon on a continuous basis and it’s easy to lose track of what exactly is meant by which update. Well, here’s my shot at explaining what’s going on.

    What’s the “R” in R8?

    R8 means Release 8. OK, so what are the previous seven versions then? They don’t refer to CRM 1.0, 1.2, 3.0, 4.0 or 2011 (there never was a 2.0, as some of you will remember). This R-based naming policy comes from the CRM Online product, which used to have its own release schedule with no UR’s and a slightly different code base from the on-premises product. The first R was presumably released when CRM Online was announced in April 2008. Things changed when Microsoft Dynamics CRM 2011 was released on January 15th, 2011, after which both the Online and on-premises version have pretty much gone hand in hand.

    The “Rx” naming signifies a new functionality release and should never be used to refer to Update Rollup versions. Don’t shorten UR8 to R8, because the two are not the same (even though they are intertwined as we’ll later see). The Update Rollup version numbers always start from 1, so there’s been an Update Rollup 1 for both Dynamics CRM 2011, CRM 4.0 as well as CRM 3.0. Makes googling for information all the more merrier, eh? The Rx releases are a product of the cloud era and until we reach the next era beyond cloud apps, I don’t expect Microsoft to start the numbers from R1 all over again.

    What’s the Q2 2012 Service Update?

    Since it would have been confusing for on-prem customers to first release Microsoft Dynamics CRM 2011, then follow it up with a “Release 7” all of a sudden, Microsoft decided to come up with a different naming policy for these new, agile releases. Unfortunately, the naming policy they chose gave us monsters like “Microsoft Dynamics CRM 2011 Q4 2011 Service Update”. Wow, how catchy, and only 50 characters long! As a result of this, what was originally supposed to be just internal jargon became the preferred option for human communication and we learned to know the update as R7. 50 vs. 2 chars, which one would you expect to fly in the age of Twitter? ‘Nuff said.

    Most of you must surely be already familiar with the contents of R8, the next release, and if you’re not, here’s a link to the Release Preview Guide. The real catch is in how the promised new features will actually be delivered. The correct answers to this question are:

    • In multiple Update Rollup versions
    • As solution files
    • Through Microsoft hosted, subscription based services or 3rd party licensing
    • In other Microsoft products

    A, B, C, D – tick ’em all. This is the reason why there will not be any single place where you can “download R8”.

    What will the Update Rollup 9 contain?

    The official release announcement of Q2 2012 Service Update will most likely coincide with Update Rollup 9. However, if you study the contents of the Guide, you’ll find features that have already been released before UR9. Rapid View Forms were introduced in March as part of UR7 and re-labelled as Read-Optimized Forms. The same is true for SQL Server 2012 compatibility.

    As we know from the previous R7 release, Activity Feeds are delivered as a solution package that you will need to download from the Dynamics Marketplace and configure manually. The Activity Feeds solution is not a part of the “core” Dynamics CRM product. However, there are parts of it that have been built into the platform, which is why at least Update Rollup 5 is required in order to install the solution. Similarly, you will need to get an updated version of the Activity Feeds solution after installing Update Rollup 9, otherwise you won’t see the new features.

    A key deliverable of Update Rollup 9 will be the cross-browser compatibility that makes Dynamics CRM available on Chrome, Firefox and Safari. Since this is such a significant change to the platform, Microsoft has been kind enough to grant access to the R8 beta release for anyone who’s willing to follow these steps. Please note that the beta bits available for download cannot be upgraded to the final release of R8, so use them in a test environment only.

    Extended browser support is completely separate from the mobile device support promised in R8. While you will be able to run CRM on an iPad Safari browser, the mobile UI demoed by Microsoft in numerous occasions is only available as 1) a subscription service from Microsoft, if you’re running Online or IFD, or 2) a perpetual license to be purchased from CWR Mobility if you intend to host the required service on your own server. Trying to access your Dynamics CRM environment after UR9 installation with an iPhone will most likely just give you the simplified Mobile Express user interface already familiar from the CRM 4.0 days.

    Oh, and do note that the Microsoft Dynamics CRM Mobile released for Windows Phone 7 back in Q4 2011 Service Update is a completely separate product, even though it carries exactly the same name as the new offering developed by CWR Mobility and later on re-labelled by Microsoft. Since CWR Mobility didn’t have a Windows Phone client, this mobile app will likely remain on a separate development roadmap from the CWR-based offering.

    What’s the role of SQL Server 2012 in all this?

    If you haven’t seen the cool drag & drop report designer or the animated bubble chart demo of Power View, take a look at this video:

    Wow, wouldn’t that look nice on a Dynamics CRM dashboard! Well, even though Power View is listed as one of the R8 features, there’s a couple things you should know:

    • It’s not available in the cloud. Sorry, CRM Online users. Maybe in R9 then?
    • CRM dashboards are a different data visualization technique that will remain “as is” for R8, not integrated with Power View.
    The pre-configured Power View templates promised in R8 will be delivered as a Dynamics Labs solution, probably as a download from the Dynamics Marketplace. The same goes for the PowerPivot models to be included. Note that if you want to publish these PowerPivots to your organization, you’ll need an on-premises SharePoint Server 2010 with Enterprise CAL’s to view their contents on a browser window in your intranet.

    In addition, if you plan to use SQL Server 2012 for hosting your Dynamics CRM database and Reporting Services, it’s good to know that you can’t achieve this configuration with the RTM bits for Dynamics CRM 2011. Update Rollup 6 has established a new baseline for CRM and you’ll need to download the server installation files from Microsoft Download Center, otherwise you’ll run into the following error while trying to install the Reporting Extensions:

    Unable to validate SQL Server Reporting Services Report Server installation. Please check that it is correctly installed on the local machine.

    What time is Metro?

    Putting things into perspective, Dynamics CRM is a small fish in the tank compared to the big whale that is Windows 8. Since R8 will be out well before Windows 8, there isn’t yet a 100% support provided for the Internet Explorer 10 browser provided with it. Hopefully the remaining issues will be addressed by upcoming UR’s as Windows 8 is nevertheless just around the corner. Presumably we’ll see a proper Metro app for Dynamics CRM once R9 is released later this year. After all, the Windows RT tablets will not be able to run Outlook and we’ll need some solution for activity tracking to and from CRM.

    When it comes to Windows Server 8, official support has not been announced. However, that doesn’t mean you couldn’t install Dynamics CRM 2011 Server on a Windows 8. Daniel Cai has done just that and offers a tutorial for anyone wanting to test R8 on the very latest Microsoft products available.

  • The price of customization

    Although this excellent article by Vjekoslav Babic is written from the ERP and MS Dynamics NAV perspective, the same list holds true for the CRM side as well:

    Top 7 reasons why to avoid (much) customization

    • Regressions can be tricky to hunt down and fix
    • Go-live schedule can be delayed if the customizations are not properly though out in advance
    • Official support does not cover custom code, how do you then identify if problems in your system are covered or not?
    • Upgrade to the next version will become more difficult and expensive
    • Know-how only exists within your organization, so proper documentation becomes a critical factor for risk management
    • Vendor lock-in is almost inevitable, which in practice means rewriting the code if the co-operation with your vendor is no longer working
    • Help for the users needs to be developed and maintained in-house, since user guides and courseware can’t possibly cover your custom processes

    The relative ease of developing custom solutions on top of applications like Microsoft Dynamics CRM can easily lead you to dangerous path. Just because you can quickly implement it, does not mean that it will be cheap in the long run. Unless you are able to identify these hidden costs of customization in advance, you may find yourself singing up for something that will ultimately cost you more than the potential benefit to be derived from the custom solution.

    So, just because you can, does not mean you should.