A few things not mentioned in the release notes of the latest EPM Client:
It might have been a mix of QuickStart Policy "flaws" or a EPM Client "bug" still unknown to me.
However, I have seen a few customers out there that I have been working with who have had benefit from this.
If you are running the EPM Client above 24.5.361 you can ignore this.
From around EPM Client 21.x 22.x, a change happened in the EPM Client that made it look at the content of our application groups differently. It caused the EPM Client to miss reporting vital data of applications when launching. For example, a PowerShell script (*.PS1) would show reporting for powershell.exe and a command line containing the script_name.ps1. This prevents us from creating a rule for the PowerShell script that the EPM Client supports, as the metadata is for PowerShell and not the PowerShell script. This was also true for *.bat, *.com, *.vbs, and *.msi files, all of which would report the main process exe file associated with the launched scripts, MSI etc. This information was sent to Analytics, rendering us unable to create rules that directly target our PowerShell Script or VBS scripts, etc.
A rule for powershell.exe with a comandline matching is not secure, as the content of the powershell script could be changed and still match the same rule.
This is a sample of a batch file.
Apologies for using the MMC snap-in, it’s just faster to work for the local policy.
My recommendation is to upgrade the EPM client to 24.5.361, or make the changes to your policy for getting the correct data into your analytics.
To validate if you have the issue, add the following file type in a folder and launch them
