In this post we will look at the steps on how to deploy software updates using SCCM 2012 R2. Deploying the software updates for the computer. Patch for a Windows 7. SCCM 2012 R2 SP1 installation of New Built Windows 10 1607 We are now with the new Built of windows 10 Enterprise 1607 version. I like to do the installation through SCCM 2012 R2 SP1. Is there any other way available to push these update through SCCM. How to download Windows 10 Anniversary Update 1607 for your home machines? Jul 29, 2015  Patch Management - Planned for Client OS using SCCM 2012 R2 SP1. We are Okay with Deploying the Patches on Every Month after the Patch Release From Microsoft. If any New Machines, Comes to Domain. Windows 10 updates with Sccm 2012 r2/WSUS. Submitted 2 years ago by n4k3dm0s3s. So everything is good for all products we use here Windows 7 and below. We are starting to implement Windows 10. Did you remember to tell your WSUS to download Windows. Hello, I have created Automatic Deployment Rule, which should download ALL Windows 7 updates. In Deployment Schedule (Software available time) is set to 14 days, and Installation deadline is 1. SCCM 2012 r2 Delay installing windows updates for N days. An update is available for Microsoft System Center Configuration Manager 2007 Service Pack 2. The update adds Windows 8.1 and Windows Server 2012 R2 to the list of supported platforms for the following features.
Microsoft has released another Cumulative Update for SCCM 2012. Learn how to update SCCM 2012 to the latest version by upgrading site components, deploying the new client, and managing consoles.

Joseph Moody

Joseph Moody is a network admin for a public school system and helps manage 5,500 PCs. He is a Microsoft Most Valuable Professional (MVP) in Cloud and Datacenter Management and blogs at DeployHappiness.com.

Latest posts by Joseph Moody (see all)

  • WuInstall: A command-line interface (CLI) for Windows Update - Thu, Apr 4 2019
  • PolicyPak Group Policy Edition: Deploy any settings and apps - Thu, Mar 21 2019
  • Total Network Inventory 4: Discover your network and stay on top of changes - Wed, Feb 6 2019
If you aren’t installing Cumulative Updates for SCCM 2012 SP1/R2, you are setting yourself up for a lot of extra work! Issues that you have with SCCM are likely fixed with one of these updates. This is especially true if you plan to start using a role in SCCM (for example, operating system deployments). Instead of spending hours troubleshooting a problem, keep your SCCM infrastructure updated and avoid the problem altogether!
Cumulative Updates should not be thought of as a standard single issue hotfix. Rather, they are a collection of fixes and feature enhancements. Today, we are going to install Cumulative Update (CU) 3 for SCCM 2012 R2. These steps are the same for 2012 SP1 and are identical for nearly all CU installations.

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. If you are unsure of the latest available CU for your product, check out the Configuration Manager Team Blog. All CUs are announced there.
Before installing the update, you need to check your site status, back up your database, and ensure all pending reboots are cleared. Launch the Configuration Manager console and navigate to Monitoring/System Status/Site Status. All roles should be normal. If you have any roles in a warning or error state, resolve those issues now.

Site Status showing a healthy Configuration Manager environment

Ensure that you have a recent backup of your SQL database, as this CU will make changes to the database. If you do not currently back up your SQL database, read more about backups in Configuration Manager 2012 here.Finally, check your servers for pending reboots, or reboot your servers manually. I use Server Manager to achieve this. Servers with a pending reboot will report their manageability as Online – Pending Reboot.

Using Server Manager to check for pending reboots

Installing a SCCM 2012 Cumulative Update ^

The SCCM Cumulative Update process has three major steps. First, you apply the update to the site server. Next, you install the updated console on administrative machines. Finally, you deploy the updated Configuration Manager client packages.
Take advantage of our limited time offer and gain access to unlimited downloads for $3.99/mo! Our members download database is updated on a daily basis. Killing time uncensor patch download. We currently have 440,948 full downloads including categories such as: software, movies, games, tv, adult movies, music, ebooks, apps and much more.
For safety, close the Configuration Manager console on any administrative machine. On your site server, launch the CU install and proceed through the wizard.

Server that is ready to install CU3 for SCCM 2012 R2

In most installs, you will accept all of the default options in a CU installation. To deploy the updated client/console, you will certainly want to update the site server’s console version. You will also want to update the site database during the CU installation.
The CU update will create new client and console packages for deployment. By default, these installs are stored in SITE-ServerSMS_SITECODEhotfix.

Creating packages for each update component in SCCM 2012

In my environment, the install took about 15 minutes. If you have any issues, you can view the installation log in C:WindowsTemp.

Site server that has been successfully updated to the current CU

