Microsoft just released the Cumulative Update 1 for Configuration Manager 2012 R2.
Here you will find what they fixed in this CU1 release (it’s a lot!): http://support.microsoft.com/kb/2938441/en-gb
Changes to Powershell cmdlets
They did really well with this new release and what I’m really happy about is the fixes they made to the Powershell cmdlets.
Read here to see which cmdlets they changed: http://support.microsoft.com/kb/2932274
How to install the CU1 for ConfigMgr 2012 R2
Here’s a quick walkthrough of how to install the CU1. After downloading the about 82MB large CU1, you first need to extract it to get to the CM12-R2CU1-KB2938441-X64-ENU.EXE file. Execute and accept the EULA. The pre-req check runs and shows you if there is anything preventing the update from running. I don’t know why it detected a pending restart, I just rebooted that machine.
After this the installer will ask you if you want to also install the update for the Admin Console (which will also have the update to the Powershell cmdlets), tick that box!
This update also contains an update to the database. You can chose not to do this, if for example you don’t have any permissions on the DB. Then you’ll need to provide your DBA with the SQL file to update the DB, otherwise the CU1 update will not be complete! You will find the update.sql file in a folder similar to this: C:\Program Files\Microsoft Configuration Manager\hotfix\KB2938441
You will also want to have the update packages created for the console, the clients and Site Servers / Systems.
You can now chose to specify your own names for the update packages and then get an overview of the update process.
Fire the installation off and watch it go all the way through.
The hotfix will have created the following packages, it is now your responsibility to deploy them to the correct machines. Remember, you can’t use the ‘Automatic Upgrade Client feature’ for Cumulative Updates!
Your clients and consoles will show the new version of 5.0.7958.1203 after successful installation of the CU1 update. Furthermore on your Site Server you can check the following registry location:
Good luck with your update!