I’ve been installing a few lab and production ConfigMgr environments recently and found a little quirk with the versioning to go along with the service pack madness / confusion of the 2012 SP2 / 2012 R2 SP1 release. Here’s the scoop:
After installing ConfigMgr 2012 SP2 as a new / fresh install, how do you know if R2 is installed? There are really only two ways I can find:
- Launch the Configuration Manger Admin Console and check the about screen. The console version will be 5.0.8239.1000 and the site version 5.00.8239.1000 for both SP2 / R2 SP1; however the product name will show “System Center 2012 R2 Configuration Manager SP1” or “System Center 2012 Configuration Manager SP2” to indicate the difference.
- Review the 2012 R2 release notes (What’s New in System Center 2012 R2 Configuration Manager) and note the new features. If these exist within the Admin Console on the connected site, then R2 is installed. Probably the easiest check is in Software Library –> Operating Systems –> Virtual Hard Disks. The VHD feature set is part of R2 and won’t exist in a non-R2 site.
Some additional details
Where can the R2 installer be download from?
- If installing ConfigMgr 2012 SP2 / 2012 R2 SP1 from evaluation media, you’ll easily notice that there are 2 files to download and install. The small (1.1 mb) file is the “R2” installer / enabler. Otherwise the code base is identical between the versions / editions.
- If installing from MVL media, the small “R2” installer may not exist for download. I’ve only see 1 company’s MVL site and the file didn’t exist in any place we could think to look. Installing “R2” from the evaluation file, SC2012_R2_SP1_ConfigMgr.exe, worked fine on multiple MVL installed sites.
When I installed R2, there were almost no indications of the change.
- The actual install, ConfigMgr2012R2SP1.msi did not generate a log file that I could find
- The Windows Application Event Log did show that “Product Name: Microsoft System Center Configuration manager. Product Version : 5.00.8239.1000 … Reconfiguration” succeeded, but notice that the name does not identify SP2 or R2 SP1.
- C:\ConfigMgrSetup.log was not changed
- C:\ConfigMgrAdminUISetup.log was not changed
- C:\ConfigMgrAdminUISetupVerbose.log was not changed
- I could see no entries in any ConfigMgr site logs that gave any reference to a change
- I could see no changes in the Windows Registry at HKLM\Software\Microsoft\SMS\*
- The site properties in the Admin Console showed no changes
- Re-running the R2 installation gave no indication that it was already installed
- Re-running the R2 installation (ConfigMgr2012R2SP1.msi) with verbose logging did create a log file but there was no indication that it was already installed
- Windows Programs and Features (Add / Remove Programs) did not change the product name
So much for clarity!
Chad June 16, 2015
Posted In: Uncategorized
Tags: ConfigMgr; SCCM