> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/cloud/infrastructure-as-a-service/vcloud-director-legacy/virtual-machines-and-vapps/accessing-the-vm-console.md).

# Accessing the VM console

The vCloud Director interface offers two ways to connect to the console of the VM to manage it without requiring a direct network connection to the VM itself.

The two ways to connect are:

* Web Console, this launches a HTML5 console session to the VM
* Remote Console, this launches the 'VMware Remote Console' which requires additional software to be installed to use

To access one of the two consoles follow the steps below:

**Step 1.** Login to the vCloud Director portal

<figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2F5Bhu5wOpXtrpzJswSzQe%2Ffirefox_J5TBq9TLbs.png?alt=media&amp;token=2a9d4836-e6ce-4ae6-9e30-e1fb06950dd7" alt=""><figcaption></figcaption></figure>

**Step 2.** Select the Virtual Datacenter that has the VM you want to access the console of

<figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2FaZmQHI5MYs1hGu31wKLf%2FiZOQotL0cP.png?alt=media&amp;token=d2e3ed73-a526-4993-ba7b-f495117236b8" alt=""><figcaption></figcaption></figure>

**Step 3.** The portal should show the default view of all the Virtual Machines in the Virtual Datacenter, find the VM you want to access and click the 'Actions' button

<figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2FOVIyoDmEXeGNnTC3J0ZQ%2FvD2iV7atmo.png?alt=media&amp;token=5bf34a76-02ad-46a0-adc1-a88e73268659" alt=""><figcaption></figcaption></figure>

**Step 4.** From the dropdown menu go to 'VM Console' and then select one of the two methods to open the VM console.

<figure><img src="https://3953723498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LYYiX2aEcPAPdzrvDc4%2Fuploads%2F7rPGzROFctmWkXEyypLm%2FLiHg2UVfk0.png?alt=media&amp;token=72f70e4f-8924-4b6c-848a-4243b8a9670f" alt=""><figcaption></figcaption></figure>


---

# 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://kb.hostednetwork.com.au/support/services/cloud/infrastructure-as-a-service/vcloud-director-legacy/virtual-machines-and-vapps/accessing-the-vm-console.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.