VMware Horizon Community
JMcWhirter
Contributor
Contributor

Horizon View Client - Closing doesn't stop application

We have used some small PCs as thinclients for connecting to View and now Horizon View.  When we use the Horizon View Client (currently using 3.3.0) and the application is closed, the UI disappears but the software does not close.  The application can be viewed in taskmanager as still running.  The reason this is a problem is multifold.  We have the machines setup as a semi kiosk system.  They boot into windows, autologon to windows with a specified user, and run a batch file that restarts the View Client upon it being closed.  The batch file will not start the View Client when it is "closed" by the user as the UI disappears but the software continues to run.

The View Client is started with serverURL, desktopName, connectUSBOnInsert, and connectUSBOnStartup .  Our goal is to have the thinclient pc to be at view client login prompt without user interaction.  This worked until the Horizon View Client.  If a user hits cancel to the connection or a user connects to a desktop and logs off the desktop, the view UI promptly disappears and the user is presented with a blank windows screen (since the command prompt is waiting on vmware-view.exe to close).

Any tips or suggestions would be appreciated!

0 Kudos
2 Replies
CorvaxTC
Contributor
Contributor

They added a gpo to hide the client once connected.

If you download the latest adm files and load the client vdm_client.adm via gpedit.msc

go to computer configuration ­> Classix Administrative Templates > VMware View Client Configuraiton

Enable the `Deftault Value of the 'Hide Selector After Launching an item'

or

via registry under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\VMware, Inc.\VMware VDM\Client

add a string value called "HideClientAfterLaunchSession"  and set it to "true"

Hope this Works for you.


JMcWhirter
Contributor
Contributor

I have changed my shell call to cscript drive:\path\VMware-view.exe from wscript drive:\path\VMware-view.exe and added the registry entry you mentioned.  So far things are looking bright!

0 Kudos