Create SCCM Global Conditions Step by Step Guide Check Office 365 ProPlus Version

Let’s learn how to create SCCM Global Conditions using the admin console. There are 22 out-of-the-box global conditions available and ready to use.

How to create custom global conditions is what you will learn from this post.

In this post, I will give you an end-to-end walkthrough of the process of creating an SCCM Global Conditions rule to check the Office 365 ProPlus version numbers.

NOTE! – This post should be considered an example of creating SCCM Global Conditions with registry values.

Patch My PC

Related PostsLearn How to Create Install Office 365 ProPlus Client Package & Learn How to Download, Deploy and Install Office 365 ProPlus Updates.

IMP – Office 365 ProPlus Bandwidth Consideration PostsLean/HybridBuilding dynamic, lean & universal packages for Office 365 ProPlus & Office 365 ProPlus Deployment and Proxy Server Guidance!

Introduction – Create SCCM Global Conditions

SCCM global conditions are rules that represent a business or technical conditions that you can use to specify how an application is deployed to devices.

Global conditions are accessed from the Requirements page of the Deployment Type Wizard application. The Global Condition is an excellent feature in the SCCM Application model.

Adaptiva

With the help of global conditions and requirement rules, you can deploy applications on a set of devices with some specific needs that will match the device, and your application will install. The global condition helps you to reduce human error.

Besides that, you can create custom conditions such as the registry value of applications, versions, etc. Creating custom conditions can be very powerful, and all you need is a few steps to get started.

What is the Scenario to Create SCCM Global Conditions

I want to install Office 365 ProPlus application on a set of computers that are running on lower versions of Office 365 ProPlus.

And SCCM Global Conditions I’m going to create will help skip the Office 365 ProPlus application installation on computers that have already installed a higher version office.

NOTE! – If the global condition is not met, you can see the
application deployment status as “Requirement not met” from the monitoring workspace.

In this post, I’ll explain how you can create a global condition based on Registry, and that can be used when deploying applications to specific Version where requirements should not meet.

For testing, I have created an Office 365 ProPlus Application that must only be installed on all Laptops which does not have a specific version or lower than that.

Related PostsLearn How to Create Install Office 365 ProPlus Client Package & Learn How to Download, Deploy and Install Office 365 ProPlus Updates.

How to Create SCCM Global Condition

Let’s create a custom SCCM Global Condition. Follow the below steps to make a global condition.

  • Open SCCM Admin console
  • Navigate to Application management from the Software Library workspace
  • Right-click on Global condition and create Global Condition
SCCM Global Conditions Node
SCCM Global Conditions Node – Create SCCM Global Conditions

Fill out SCCM Global conditions details as per your requirements. In the following example, I will give you a walkthrough of a global condition to check the Office 365 ProPlus Version Lower than 1708 Build.

  • Name of the global condition – MS Office365 Lower than 1708 Build
  • Description – If you want to explain what this Global condition is for?
  • Device Type – Windows
  • Condition Type – Setting (for file, folder, or registry key value )
  • Setting Type – Registry Value
  • Data Type – String
  • Specify the Registry Value(below) to assess the compliance on computers
  • Hive Name – HKEY_LOCAL_MACHINE
  • Key Name – SOFTWARE\Microsoft\Office\ClickToRun\Configuration
  • Click OK to complete the SCCM Global Conditions creation process
Create SCCM Global Conditions with Registry Values - Create SCCM Global Conditions
Create SCCM Global Conditions with Registry Values – Create SCCM Global Conditions

Configuring SCCM Global Condition within an Application

Now you have created the SCCM global condition. It’s time to configure requirement rules in the SCCM application deployment type called “MS office 365 ProPlus_16.0.8431.2270.” You need to configure the Global Condition rule in Application deployment types.

NOTE! – A Global condition is a requirement rule that is evaluated in real-time by an SCCM client. The SCCM client will only start downloading the application if the global condition is TRUE.

In the following screenshot, we can see that the required option is available in application deployment type properties.

Requirements = Global Condition Rules

Follow the steps to configure the Global Condition Rules for a particular application.

  • Navigate to \Software Library\Overview\Application Management\Applications
  • Select the Office 365 application you want to deploy and go to properties
  • From Application Properties, go to Deployment Types
  • Select the Deployment Type called “MS office365 ProPlus_16.0.8431.2270” and click the EDIT button.
  • Go to the Requirements tab.
  • Click on the ADD button to add and configure SCCM Global Condition for that application deployment.
