Hello,

In SCCM 2007 I often use program deployment to push out registry keys or in this case delete them. I want to deploy a registry .reg file that deletes keys from the registry. In fact I want it to run every now an then and rerun the reg script to make sure that certain startup items aren't in the registry. A good example is the java updater. Every time some one installs java on a PC it replaces the java updater and then starts prompting my users to update java, which they cant do because they do not have admin rights.

I want my .reg script to run once a week and search and destroy all these entries that I have listed in the .reg file.

Problem is that since nothing is being installed or added, SCCM 2012 wont let me build a package without a detection rule. Since I am only deleting a file, I cant seem to make a rule that makes any sense.

I thought about creating a subsequent script that adds a registry or a file when the script runs but the next time I want to run the script it wont run because the file is there.

The second idea I had was to list a file that will never exist so that it will always rerun, but then the deployment errors because it seems to look for that file to check if the deployment completed successfully.

I must be missing something. Is there a way to delete something using SCCM?

You only need the detection method for ConfigMgr Application model. You can still create the traditional Package/Program model that we had with ConfigMgr 2007.

Per Gerry's answer, make sure you are not creating an "Application" but instead are creating a Package -- the classic Package/program paradigm still exists and is almost entirely unchanged.

Awesome! Thanks guys. All the 2012 literature and things I have read have steered me towards making "Applications". I thought that they had abandoned the old package system. I will try that. Thanks, you made my day.

Thanks again guys. I cant believe I missed that. I was thinking, "Man, why did MS have to change this so much?"....