Cumulative Update 3 for ConfigMgr 2012 R2 SP1 and 2012 SP2 released

Yesterday (February 25th) Cumulative Update (CU) 3 for ConfigMgr 2012 R2 SP1 and 2012 SP2 is released. This update contains 23 (!) fixes for various issues including an update version of the SCEP client, and contains all of the changes from prior cumulative updates.
 
Here's a list of issues that are fixed, there are quite a lot of them:
-Administrator Console (4 fixes)
-Operating system deployment (3 fixes)
-Configuration Manager client (1 fix)
-Microsoft Intune and mobile device management (3 fixes)
-Site systems (6 fixes)
-Software distribution and content management (4 fixes)
-Settings management (2 fixes)
 
Additional changes that are included in this update:
-Endpoint Protection - Revised February 2015 anti-malware platform update for Endpoint Protection clients
-Supported operating systems - Mac OS X 10.11 can be targeted as a client platform for the following features: Application Management & Settings Management
-Software updates management on operating system deployment - A new optional task sequence variable, SMSTSWaitForSecondReboot, is available to better control client behavior when a software update installation requires two restarts. This variable should be set before the "Install Software Updates" step to prevent a task sequence from failing because of a "double reboot" of a software update. This can be useful when hundreds of updates are being applied in a single "Install Software Updates" task sequence step. (like on Windows 7 images)
-Reporting - Windows 10 is now available in the Upgrade Assessment Report (Upgrade Assessment Tool required)

Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update. Great that CU3 is available now!

This update replaces Cumulative Update 2 for System Center 2012 Configuration Manager R2 SP1 and 2012 SP2

For more information or download the update have a look here:
Microsoft Support

Install Cumulative Update 2 for ConfigMgr 2012 R2 SP1 and 2012 SP2

Today Microsoft called me with the news that Cumulative Update 2 (CU2) for ConfigMgr 2012 R2 SP1 and 2012 SP2 is released. This because I had some issues at customer location with Intune extensions not working in a hybrid ConfigMgr environment. With CU2 those issues must be gone now! KB3100144 (CU2) solves a lot of issues and is therefore highly recommended. It contains 34 (!) fixes and improvements and some additional changes too.

More about that can be found in another blogpost. No need to install KB3074857 (CU1) anymore after installation. This because it's integrated in CU2 now.

During installation (which is default as always) update packages will be created for site servers, ConfigMgr consoles and clients. When having Intune integrated in ConfigMgr (hybrid configuration), extensions will be updated as well. Great that CU2 is available now, and hope that ConfigMgr vNext will released soon too.

After installation you will see Console version 5.0.8239.1301 now, which is the latest release. Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update.

Update: There was a minor bug in the first CU2 release. The product group has released a new build now. If you are installing using the new build, the console version will be 5.0.8239.1302

Cumulative Update 2 for ConfigMgr 2012 R2 SP1 and 2012 SP2 released

Yesterday (November 10th) Cumulative Update (CU) 2 for ConfigMgr 2012 R2 SP1 and 2012 SP2 is released. This update contains 34 (!) fixes for various issues including an update version of the SCEP client, and contains all of the changes from prior cumulative updates.

Here's a list of issues that are fixed, there are quite a lot of them:
-Administrator Console (3 fixes)
-Configuration Manager client (3 fixes)
-Site systems (6 fixes)
-Operating system deployment (8 fixes)
-Software distribution and content management (7 fixes)
-Microsoft Intune and mobile device management (5 fixes)
-Software update management (2 fixes)

Additional changes that are included in this update:
-Endpoint Protection - Revised February 2015 anti-malware platform update for Endpoint Protection clients
-Software distribution and content management - Distribution Manager can now process pull-distribution point packages more efficiently in large environments.
-Microsoft Intune and mobile device management - This update contains general performance improvements to the device enrollment process in Intune hybrid environments.
-Microsoft Intune and mobile device management - Update to implement oneClick quarantine of email messages in System Center 2012 Configuration Manager SP2

Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update. Great that CU2 is available now!

This update replaces Cumulative Update 1 for System Center 2012 Configuration Manager R2 SP1 and 2012 SP2

For more information or download the update have a look here:
Microsoft Support