Create SCCM Global Conditions Step by Step Guide
Create SCCM Global Conditions Step by Step Guide

Select the Custom Category from the below three(3) categories.

  • Device
  • Custom
  • User
Different Categories of Requirement Rules
Different Categories of Requirement Rules – Create SCCM Global Conditions Step by Step Guide

NOTE! – Following are the default conditions in the Device category.

Default SCCM Global Conditions or Requirements options
Default SCCM Global Conditions or Requirements options – Create SCCM Global Conditions Step by Step Guide.

As you have already created a new custom global condition in the above section, you can select that custom global condition in the following section.

  • Select the custom in the category
  • Select one custom SCCM Global conditions you created in the “Office 365 1708 Version.”
  • Rule Type – Select Value
  • Add the operator as “None of.”
  • You have to give all higher versions of office 365 which you want to exclude in the Values section, as shown in the below picture
    • 16.0.8431.2329
    • 16.0.8431.2351
    • 16.0.8431.2366
    • 16.0.8431.2372
  • Click the OK button to finish the configuration (Requirement Rule) with SCCM Global Conditions.
Create or Select Office 365 ProPlus Application Requirements
Create or Select Office 365 ProPlus Application Requirements

Click OK from the Application Deployment Windows as shown in the below picture.

Create SCCM Global Conditions Step by Step Guide Check Office 365 ProPlus Version
Create SCCM Global Conditions Step by Step Guide Check Office 365 ProPlus Version

Now, you are ready to deploy the Office 365 ProPlus application. We have covered end-to-end Office365 ProPlus deployment in the following post. Learn How to Install Office 365 ProPlus Client Package.

Results – Deployment Status

Once the Office 365 ProPlus application is deployed to the collection, you can monitor the deployment status from deployment in the Monitoring workspace.

The deployment status of the application; shows that a few computer requirements are not met, as you can see in the below picture.

Create SCCM Global Conditions Step by Step Guide
Create SCCM Global Conditions Step by Step Guide

Resources

Author

Sharad has been working in the industry since 2007. Since starting, he’s worked with Active Directory, Group Policy, SCCM SCOM, MS Intune, and PowerShell. Sharad currently works as a Senior consultant in Japan. His focus has been on SQL reporting for SCCM, MS Intune, and SCCM migration.

12 thoughts on “Create SCCM Global Conditions Step by Step Guide Check Office 365 ProPlus Version”

  1. Any idea here, I have a feeling something is wrong with how I have done the powershell? I am using custom string global condition to report back all NICs detected using this:

    $NIC= ((Get-NetAdapter -physical).InterfaceDescription | format-list -Property *)
    $NIC

    I can run this in PS console from target PC and I get:

    PS C:WINDOWSsystem32> $NIC= ((Get-NetAdapter -physical).InterfaceDescription | format-list -Property *)
    $NIC
    Realtek USB GbE Family Controller
    Intel(R) Wi-Fi 6 AX201 160MHz

    Note 2 nics listed. However, in SCCM monitoring it falls under “Requirements not met tab” and often only shows one client value, not both client values which should be two line items with each NIC listed. I am perplexed why sometimes 2 client values are detected and sometimes only 1 is detected, even though verifying on client there really is 2.

    I have deployed app and it keeps saying in appintent log that it is not applicable. For my app requirement I am using, value, ONE OF:

    Intel(R) Wi-Fi 6 AX201 160MHz
    Intel(R) Wi-Fi 6 AX201
    Intel(R) Wi-Fi 6 AX201%

    Hope you’re tracking and I appreciate any assist!

    Reply
  2. Hi, good article, but I have some devices that do not have the application installed, so I thought I could use the “none of” operator, but it does not seem to work. The application in question is inhouse built that does not put an entry in the registry, which in turn does not create an entry in add and remove programs. It creates a folder with the necessary files, then a shortcut on the desktop to launch it. I use a file version for detection method. Now it is time for an upgrade, they want any devices that do not have it to be published as available, and the ones that do, to get it as required. So, I created two applications, and used a global condition that looks for the file version lower than the one being deployed, and that works fine for those. For the second application, I tried using another global condition with the “none of” operator and listed the new and old versions for the value thinking if the devices that don’t have it installed should meet the requirements, but they don’t per the monitoring results.

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.