Client Management Part 1
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.
Applications
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 t…
No comments yet. Add the first comment to start the discussion.