In Active Directory (AD) domain environments, all machines normally have DNS resolution in all directions of communication. You can configure the ControlUp for VDI Agent to operate as either inbound or outbound mode. An outbound Agent initiates a connection by contacting the ControlUp Monitor.
In non-AD domains, we recommend to use outbound communications. Make sure that:
Monitors use port 443 for inbound communication and are available in any firewalls (Windows or network).
Monitor FQDNs are resolvable from the machines where the Agents will run.
The following table outlines the available options to connect your organization's machines to your ControlUp for VDI virtual infrastructure, comparing workgroup (non-domain-joined) and domain-joined configurations. See the requirements and implications for each component's installation method.
Component | GUI Installation | MSI Installation | PowerShell Installation |
|---|---|---|---|
Real-Time DX Console | Download and run. | N/A | N/A |
Agent or Monitor on Domain Machines | With WMI and RPC ports open, GUI deployment from the Console is recommended for ease and simplicity. | Leverage GPOs or other domain mechanisms to deploy applications. You can also run the MSI. | N/A |
Agent on Non-Domain Machines | Agent can't be deployed via Console GUI due to missing trust between them. Recommended to add Agent to folder tree using EUC connection (Citrix, Horizon, AVD) to automatically sync them. | Preferred option, Agent DNS address must be resolvable from your monitors. | Must be version 9.0 or higher, and provide an API token. You can also add Agent to organization tree if the API token has the necessary permissions. |
Non-Domain Monitor | N/A | N/A | Must be version 9.0 or higher, and provide an API token. You can only deploy Monitor using PowerShell cmdlets. |