Custom Global Condition for Windows Features in MECM

-

It’s time for another back to the basics on Application building in MECM. You’re getting ready to create an Application in MECM. Said Application requires that a specific Windows Feature is enabled. I know I could use PowerShell App Deployment Toolkit or even a small custom PowerShell script to handle enabling the feature and running the install, but in this case I don’t want the Application to install if a particular Windows Feature is not enabled. To do this, I’m going to create a Custom Global Condition to detect if the Windows Feature in question is enabled.

Open your MECM console and go to \Software Library\Overview\Application Management\Global Conditions. Click on Create Global Condition on the ribbon. Give your Global Condition a name that makes sense for your environment. Put in a quick description of what it checks for. Device type is Windows and Condition type is Setting. Setting type is Script and Data type is String. Click the Add Script button.


For the Script language you’ll pick Windows Powershell. Paste in this script and click OK. Click OK one more time and you have created your Global Condition.

For the script I’m using for this demo, we’re looking to see if MSMQ-Triggers is enabled. You can check for any Windows Feature by swapping out ‘MSMQ-Triggers’ for the exact name of the Windows Feature you want. To lookup Windows Features in a graphically pleasant way, use the command Get-WindowsOptionalFeature -Online | OGV to dump out all the Windows Features to grid view.

# Set variables

$Feature = Get-WindowsOptionalFeature -Online | where -Property FeatureName -EQ 'MSMQ-Triggers'

 # Detect if feature is enabled

if ($Feature.State -eq 'Enabled')

{

    $Detect = "Enabled"

}

else

{

    $Detect = "NotEnabled"

} 

$Detect

Now it’s on to adding this Global Condition to your Application. Build your Application in MECM to your org’s standards, and then go to the properties for the Deployment Type. Go to the Requirements tab and click Add. Category is Custom, Condition is the name of the one you just created, Rule Type is Value, Operator is Equals, and Value is Enabled. Click OK to save the Requirement and OK to leave the Deployment Type properties.


Now you’re off to the races. Try to deploy your application on a computer where you know the Windows Feature is enabled and make sure it works. Then try to deploy your application on a computer where you know the Windows Feature is not enabled and make sure it doesn’t work. When it doesn’t work, you’ll see a status of “Requirements Not Meet” in the monitoring pane and on the local Software Center you’ll see a message that says the software isn’t applicable. Keep Calm & Global Condition On.

Comments

  1. UnknownMarch 1, 2022 at 3:44 PM

    Of course you would have a blog! Why am I just finding this out now? :)

    ReplyDelete

Post a Comment

Popular posts from this blog

CMPivot to check Services and start them (with a little help)

-
Image
Have you ever needed to get a really fast real-time look at if a service is running on a set of servers or workstations? Open CMPivot against a collection, type in your query, and send it. Seconds later you get real-time answers to your query for any online device. Queries for CMPivot run on 42 devices at once, until all devices you're querying have responded.  The last time my organization did server updates, I (and a trusty super awesome coworker) had to verify if a couple of SQL services were running on a small collection of servers. As we were manually checking these one by one, I came up with the idea that it would be incredibly helpful to use CMPivot.  The below query in CMPivot will return all devices where a SERVICE with the name containing SQL is NOT RUNNING and the service's start type is AUTO. In other words, if a service with SQL in the same is supposed to be automatically running and it's not, this query tells us. Service | where Name contains 'sql' ...
Read more

Run Scripts with Parameters in MEMCM (R.I.P. SCCM)

-
Image
How do you use Parameters in MEMCM's (R.I.P. SCCM) Run Scripts? How do you use Parameters on the Run Scripts  feature? You get three guesses, but the first two don't count. That's right, you create a script with standard PowerShell Parameters and you build it out in MEMCM. In your MEMCM console, navigate to Software Library > Overview > Scripts. If you're not familiar with Run Scripts  in MEMCM, check out my previous Blog articles on it. Click on Create Script . In the Create Script Wizard  that pops up input a Script Name , pick between PowerShell or PowerShell in your Script Language , import or paste in your script with Parameters, and click on Next . My demo script for this article ( scroll alllll the way down, it's at the bottom ) is about an 8 out of 10 on the cool factor, and about a 3 out of 10 on the usefulness factor. Long story short, the script will make a computer talk. There are two Parameters that you can input, one for "what do y...
Read more

SCCM CMPivot and Run Scripts

-
Image
What is CMPivot? What are Scripts? Why do I care about either of them? I recently attended MMS 2019 and took a great session from Jason Sandys and Tom Degreef on CMPivot and Run Scripts. They dove deep into the technical aspects of both of these somewhat new "fast channel" features of SCCM. Full disclaimer: I do not know everything and I may occasionally not know as much as you. Test everything you see here on a LAB environment and make sure you fully understand it. If you have any suggestions for improving this post, please feel free to drop a comment and I'll give you some kudos for your edit. Over simplified, CMPivot is a near real-time (not milliseconds, but usually seconds, and definitely no more than a few minutes) way to query information about your systems. You can find out literally anything about any system within your reach. Scripts pairs nicely with CMPivot because it is a real-time way to run scripts against your query results, or just another old col...
Read more