This article describes the issues that are fixed and functionality that is updated in Cumulative Update 3 (CU3) for Microsoft System Center 2012 R2 Configuration Manager.
Issues that are fixed
Software distribution and application management
- Content distribution from a Central Administration Site (CAS) to remote distribution points can take longer than expected. This can occur when multiple applications are updated across all distribution points.
- An application that is deployed to a collection is not removed from the software center if the computer is removed from that collection.
- The Export Application Wizard finished with errors when the source contains nested sub-folders, and the content is updated. Errors that resemble the following are displayed in the Export Application Wizard: Error: The target file "C:\Export\A_files\Content_XXXXXXXXXXXX\F2" is a directory, not a file.
- Applications in a dependency chain may not install when an immediate restart is initiated by the Configuration Manager client. This scenario affects applications and application dependency chains that are deployed by using Application Management in which the application has the following option enabled:Only when no user is logged on / CM client will force a mandatory device restart
Wake on LAN
- Wake on LAN requests from a site server to a client may time out in large environments of 30,000 or more clients.
- The data collecting process may time out when Configuration Manager is migrated from Configuration Manager 2007 to System Center 2012 R2 Configuration Manager. This issue can occur in sites in which multiple source sites are used, and many (100,000 or more) records exist only in the database at the destination site.
- Clients may not configure settings for the company portal for sites in which multiple Application Catalogs are installed. Entries that resemble the following are logged in the UpdateTrustedSites.log file:
- The Administrator Console can quit unexpectedly when modifying the following task sequences:
- Join a domain or workgroup
- Apply Network Settings
- Policy assignment is not updated a Windows Embedded Handheld device is moved from one collection to another. For example, when a device is moved from a collection for installing an application to an uninstall collection, a rules conflict status occurs. Entries that resemble the following are recorded in the SMS_DM.log file:
- A race condition may cause renewing the Microsoft Intune Connector certificate to fail. Entries that resemble the following are recorded in the DMPDownload.log:
- The Simple Certificate Enrollment Protocol policy may not be delivered to a device that is enrolled in Microsoft Intune and then later renamed by the user.
- State messages are marked incorrectly as corrupted from Simple Certificate Enrollment Protocol Configuration Items that are targeted to devices and that contain a user entry of SYSTEM.
- Simple Certificate Enrollment Protocol certificate requests can fail for workgroup clients that Configuration Manager manages. Entries that resemble the following are recorded in the CRP.log file:
Operating system deployment
- When an unknown x64 UEFI computer is started by using PXE in a Configuration Manager 2012 R2 environment, the x86 Unknown Computer object is used incorrectly instead of the x64 Unknown Computer. This can potentially cause the computer to receive incorrect task sequences.
- The SMS Agent Host service may quit unexpectedly during the processing of task sequences.
Site servers and site systems
- The SMS_Executive service may quit unexpectedly when removing a package from a large number (100+) of distribution points. Entries that resemble the following are logged in the distmgr.log file before process termination:
Note These log entries do not always indicate a problem state that will lead to a process termination.
- Changing the properties of a distribution point on a Windows Server 2012 R2 server can disable date and time logging in Internet Information Services (IIS).
- Changing the properties of a distribution that was migrated from Configuration Manager 2007 to System Center 2012 R2 Configuration Manager can result in the upgrade process starting again.
- Windows PowerShell issues that are corrected in Cumulative Update 3 are described in the following article:2999304 Description of Windows PowerShell changes in Cumulative Update 3 for System Center 2012 R2 Configuration Manager
Additional changes that are included in this update
Management point communications
- This cumulative update introduces a new registry entry for clients. This entry will restrict which management point (MP) a client can communicate with. This can be useful in environments that have multiple MPs in different forests, and the clients can only communicate with a subset of them. Setting the registry value to only those MPs that can be reached by the client can improve overall efficiency. The new registry value is AllowedMPs, a REG_MULTI_SZ (multi-string) type that is under the following subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\CCM
Each entry is the Fully Qualified Domain Name of the management point(s) with which the client is able to communicate. This value does not affect the selection of any other site systems such as distribution points, software update points, and so on. The value only affects the primary site MP selection.
Note After this value is defined, there is no fallback or other method for clients to communicate with other MPs. This new entry is only intended for permanently located workstation and server clients and is not portable to devices such as mobile PCs or tablets.
Operating systems other than Windows
- The following operating systems are added to the list of supported platforms for software distribution:
- Debian 7 (x86)
- Debian 7 (x64)
- Red Hat Enterprise Linux 7 (x64)
- CentOS 7 (x64)
- Oracle 7 (x64)
- Child sites may perform partial WSUS synchronization when the primary is under heavy load. This partial synchronization occurs when the WSUS Synchronization Manager component on a primary site begins synchronization before WSUS has completed processing all updates metadata. To prevent this scenario, the following registry subkey can be configured to use a new value in seconds:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER\SyncGracePeriod
The default value is 120 seconds, and values between 5 seconds and 10 minutes (5 and 600) are accepted. This setting should not have to be changed in most environments.
How to obtain Cumulative Update 3 for System Center 2012 R2 Configuration ManagerA supported update is available from Microsoft Support. However, this update is intended to correct only the problems that are described in this article. Apply this update only to systems that are experiencing the problems described in this article. This update might receive additional testing. Therefore, if you are not severely affected by these problems, we recommend that you wait for the next service pack that contains this update.
If the update is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the update.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific update. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which this update is available. If you do not see your language, it is because an update is not available for that language.
Restart informationYou do not have to restart the computer after you apply this update.
Note We recommend that you close the Configuration Manager Administrator Console and any associated applications such as the Remote Control Viewer or Status Message viewer before you install this update.
You may be prompted to restart the computer to which the Administrator Console update is being applied if the Remote Control Viewer (CmRCViewer.exe) is being used during the update process.
This can be avoided by closing the Remote Control Viewer before you install the update, or by adding the REBOOT=ReallySuppress parameter to the update installation properties.
Update replacement informationThis update replaces Cumulative Update 2 for System Center 2012 R2 Configuration Manager .
How to determine the installation status of this cumulative updateThis cumulative update changes the following Configuration Manager version numbers and installation properties.
Site systemsThe CULevel value is located under the following registry subkey:
Note The CULevel value is set to 3 for Cumulative Update 3.
Administrator ConsoleThe version that is displayed in the About System Center Configuration Manager dialog box is 5.0.7958.1401.
ClientThe version that is displayed on the General tab of the Configuration Manager Control Panel item or the Client Version field of device properties in the Administrator Console is 5.00.7958.1401.
For more information about how to install this cumulative update, go to the following Microsoft TechNet websites:
Update System Center 2012 Configuration ManagerLearn about the terminology that Microsoft uses to describe software updates.
New cumulative update servicing model for System Center 2012 Configuration Manager
New cumulative update servicing model for System Center 2012 Configuration Manager
Article ID: 2994331 - Last Review: Apr 26, 2017 - Revision: 4
Microsoft System Center 2012 R2 Configuration Manager