Doing a Windows 10 upgrade with ConfigMgr 2012 R2 SP1

Recently I did a Windows 10 upgrade with ConfigMgr 2012 R2. I used the new Windows 10 upgrade task sequence in ConfigMgr Technical Preview 3 before, but this one was new for me. Looking at Microsoft Technet there is a task sequence and multiple scripts available to do the job. With these components you can start an in-place Windows 10 upgrade right away, without the need to wait several weeks (or months) before ConfigMgr vNext is released.

On Microsoft TechNet the following posts are found:
How to upgrade to Windows 10 using the task sequence in System Center 2012 R2 Configuration Manager
and
Revised content for the Windows 10 in-place upgrade via task sequence for Configuration Manager
Within these posts the upgrade path can be found with the files (task sequence and scripts) needed.

Just create a deployment on the task sequence, and choose Install. In this case I choose an available deployment, so users can start the deployment when needed.

Before Windows 10 installation a Presetup takes place. This runs a corresponding Windows PowerShell script (PreSetup.ps1) to perform a variety of necessary actions prior to running Windows Setup.

This is where setup is actually run from the media package to automatically upgrade Windows. Both Windows media and scripts will be downloaded in the _SMSTaskSequence folder.

Windows restarts into a low-level mode to perform the upgrade and there are two possible outcomes: Upgrade completes successfully or Upgrade encounters a problem and rolls back the system to the down-level operating system.

In my case the Upgrade completes successfully. It was done in around 50 minutes. Additional steps can be added to this group as needed, such as Install Applications or Run PowerShell Script. The Install Software Updates step is provided as an example. The Cleanup step just removes the local staging directory.

Just great to have this functionality in ConfigMgr 2012 R2 too!

Update ConfigMgr 2012 R2 SP1 with Windows 10 boot images

When installing ConfigMgr 2012 R2 SP1, Windows 8.1 ADK is needed as a prerequisite. You can however upgrade to Windows 10 ADK after installation. Let's have a look. Let's download Windows 10 ADK first on Download kits and tools for Windows 10. At the bottom of the page you will find the Download button. When using ConfigMgr 2016 (Technical Preview), Windows 10 ADK can be used at start already.

Before this can be installed, it's needed to uninstall Windows 8.1 ADK first. After that start adksetup.exe for Windows 10. During setup multiple components must be selected, three of them are the same as in Windows 8.1 ADK. Imaging and Configuration Designer (ICD) is a new one, which is needed to configure Windows 10 settings.

Just select this four items and choose to install them. After installation however, boot images are still on Windows 6.3 (which is Windows 8.1). This because it's needed to update boot images manually. You can choose to change existing boot images or create new ones.

Here are the paths to both boot images:
-x86: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim
-x64: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim

 

Just copy (and rename) them to the <ConfigMgr folder>\OSD\Boot\i386 and x64 folders. Within the Boot images properties change the Data source location for both files or create new Boot images to the location. Just make sure to select -Distribute Content- and -Deploy this boot image from the PXE-enabled distribution point- (properties) as well. After that both boot images will be on v10.0.10240.16384 which is fine.

Note: As mentioned on TechNet Blogs, don't forget to reboot after ADK installation. Otherwise boot images won't get updated on the DP.

Source: How to switch to Windows 10 ADK on ConfigMgr 2012 R2 SP1

Hope it helps!

Automatically updating the Configuration Manager client

Great news! With the release of ConfigMgr 2012 R2 SP1 and 2012 SP2 it's now possible to automatically update the ConfigMgr client. No need to use the client packages again (which are still created by default). The only thing needed is to have ConfigMgr 2012 R2 SP1 or 2012 SP2 in-place, and make sure the automatic client upgrade feature is enabled on the Site server. After that all ConfigMgr clients will be upgraded to the new version, which is v5.0.8239.1203

Note: Select "Upgrade client automatically when new client updates are available". This is set on 7 days by default and is done on servers too. Just select "Do not update servers" if you don't want too.

Note: The new installation page is only present when the automatic client upgrade feature is enabled. Otherwise above screen will be skipped during installation. You can enable it after the update and then re-run the installer at a later time.

