---
title: "Add Non-Domain Machines to ControlUp"
slug: "adding-non-domain-computers-to-controlup"
updated: 2025-06-17T14:06:58Z
published: 2025-06-17T14:06:58Z
canonical: "support.controlup.com/adding-non-domain-computers-to-controlup"
---

> ## 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.

# Add Non-Domain Machines to ControlUp

ControlUp requires a valid and reachable FQDN of a machine before adding it. However, you can add machines that aren't part of an Active Directory domain to your ControlUp environment. 

From versions 9.0.5 and higher, you can add non-domain joined machines to your organization with the [Real-Time Console](/v1/docs/adding-non-domain-computers-to-controlup#add-nondomain-machine-via-console-from-905). You can also locally install an agent with the [**Install-CUAgent**](/v1/docs/install-cuagent-install-an-agent) PowerShell cmdlet. 
For lower versions, you can locally install an agent with the [**Add-CUComputer**](/v1/docs/adding-non-domain-computers-to-controlup#add-nondomain-machine-via-powershell-pre-905) PowerShell cmdlet.

Before you add a non-domain joined machine, first make sure to [install a non-domain joined  ControlUp Monitor](/v1/docs/install-cumonitor).

### Add Non-Domain Machine via Console (from 9.0.5)
1. Login to the Real-Time Console and click **Add Machines** > **Add Non-Domain Machine**.
!['Add Machines' window. The 'Add Non Domain Machine' tab is highlithed.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AddNonDomainMachine.png){height="" width="350"}
2. In the **Machine DNS Name**, enter the DNS names of the non-domain joined machines you want to add as needed. Optionally, enter a description.
3. Select the machine that you want to add and click **Add**. The pane on the right shows the machines currently selected to add to ControlUp. You can:
    * Hold ctrl or shift to select multiple machines.
    * Click **Add All** to add every machine in your search result. 
!['Add Machines' window. Some machines from the left-hand side have been moved to the right-hand side to get ready to add. ](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AddNonDomainMachine2.png){height="" width="360"}
4. If your organization has multiple ControlUp sites, from the **Select Site** dropdown, select which site to add the machine(s) to.
5. Click **OK** to confirm your selection. You can now manage the non-domain joined machine(s) in your organizational tree.

### Add Non-Domain Machine via PowerShell (pre 9.0.5)
In the following section, we show you how to add a non-domain joined machine with the hostname "**NoDomainPC**" to ControlUp.
![A PowerShell console window shows the command [System.Net.DNS]::GetHostByName($env:computerName) being executed. The output displays three columns: "HostName", "Aliases", and "AddressList". Below these headers, "NoDomainPC" is listed as the HostName, an empty set {} for Aliases, and {10.160.100.125} for AddressList.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-VIPH296V.png){height="" width=""}
1. Add an A record for the non-domain joined machine on the Active Directory domain controller. Despite the FQDN being displayed, the machine does not have to be domain-joined.
![A Windows dialog box titled "NoDomainPC Properties" is displayed. It has two tabs: "Host (A)" and "Security", with "Host (A)" currently selected. Under the "Host (A)" tab, the following fields are visible:
Host (uses parent domain if left blank): with "NoDomainPC" entered in the text box. Fully qualified domain name (FQDN): with "NoDomainPC.AD2012.LOC" entered in the text box.
IP address: with "10.160.100.125" entered in the text box.
A checkbox labeled "Update associated pointer (PTR) record" is checked.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-RMUVF5GF.png){height="" width=""}

2. Login to the Real-Time Console and click **Settings** > **Agent**. Under **Agent Authentication Key**, click **Copy** to copy the Authentication Key to the clipboard. Under **Registration Key**, click **Copy** to copy the Registration Key needed for [agent outbound communication](/v1/docs/agent-outbound-communication). Ignore this key if you don't want to use this feature.
![Agent Deployment Settings window. Under 'Agents Authentication Key', the 'Copy' button is highlighted.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-7GHLKQIY.png){height="" width="550"}

3. Remote connect to the machine and download the ControlUp Agent from our [Download Center](https://www.controlup.com/products/controlup/download-center/). Run the MSI installer. 

4. During the installation, paste the Authentication Key and Registration Key from your clipboard. 
![ControlUp Agent for VDI & DaaS Setup window. The Agent authentication key and registration key fields are filled out.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-3NWBIAUR.png){height="" width="450"}

5. When the installation is complete, switch back to the Real-Time Console and add a folder by right-clicking **Add > Folder**. In our example, we want to add the non-domain joined machine to a folder named “Non Domain Computers”.
![GIF of adding a folder title 'Non Domain Computers' by right-clicking in your ControlUp organization tree and selecting the action 'Add > Folder'.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AddFolder.gif){height="" width=""}

6. Open a PowerShell session on a ControlUp Monitor machine. 
    a. Import the ControlUp.PowerShell.User module.
    ``` powershell
    $pathtomodule = (Get-ChildItem "C:\Program Files\Smart-X\ControlUpMonitor\*ControlUp.PowerShell.User.dll" -Recurse | Sort-Object LastWriteTime -Descending)[0]
    Import-Module $pathtomodule
    ```
    b. Add the machine to the new folder by running the [Add-CUComputer](https://support.controlup.com/tim-reorg/docs/controlup-powershell-commands?highlight=PowerShell#addcucomputer) cmdlet.
     ``` powershell
     Add-CUComputer -Name "NoDomainPC" -Domain "AD2012.LOC" -FolderPath "\non domain computers"
     ```
     
    :::(Info) (Tip)
    To avoid misspellings in the folder path, run the [Get-CUFolders](https://support.controlup.com/tim-reorg/docs/controlup-powershell-commands?highlight=PowerShell#getcufolders) cmdlet and copy the **Path** to the -**FolderPath** parameter.  
    ![PowerShell result from running Get-CUFolders. The 'Path' output is highlighted.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-P3ST6PCX.png){height="" width="350"}
    :::

7. You can now manage the non-domain joined machine as any other domain-joined machine in your organizational tree.
!['Machines' view in ControlUp listing a non domain-joined computer.](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/image-J59XIJGG.png){height="" width=""}