> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/overview/workstation-requirements/installation-and-permissions.md).

# Installation & Permissions

## Installation requirements

Installation of RT-LAB requires **administrator permissions**.

The default installation path is `C:\OPAL-RT`.

Installation on a different drive is possible if:

* Short name (8dot3) is enabled (see [fsutil 8dot3name](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-8dot3name)).
* No consecutive spaces in the path.

## Workspace folder <a href="#workspace-folder" id="workspace-folder"></a>

* Must be a **local folder** with full write access.
* Online folders (SharePoint, OneDrive) are **not supported**.

## Required accessible ports

Firewall settings must allow the processes in the table below to access the ports they require.

| Process Name                     | Usage                                               | Ports                                     |
| -------------------------------- | --------------------------------------------------- | ----------------------------------------- |
| **OpalDLoader**                  | Starts simulation on Host PC                        | 1987                                      |
| **MetaController**               | Manages Controller processes                        | 2002                                      |
| **OpTargetD:TCP**                | Broadcasts target status to RT-LAB                  | 2525                                      |
| **RT-LAB**                       | Graphical user interface                            | 33673, 47386–57626\*                      |
| **Controller**                   | Manages simulation                                  | <p>25250–25349\*;</p><p>47386–57626\*</p> |
| **Sshd:rtserver**                | Handles SSH communication                           | 51964–51969\*                             |
| **opald.sh / OpalD**             | Starts simulation on OPAL-RT target                 | 58060                                     |
| **Opal One Database**            | PostgreSQL database service                         | 60770                                     |
| **Opal One App Server**          | Unicon processes manager                            | 60780                                     |
| **Unicon**                       | Resource manager for OPAL-RT applications           | 49152–65535\*                             |
| **Maestro (TCP/IP)**             | Resource management server (shared socket)          | 60781                                     |
| **Maestro (gRPC)**               | Resource management server (gRPC)                   | 60782                                     |
| **Maestro (gRPC proxy)**         | Resource management server (gRPC proxy)             | 60783                                     |
| **Opal-services-handler**        | Launches Opal One Database, Maestro, and App Server | None                                      |
| **Unified Database**             | Schematic Editor database                           | 60777                                     |
| **Unified Database HTTP server** | Schematic Editor back-End                           | 60778                                     |
| **Schematic Editor**             | Electron App                                        | 61823                                     |
| **Schematic Editor**             | .NET Servers                                        | 61822, 65011                              |
| **Schematic Editor**             | Node Server                                         | 65012                                     |

{% hint style="info" %}
\*RT-LAB selects the first available port in a range if the default is occupied. Firewall exceptions must be configured accordingly.
{% endhint %}

<details>

<summary>MinGW Compiler (Workstation as Target Node)</summary>

To use the workstation as a target node, RT-LAB requires the free, open-source **MinGW compiler**.

* The compatible MinGW version is installed automatically during RT-LAB setup.
* If the installation fails, it can be started manually using:\
  `<Installation_directory>\<RT-LAB_Version>\mingw\mingw_download.bat`
* RT-LAB enforces the use of a specific, verified version of MinGW to ensure compatibility.

</details>


---

# 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://www.opal-rt.com/docs/rt-lab/overview/workstation-requirements/installation-and-permissions.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.
