Skip to Main Content
Patch My PC Feature and Application Request

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:

3 VOTE
Status SUBMITTED
Created by Ben Lee
Created on Apr 7, 2025

Alternate method of "Conflicting Processes"

I only have one app in mind at the moment, but it would be useful to be able to use other conditions for "Conflicting X", such as registry key, or file existence, or more specifically in the case of the app I have in mind (Cisco Secure Client - AnyConnect VPN), run a command to get a string result that can be compared.

Reason, "Cisco Secure Client - AnyConnect VPN" has a command available to detect if it is actually connected. The default method of "Conflicting Processes" is not ideal, since the VPN client starts at logon by default, so it will basically always be running.

Rather than prompt to user to defer if the process is running, we would prefer to prompt only if it is actively connected, so this type of "Conflicting X" would cover that.

In the meantime, we use a PSADT script to detect VPN connectivity, then copy and rename a local exe file (timeout.exe) to a temp folder, then run it under that new name that has been added to PMPC "Conflicting Processes" so that PMPC will detect that running process, then have a PSADT postscript to remove the copied file. Not the cleanest solution but has been working for us.

  • Attach files
      Drop here to upload
    • +2