During month of March 2014,Microsoft released first Cumulative Update CU1 for Configmgr 2012 R2 and now ,Microsoft released 2nd Cumulative Update CU2 for System Center Configuration Manager 2012 R2 with lot of fixes,powershell changes and some of them been modified.
This Update (Cumulative Update 2) Replaces Cumulative Update 1 .If you have not installed R2 CU1 yet,you can directly go with Cumulative Update 2.
Download the Cumulative Update 2 from http://support.microsoft.com/kb/2970177
Description of Windows PowerShell changes in CU2 http://support.microsoft.com/kb/2962855
About Cumulative Update documentation,creation of collection ,refer http://technet.microsoft.com/en-us/library/jj553405.aspx
You can apply this update to:
Central Administrative site
Primary Site(Stand Alone)
Primary Site(Hierarchy)
Secondary Site
SMS Provider
Configuration manager console
Client
Admin Console Version :5.00.7958.1303
Configmgr Client Version:5.00.7958.1303
No Version change to Site System :5.00.7958.1000
So what are issues that are fixed and functionality that is updated in Cumulative Update 2 (CU2) ?
- Administrative Console
- Remote Control
- Mobile Device Management /Intune
- configmgr Client
- Operating System Deployment
- Site Systems
- Application Virtualization
- Content Management
- Windows Powershell
- Additional changes to Ubuntu OS 14.04
- Cloud based Distribution Point
This update do not require Restart after the installation but recommended to close the admin console before you start the installation.
How to determine the installation status of this cumulative update:
This cumulative update changes the following Configuration Manager version numbers and installation properties.
The CULevel value is located under the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup
The CULevel value is set to 2 for Cumulative Update 2.
Admin Console Version :5.00.7958.1303
Client Version:5.00.7958.1303
10 Comments
Hi
Installed CU2 on sccm2012 R2.
1) OSD deployment has became very slow. It was working fine.
2) The client on the desktops are still with old version (500 7958 1000)
Suggestion please.
did you install the CU2 hotfix on all clients ? if you have clients with 1000,you need to install the CU2 on clients .
for OSD slowness,check the smsts.log what is causing the problem
you will have to provide more information about the OSD slowness problem.
Note about version numbers...
5.0.7958.1303 --- Admin Console
5.00.7958.1303 -- Client
Very important when creating collection membership query based on installed Admin Console version...
They are already available on the post.To Create collections for R2 CU2,refer http://eskonr.com/2014/07/sccm-configmgr-2012-r2-collections-to-upgrade-clients-to-cu2-version/
it did same for CAS and primary sites. there was no other application deployment pending reboot. It didn't ask for reboot even in my lab. You didn't hear about this from any clients?
no,i dont see any information about reboot from any of my clients so far.
The cu2 update does need a reboot
I found this in the updatesetup log
To complete the installation, close this wizard and restart the computer.
Setup exit status: 0 (SuccessPendingReboot)
I have not seen in lab/production asking for reboot and CU2 article doesn't even say about reboot required. Updatesetup.log is something refers to other updates/applications installed and prompt for reboot ?
Does the CU2 include any of the fixes from CU1? If we still want to update with CU1 and CU2, do we need to install both in any particular order?
Thanks!
CU2 include all the fixes available in CU1,so you can directly go with CU2 ,skip CU1 if you have not installed it.