Global Conditions in SCCM – Client OS condition

This blog post explains how you can use global conditions in SCCM to reduce your administrative load. Global conditions are rules that defines business or technical conditions that you can use for application deployments.

So you have an application that you only want to install on Windows 7 and Windows 8.1, and under no circumstance is this application to be installed on a server. The easy solution SCCM is to put a requirement on the deployment type specifying that it will only install on Windows 7 and Windows 8.1 operating systems. This is great, and it works brilliant. But then your company decide to implement Windows 10 and now none of these applications will install on any Windows 10 client because of these requirements. And to change this manually on every deployment type for every application is not something I want to do.

Global Conditions in SCCM – Client OS

An easy solution to this is Global Conditions in SCCM. If you instead had created a global condition named Client OS that required Windows 7 and Windows 8.1, and all your application deployment types required the global condition “Client OS” to be true, all you needed to change what the global condition to now also support Windows 10 and you where good to go.

Create a global condition named Client OS and add a clause specifying Windows 7 and Windows 8.1 as operating system. Then set your application deployment types to use Client OS as a requirement instead of specifying the operating systems on the actual deployment types. Later, when you implement Windows 10, all you need to do is change the global condition to support Windows 10 and all your applications are good to go, and now allow installation on Windows 10 as well. That was easy.

Software Library -> Application Management -> Global Conditions

Software Library -> Application Management -> Applications

Create a custom requirement for your application deployment type.

My application Adobe Reader DC will now only install on the operating systems specified in the global condition “Client OS”.


Global Conditions in SCCM – Hardware

You can also create global conditions that matches certain hardware requirements, like the computer has to be a certain model. Our global condition will now use the

So I want to make sure that the application Adobe Reader DC will not install on any Hyper-V virtual machine, but I don’t want to mess around with many collections and excluding only those. So we create another global condition where we use the Model property from Win32_ComputerSystem in WMI.

Now the application Adobe Reader DC will only install on operating systems we specified, and never install if the computer is a Hyper-V virtual machine.


Anders Rødland

Anders Rødland started his IT career in 2006. My main focus is MS Configuration Manager and client management, and I currently hold active 15 Microsoft certifications. Certified on Windows Server, Windows Client, SQL, Exchange and System Center Configuration Manager. Anders Rødland also holds an ITIL Foundation certification.This is my private blog and do not represent my employer. I use this to share information that I find useful. Sharing is caring.

Leave a Reply

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