Are you planning to upgrade SCCM 2012 R2 very soon? OK, take a minute to go through the following list about already identified issues or known issues with CM 12 R2.
I’ve already noticed 10 issues with SCCM 2012 R2. I’ll keep this list updated whenever I hear about new issues. Also, the SCCM 2012 R2 upgrade checklist is available for the SCCM 2012 SP1 to R2 Upgrade Checklist.
SCCM ConfigMgr 2012 R2 Known Issues
Also, check out the comments section to know more about known issues.
SCCM 2012 R2 Cu2 has already been released. You don’t need to install SCCM 2012 R2 CU1 if you’ve not installed it yet.
More details Download and Install SCCM 2012 R2 CU2 Cumulative Update 2 on CAS and Primary servers – See more at: https://www.anoopcnair.com/2014/07/09/download-install-sccm-2012-r2-cu2-cumilative-update-2-cas-primary-servers/
SCCM ConfigMgr 2012 R2 CU1 has been released. Download and keep it ready to apply CU1 to post R2 installation.
Download SCCM Configmgr 2012 R2 Cumulative Update CU1 – See more at: https://www.anoopcnair.com/2014/03/28/download-sccm-configmgr-2012-r2-cumulative-update-cu1/
Also, a List of Post SCCM ConfigMgr 2012 R2 Hotfixes will be helpful for SCCM admins !! SCCM ConfigMgr 2012 R2 Known Issues.
The package replication will fail when we change the maximum number of retries to less than the default value (100 retries). Also, SMSExec will crash. Awaiting for hotfix soon 🙂
End-user systems were getting rebooted after ConfigMgr 2012 R2 client upgrade. Microsoft Visual C++ 2010 Redist (version 10.0.40219.1) is now a prerequisite for the ConfigMgr 2012 R2 client – See more
A hotfix is available to resolve this issue. –> http://support.microsoft.com/kb/2905002
It seems SCCM or ConfigMgr 2012 R2 upgrade is causing some slowness to the OSD process. This is related to BITS downloads (Windows Image, boot image, and other contents) during WinPE. – See more
3. Another post talks about MDT 2013 known issues that Microsoft already documented. More details here.
SCCM 2012 R2 CAS and ConfigMgr 2012 primary servers went into Maintenance mode after the R2 upgrade. This is applicable if you’re using PULL DP in your environment. More details here.
Following error in the log file. The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: Logon failure: unknown user name or bad password. (rsRuntimeErrorInExpression).
The workaround to this issue is in the following link here.
Update: The above workaround is not working for some users, and the registry values are getting automatically changed again and again. Some more analysis and solutions in my latest post here SCCM 2012 R2 Upgrade Breaks SSRS with UserTokenSIDs contains an error.
“Device Variables of newly added devices aren’t available during OSD and OSI Task Sequences.” This issue is only applicable: When you add collection variables to a device or computer object rather than defining collection variables to a collection.
Fix available for the issue kb/2907591
7. Asset Intelligence Sync Stops working after SCCM ConfigMgr 2012 R2 Upgrade
SCCM ConfigMgr 2012 R2 Asset Intelligence (AI) synchronization works for a couple of days and then stops. More details here.
Several customers reported that child primary sites were entering maintenance mode after upgrading the central administration site from SCCM 2012 (SP1) with CU2 or CU3 to CM 12 R2. Entries similar to the following were recorded in the RcmCtrl.log file at child primary sites: More Details here. SCCM ConfigMgr 2012 R2 Known Issues.
9. Network access account (NAA) credentials are lost during the update this may cause you TS failure error with error 80070002.
Removing the network access account (NAA) and re-entering the NAA again may solve the issue. SCCM ConfigMgr 2012 R2 Known Issues.
ContentProgressEx invalid request GUID handle). Changing the TS setting to download locally as needed “fixes” the problem. This is registered as a bug (Bug ID: 201683) with no hotfix available. This is the latest update available.