Feature Request - Posture Check - Resolve Symbolic Links

[NicFragale]

The posture check functionality in (at least) Windows, when pointed at a "symlink" created in the base of an example app directory that is emulating versioned folders, is never found to be a "running process". It seems the reason for this is because when the process is actually run on the OS, (AKA I click the sym link to run it vs the versioned one in the subdirectory), the path that is reflected by the OS for that running process is the actual end of the link. The OS resolves the link in what it reports as running processes, but Ziti Posture Checking does not. Therefore, symlink usage for Posture Checking will always fail.

SYMLINK = C:\A\B\X.exe [--> C:\A\B\C_V1\X.exe] or [--> C:\A\B\C_V2\X.exe] or [--> C:\A\B\C_V3\X.exe] etc. etc.
OS reports: NOT THIS --> [THIS]
Posture Checks for: [THIS] --> NOT THIS

Alternative to this function would be to have an allowance for "" to expand all directories as a posture check (IE: C:\A\B\C_V\X.exe). This would then allow the posture check to pass.

So...this fails when running the binary using the symlink Posture check pointed to the symlink (C:\Users\nicfr\Desktop\NetFoundry\Utilities\rufus.exe)

And this is the only way it will pass Posture check pointed to the actual binary that symlink executes (C:\Users\nicfr\Desktop\NetFoundry\Utilities\Rufus-V1.0\rufus.exe)