> ## Documentation Index
> Fetch the complete documentation index at: https://docs.visualradioassist.live/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the names from the glossary at https://docs.visualradioassist.live/glossary: Audio Manager (two words), command (never commando), on air and off air (never live) for programs and studios, and server apps for the VRA apps installed in the studio.
> Say which app an answer applies to, like VRA Cloud, the Core or the Output Player, and the version when the page names one.
> Only give settings, values and steps that are in these docs. Never invent one. If the docs don't cover it, say so.
> When the docs don't answer the question, send the user to Visual Radio Assist support at https://cloud.visualradioassist.live/support.

# Install the Machine Agent

> Install the Machine Agent on a studio computer, or move a computer that runs the previous Core. The Machine Agent installs your VRA apps and keeps them running.

The Machine Agent is the one app you install on a studio computer. It installs the Core and the other server apps the studio needs, starts them, and keeps them up to date. A computer that runs the previous Core moves to the Machine Agent by itself, with its studio, settings and connection kept.

New to the new Core? See [What changed in the new Core](https://docs.visualradioassist.live/set-up/whats-new-in-the-core.md).

## How the Machine Agent sets up a studio computer

The Machine Agent works from what the Cloud knows about the studio:

1. The Machine Agent installs and starts the Core.
2. The Core connects to the Cloud and tells the Machine Agent which apps run on this computer.
3. The Machine Agent installs each app that is missing, like the Audio Manager or the Output Player, and starts it. An app that is already installed is reused.
4. The Machine Agent keeps every app running and up to date. An app that crashes restarts by itself, after 2 seconds at first and up to 30 seconds after repeated crashes.

After 10 crashes in 10 minutes the Machine Agent stops restarting that app, until someone restarts the app or its configuration changes.

## Install the Machine Agent on a new studio computer

A new studio computer needs only the Machine Agent. The studio onboarding in the Cloud walks you through it in 3 steps: **Download Machine Agent**, **Connect Machine Agent** and **Apps**.

**1. Download the Machine Agent**

Open the studio onboarding in the Cloud and select **Download Machine Agent**. The download carries a connect code for this studio in its file name, like `MachineAgent-setup connect-123456`. Keep the file name as it is. The code is valid for 24 hours.

**2. Run the installer**

Run the downloaded installer on the studio computer. It needs no administrator rights and starts the Machine Agent when it is done. The Machine Agent installs the Core, and the Core connects to the studio with the code from the download.

**3. Paste the connect code when the Core asks for it**

A Core that could not use the code from the download, for example because the code is older than 24 hours, shows a setup window. Select **Continue** in the onboarding, copy the connect code from the **Connect Machine Agent** step and paste it on the studio computer.

**4. Choose the apps for the studio**

In the **Apps** step, select the apps the studio uses: **Media Server**, **Output Player**, **Audio Manager** and **Camera Assist**. Then select **Install apps**.

**5. Watch the apps install**

The onboarding lists each app with the status **Installing** until the Machine Agent has installed and started it. Select **Open studio** when the apps are listed.

> [!NOTE]
>
> A studio runs one Core at a time. When the studio already has a Core, the onboarding shows **This studio already has a Core on** with the name of that computer, and asks you to confirm before it downloads the Machine Agent or shows a connect code.

## Move a computer that runs the previous Core

A studio computer that runs the previous Core moves to the Machine Agent without anyone at the computer. The previous Core is the app called **Server Core** in the Windows app list. The new Core is version 4.8.0.

1. The previous Core updates itself to its last version. With automatic updates on, that happens in the night after the release of the new Core. Without automatic updates, it happens when you update the Core to 4.8.0 from the Cloud with the [manual update process](https://docs.visualradioassist.live/advanced-installation/manual-update-process.md).
2. 60 seconds after it starts, the previous Core downloads the latest Machine Agent to the desktop of the computer, as `MachineAgent-<version>-setup.exe`, and installs it.
3. The Machine Agent downloads the new Core while the previous Core keeps running.
4. Once the new Core is downloaded, the previous Core removes itself from the Windows startup and closes.
5. The Machine Agent starts the new Core. The new Core keeps the studio, the settings and the connection of the previous Core, so you don't enter a connect code.
6. Once the new Core runs, the Machine Agent uninstalls the previous Core and the previous Audio Manager, and installs the new Audio Manager.

During the move only the Core restarts, for about 30 seconds. Output Players keep running. Audio triggers pause while the new Audio Manager starts. The previous Core and the new Core never run next to each other.

> [!NOTE]
>
> The new Audio Manager needs the Microsoft .NET runtime. A computer without it shows one Windows administrator prompt to install it. Until someone accepts the prompt, the Audio Manager waits. The Machine Agent asks again 60 minutes after a declined prompt.

## What happens when the new Core doesn't start

The Machine Agent gives the new Core 5 minutes to connect to its studio. When it does not, the Machine Agent stops it and starts the previous Core again, so the studio keeps working. The previous Core tries the move again 24 hours later, at most 3 times in total. Contact VRA support when a computer stays on the previous Core.

## The previous Core is supported until 21 December 2026

VRA supports the previous Core and the previous Audio Manager until 21 December 2026. Move every studio computer to the Machine Agent before that date. The notice is on [status.visualradio.cloud](https://status.visualradio.cloud).

## Install the Machine Agent by hand on a computer that runs the previous Core

You can also start the move yourself: download the Machine Agent from the **App Download Center** in the Cloud and run the installer on the computer that runs the previous Core. The Machine Agent finds the previous Core and moves the computer in the same way. It downloads the new Core first, then closes the previous Core when it has not closed by itself within 3 minutes. You don't enter a connect code.

## Check that the computer moved to the Machine Agent

A computer that moved shows the Machine Agent icon in the Windows notification area, and **Server Core** is no longer in the Windows app list. In the Cloud, open **Settings → Studio → Overview** to see which version each app of the studio runs. A studio that moved shows the Core on version 4.8.0 or later.

The installer on the desktop is no longer needed after the move. You can delete it.

## Add a second computer to a studio with the Machine Agent

A second computer in the studio, like one that runs only an Output Player or the Audio Manager, also gets the Machine Agent. It takes its app list from the studio's Core.

1. Make sure the studio's Core runs on the Core computer. A clean computer that finds no Core on the network within 30 seconds becomes the Core computer itself.
2. Install the Machine Agent on the second computer.
3. Open the Machine Agent menu in the notification area and choose **Install apps** once, to pick the apps for that computer.

After that the Machine Agent keeps those apps running on the second computer.

## Run several studios on one computer with the Machine Agent

One computer can run several studios, with one Core for each studio. This replaces starting Cores as master and slave in the previous Core. A computer that ran several studios with the previous Core keeps them: the Machine Agent imports the existing setup.

A studio has one Core. A second Core that connects to the same studio is refused and stops.

## Limitations

The previous Core moves a computer by itself only on Windows.

The Machine Agent does not support a studio computer without an internet connection.

The Machine Agent puts the previous Core back only when the move fails. A regular update of the new Core does not roll back by itself.

The Machine Agent does not replace the classic Output Player. It keeps running as before.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.