Hello,
with the latest update 8.14 the Horizon Client is renamed from VMware to Omnissa.
Changing the installation path in RDM is not working, because it is looking for a vmware-view.exe, but in the new version the executable is named horizon-client.exe now.
Hello,
Thank you for reaching out to us regarding this,
If you create a copy of your executable and rename the file to vmware-view.exe is RDM to start it as expected?
Let me know,
Best regards,
Samuel Dery
Hi Samuel,
yes that works.
Thank you.
Hello,
Thank you for your reply,
Perfect, I'm glad to hear!
Best regards,
Samuel Dery
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,
Thank you for your reply,
I will check with some of my colleagues regarding your request and get back to you,
For now, this issue should be resolved in the more recent versions of RDM if you are still encountering this problem.
Best regards,
Samuel Dery
no worries! I was not aware it was already patched, or patched in an upcoming update.