Deploy an Application with System Center Configuration Manager R2

A System Center 2012 Configuration Manager application contains the files and information that are required to deploy software to a device. An application contains one or more deployment types that comprise the installation files and information that are required to install software. A deployment type also contains rules that specify when and how the software is deployed.

This document shows how to deploy an MSI application to users.


  • Create the application.
  • Create deployment Type.
  • Distribute Content.
  • Deploy Application.

Create the Application:

Open up SCCM.


  • Step 1 -> Click on Software Library.
  • Step 2 -> Click on Application Management.
  • Step 3 -> Click on Applications.


  • Right Click on Applications and then click on “Create Application”


  • When the screen above shows click the second radio button to manually specify the application information and then click Next.


  • Fill in the following information:
    • Name
    • Publisher
    • Owners
    • Support contacts.
  • You can select Administrative Categories.
  • Once done click Next.


  • Fill in your Keywords, you can change the Icon by clicking the Browse Button. Once finished click Next.


  • You can configure “Deployment Types” now or later, we will do this later, click Next.


  • Confirm the settings, click Next.


  • Progress status.


  • The wizard has completed. Click the Close button.

 Create Deployment Type:


  • Step 1 -> Right click on the new application we just created.
  • Step 2 -> Click on “Create Deployment Type”


  • Once the Wizard has started, click on the second radio button to manually specify the info and click Next.


  • Step 1 -> Type in the Name of the application.
  • Step 2 -> Click on the Select button to choose your language.
  • Click Next.


  • Step 1 -> Click on the browse button to location the MSI file. After this SCCM will fill in the parameters. Alternatively you can specify them.
  • If you want to provide uninstall options then click the Browse button next to “Uninstall Program”
  • Step 2 -> Click on the checkbox to “Run installation and uninstall program as 32-bit process on 64-bit clients”
  • Click Next.


  • On the above screen click on the “Add Clause Button”


  • Step 1 -> Click the dropdown and choose your selection, in this exercise I went with “Windows Installer”.
  • Step 2 -> Click on the browse button and select the MSI file. Once done click OK.


  • As shown above the Clause has been added. Click Next.


  • Step 1 -> Select the Installation Behavior.
  • Step 2 -> Select the Logon requirement.
  • Step 3 -> Select the program visibility
  • You can also change the maximum allowed run time.
  • Click Next.


  • If you have any specific installation requirements then click the “Add” button.
  • Click Next.


  • If you have any dependencies then click the “Add” button.
  • Click Next.


  • Review the information and then click Next.


  • Progress screen.


  • Once the deployment wizard finishes then click close.

Distribute Content:


  • Step 1 -> Right click the application.
  • Step 2 -> Click on “Distribute Content”


  • When the Wizard starts click the Next button.


  • Click Next.


  • Step 1 -> Click on the Add button.
  • Step 2 -> Click on Distribution Point.


  • Step 1 -> Select your server.
  • Step 2 -> Click on OK.


  • Once you have clicked “Add” and selected your Distribution point it will show above.
  • Click Next.


  • Review the information. Click Next


  • Progress.


  • Distribute content complete. Click the close button.

Deploy an Application:


  • Step 1 -> Right click the application.
  • Step 2 -> Click on deploy.


  • Step 1 -> Click on the browse button (collections) and select the target audience.
  • Step 2 -> Leave this as default or deselect it to distribute content.
  • Click Next.


  • Verify the distribution points and then click Next.


  • Step 1 -> Select the Action (Install or Uninstall). We going to install the application.
  • Step 2 -> Select the purpose (Available or required).
  • Click Next.


  • You can set a schedule or leave the default and click Next.


  • Specify the user experience settings. Click Next.


  • Here you can specify alert options. Click Next.


  • Confirm the settings, click Next.


  • Progress screen.


  • Once success completed you can click the close button.

Hope it helps.


Deploy Windows Updates with System Center Configuration Manager 2012 R2 (SCCM)

System Center Configuration Manager (SCCM) 2012 R2 adds a feature that enables software updates to be automatically approved and deployed to selected machines in your organization.

Icon Descriptions and Explanations:


The icon with the green arrow represents a normal software update.


Normal software updates have been synchronized and are available for software deployment.

Operational Concerns:

There are no operational concerns.



The icon with the black X represents an expired software update. You can also identify expired software updates by viewing the Expired column for the software update when it displays in the Configuration Manager console.


Expired software updates were previously deployable to client computers, but once a software update is expired, new deployments can no longer be created for the software updates. Expired software updates contained in active deployments continue to be available to clients.

Operational Concerns:

