The official blog of the Microsoft System Center Configuration Manager Product Group
Cumulative Update 3 (CU3) for System Center 2012 Configuration Manager SP1 is now available as a hotfix download from KB 2882125. This update contains fixes for various issues, and an updated version of the Endpoint Protection client, and adds support for Windows 8.1-based clients.
CU3 introduces a new version of a SQL CLR stored procedure. As a result of this change, some additional steps are required when running the update.sql script manually. These steps are not required if you choose to allow the cumulative update installer to perform the database update. In order to manually run the update.sql script after CU3 has been installed, perform the following steps:
If the site database is installed on the site server, use the steps below.
If the site database is installed on an instance of SQL remote from the site server, use these steps instead.
As with other cumulative updates, this release is optional and does not affect the product support lifecycle.
For more information about cumulative updates, refer to Update System Center 2012 Configuration Manager and New cumulative update servicing model for System Center 2012 Configuration Manager.
This posting is provided "AS IS" with no warranties and confers no rights.
Why shouldn't we just wait for R2?
Any advice on how do we deploy the updated SCEP Client, 18.104.22.168 that is included? I've noticed that when I apply the CU3 update to my CU2 users, that SCEP doesn't get updated, however when clients get provisioned through OSD and get the initial client installation through PUSH then they get the 4.3.215 client.
@Steve - the updated SCEP client was originally released in KB2865173 and that KB seems to have your answer. support.microsoft.com/.../en-us
CU3 has been applied to our primary site server, and two secondary site servers using the extracted KB Installer (CM12-SP1CU3-KB2882125-X64-ENU). One of the two secondary servers is where the problem with DB replication lies.
1. Primary - to - Secondary_Site_1 is completely fine...
2. Primary - to Secondary_Site_2 is the one showing Link Failed.
The thought here is the analyst who installed the CU chose the option to update the DB later. Does this article apply when dealing with Secondary site DB updates? If so, how do we perform the DB update steps from the secondary site?
Any help would be greatly appreciated,
Can anyone advise if the database update makes changes to the schema? Before we go live I need to confirm that external processes which directly query the SCCM database will not be affected. Thanks.