Wie ich bereits vor ein paar Stunden über Twitter geschrieben habe, hat Microsoft in der Nacht das Cumulative Update 3 für den System Center 2012 R2 Configuration Manager veröffentlicht.
Das Cumulative Update 3 (CU3) für ConfigMgr 2012 R2 kann über folgenden Link heruntergeladen werden:
Neben zahlreichen Bugfixes hat Microsoft auch ein paar neue Funktionen spendiert.
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:
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:
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.