> For the complete documentation index, see [llms.txt](https://docs.faronics.com/faronicsdeploy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.faronics.com/faronicsdeploy/ticketing/ticket-actions/remote-access-a-computer-via-a-ticket.md).

# Remote Access a Computer via a Ticket

When a Ticket is open and in the Ticket grid, it is possible to Remote Access the computer. This can be done by selecting the ticket and accessing the machine via the Action Toolbar.

### Remote Access Computer Using the Action Toolbar

![](/files/2OV5sDlrWXRCg5F2Pusq)

1\. Select the **Tickets View** tab on the top menu bar.

2\. Select a Ticket from the list in the grid.

3\. Click the red **REMOTE** button on the **ACTION TOOLBAR**.

4\. Select the **VIEW** Screen button from the drop-down menu.

5\. The screen will now be displayed; click the **OPTIONS** button to configure the view.

![](/files/w9Eb4miY59zJTPNsQG3T)

6\. Select which monitor to view (if there is more than one monitor connected to the computer), options are monitor **1**, monitor **2** or **All** monitors.

7\. The screen can be refreshed at the specified interval; the default setting is 5 seconds (this can be changed to 10, 20, 30, 40, 50, or 60 seconds).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.faronics.com/faronicsdeploy/ticketing/ticket-actions/remote-access-a-computer-via-a-ticket.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.