A VMware resource can connect a VMware server/farm in three different ways:
- Server Address: Below, we show an example of a vmware resource of this type on a Desktop presentation mode.

As soon as the connection is established, all resources available on the server (including published applications and desktops) will be displayed in the interface, and the icon corresponding to the VMware server address will disappear.
\
- VMware Configuration file: this type of connection uses the VMware Horizon View Client installed on the device.

As soon as the connection is established, it opens the VMware Horizon View Client will open, displaying all the resources available on the server.\
\
- VMware Kiosk mode: This mode allows the usage of the VMware Kiosk Mode, which must be configured on the server side (for more information, see VMware documentation). It utilizes the VMware Horizon View Client installed on the device.
¶ Resource Type and name
Select VMware and write the name of the resource.
- Autostart: When enabled, the resource starts immediately after the boot or after the ThinMan Login connection. If more than one resource has been configured with the Autostart parameter activated, all these resources will start simultaneously.
- ThinMan Smart Identity Pass-through: To be used only when using the ThinMan Login. When enabled, the resource uses the ThinMan Login credentials to log in the resource.
- Ignore SSL errors: When enabled, the connection to the resource is established despite the certificate problems. This option is typically used in a test environment.
- Hide Topbar: when this option is enabled, it hides the VMware topbar on a desktop.
- Use UPN format for username: when this option is enabled, the user field will need to be filled following the UPN login format (e.g. UserName@DNSDomainName).
Credentials Pass through & Presentation modes
Please remember that you can use the ThinMan Smart Identity Pass-through functionality to directly access the resource. Note that ThinMan Login is not available in the Classical Windows presentation mode.
It is possible to set a specific action when a resource is closed.
- No Action: It is the default value. When selected and the resource is closed the device does not execute any other actions.
- Logout: When selected and the resource is closed the device executes a logout operation. This option is useful when using the ThinMan Login feature. Without ThinMan Login, this option closes all the opened resources.
- Reboot: If selected, when a resource is closed the device is rebooted.
- Poweroff: If selected, when a resource is closed the device is powered off.
Select Server Address as connection mode. Then, provide the URL of the farm that can be reached using a browser.

-
Domain: Write the domain field in order not to be editable by the end user in the login phase. When left empty, the user can insert it later on the credentials form.
-
Hide domain in login form: It allows hiding the domain field in the login form. If the Domain field is left blank then the user can log in using the UPN or DLN login name formats (e.g. UserName@DNSDomainName or DOMAIN\UserName). If the Domain field is precompiled, the user cannot change it using the previous formats and could only insert its username.
-
Remote Applications Options

- Autostart resource if unique": when enabled, and there is only one desktop/app available to the user, it will be launched automatically right after the connection to the farm has been established.
- Autostart resource name: write the name of the published desktop/app to start automatically right after the connection to the farm has been established.
-
Resources filter by type and Resources filter by name

Use the Filter Configuration to define some rules that will filter the desktops and the applications that are shown to the user. Remember that resources can be automatically distributed to different users using the ThinMan Login and User Policies whenever you use the locked-down presentation modes: Desktop, Multi-Apps, Single-App and Quick-App.\It is possible to select only Desktops, only Applications or both of them.

Click on Add filter to apply filters to the resources based on the name and type of operation. The name is evaluated case-insensitively, meaning that desktop is considered equal to Desktop.

Valid Operations are:
- ==: resources whose name is exactly the Text field.
- !=: resources whose name is different from the Text field.
- like: resources whose name contains the Text field as a substring.
- not like: resources whose name does not contain the Text field as a substring.

On the above example, the resources shown are whose name contains Desktop as substring (e.g.: desktopWin10, PersonalDesktop, StrangeDesktopForAll, etc.).
You can add multiple filters in the Resources filter by Name section. All these filters are composed using the logical union operator.
Examples:
- == Notepad + like Desktop: it will show the resource named "Notepad" and those that contain the word Desktop in the name.
- == notepad + == Word: it will show the resource named "notepad" and the resource named Word.
- not like Paint: it will show all the resources that not contains paint as part of the name.

-
Connection Server: Write the server to use when launching the VMware Horizon View Client. If specified, it cannot be changed afterwards by the user who launches the connection.
-
Protocol: three options are available: default, PCoIP, RDP. Leave default in the case the protocol is selected by the server; set RDP to force the RDP protocol to be used; set PCoIP to force the PCoIP protocol to be used. This parameter cannot be changed afterward by the user who launches the connection.
-
Desktop Name and layout

Write the desktop name to connect. If not present in the desktop pool, the connection produces an error and exits. Also, specify the desktop layout (default, fullscreen, multimonitor, windowlarge, windowsmall) for the connection window. It cannot be changed afterwards by the user who launches the connection.
-
Connect USB on startup

When enabled, it allows the virtual desktop to automatically mount USB devices already inserted into the device when the virtual desktop startups (if not enabled the mount has to be executed explicitly)
-
Connect USB on insert

When enabled, it allows the virtual desktop to automatically mount USB device at the insertion time (if not enabled the mount has to be executed explicitly)
-
Log in as domain user

If the device is joined to a domain, the connection will use the domain credentials to connect to Horizon View server.
- Username: If specified, it cannot be changed afterwards by the user who launches the connection.
- Domain Name: If specified, it cannot be changed afterwards by the user who launches the connection.
- Hide domain in login form: allows hiding the domain field in the login form. If the Domain name field is left blank, the user can log in using the UPN or DLN login name formats (e.g. UserName@DNSDomainName or DOMAIN\UserName). if the Domain name field is precompiled the user cannot change it using the previous formats and could only insert its username.
- Password: If specified, it cannot be changed afterwards by the user who launches the connection.

-
Connection Server: Write the server to use when launching the VMware Horizon View Client. If specified, it cannot be changed afterwards by the user who launches the connection.
-
Username and Password: Write the credentials of the user that has been configured on the VMware Server for the Kiosk Mode.