Since a user might do ANYTHING, maybe the only way to check if he/she's used the correctl link to start the application is by using (and checking) some arguments in the link (and then still he / she might fake it by specifying the needed argument in another link, directly to the executable).

One way to resolve this issue is to put the applications onto a portal page, we use Citrix for our portal.

The apps is never on the client platform/VM/desktop, so they are always required to start the correct version of the EXE.

Another option, similar to the first, is to load the EXE in a controlled environment and only load shorts to the actual EXE onto the client platforms.

Later -

Olan

Roaming folder is a hidden system folder... typically, developers know about it but end users don’t look through its contents and execute .EXE there.  But regardless, we will try to do something to further reduce likelihood users launch the wrong thing.

Hi Ephraim;

  Yes, the Web Link is the only way to ensure that the PowerClient Launcher is start-ed first. This is very important because it starts the App launcher (AL). The AL is the one that checks for updates to the App, PB run-time and other dependent software prices. If out-of-date, the launcher will first update these entities before launching your specific PB App.

  Unfortunately, there is no current way of blocking an App EXE from being started directly from the deployed EXE or a short-cut for the same at the moment. Please open a Beta support ticket for this issue so that Engineering can track this requirement for implementation consideration.

Regards ... Chris