For operating system deployment (OSD) scenarios, you can still use the PATCH= parameter if you need the update applied right away. Otherwise, the installation of the update will take place at some random interval within the value specified.

After that clients will be updated within 7 days from installation time. Just great and handy to have this functionality now :-)

Cumulative Update 1 for ConfigMgr 2012 R2 SP1 and 2012 SP2 released

Last month (August 4th) Cumulative Update (CU) 1 for ConfigMgr 2012 R2 SP1 and 2012 SP2 is released. This update contains 25 fixes for various issues including an update version of the SCEP client, and contains all of the changes from prior cumulative updates.

Here's a list of issues that are fixed, there are quite a lot of them:
-Configuration manager client (2 fixes)
-Software distribution and content management (3 fixes)
-Operating system deployment (3 fixes)
-Administrator Console (2 fixes)
-Site systems (7 fixes)
-Microsoft Intune / Mobile Device Management (2 fixes)
-Reporting (2 fixes)

Additional changes that are included in this update:
-Asset Intelligence - An update for the authentication certificate in ConfigMgr Asset Intelligence is available
-Endpoint Protection - Revised February 2015 antimalware platform update for SCEP clients
-Endpoint Protection - The Citrix Connector Synchronization Task is unsuccessful when you install or use the Citrix Connector for ConfigMgr
-Operating systems other than Windows - Debian 8 is added to the list of supported platforms for software distribution

Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update. Great that CU1 is available now!
 
For more information or download the update have a look here:
Microsoft Support

Doing a ConfigMgr 2012 R2 SP1 fresh installation

Recently I did a blogpost about doing a ConfigMgr 2012 R2 SP1 upgrade. This because it will result in different behavior, and running tasks in the background after the upgrade. This time I started a ConfigMgr 2012 R2 SP1 fresh installation, which is something different really. Installation is doing fine with no running tasks in the background after installation. Much better this way!

And I needed both installation media this time as well :-)

This because starting with this release, Microsoft has merged the 2012 and 2012 R2 codebase. This means form this point forward both 2012 and 2012 R2 use the exact same files. The ONLY difference is a setting that blocks 2012 users from certain features to R2 because they've not paid for it. This is where the two files come in:

SC2012_SP2_ConfigMgr_SCEP.exe is the actual install/upgrade binary that everyone needs to run.
SC2012_R2_SP1.exe is the file which serves one purpose only: an upgrade path for people from 2012 to 2012 R2, if they upgrade their license to unlock the locked-out features. That's why it's so small. Remember it will NOT upgrade your ConfigMgr infrastructure.

More about that here: System Center Configuration Manager Team Blog (in comments)

Installation progress in short:

Installation is done within 35 minutes, with no running tasks left. Use the file 'SC2012_SP2_Configmgr_SCEP.exe' for that.

After installation you have System Center 2012 Configuration Manager SP2 in-place, with no R2 features available.

After that start the file 'SC2012_R2_SP1_Configmgr.exe' to continue. This file unlocks R2 features missing in the other installation. You will need a R2 license for that officially.

Installation is done in a blink of an eye. This because it's used only to unlock R2 features in the ConfigMgr console.

When starting the console again, you have System Center 2012 R2 Configuration Manager SP1 now. Very nice indeed :-)

From now on this will be the way for fresh ConfigMgr installation. Stay tuned for more ConfigMgr news soon!

More blogposts about ConfigMgr 2012 R2 SP1:
ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)
New functionality in System Center 2012 R2 Configuration Manager SP1

Object Replication errors after a ConfigMgr 2012 R2 SP1 upgrade

Right after a ConfigMgr 2012 R2 SP1 upgrade, you may have Object Replication errors in the SMS_Object_Replication_Manager. After 7 upgrades this is the first one having this kind of errors.

