The final detection method to discuss is a custom script. The possibilities are endless when using a custom script. Most of your applications need standard detection methods (Windows Installer product code, file, or registry), but eventually you will encounter an application requiring a more complex way to determine installation state.
You write a custom script that ConfigMgr can use to determine if the software is installed. Be sure to return text from the script to confirm that the software is installed. If no text is returned, ConfigMgr understands that to be “not installed.” The next two sections provide sample scripts for leveraging a custom script detection method.