I am in the process of creating a baseline to check that all required applications are installed on clients.

This script install application has the following Detection Method:

 

When creating the Configuration Items I have left the Detection Method as "Always assume application is installed" (this may be the issue!) I then created the following Settings item:

I created a test Configuration Baseline and deployed this to my test collection.

This reports as being Compliant (great!) so to test for non-compliant I edited the registry setting on the device for the PowerShellVersion from 4.0 to 3.0.

Unfortunately this still shows as being compliant after evaluating the baseline.

What is the correct way to set up the Configuration Item in this instance?

Thanks in advance.

Clint

• Edited by Clint1984 22 hours 3 minutes ago

For clarification, could someone confirm that for a Configuration Item you can only use the Detection Method "Detect a specific application and deployment type" when the application uses an msi installation? 

The reason I ask is applications using a script installation do not show up when selecting this detection method.

Yes, not all apps/DTs are listed when using the wizard. That's by design. 

Open the control panel applet on the client and view the compliance report for details. 

Thanks Torsten.

Was I correct in thinking its only .msi deployed applications that show in this list?

That's where I was checking the compliance from but its not really giving me any useful information.

I'm thinking I will probably just need to create a script for detecting if these applications are installed, was just wanting to check if there was an easier way using the reg keys listed.

That's where I was checking the compliance from but its not really giving me any useful information.

Why not? It should tell you which value was expected and what was currently seen on the client.

I *think* that only msi DTs will be listed. 

The report shows Microsoft Windows Management Framework 4.0 as being compliant however as I changed the registry key on the machine for PowerShellVersion from 4.0 to 3.0 I was expecting this to show as Non-compliant.

As stated I think this could be to do with the "Always assume application is installed" option being used in the Detection Method.  I am looking for the best way to check this registry version is the same as specified in the Condition shown as this is the Detection Method outlined in the actual application.