SCCM deployment is not going through, or has managed to break down a user’s application. Sound familiar? We are now introducing a new feature for our CSM for SCCM patch management product to help you avoid these situations even better.

One challenge for Configuration Manager’s application deployment is a situation where the updated application is currently being used. As a rule, the modern applications can handle the situation, one way or another, but in the Windows world, there are as many exceptions as there are applications. A problematic situation can cause an uncontrollable boot or even break down the application.

Another challenge is installing plug-ins or add-ons. There’s a chance the installation mechanism only allows the update when the host application (Word, Outlook etc.) is not running, or the installation shuts down the host application without a warning.

There are different ways for solving these situations: you can build additional checks into the installation package, or support the deployment with additional tools.

Be it as it may, not many things bug you as much as a technical issue interrupting your work flow. Just think how much valuable working time even a single break can steal from the end user, and just how long it takes to find the thread of thought you lost when the issue arose.

How to handle the situation in the Config Manager

In SCCM, in version 1702 and newer, the package settings have included a feature known as Install Behavior. The great thing about this feature is that Config Manager client runs a check on the running applications before installing the actual installation package.

The feature is easy to use:

  1. Open Application deployment type and
  2. go to the Install Behavior tab.
  3. Add the EXE’s you do not want to be running on the device when the installation starts.

Feature’s function depends on the deployment type

Required deployment crashes, and the Config Manager retries the installation according to the normal schedule.

 

Available deployment prompts the user they need to close the application.

 

In addition, with Required deployment you can configure a rule that automatically closes the specified process before starting the installation.

 

The prevented installations are reported in the Deployment Status view.

 

How to turn on the feature in CSM for SCCM

You can manage the Install Behavior feature in CSM’s Deployment Process view.

 

Do remember that for the feature to work, you need the CSM Integration Client version 1.0.5081, that will be released for our CSM for SCCM customers shortly. Follow these instructions to check if the update is already available for you. If you run into any issues with the new version, or have any questions, don’t hesitate to contact our support.

Read more on this topic:

Comparing Patch Management solutions – Part 1/12 – Background on the comparison

We are launching a series of blog posts based on our Patch Management Tools’ Comparison, conducted in 2019. We’ll start the blog series by explaining the background of the tool comparison. Hop along and dive into the world of Patch Management!

Top Things that Annoy People regarding Continuous Security Updates

We asked people to tell us what the most annoying things are regarding security updates. Security updates are clearly a source of great annoyance.