The errors will looks like this:
Microsoft SQL Server reported SQL message 547, severity 16: [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentRuleDetail_CIID_FK". The conflict occurred in database "CM_***", table "dbo.CI_CurrentRuleDetail", column 'Setting_
Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

When looking in objreplmgr.log you will see the following errors:
*** delete vCI_ConfigurationItems where CI_ID=16835455
*** [23000][547][Microsoft][SQL Server Native Client 11.0][SQL Server]The DELETE statement conflicted with the REFERENCE constraint "CI_CurrentRuleDetail_CIID_FK". The conflict occurred in database "CM_***", table "dbo.CI_CurrentRuleDetail", column 'Setting_CI_ID'.
Failed to delete Deployment Type ScopeId_5D63A272-7854-4697-8F30-AF7069C4E611/DeploymentType_00b65bce-7f88-467a-8e5a-10c1755d3b8a/4
These errors will come back every 30 minutes!

The solution for this can be found on the ConfigMgr database, starting the query:
delete from dbo.CI_CurrentRuleDetail where Setting_CI_ID='16835455'

When restarting SMS_Object_Replication Manager within Configuration Manager Service Manager, you see the lines:
Successfully deleted Deployment Type ScopeId_5D63A272-7854-4697-8F30-AF7069C4E611/DeploymentType_00b65bce-7f88-467a-8e5a-10c1755d3b8a/4
*** delete vCI_ConfigurationItems where CI_ID=16835455
Very good, but another error came back immediately with another ID!

In my situation I did a query 6 (!) times on the ConfigMgr database:
delete from dbo.CI_CurrentRuleDetail where Setting_CI_ID='16835455'
delete from dbo.CI_CurrentRuleDetail where Setting_CI_ID='16835731'
delete from dbo.CI_CurrentRuleDetail where Setting_CI_ID='16846410'
delete from dbo.CI_CurrentRuleDetail where Setting_CI_ID='16847715'
delete from dbo.CI_CurrentRuleDetail where Setting_CI_ID='16857770'
delete from dbo.CI_CurrentRuleDetail where Setting_CI_ID='16857778'

After that everything went fine again. Is it supported? No, i guess not! Is it working? Yes, the errors are gone now! More information can be found on Microsoft TechNet: After R2 SP1 installation: Object Replication manager has errors. Hope it helps!

More blogposts about ConfigMgr 2012 R2 SP1:
ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)
New functionality in System Center 2012 R2 Configuration Manager SP1
Doing a ConfigMgr 2012 R2 SP1 upgrade (Notes from the field)
Check the database before doing a ConfigMgr 2012 R2 SP1 upgrade

Check the database before doing a ConfigMgr 2012 R2 SP1 upgrade

When doing a ConfigMgr upgrade (like ConfigMgr 2012 R2 SP1), it's good to check the database first. When upgrading a production environment, you want to make sure that everything went fine, and no error is given on the database. This can be done with the following command(s), which are recommended before upgrade.

When you want to start a Database Consistency Check against the ConfigMgr database, run the command: DBCC CHECKDB
This performs the following operations:
-Runs DBCC CHECKALLOC on the database.
-Runs DBCC CHECKTABLE on every table and view in the database.
-Runs DBCC CHECKCATALOG on the database.
-Validates the contents of every indexed view in the database.
-Validates the Service Broker data in the database.

Source: https://technet.microsoft.com/en-us/library/bb693745.aspx 

After that build a new server with the same SQL installation (version and configuration like collation) and import a copy of the ConfigMgr database on that server. This because you cannot test a database upgrade on a active ConfigMgr Site server! To test the database upgrade before doing it in production environment, just run the command: SMSSETUP\BIN\X64\Setup.exe /TESTDBUPGRADE <database> (from new ConfigMgr installation media)

Start Begin TestDBUpgrade

Yes, I'm sure about it :-)

TestDBUpgrade is done

After some time (22 minutes in my case) the following message is displayed in ConfigMgrSetup.log: Configuration Manager Setup has successfully upgraded the database. With that it's time to start the upgrade in production environment as well. Don't forget to have a good backup (as mentioned earlier) all times.

Happy upgrading! :-)

More blogposts about ConfigMgr 2012 R2 SP1:
ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)
New functionality in System Center 2012 R2 Configuration Manager SP1
Doing a ConfigMgr 2012 R2 SP1 upgrade (Notes from the field)

Doing a ConfigMgr 2012 R2 SP1 upgrade (Notes from the field)

Last week I did a lot of ConfigMgr 2012 R2 SP1 upgrades already. I did 5 upgrades on different environments, resulting in different behavior. Let's have a look at that. Before you begin just make sure you have a good backup! Most of time I start with a ConfigMgr backup and snapshot of ConfigMgr and SQL VM's. Better safe then sorry :-)