You will need to repeat this process for all site servers in your Configuration Manager hierarchy. Restart your site server(s) before proceeding to the next part of this guide. Once your server is back up, you can verify the installation by navigating to HKEY_LOCAL_MACHINESOFTWAREMicrosoftSMSSetup and checking the value of CULevel. For CU3, the value should be 3.

Updated server with a new version number

Updating the Configuration Manager console and clients ^

On your site server, launch the Configuration Manager console. Navigate to Software Library/Packages/Configuration Manager Updates. You should see four new packages: one for site servers, one for consoles, and two for clients.

R2 CU3 update packages

Masters of the world patch download. Start by deploying the console update to any machine with the Configuration Manager console. You can use this query to create a collection that targets just those machines:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId=SMS_R_System.ResourceId whereSMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like'%System Center 2012 R2 Configuration Manager Console%'
Be sure to edit the DisplayName line to reflect the console name used in your environment.

Successful deployment of the SCCM 2012 R2 CU3 console

Finally, deploy the client packages to their correct architecture. If needed, you can use this query to create a collection for x64 clients or to modify it for x86 clients:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID=SMS_R_System.ResourceId whereSMS_G_System_COMPUTER_SYSTEM.SystemType='x64-basedPC
With your client updates being deployed, you have successfully updated your Configuration Manager infrastructure to the latest Cumulative Update! If you ran into any issues or have any other update tips, be sure to post a comment below.
Benoit Lecours

Ms17-010 Patch Download Windows 7

SCCM
Microsoft has recently announced the release of SCCM 2012 SP2 and SCCM 2012 R2 SP1. Before performing an SCCM 2012 R2 SP1 upgrade, we recommend that you read carefully all the available resources and carefully plan the upgrade process throughout your SCCM 2012 R2 hierarchy. The good news is that our SCCM 2012 R2 SP1 Upgrade Guide will list everything you need to know before applying this major upgrade to your existing SCCM 2012 installation. We’ve got you covered !

What’s new

The main reason you’ll want to upgrade to SCCM 2012 R2 SP1 is probably for Windows 10 support. No plan for Windows 10 deployment in your organisation? There’s interesting new features and a lots of bug fixes (thousands, which are not fully documented) in this release that are worth it. Do I still need to perform the SCCM 2012 R2 SP1 upgrade? See the full list of features on this Technet Article to figure it out.

Naming Confusion

Following the announcement, the community was confused on how to apply this Service Pack because Microsoft decide to release it under one binary even if there’s 3 possible “version” of SCCM 2012. (SCCM 2012 RTM, SCCM 2012 SP1, SCCM 2012 R2)
Fellow MVP Jason Sandys explain all the upgrade options in an excellent post. The key is really to understand the upgrade process by identifying your actual version and the desired final version.

Prerequisites

Download Sccm 2012 R2 Sp1

Our post focus on what needs to be done to upgrade a stand-alone SCCM 2012 R2 Primary Site to SCCM R2 SP1. This post is
If you have a hierarchy with a Central Administration Site and multiple Primary Site, start with the top of the hierarchy (CAS) and go down, upgrading all Primary Sites and Secondary Sites.
If you’re already running SCCM 2012 R2, the upgrade process won’t do a site reset :
From Technet: When you run this upgrade, it enables additional capabilities throughout your hierarchy. Because this upgrade enables additional functionality and does not upgrade features and components, there are no considerations or changes to settings or site system roles as there is when you install a new service pack.

Database Replication

