--- title: "Connect to Your Machines with GUI or MSI" slug: "connect-to-your-machines-locally" updated: 2026-06-23T08:07:16Z published: 2026-06-23T08:07:16Z canonical: "support.controlup.com/connect-to-your-machines-locally" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.controlup.com/llms.txt > Use this file to discover all available pages before exploring further. # Connect to Your Machines with GUI or MSI The following article explains how to install a ControlUp Agent manually with GUI or with MSI. For machine requirements, see [here](/v1/docs/connect-to-your-machines#machine-requirements). Depending on your organization's infrastructure and deployment preferences, ControlUp offers several flexible methods to deploy the agent across your environment: | Deployment Method | When to Use | | --- | --- | | [PowerShell Cmdlets](/v1/docs/install-cuagent-install-an-agent) | Best for automation pipelines, bulk provisioning, CI/CD workflows, and scripted golden‑image preparation. Gives full control and repeatability for large‑scale deployments. Installs agent on a machine with no need to use the Real-Time DX Console. | | [Console](/v1/docs/connect-to-your-machines#remote-agent-installation) | Best for centralized, automated deployment across domain‑joined VDI machines. To learn how to add machines remotely, watch [video](https://cuacademy.controlup.com/real-time-dx-setup-3-deploment-add-machines/). | | [MSI Installer](/v1/docs/connect-to-your-machines-locally#manual-installation-with-gui) | Best for offline, non‑domain, image‑based installs, or restricted environments using an enterprise software distribution tool (SCCM, GPO, PDQ). Manual, silent installation. | | [Microsoft Intune](/v1/docs/controlup-deployment-with-microsoft-intune#cuagent-for-vdi-daas) | Best for cloud‑managed endpoints and hybrid Azure AD‑joined devices. Leverages Intune’s Win32 app model for scalable, policy‑driven deployment, standard MSI distribution. | ## Local Agent Installation Install the ControlUp Agent locally on a machine using an MSI package if remote installation requirements can't be met in your environment. To learn more about the MSI deployment, watch our [video](https://cuacademy.controlup.com/real-time-dx-setup-3-deployment-via-msi/). ### Manual Installation with GUI 1. To download the Agent MSI package from our [Download Center](https://www.controlup.com/products/controlup/download-center/), under **ControlUp for VDI Agent** > **Current version**, click **Agent ZIP for ControlUp.Automation module**. 2. Execute the MSI package installation on the machine where the Agent is to be installed. 3. From the Real-Time Console, navigate to **Agent Settings**, and copy your **Agent's Authentication Key**. This key connects the Agent to your ControlUp environment. ![Copy button under the 'Agents Authentication Key' section.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AgentAuthKey.png) 4. A new Registration Key is required for outbound communication, enabling agents to obtain a Personal Access Token (PAT) from our security service. Ignore this key if you don't want to use this feature. ![Copy button under the 'Agent Registration Key' section.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AgentRegKey.png) To activate outbound later, manually add the key to the agent's registry under `HKLM\SOFTWARE\Smart-X\ControlUp\Agent\Communication`. **Key name**: RegistrationKey 5. Paste the authentication key you copied from the Real-Time Console during installation. ![ControlUp Agent for VDI & DaaS Setup screen with the Agent authentication key and registration key added.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-3NWBIAUR.png) 6. Finish the MSI installation process 7. If the machine is new and not yet part of your ControlUp organization tree, you must add it using one of the following methods: 1. In the console, click **Add Machines**. 2. Execute the `Add-CUComputer` cmdlet on any monitor machine. For instructions to use this cmdlet, see [here](https://support.controlup.com/docs/controlup-powershell-commands?highlight=add-cucomputer#addcucomputer). ### Command Line Installation with msiexec You can install the agent by using the command line. *Msiexec.exe* allows you to run the installation of the agent in different ways. In this section, we show you some examples of how you can install the agent: Make sure you download the agent from our [Download Center](https://www.controlup.com/products/controlup/download-center/). #### From version 9.0 and higher **Silently install the 64-bit version agent 9.1.5 + provided authentication key:** ```plaintext msiexec /i ControlUpAgent-RealTimeAgentManager-net6-x64-9.1.5.336-signed.msi /qn AUTHKEY="enter your authentication key" ``` **Silently install the 64-bit version agent 9.1.5 + provided authentication key + registration key (needed for** [**agent outbound communication**](/v1/docs/agent-outbound-communication)**):** ```plaintext msiexec /i ControlUpAgent-RealTimeAgentManager-net6-x64-9.1.5.336-signed.msi /qn AUTHKEY="enter your authentication key" RegistrationKey="enter your registration key" ``` **Silently install the 64-bit version agent 9.1.5 + provided authentication key + registration key + use certificate for agent authentication:** ```plaintext $authkey = "enter your authentication key" $registrationKey = "enter your registration key" $msiPath = "path to MSI" $arguments = @( '/i', "`"$msiPath`"",   '/qb', "AUTHKEY=$authkey", "RegistrationKey=$registrationKey", "CERTONLY=TRUE" ) Start-Process -FilePath 'msiexec.exe' -ArgumentList $arguments -Wait -NoNewWindow ``` When using **CERTONLY=TRUE**, you instruct the agent to only accept connections from the console/monitors that are configured to use the [Certificate-based agent authentication](/v1/docs/certificate-based-agent-authentication) if the relevant agent-side registry keys aren't configured. **Silently install the 64-bit version agent 9.1.5 in a** [**master image**](/v1/docs/agent-outbound-communication#configure-agent-for-master-images) **+ provided authentication key + registration key + use certificate for agent authentication:** ```plaintext msiexec /i ControlUpAgent-RealTimeAgentManager-net6-x64-9.1.5.336.msi /qb AUTHKEY="enter your authentication key" RegistrationKey="enter your registration key" CERTONLY=TRUE MASTER_IMAGE=true ``` #### Legacy: Lower than version 9.0 **Silently install the 64-bit version agent 8.8 + provided authentication key:** ```plaintext msiexec /i ControlUpAgent-net45-x64-8.8-signed.msi /qn AUTHKEY="enter your authentication key" ``` **Silently install the 64-bit version agent 8.8 + provided authentication key. No restart after installation + log output:** ```plaintext msiexec.exe /i ControlUpAgent-net45-x64-8.8-signed.msi AUTHKEY="enter your authentication key" /quiet /norestart /l*v C:\temp\agentinstallation.log ``` **Silently install the 64-bit version agent 8.8 + provided authentication key. Use a non-standard port and custom installation path:** ```plaintext msiexec.exe /i ControlUpAgent-net45-x64-8.8-signed.msi AUTHKEY="enter your authentication key" /qn PORT=40777 APPDIR="enter installation path" ``` To troubleshoot installing agents, see [here](/v1/docs/connect-to-your-machines#troubleshooting).