Replace expired software updates when possible. When software updates become expired, Configuration Manager does not remove the software updates contained within active software update deployments. Configuration Manager continues to assess software update compliance on expired software updates in deployments, but they are considered “not required” for reporting purposes.



The icon with the yellow star represents a superseded software update. You can also identify superseded software updates by viewing the Superseded column for the software update when it displays in the Configuration Manager console.


Superseded software updates have been replaced with newer versions of the software update. Typically, a software update that supersedes another software update does one or more of the following:

  • Enhances, improves, or adds to the fix provided by one or more previously released software updates.
  • Improves the efficiency of its software update file package, which clients install if the software update is approved for installation. For example, the superseded software update might contain files that are no longer relevant to the fix or to the operating systems now supported by the new software update, so those files are not included in the superseding software update’s file package.
  • Updates newer versions of a product, or in other words, is no longer applicable to older versions or configurations of a product. Software updates can also supersede other software updates if modifications have been made to expand language support. For example, a later revision of a product update for Microsoft Office might remove support for an older operating system, but add additional support for new languages in the initial software update release.

On the Supersedence Rules tab in the Software Update Point Component properties, you can specify how to manage superseded software updates. For more information, see theSupersedence Rules section in the Planning for Software Updates in Configuration Manager topic.

Operational Concerns:

When possible, deploy the superseding software update to client computers instead of the superseded software update. You can display a list of the software updates that supersede the software update on the Supersedence Information tab in the software update properties.



The icon with the red X represents an invalid software update.


Invalid software updates are in an active deployment, but for some reason the content (software update files) is not available. The following are scenarios in which this state can occur:

  • You successfully deploy the software update, but the software update file is removed from the deployment package and is no longer available.
  • You create a software update deployment at a site and the deployment object is successfully replicated to a child site, but the deployment package has not successfully replicated to the child site.

Operational Concerns:

When the content is missing for a software update, clients are unable to install the software update until the content becomes available on a distribution point. You can redistribute the content to distribution points by using the Redistribute action. When content is missing for a software update in a deployment created at a parent site, the software update must be replicated or redistributed to the child site. For more information about content redistribution, see the Redistribute Content on Distribution Points section in the Operations and Maintenance for Content Management in Configuration Manager topic.

Steps to download and deploy Windows updates.


  • Open SCCM and then Click on Software Library -> All software updates.


  • Select the updates you want to download and deploy. You can select multiple items by holding down the shift key or individual ones using the ctrl key.


  • You can leave the Deployment Name as is or give it your own description.
  • Click on the browse button to select the collection you want to target these updates to. Once done click the Next button.


  • Select the Type of Deployment, if you want to use Wake-on-LAN then select the checkbox.
  • Choose your detail level and then click Next.


  • Here you can configure the schedule for updates. Once you have made your selections click Next.


  • This window all you to specify deadline behaviour.
  • To suppress restarts on servers make sure the checkbox under “Device Restart Behavior” is checked.
  • Click Next.


  • Make your selection here regarding alerts and then click Next.


  • Specify your download settings and then click Next.


  • Click on the Browse button to select your deployment package and then click Next.


  • If you download updates from the internet then leave the default setting above, otherwise chose to download updates to a share.
  • Click Next.


  • Select your language and then click Next.


  • Confirm the settings, you can review the details of all updates you selected.
  • Click Next to start downloading the updates.


  • Updates download starting.


  • Updates downloads in progress.


  • Once all the updates have finished downloading it will show you the screen above. If there were any failures or errors it will also list it here for you to review.


  • It takes a few minutes for the database to update but once you refresh the screen it will show the updates have been deployed.

Hope it helps.



System Center Configuration Manager 2012 R2 Installation with local SQL 2012 SP1

Active Directory Setup:

Create the following accounts/Groups in Active Directory.

  • DOMAIN\ConfigMgrAdmins            ConfigMgr Administrators security group
  • DOMAIN\ConfigMgrLocalAdmin     ConfigMgr Client Push account

Add your account or any other member that is going to administer SCCM to the “ConfigMgrAdmins” group.

Prerequisites List (SCCM Server):

  • Install Server 2012 OS
  • Join server to the domain
  • Install all windows updates so the server is fully patched.
  • Install Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1
  • Install SQL 2012 SP1.
  • Add the “ConfigMgrAdmins” domain global group to the Local Administrators group.

Windows Features Requirement:

Run the following from PowerShell (run as Administrator):

  • Add-WindowsFeature Web-Windows-Auth,Web-ISAPI-Ext,Web-Metabase,Web-WMI,BITS,RDC,NET-Framework-Features,Web-Asp-Net,Web-Asp-Net45,NET-HTTP-Activation,NET-Non-HTTP-Activ,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Redirect,Web-App-Dev,Web-Net-Ext,Web-Net-Ext45,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-HTTP-Tracing,Web-Security,Web-Filtering,Web-Performance,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Mgmt-Compat –Source D:\sources\sxs –Restart

After installing these roles/features, you might have to register ASP.NET with IIS.  The simplest way is to open an elevated command prompt: C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe –r

 Prepare Active Directory for Configuration Manager



  • Connect to a domain controller in your environment and load ADSIEdit. ADSIEdit is found under Administrative Tools. Expand Default Naming Context and then expand the DC name and under the System OU create a new Object as Shown Above.

create Object



  • Click on container and then click Next.

create object 2


  • Enter in System Management and click the Next button.
  • Complete the Wizard and then close ADSIEdit.

Delegate control on the newly created container.

  • Open up ADUC.MSC (Active Directory Users and Computers)
  • Expand the System Container. You will see the System Management container you just created above.
  • Right click on the System Management Container and select Delegate Control.

delegation of control


  • Click on “Create a custom task to delegate” and click the Next Button.

delegation of control 1


  • Make sure the first option is selected and click the Next Button.

delegation of control 3


  • Check all Permission boxes and click Next and then complete the delegate wizard.

Extend the Schema.

Open up the ISO file that contains the SCCM 2012 R2 installation files and navigate to the following directory.

  • \SMSSetup\Bin\x64\

Or open up and elevated command prompt and Navigate to that folder.

If you opened up the directory using explorer then Right Click on the Extadsch.exe and “Run as Administrator” or from the prompt run the same file.

A log file ‘ExtADSch.log’ will be generated on the root of the C:\ Drive. Look for the entry ‘Successfully extended the Active Directory schema.’

**Note that replication can take time so rather wait or force replication**

Install Windows Assessment and Deployment Kit for Windows 8.1 (ADK)

Click on the link below to download the ADK



  • Click on the checkbox to accept the terms for .NET and then click on the “Accept & Install” button for .NET Framework 4.5 to install.

adk confirmation


  • When you get prompted to restart click the Ok button.

adk setup 1


  • After the server has rebooted the installation will resume. You can choose the default option as shown above or Download the ADK to a share and run the install from there. I chose the default, click the Next Button to proceed.

adk ceip


  • Make your selection and then click the Next button.

adk license agreement


  • Accept the License agreement for the installation to continue.

adk feature setup


  • Only install the following options above:
  • Deployment Tools
  • Windows Preinstallation Environment (Windows PE)
  • User State Migration Tool (USMT)
  • Click the Install button.

adk installation progres


  • Progress screen..

adk setup complete


  • Once the installation finishes you will get the screen above. Click the close button. The ADK is now setup.

Install SQL Server (2012 SP1)

sql server setup 1


  • Double click the setup file located in the SQL 2012 SP1 Media
  • The screen above will show, click on “New SQL Server Stand-alone installation or add features to an existing installation”

sql server setup 2


  • The above screen will show, if there are any warnings or errors it will list them. Click Ok to continue.

sql server setup 3


  • Here you can enter a product key that you received from MS found on the media.
  • In this Sandbox setup we will choose “Evaluation” and then click the Next button.

sql server setup 4


  • Click the checkbox to accept the license terms and then click the Next button.
  • If there are any updates on the next screen let them download and proceed with the install.

sql server setup 5


  • Again the support rules will run, click Next to continue

sql server setup 6


  • Select the first option and click the Next button.

sql server setup 7


  • On the feature selection screen, choose the following options:
    • Database Engine Services with Full-Text and Semantic Extractions for Search
    • Reporting Services – Native
    • Management Tools and its sub-feature.

sql server setup 8


  • Click Next to continue

sql server setup 9


  • I left the instance as default, click the Next button to continue.

sql server setup 10


  • Click Next to continue.

sql server setup 11


  • As this is a Sandbox environment the defaults were chosen but you will want to add in the Domain accounts that have access to SQL in a production Environment.
  • Don’t click next just yet, we need to set the Collation as with SCOM. Click the Collation Tab next to the Service Accounts Tab.

sql server setup 12


  • Click on the Customize button to change the collation.

sql server setup 13


  • Click on the radio button labelled “SQL Collation, used for backwards compatibility”
  • Scroll down until you see “SQL_Latin1_General_CP1_CI_AS”. Click on it and then click OK.

sql server setup 14


  • Add in the Current User and any other user that will be managing SQL. Click Next to continue.