If you have a database replica for management point, disable Database replication. If you don’t use this function, skip this step and go to the Backup and Testupgrade section
  • Open the SCCM Console, browse to Administration / Site Configuration /Servers and Site System Roles
  • Select the Site System that hosts the management point that uses the database replica
  • Right click Management point and select Properties
    • On the Management Point Database tab, select Use the site database and click Ok
    • Connect to the SQL server hosting the replica databases
    • Open SQL Management Studio
    • Go to Replication / Local subscription
    • Right click the replica and select Delete. Select Yes to the warning prompt
    • Right click the publisher database and select Delete. Select Close existing connections and click OK
    • Connect to the SQL server hosting the site database
    • Open SQL Management Studio
    • Go to Replication and select Disable Publishing and Distribution
    • On the next screen, click Next
    • Select Yes, disable publishing on this server and click Next, Next, Next
    • Click Finish

    Backup and TestUpgrade

    • Before upgrading, perform a backup of your SCCM database.
    • It is recommended to test your CM database before the upgrade. Detailed procedure is available on Technet, here’s the resumed version :
      • Backup your site databse
      • Restore it on a SQL server running the
      • On the SQL server, run the SCCM setup command line using the Testdbupgrade switch
      • Open the log file on C:ConfigMgrSetup.log
      • If the process is successful, you can delete the database copy
      • If you have errors, resolve them on your SCCM server, do a new backup and restart this procedure
    After you successfully upgrade a copy of the site database, proceed with the “real” upgrade.

    Running Console

    Close all running console on the server. Check also if remotely logged users are running the console in their sessions. The setup won’t check that and you’ll endup having an error in the installation log at the end of the process.
    ERROR: Configuration Manager console uninstallation failed. Check log file ConfigMgrAdminUISetup.log.

    Installation

    The installation process is not like a CU installation. The user experience is like a new SCCM installation.
    • Download the necessary files. You can download the file from the Technet Evaluation Center. The non-eval files will be available on the Microsoft Volume Licensing Site on May 27th. You can install the evalutation version on a non-eval site without problem, it won’t “convert” your site to an evaluation version.
    • You’ll notice that there’s 2 available SP2 executables.
      • Refer to the table in Jason Sandys post to understand which one to run. (Depending of your actual site version and the desired final version)
    • In our case, the site is already R2 so we extract the SC2012_SP2_Configmgr_SCEP.exe to a folder and execute Splash.hta
    • On the main menu, select Install
    • On the Before You Begin screen, click Next
    • On the Getting Started screen, select Upgrade this Configuration Manager site
    • On the Microsoft Software License Terms, check I accept these license terms and click Next
    • On the Prerequisite Licenses, check all 3 boxes and click Next
    • On the Prerequisite Downloads screen, specify a location to download the prerequisite files. This folder can be deleted after the upgrade process
    • The prerequisite files are downloading
    • On the Server Language Selection screen, select the language you want to display in the SCCM Console and Reports
    • On the Settings Summary screen, you will see that you are performing an Upgrade
    • The Prerequisite Check is running
    • You should have no errors since your site is already installed and running
    • Wait for Prerequisite checking has completed and click on Begin Install
    Download
    • The installation is in progress. The installation will run for about 30 to 45 minutes depending of your server specifications
    • You can follow the progress by clicking the View Log button or open the ConfigMgrSetup.log file on the C: drive
    • Wait for Core setup has completed and close the wizard

    Verification

    Once the setup has completed, there’s a couple of check that you can make to be sure the upgrade process was successful.
    • C:ConfigMgrSetup.log – Display detailed installation steps

    Console

    • Open the SCCM Console and click on the upper left corner on the blue arrow and select About Configuration Manager
    • The Console has been upgraded to SP1
      • A new addition is the Site version which was not available on this screen before

    Site

    • Go to Administration / Site Configuration / Sites
    • Right-click your site and select Properties
    • The Site Version and Build Numbers has been upgraded to 5.00.8239.1000

    Clients

    The site server client version will be upgraded to 5.00.8239.1000. A full list of client version is available on this post.

    Boot Image

    • Go to Software Library / Operating Systems / Boot Images
    • You’ll notice that the Boot Images has been automatically upgraded on your distribution points

    Packages

    • Go to Software Library / Application Management / Packages
    • The Configuration Manager Client Package has been automatically upgraded on your distribution points

    Database Replication

    Enable the database replicas for Management Points, if it was configured before the upgrade.

    Updating the Clients and Consoles

    Once your site is upgraded, you need to upgrade the clients and console to SP1.

    Console

    You can manually upgrade by browsing to .ConfigMgrInstallationFoldertoolsConsoleSetup and execute ConsoleSetup.exe on each computer running the console.
    We suggest to create a package or application pointing on the same directory and deploy it using a collection.

    Clients

    To upgrade the clients, you have various options.

    Automatic Client Upgrade

    Using the Automatic Client Upgrade option, your client will be upgraded automatically within x days using the value specified
    • Go to Administration / Site Configuration / Sites
    • Click on the Hierarchy Settings button on the top ribbon
    • Check the Upgrade client automatically when new client updates are available
    • Select the desired number of days you want your upgrade to be run
    • A schedule task will be created on the clients and run within the specified number of days

    Client Push

    Create manual collection and use the client push function to deploy your clients. This method gives you more control on the group of computer you are upgrading.
    I like to create a collection that targets clients
    Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script which contain this query)

    Sccm 2012 Configuration Manager Download

    Report

    You can run our Client Health Check custom reportto track your client versions.

    Additional reference

    Sccm 2012 R2 Patch Download Windows 7 Image

    Microsoft SCCM 2012 R2 SP1 FAQ
    Technet – Planning to upgrade to System Center 2012 Configuration Manager SP2
    Happy updating ! ?