Purpose: another fundamental thing to know when creating a Custom Detection script in SCCM 2012
After you have understood how to use Custom Detection Method in SCCM 2012, you will discover multiple ways to use it efficiently in you deployments. One such way is to use Custom Detection Method with a User Profile variable. However, there is a catch how to do this.
Purpose: Return true if predefined Windows Service Exists, return false if it does not exist
You might find yourself in a situation where some of the applications have been installed in one way and the others in another way. Depending on the problem, you might just want to clean the table and reinstall the the applications with your definitions. If this is not possible or would not be cost efficient, you could use SCCM to check if “something” exists and alter the workstations where this something is missing. In this example this “something” is a missing Windows Service.
Usage: cscript.exe IT_APP_VBS_GetWindowServiceStatus WINDOWSSERVICENAME
Configuration: You need to insert your own WINDOWS SERVICE NAME as a parameter for the script.
Purpose: a fundamental thing to know when creating a Custom Detection script in SCCM 2012
Creating a custom application detection script will require one thing to be understood before you begin scripting: How the SCCM understands that the application is installed or is not installed. You might think that if your script is returning true or false, or if it is returning zero or one – you would have found the syntax, but you are wrong.