Last week, Microsoft announced the release of Configuration Manager 2012 SP2 and Configuration Manager 2012 R2 SP1. Our post will list everything you need to know before applying this major update.
The main reason you will want to upgrade to Configuration Manager 2012 R2 Service Pack 1 is probably for Windows 10 support. No plan for Windows 10 deployment in your organisation? There’s interesting new features and a lots of bug fixes (thousands, which are not fully documented) in this release that are worth it. See the full list of features on this Technet Article.
Following the announcement, the community was confused on how to apply this Service Pack because Microsoft decide to release it under one binary even if there’s 3 possible “version” of Configuration Manager 2012. (RTM, SP1, R2)
- If you’re running Configuration Manager 2012 SP1 (non-R2) the upgrade process will bring your site to SCCM 2012 SP2
- If you want to upgrade to Configuration Manager 2012 R2 SP1 afterward, you’ll need to run another executable which will enable the R2 features
- If you’re already running Configuration Manager 2012 R2, the update process will bring your site to Configuration Manager 2012 R2 SP1
Fellow MVP Jason Sandys explain all the upgrade options in an excellent post. The key is really to understand the upgrade process by identifying your actual version and the desired final version.