0/1 Lessons

Getting Started with this Course

• 26min

0 / 3 lessons complete

System Center Configuration Manager - Features and Capibilities

• 31min

0 / 5 lessons complete

SCCM 1902 Lab Setup

• 51min

0 / 12 lessons complete

Installing SCCM 1902 Installation

• 1hr 32min

0 / 11 lessons complete

Configuration Manager Basics

• 1hr 58min

0 / 8 lessons complete

Updating SCCM

• 30min

0 / 7 lessons complete

SCCM Client Installation

• 46min

0 / 4 lessons complete

User and Device Collections

• 1hr 6min

0 / 13 lessons complete

Application Management

• 2hr 34min

0 / 12 lessons complete

Operating System Deployment

• 23min

0 / 7 lessons complete

Endpoint Protection

• 1hr 12min

0 / 10 lessons complete


• 37min

0 / 4 lessons complete

Problems and Solutions from the Message Board

• 14min

0 / 5 lessons complete

Client Management Part 1


Q&A (0)

Notes (0)

Resources (0)

Saving Progress...


There are no resources for this lesson.

Notes can be saved and accessed anywhere in the course. They also double as bookmarks so you can quickly review important lesson material.

Create note

Welcome to SCCM Features and Capabilities Overview.

We have already talked about Asset Management and Administrative Tasks. Now let’s get into Client Management.

In part 1 of this section, we will discuss Application Management, Operating System Deployment, and Software Updates

Application Management 

When it comes to application management, we need to understand the deployment type and the deployment location

  • First, the deployment type of an application can be MSI (Microsoft Software Installer) or an EXE, (Executable)

Or a deployment type could be a phone app or several other packages.

  • There are two ways you can deploy software in SCCM. You can choose to create and deploy an application or package. We’ll talk about the differences between a package and an application in a minute.


Now that we understand the types of Deployment let’s take a look at Deployment Location.  We can deploy applications or packages to a user or a device collection

  • A collection is a group of users or computers.
  • In this case, we have deployed Chrome, Notepad ++ to a device collection called laptops.

In which the computer named SAWS01 is a member.

  • Displayed is the Software Center on the computer SAWS01 showing the software that has been deployed and installed on this computer.

Applications vs. Packages – The pro’s and the Cons 

  • With applications, you can deploy MSI, Exec, and others. The default is MSI.
  • You can detect if the deployed software has already been installed on your target computer. For example, if you are trying to deploy Adobe Acrobat and adobe acrobat has already been installed on the target computer, SCCM would detect that and not install the software.
  • The process of updating an application version is referred to as Software Supersedence.
  • Applications have a new approval request feature, so what that means is that the user has to request permission from the admin before the software is installed from the software center.
  • You can deploy applications from the Apple store or the google play store for Android or Apple devices.
  • With Applications, you get more detail from Reporting. Reporting uses SQL to store information about your SCCM infrastructure. 


  • More complicated to deploy, more time consuming


  • You can deploy MSI and Exec’s as well when deploying packages.
  • Packages are good for scripts because packages have reoccurring schedules. 
  • Packages are more straight forward and less time consuming to configure.
  • There are not as many requirements, only about 5 screens to go through.


  • Packages have limited configuration choices.
  • Reporting of Package deployment is limited to success or failure.
  • You can’t detect if the software has already been deployed to the target without using a script.
  • There is no approval request feature.

In the Application Section of this course, I’m going to show you how to deploy Msi’s and executable Software applications.

Operating System Deployment

  • Operating system Deployment gives administrators the option of deploying the Windows 10 operating system complete with drivers and their choice of applications or tools that the user or group may need to accomplish their daily tasks.
  • Pictured is the Windows 10 Pro operating system image that will be deployed to a collection of computers referred to in SCCM as All unknown Computers.

in SCCM, an unknown computer is a computer where the configuration manager client is not installed. Or that computer is unknown to the Configuration Manager database.

  • Here this computer has already received an IP address and is ready to boot into the Windows PE or preinstallation environment (Think of the preinstallation environment like a really light bootable Operating System)
  • I’ve created a Task Sequence called Windows Pro 1809 TS. A Task sequence references a boot image that starts the destination computer, and any additional content like applications and updates.
  • Here the task sequence is installing the operating system
  • The Operating has been installed
  • You can see the computer name in the control panel, system
  • And the same computer name appears in the configuration manager console. 

Server Academy Members Only

Sorry, this lesson is only available to Server Academy Full Access members. Become a Full-Access Member now and you’ll get instant access to all of our courses.

0 0 votes
Lesson Rating
Notify of
profile avatar
Inline Feedbacks
View all comments