Then start the SP2 media (still confusing) to implement SP1 in your environment. It will be finished in around 30-45 minutes. The crazy part is starting after that. ConfigMgr isn't done with the upgrade, but running tasks in the background. Strange enough it's hard to see what's the status of that, and sometime it's stuck too and a reboot is needed. Let's have a look again.

When the upgrade wizard is finished and you start the ConfigMgr console, have a look at Site & System status. The MP will be down for almost one hour. When looking at Software Library the ConfigMgr client package and boot images are not updated yet. Because of that OS deployment isn't possible too. Sometimes it will be started automatically within one hour, sometimes a reboot is needed to start processing again. A nasty situation for sure.
 
Installation progress in short: 

Installation done in the wizard

 

Installation done in the logfile 

 

Installation is done, but a lot of components still needs to be updated:

-Monitoring components installation
-Monitoring server roles installation
-Setting up management point
-Installing services
-Installing Component Monitor
-Installing SMS Executive
-Installing Database Notification Monitor
-Installing Site Control Manager
-Installing Hierarchy Manager
-Installing Inbox Manager
-Installing policy provider
-Installing management point control manager

 

Management point in critical state

 

SMS Replication Configuration Monitor stops

 

SMS Site Component Manager degraded

 

Site Component Manager stopping

 

Site Component Manager shut down

  

The Management point is in critical state, because it must be installed again. No communication possible for almost one hour. The SMS Site Component Manager is degraded, because most of Site components needs to be installed again. When installation is stuck, it may help to reboot the Primary server. (not recommended, just wait first)

 

 

When looking at Component Status, they will be gone (66 items) because communication is down. Big oops moment :-)

SMS MP Control Manager back online

 

Site Components back online

 

As I sayed earlier, it can take on hour before the Management point is healthy again and Site Components are back in business. It may help to reboot the Primary server once, when there's no progress seen (recommended only when nothing changed after one hour). After the reboot you will see that functionality is restored soon! When looking at Software Library the ConfigMgr client package and boot images will be updated now. Still it's a nasty upgrade, because you think it's done in 30-45 minutes, and not one hour after that. Strange enough it's hard to see what's the status of that, and sometimes it's stuck too and a reboot is needed.

Why not mention in the wizard, installation is not finished and will take another hour? Or count another hour on the wizard and finish it in 60-90 minutes, instead of running tasks in the background? I guess this can be better with another release in future. Hope it helps!

More blogposts about ConfigMgr 2012 R2 SP1:
ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)
New functionality in System Center 2012 R2 Configuration Manager SP1

Update: More status pictures will be added soon!

New functionality in System Center 2012 R2 Configuration Manager SP1

Last week I did a few blogposts about the System Center 2012 R2 Configuration Manager SP1 Release and Upgrade. After the upgrade both Consoles and Clients must be upgraded as well. ConfigMgr clients can be upgraded with the Automatic Client Upgrade (like always when installing big updates). Let's have a look at new functionality added to the ConfigMgr console and boot images.

After installation the version has changed to 5.00.8239.1000 in About Configuration Manager dialog box and Site server properties. The current ConfigMgr 2012 R2 key will work with R2 SP1 also.

The OSD screen is changed and looks a little better if you ask me..

With all checkmarks enabled (which is default), only drivers that match the architecture, which are in the storage or network class, and are digitally signed are available. Much better, because I've seen complete driver packages in boot images before!

Deployment Verification is a cool feature, that makes sure no deployment on default collections (except All Unknown Computers) and collections with more then 100 systems (which is a default value) can be done. No more Required deployments on the All Systems collection from now on :-)

During deployment no default collections (except All Unknown Computers) and collections with more then 100 systems (which is a default value) are available. A message is displayed, that deployment has potential to be a high risk one.

When a required deployment is done, and the checkmark "Hide collections with a member count greater than site's minimum size configuration" is unchecked, a message is displayed. A checkmark must be set on "I want to create this high risk deployment (This wil generate an audit status message)" to continue.

