We are happy to announce that Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2 is now available for download. This update includes an extensive list of fixes for the following components:
- Configuration Manager client
- Software distribution and content management
- Operating system deployment
- Administrator Console
- Site systems
- Microsoft Intune / Mobile Device Management
- Reporting
A SCCM 2012 R2 environment without the current Cumulative Update Getting the correct SCCM Cumulative Update and installation checklist ^ CU3 for SCCM 2012 R2 can be downloaded from here. How To Deploy Software Updates Using SCCM 2012 R2. There are 2 ways to deploy software updates using SCCM 2012 R2, Manual and Automatic. In Manual software. The wizard will now download the updates and deploy them to the collection as per the schedule defined.
It also includes updates for Asset Intelligence, Endpoint Protection (SCEP) and Debian 8.
Of special note is that with the release of CU1 for ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2, Windows 10 drivers can now be imported into the DriverCatalog.log file with no errors. Prior to the release of Windows 10, OSD would not import drivers marked for Win10. This was due to the way version number recognition was performed. This has now been fixed within CU1.
For the latest information regarding Cumulative Update 1 as well as all the details regarding the fixes and updates included, please see the following:
3074857Description of Cumulative Update 1 for System Center 2012 R2 Configuration Manager Service Pack 1 and System Center 2012 Configuration Manager Service Pack 2
For more information about Cumulative Updates, please see Update System Center 2012 Configuration Manager, New cumulative update servicing model for System Center 2012 Configuration ManagerandConfiguration Manager Servicing Update.
J.C. Hornbeck| Solution Asset PM | Microsoft GBS Management and Security Division
Get the latest System Center news onFacebookandTwitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/
Sccm 2012 R2 Cumulative Update Download
Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
Sccm 2012 R2 Patch Download
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Updating of computer equipment is an aspect often overlooked by companies because there are too many constraints. It is necessary to manage downtime, while patches provide sometime malfunctions. However, updates computer equipment is a necessity for security. In this article series I will introduce you how to update your computers limiting constraints with SCCM Software update.
WSUS
WSUS (Windows Server Update Service) is a role that provides a central management point for Microsoft Update. Thanks to WSUS, all servers no longer need to connect to Microsoft Update to download patches and hotfix. WSUS is in charge of downloading updates and distribute them on different machines.
Because there are a lot of updates for several products, downloading updates is performed according to some rules such as classification, languages or products.
However WSUS can’t be used alone in a big IT infrastructure requiring automation. This product doesn’t have a granular scheduler to deploy update. This is why SCCM is used with WSUS.
SCCM and WSUS
SCCM has a system role called Software Update Point (SUP). This role has to be installed on WSUS server. When it is set, SCCM can manage updates catalog and binaries to make updates packages. Such as WSUS, packages can be created regarding to classification, products, languages of the update (this is not an exhaustive list). Once these updates packages is created, it can be deployed with SCCM and use its powerful scheduler:
- WSUS downloads updates catalog and update binaries when SCCM requests them.
- Primary site configures himself WSUS role. When it is done, Primary site synchronizes updates catalog and requests binaries when the update package is creating.
- Once an update package is created, it is deployed on Deployment Point
- Managed servers download this package and install it regarding to maintenance period and scheduling configured on Primary Site.
- Before installing updates, managed servers download update catalog from WSUS to validate them.
Below the network flow according to above schema:
Regarding the storage part, when WSUS is added to SCCM, it no longer stores the binary files on its own store. Binaries are on SCCM content store. However WSUS still needs a database to store update catalog.
On the next part, I will present the configuration of an SUP point. WSUS and SCCM are installed on the same machine. But it is the same process when WSUS is installed on another server. After integration of WSUS in SCCM hierarchy, I will deploy updates by two different methods:
- Create packages and deploy it manually
- Automatic Deployment rules
Once SUP is configured correctly, the catalog of updates appears in SCCM console. A filter can be created regarding some criteria (classification, updates id, products etc.). Then updates can be added to a package and can be deployed. The deployment scheduling is configured manually. Then managed servers install updates in their maintenance period. This method is very useful on complex environment such as Exchange or Hyper-V cluster where patching should be orchestrated (move Virtual Machines or databases before patching etc.). The package can be used with System Center Orchestrator to be deployed and orchestrate patching.
Moreover the Cluster-Aware Updating is not compatible with software update from SCCM. An Orchestrator runbook should be created for this task. This is why it is possible to create a package manually and then deploy this last.
Automatic Deployment rules feature provides automatic creation and deployment of updates packages. The package creation can be scheduled (such as every second Tuesday of each month) and the choice of updates is made in function of some criteria (classification, updates id, products etc.). Once the package is created, it is automatically deployed in function of scheduling configuration. Then managed servers install updates in their maintenance period. This method should be used on mockup or simple environment.