LouieBee

no worries! I was not aware it was already patched, or patched in an upcoming update.

I created a C++ program that helps with this. When compiled, it spits out an .exe file called "vmware-view.exe" that is simply a shell wrapper to pass command-line arguments thru to Omnissa Horizon Client, and open the new Horizon client. Benefit being, you just place this vmware-view.exe file into "C:\Program Files\Omnissa\Omnissa Horizon Client" and you don't have to worry about the proper "horizon-client.exe" being auto-updated by Omnissa over time.

Apologies, I am not able to quickly find the Forum rules about posting source code or linking websites. Right now the .cpp is just on my desktop but I could post the code here directly, or upload it to GitHub. @Samuel Dery, is there a preference? Just trying to help others out!

(For your team, it's nice that the only hangup for the RDM "Horizon" extension seems just a naming change... the command line arguments pass just fine when using the same syntax. The different directory is a bit of a pain though.)

Hello there,

Just wanted to add that I was able to get a RemoteApp functioning as well thru RDM. The key step for me was using the "Embedded RDP File option" in Properties ("RDP File Link" also worked, the default "Configured" option was the one that wasn't working).