> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/vmware-player-workstation-vsphere.md).

# VMware (Player, Workstation, vSphere)

Configure VMware (Player, Workstation, vSphere) entries in Remote Desktop Manager, including the application, virtual machine file, host, and credentials.

This article details the many settings and options available for ***VMware (Player, Workstation, vSphere)*** session entries in Remote Desktop Manager. The entry opens a virtual machine in VMware Player or VMware Workstation, or connects to a server with the VMware Infrastructure Client / vSphere Client.

{% hint style="info" %}
The settings available in the ***General*** tab depend on the selected ***Application***. The ***VMware Infrastructure Client / vSphere Client*** application is not supported on Linux.
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located. Click the browse button to select a folder, or click the add (<em><strong>+</strong></em>) button to create a new one.</td></tr><tr><td><strong>Display</strong></td><td>How the entry opens. This entry type only opens externally, so the display mode is locked to <em><strong>External</strong></em>. Additional lists let you choose the monitor and the virtual desktop where the window opens.</td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. <em><strong>Host configured</strong></em> uses the <em><strong>Host</strong></em> entered in the <em><strong>General</strong></em> tab. <em><strong>Linked</strong></em> uses a host entry from a vault. <em><strong>Inherited</strong></em> uses the host of a parent folder.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials do not come from the entry itself, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> of the <em><strong>General</strong></em> tab are disabled.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Application</strong></td><td><p>The VMware application used to open the entry:</p><ul><li><strong>VMware Player</strong></li><li><strong>VMware Workstation</strong></li><li><strong>VMware Infrastructure Client / vSphere Client</strong></li></ul></td></tr><tr><td><strong>Virtual machine filename</strong></td><td>The virtual machine file to open. Click the browse button to select the file. This field is available and required with <em><strong>VMware Player</strong></em> and <em><strong>VMware Workstation</strong></em>.</td></tr><tr><td><strong>Host</strong></td><td>The server to connect to. This field is required with <em><strong>VMware Infrastructure Client / vSphere Client</strong></em>. It is available with that application when the <em><strong>Host</strong></em> of the entry is set to <em><strong>Host configured</strong></em>.</td></tr><tr><td><strong>Full screen</strong></td><td>Opens the virtual machine in full screen. This option is available with <em><strong>VMware Workstation</strong></em>.</td></tr><tr><td><strong>Use Windows credentials</strong></td><td>Signs in to the server with the Windows credentials of the current user instead of the <em><strong>Username</strong></em> and <em><strong>Password</strong></em>. This option is available with <em><strong>VMware Infrastructure Client / vSphere Client</strong></em>.</td></tr><tr><td><strong>Username</strong></td><td>The username used to sign in to the server. This field is available with <em><strong>VMware Infrastructure Client / vSphere Client</strong></em> when <em><strong>Use Windows credentials</strong></em> is cleared and the credentials come from the entry itself.</td></tr><tr><td><strong>Password</strong></td><td>The password used to sign in to the server. This field is available under the same conditions as <em><strong>Username</strong></em>.</td></tr><tr><td><strong>Other parameters</strong></td><td>Additional command-line parameters passed to the VMware Infrastructure Client / vSphere Client. This field is available with <em><strong>VMware Infrastructure Client / vSphere Client</strong></em>.</td></tr><tr><td><strong>API mode</strong></td><td><p>The API mode used with the server. This setting is available with <em><strong>VMware Infrastructure Client / vSphere Client</strong></em>:</p><ul><li><strong>Default</strong></li><li><strong>Experimental</strong></li><li><strong>Legacy</strong></li></ul></td></tr><tr><td><strong>Ignore certificate errors</strong></td><td>Ignores certificate errors when connecting to the server. This option is shown with <em><strong>VMware Infrastructure Client / vSphere Client</strong></em>.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/vmware-player-workstation-vsphere.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
