Updated Version 1.0:

I have released a version 1.0 of the AutoConnection Utility with the following updates / fixes:

Updates:

• Disable Shade
  • Ability to enable / disable the “shade” for View Sessions by checking the “Disable Shade” option. This is the menu bar (shade) at the top of the Horizon Client.   This prevents the user from resizing or exiting out of the desktop back to the client desktop.  This option is only available for fullscreen or multimonitor desktop layouts.  This option will be disabled for any other choice.

• Full 64-bit View Client Support
  • Support for View 3.x clients both 32 and 64 bit
• Quit Application When Session Ends
  • Ability to quit the View AutoConnection Utility automatically when the View Desktop Session ends.  This can be useful for for thin clients so the session will automatically log off.
• Use Custom Command String
  • Will allow the user to specify a custom command string after the vmware-view.exe executable.  By clicking the “Refresh” button, the current command string will be built which can then be modified.  When this option is enabled, the application will execute the custom command string specified in the text box.
• Hide View Client After Launch
  • This is a new feature, only supported in 3.1 and later clients.   It will hide the View Client and application selector window after launching a remote session.   This option will not be enabled for clients earlier than 3.1.
• Prevent more than one copy of the app from running
  • The application now checks to see if another copy of the AutoConnection Utility is running and it will prevent the application from launching if it detects another copy running.
    

• Fixes:

• If a pool had a space in the name, it would not launch and user would get an entitlement error.  oops.
• Fixed threading issue so the app can launch several desktops without reloading
• Fixed issue with 64-bit View Clients

Everything else is the same as far as configuration and operation as detailed below.

The new version can be downloaded here:  http://goo.gl/n4HrJ8

---

Overview:

I had a few customers recently who are looking to repurpose old Windows based systems as thin clients for connecting to VMware View virtual desktops.   They asked if there was a way to directly connect into the users virtual desktop on system startup.   There are certainly ways to do it via command line or URI, but I wanted to come up with a easy, consistent way to do it.    I decided to write an app in .NET that is essentially a wrapper for the View Client.  It creates the command line variables based on what the user configures in the GUI and automatically connects to the specified desktop or application pool.  All of the user configured information is stored in the registry under the current user hive.

The application silently and automatically connects into either a desktop or application pool each time a user logs in by placing it in the startup folder.

Let’s take a look at how to use the application.

Prerequisites:

• Windows OS
• .NET Framework 4.0
• VMware View Client Installed (32 or 64 bit)

The application is delivered as a single .exe written in Visual Basic .NET 2013.   The application is called View_AutoConnect.exe.   The application requires the VMware View Client be installed to function.  If the client is not detected, the user will receive the following message:

The URL to download the latest VMware View Client is provided in the error message.   Once they have the client installed they will be able to configure the application.

The first time you launch the application you will need to specify the connection configuration data.  The data is saved to the registry in the current user hive and is dynamically saved as it is entered.

Configuration:

Mandatory Settings:

• Select either a Desktop Pool or Application Pool (View 6.x and Later Only) type
  • Traditional Virtual Desktop
  • Seamless Published Application (View 6.x and later)
• Enter the Name of the Desktop or Application Pool
• Select the Protocol Type
  • PCOIP
  • RDP
• Enter the IP or Name of the View Connection Server
• Select to either log in as the current user or enter credentials
• Select the desktop layout type
  • Full Screen
  • Multi Monitor
  • Large Window
  • Small Window

Optional Settings:

• Connect USB devices into the desktop session automatically on desktop startup
• Connect newly inserted USB devices automatically into the desktop session
• Launch the View Session Silently
  • NOTE: This suppresses all errors from the View Client directly, but the application will capture any exit codes and present them in a message box (see below)

Testing the Connection

Once you have configured all of the required fields you can test the connection by clicking the “Test Connection Button”

If any of the mandatory fields are not filled out, you will receive the following error message – this message will appear any time the app is attempting to make a connection if any data is missing.

Once this information is corrected you can test the connection to the specified pool.

NOTE:  If the connection server is not a trusted connection and the certificate checking mode is set to warn or never connect to an untrusted server and you are running in silent mode you will get the following error:

The certificate checking mode is set either on the View Client directly or through Group Policy.

Running the Application

Once you have tested your connection, you are ready to enable AutoConnection.  You enable AutoConnection by checking the “Enable AutoConnection” box.   A common use case would be to place the .exe in the Windows startup folder so that every time a user logs in it will automatically connect to the Virtual Desktop.

This will run the application with the GUI hidden and will automatically connect to the specified pool.   The application will minimize to the system tray and a balloon will indicate the connection process is occurring.

At this time the View Session will be connected based on the user specified information.

If there are any errors encountered while running silently, the application will capture any exit codes from the View Client and present them to the user as shown below:

Updating the Application

If you need to make changes to the application when it is running in AutoConnect mode you need to find the tray icon and either right-click it and choose “Update Settings” or Double-Click it.

Tray Icon:

This will bring the form back up so changes can be made.

Exiting the Application 

The close box on the form minimizes the application to the system tray and does not close it.  It will continue to run in the system tray until it is manually ended.   To end the application either choose File | Exit from the menu bar or Exit by right-clicking on the tray icon.  You will receive the following notice before ending the application.

Hopefully this application will be useful for some other people out there.   I would appreciate feedback on errors or suggestions for improvement.  Please add comments to this post and I will get back to you as soon as I can.

Here is the download link: http://goo.gl/n4HrJ8