I'm wanting to deploy an application in SCCM to machines in which a particular registry key does NOT exist. By default, "This registry setting must exist on the target system to indicate presence of this application" but I don't have any other available options because I am not looking for any particular value of the key.

Below is my current Detection Rule:

Basically, I'm in search of a way to set it to "This registry setting must NOT exist on the target system to indicate presence of this application.

Any suggestions?

• Edited by yesmarcs Wednesday, December 17, 2014 3:57 PM screenshot

I'm wanting to deploy an application in SCCM to machines in which a particular registry key does NOT exist. 

Detection rules are not intended to be targeting mechanisms at all and it sounds as if you are wanting to do that ... 

Detection rules run *before* and *after* the installation in order to check (a) if the application is already installed and (b) if it was installed successfully. 

You can use a basline / CI in order to find clients where that regkey is present or absent though.

Honestly, if there is no applicable detection, then you shouldn't be using an application but instead should use a package an

See Torsten's reply. I'm confused as to why you would use the above criteria for detecting whether an application is installed or not though. Are you simply trying to execute something on system's where the above value doesn't exist, like a one-time script? Then why not build the detection into the script itself? Thus, the script only really does something on systems where the value does

You're ultimately using the toolset in a way it was not really designed for and thus slipping into the cracks.

If the info is important though, you could modify your script to create a custom WMI namespace, a custom WMI class and populate it with an object containing the run information. This is then trivial to pick up with hw inv. This post will help you get started on that: http://blog.configmgrftw.com/wmi-manipulations-and-manifestations/

The usual answer of system being used in wrong way, blah blah blah.

And who says what way is correct?

There is obviously a faulty design, which allows to chose EXIS option, but somebody forgot to program NOT EXIST logic into it.

It is not a fault of the user, it is a fault of the lame programmer.

It is obvious, if there is NOT something there, I want to run program A. If something is there, then I no longer need/want to run this program.

What is wrong with that?

Package/program is an old way of doing it, which keep it at all?

Seb

Do not mistake your own opinion (and worshiping Microsoft programmers) are the truth & the only truth.

Just because you do not use it, it does not mean that it must be good way.

And do not make childish examples (as the above are). Using the tools this way & only this way, because they are inflexible, does not make them good tools!

If an option exists to check FOR then there should be an option to check AGAINST.

Plain & simple logic!

Make your comments useful please:

So how do you install something (a simple service that does simple action) if the ONLY indication that it exists, is the registry service entry?

Existence of the file itself does NOT matter (as it could exists in filesystem, but not be used)

If it exists, I DO NOT want/need/should run install. but if it is NOT there, then please do install

Seb

• Edited by scerazy 10 hours 44 minutes ago

Do not mistake your own opinion (and worshiping Microsoft programmers) are the truth & the only truth.

Just because you do not use it, it does not mean that it must be good way.

And do not make childish examples (as the above are). Using the tools this way & only this way, because they are inflexible, does not make them good tools!

If an option exists to check FOR then there should be an option to check AGAINST.

Plain & simple logic!

Make your comments useful please:

So how do you install something (a simple service that does simple action) if the ONLY indication that it exists, is the registry service entry?

Existence of the file itself does NOT matter (as it could exists in filesystem, but not be used)

If it exists, I DO NOT want/need/should run install. but if it is NOT there, then please do install

Seb

• Edited by scerazy Friday, September 04, 2015 9:09 PM