Friendly reminders about applying Microsoft Dynamics CRM Update Rollups

1. Customized web.config files need to be manually updated. If you modify the web.config file for any reason, such as increasing the attachment size restriction, the rollup installer will not replace it with any updates. For this reason, it’s always a good idea to keep a backup of the original web.config file so you can allow the rollup to replace it, and then compare changes. 

2. Rollup 7 is a prerequisite for applying subsequent rollups for the Outlook Client and the Data Migration Manager. There were a few “significant” updates included in rollup 7 that rollups 8 and 9 are expecting to be in place before they can be applied. A good sign that you are trying to apply a post 7 rollup without this prerequisite is the error: “KB971782_Client was not found on the system.” (KB971782 is the Update Rollup 7 release) 
   
    

3. It’s always a good idea to keep the server rollup version and client rollup versions in sync. Technically speaking they don’t need to be in sync, but if not, it’s just one more variable when troubleshooting issues. 

4. Backup, backup, backup. Occasionally there are issues with the rollups (see rollup 2), and they are re-released after the bugs are fixed. 

Feel free to comment if you have any questions about these watch-outs.