sql server setup 15


  • Select the option “Install Only” and then click Next.

sql server setup 16


  • Make your selection and click Next.

sql server setup 17


  • Click Next to continue.

sql server setup 18


  • Review all the options you just made, if happy click the Install button.
  • Sit back and wait for the installation to finish, it can take a while.

Install System Center Configuration Manager 2012 R2 (SCCM)

sccm setup 1


  • Go to the folder where you extracted the SCCM setup files and double click the setup. The above screen will show. Click Next to continue.

sccm setup 2


  • Click on the option “Install a Configuration Manager Primary Site” and then click Next.

sccm setup 3


  • As this is a sandbox install we will install the evaluation edition of the product. Click next to continue.

sccm setup 4


  • Click tickbox to select and accept the license terms and click Next to continue.

sccm setup 5


  • Accept all the license terms (3 Tick Boxes) and then click Next to continue.

sccm setup 6


  • SCCM will required a number of files. I chose the default “C:\Downloads” but you can add in your own share or directory. If you have manually downloaded the files then you would select the 2 radio button and browse for them.

sccm setup 7


  • A new window opens and displays a progress bar of the downloads.

sccm setup 8

  • Select your desired Server language and then click Next to continue.

sccm setup 9

  • Select your desired client language and then click next to continue.

sccm setup 10

  • Enter in your site code and site name. Your site code needs to be unique, you cannot go and change it later on as all this information will be written to AD.
  • I used TLB for Test Lab and the site name as SCCM 2012 Test lab. Click Next to continue with the installation.

sccm setup 11

  • Select the radio button to install this as a stand-alone site and click Next to continue.

sccm setup 12

  • Click Yes to continue.

sccm setup 13

  • All the boxes will be populated, leave the defaults and click Next to continue.

sccm setup 14

  • You can leave the defaults where SQL is located or you can change the paths, in this setup the defaults were used. Click Next to continue.

sccm setup 15

  • Enter your current server as the SMS Provider and click Next to continue.

sccm setup 16

  • Select the 2nd radio button as shown above as we not running PKI. Click next to continue.

sccm setup 17

  • Install both Management Points and Distribution Points on the server, enter in the server FQDN. Click Next to continue.

sccm setup 18

  • Make your selection and click Next to continue.

sccm setup 19

  • Review the summary and then click Next to continue.

sccm setup 20

  • The setup will do a prerequisite check, the warnings above can be ignored but in a production environment you might want to make sure you have not errors/warnings. Click Next to continue.

sccm setup 21

  • The installation has started. Sit back and wait.

sccm setup 22

  • After a little while the installation completed. You can click the close button and launch the SCCM Console and start your configuration.

SCCM 2012 WSUS Sync Failed: The operation has timed out.

Today I went to check and download windows updates and I use a tool called the Configuration Manager Trace Log Tool to read the WSYNCMGR.LOG file.

I noticed the sync started and then just hangs, after a while an error is presented:

Sync error

I went and checked the WSUS service and it was stopped, in my attempt to start it I was presented with the following error:

  • Could not start the WSUS service on local computer. Error 193: 0xc1

wsus service error

I saw after a reboot Windows was complaining about a file rename and under the root of C:\ I had this file called program.

Upon renaming and deleting it I was able to start the WSUS service. After that I ran “Syncronize Software Updates” from SCCM and the error was gone.

Hope it helps.

SCCM 2012 R2 CU1 and SQL 2014

Today I got my hands on SQL 2014. I decided to upgrade my System Centre Configuration Manager Server.

It took a couple of hours as SQL 2008 R2 needed to be on SP2 and SQL 2012 R2 needed to be on SP1.

After 2.4GB’s of updates the SQL 2014 checks passed. The upgrade from SQL 2008 R2 or SQL 2012 takes about 30-60 min.

After the upgrade I rebooted the server, upon starting up SCCM I clicked on the Monitoring tab and went to Reports and lone and behold I was presented with a SOAP error.

I removed the Reporting Services Point, rebooted the machine and the event log was flooded with alerts that SQL Reporting was not functioning. I then attempted to Add the Reporting Services Point back and it wouldnt show the SQL Reporting Services Instance.

Upon some investigation I found CU1 for SCCM 2012 R2. After I applied this I rebooted the server, logged back in and then configured SQL Reporting Services. I made sure that it was looking at the correct DB’s which is ReportServer.

I then stopped and started the Reporting Service, waited a few minutes and no more errors were logged. I went back into SCCM -> Monitoring -> Reports and all 469 reports were showing.

Upon running them I didn’t get a SOAP error again and the reports showed correctly.

Hope it helps.