With Cumulative Update 1 to 5 included, and a bunch of improvements, it's a must-have to install SP1 in your organization. I installed it twice already without any problems. Let's wait for ConfigMgr 2016 later this year (Q4 CY2015) now!

Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)

Today I started my first (and second) ConfigMgr 2012 R2 upgrade. When looking on Microsoft Evaluation Center, there is the choice between ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 media. When looking at ConfigMgr 2012 R2 SP1 there's the choice between a SP2 and SP1 file as well. Strange thing is SP2 is 762MB in size and SP1 is only 1,10MB in size. Let's have a look at some more information about this (Preinstall Information).
 

Upgrading your installation: If you have a System Center 2012 R2 Configuration Manager installation, you can use the System Center 2012 Configuration Manager SP2 media to install the latest patches and automatically upgrade to System Center 2012 R2 Configuration Manager SP1.
New installation: Install System Center 2012 Configuration Manager SP2 first, and then install System Center 2012 R2 Configuration Manager SP1 at the top-tier site of your hierarchy. Both of these installation files are included as part of this evaluation.
 

Error message when starting SP1 installation before SP2

When SP2 is installed, you can install SP1 successfully
(but it's needed only on new installations)

So yes, you must actually run ConfigMgr 2012 SP2 when you have ConfigMgr 2012 R2 SP1 installed. Very confusing if you ask me? Using ConfigMgr 2012 R2 SP1 is needed only for new installations at the top-tier site of your hierarchy. Crazy it's less then 5MB in size!? Otherwise it's not needed to install this file (but it surely does install fine after ConfigMgr 2012 SP2 too). Just checked that one too.

The installation/upgrade went fine after all, and was done within 60 minutes. The second upgrade was done within 100 minutes, but was a larger site to upgrade. There will be new functionality added to the ConfigMgr console and boot images as well. This will be mentioned in another blogpost published soon. Because R2 functionality is built-in, no need to use R2 media anymore!

After installation the version has changed to 5.00.8239.1000 in About Configuration Manager dialog box and Site server properties. The current ConfigMgr 2012 R2 key will work with R2 SP1 also.
 
More information about the servicepack can be found here: ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
 
Microsoft websites to visit:
What's New in System Center 2012 R2 Configuration Manager SP1
Announcing the availability of System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2
Planning to Upgrade System Center 2012 Configuration Manager

ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released

As mentioned on Microsoft Ignite last week, ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 are now released and can be downloaded. The service packs deliver full compatibility with existing features for Windows 10 deployment, upgrade, and management. Also included in the service packs are new hybrid features for customers using ConfigMgr integrated with Microsoft Intune to manage devices. Some of the hybrid features that you can expect to see are conditional access policy, mobile application management, and support for Apple Device Enrollment Program (DEP). You can view the full list of hybrid features included in these service packs here: What's New in System Center 2012 R2 Configuration Manager SP1
 

 
Here's a list of improvements included, there are quite a lot of them:
-Sites and Hierarchies (2 improvements)
-Application Management (2 improvements)
-Content Management (6 improvements)
-Operating System Deployment (8 improvements)
-Reporting (3 improvements)
-ConfigMgr and Microsoft Intune (17 improvements)
 
Additional improvements that are included in this update:
-ConfigMgr Company Portal App (Windows 10 support)

To apply this update, you must have ConfigMgr 2012 (SP1/R2) installed. SP1/SP2 provides support for Windows 10 and improves data transfer reliability for slow and latent networks with new checkpoint restart functionality for distribution points and pull DPs. Increases secondary site from 5,000 clients to 10,000 clients and standalone primary to 150,000 clients. The version that is displayed in the About Configuration Manager dialog box is now 5.00.8239.1000.
 
This update replaces Cumulative Update 1 to 5 for System Center 2012 Configuration Manager R2

For more information have a look here: System Center Configuration Manager Team Blog
 
MSDN subscribers can expect these service pack downloads to be available next week. Microsoft is also planning to make these service packs available on the Volume Licensing Service Center (VLSC) on May 27th. You may also use your existing product key to transition from the evaluation version to the full product version.
 
More blogpost on this topic:
Microsoft Ignite day 1 (Keynote) recap
Microsoft Ignite day 2 (Session) recap
Cumulative Update 5 for ConfigMgr 2012 R2 released