Installing and Uninstalling the Data Agent

The CloudRadial data agent is a lightweight client installed on each device to collect key information such as hardware details, software compliance, and usage statistics. This data populates the Infrastructure, Policies, and Dashboards sections within CloudRadial UCP and is used to generate infrastructure reports.

Each installer is custom-built for your company and supports Windows 7 or later, as well as Windows Server 2008 or later, on both 32-bit and 64-bit systems. After installation, the agent checks in at startup and then once per day over a standard HTTPS connection.

• Installation
• Using One Agent for All Companies
  • Silent Installation
  • RMM Scripting
  • Optional Security Key
  • Ports and FQDNs for Allow Listing
  • Automatic Removal
  • .NET Framework Required
  • Uninstall
    • Temporary uninstall (recoverable)
    • Permanent uninstall (added to the uninstalls list)
  • Changing Companies after Installation without an Uninstall
• Known Issues
  • Windows Defender and Other Malware

Installation

Partners can download the correct agent by navigating to the company from the Partner > Clients section of the feature set.

From there, they can click on the individual company and use the Download Agent button to get access to it, or use the URL to download the agent to the same effect.

Each installation overwrites any previous agent settings. Please allow up to 24 hours after installation for the endpoint or server to appear in the Infrastructure reports.

Note: For those evaluating CloudRadial, one agent is typically enough to showcase how the data flows into CloudRadial. Remember to view Infrastructure > Endpoints, Compliance > Policies, and Account > Dashboards to see how the data populates into the tenant. 

Users can self-install the correct data agent by:

1. Clicking on their name in the top-right corner of the CloudRadial application and following the link in the orange prompt window 
   
                      
    
2. Downloading the installation program highlighted on their profile page
3. Running the installation program.

Using One Agent for All Companies

You can use any agent you download for other companies by specifying the parameter /companyid on the agent install command line.

C:>DataAgent-{company-name}-version.exe /companyid=1

The companyid value is the company's CloudRadial ID value. If no companyid is specified, the default company will be the company the agent was built for. You can find the company ID in Partner > Clients > Agents tab.

Be sure you have downloaded the latest version of the agent to use this feature.

Silent Install

The data agent can also be remotely deployed. Partners will need to make sure they have the correct data agent for the company and can install it silently using the command:

C:>DataAgent-{company-name}-{version}.exe /verysilent

Note: For a completely silent installation, be sure that .NET Framework 4.6.2 or greater is already installed. The agent setup program will install this version if not installed and a .NET dialog may result from this installation.

After installation, the data agent starts as a Windows service and is set to start automatically with each computer restart.

The Optional Security Key

Before installing the Data Agent, partners can optionally enable a Security Key for added validation and protection. When enabled, this key becomes required both during installation and at every agent check-in, ensuring data is only accepted from trusted sources. Enabling a Security Key applies it to all Windows installers and Mac install scripts.

• If turned on, all existing agents must be rebuilt and redeployed to use the new key.

For full details on how the Security Key works and how to configure it, please see the dedicated article.

RMM Scripting

The data agent is easily deployed using your RMM's installation capabilities. You should install the data agent on all Windows workstations and servers where your RMM is installed. Sample scripts for RMMs and Intune are available in the CloudRadial Community at https://community.cloudradial.com.

We encourage you to share scripts and/or provide feedback on the ones provided by other partners.

Where possible, use your RMM to detect the Windows service "CloudRadial". If that service is not there, install the agent on that machine.

Ports and Fully Qualified Domain Names (FQDNs) for Allowlisting

Partners may have more locked-down security permissions and may require specific IPs and domains to whitelist to get the agents to report in correctly. The following are the specific FQDNs required to allow so that the agent may report correctly:

• [partnername].[region].cloudradial.com - ex: supermsp.us.cloudradial.com
• *.services-us.cloudradial.com
• *.services-us2.cloudradial.com
• *.services-us3.cloudradial.com
• *.services-us4.cloudradial.com
• *.services-us5.cloudradial.com
• *.services-us6.cloudradial.com
• *.services-us7.cloudradial.com
• *.services-us8.cloudradial.com
• services-us.cloudradial.com
• services.cloudradial.com
• *.services-au.cloudradial.com
• services-au.cloudradial.com
• services-ca.cloudradial.com
• *.services-ca.cloudradial.com
• services-uk.cloudradial.com
• *.services-uk.cloudradial.com
• services-uk2.cloudradial.com

• *.services-uk2.cloudradial.com

   

• https://eastus-8.in.applicationinsights.azure.com

   

• https://eastus.livediagnostics.monitor.azure.com

As far as ports, the agent only uses Port 443 for SSL traffic. 

Automatic Removal

 CloudRadial's endpoint agent is designed to remove itself automatically when it can no longer be matched to a valid, active account. This keeps orphaned agents from lingering on devices that no longer belong to a managed company or partner.

Every time the agent “checks in,” CloudRadial tries to trace it back to a live account: partner → company → device. If any link in that chain is missing, the agent is told to uninstall. Depending on why the match failed, that uninstall is either temporary (recoverable) or permanent (the device is added to the uninstalls list).

You can also set workstations that don't check in on a regular basis to automatically remove themselves from the Infrastructure reporting. This option is under Partner > Clients > Agents > Settings.

.NET Framework Required

.NET Framework 4.6.2 or greater is required for the agent to operate. Most PCs have .NET installed and updated by the operating system, but some servers may not have the latest version installed. If you are automating the deployment of the agent through a RMM script, test for and install .NET as required. You can download the latest version here:

https://www.microsoft.com/net/download/dotnet-framework-runtime

Please note: Installation of the agent on older Windows servers or on workstations without .NET Framework 4.6.2 or later may force a restart.

Uninstall

To uninstall the agent silently, use the commands listed below. To ensure a successful uninstallation, you'll need to specify the directory to uninstall from.

1. Open the Command Prompt
2. Enter cd C:\Program Files (x86)\CloudRadial Agent
3. Enter unins000.exe /norestart /verysilent

Changing Companies after Installation without an Uninstall

To change the assigned Company of the Data Agent after installation without uninstalling and reinstalling, follow the steps below:

1. Open Registry Editor as an Administrator.
2. Navigate to the following Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Azurative\CloudRadial\Agent
3. Edit the REG_DWORD labeled "Id" with the new Company ID and close the Registry Editor
4. Open Services as an Administrator, and restart the service labeled "CloudRadial"

After the service restarts or the next time the machine is restarted, the Data Agent will check in to the new Company in CloudRadial. 

Note: If the service fails to restart, you may need to reboot the machine. You may also need to manually remove the Endpoint from the old Company, by opening the Endpoint in Infrastructure > Endpoints and then clicking the red trash can icon (see screenshot below).

Temporary uninstall (recoverable)

In these cases the agent is told to uninstall on that check-in, but no lasting record is created. If the underlying condition is corrected, the agent is allowed to stay the next time it checks in.

A temporary uninstall happens when:

• The agent hasn't been fully associated with a company yet. The check-in arrives without a valid company identifier, so there is nothing to match it to.
• The partner account can't be located at check-in time. The partner lookup returns no result for this agent.

What to do: Confirm the device is properly deployed and associated with the correct company, and that the partner account is active. Once the association is in place, the agent can be reinstalled / re-register and will be accepted on its next check-in.

Permanent uninstall (added to the uninstalls list)

In these cases the device is written to CloudRadial's uninstalls list. From then on, every check-in from that device is matched against the list (by device name, or by serial number + manufacturer) and answered with an uninstall command. Because the record persists, the agent will not come back on its own — even if it is reinstalled — until the record is cleared.

A device is added to the uninstalls list when:

• The partner's database no longer exists. The agent references a partner environment that has been removed, so there is nowhere to route the check-in.
• The company or partner record can't be found. The agent connects to the tenant, but the company it claims to belong to (or that company's partner) no longer exists.
• The partner has been marked for deletion. The partner account is flagged for removal, so all of its agents are directed to uninstall.

In short: a permanent uninstall means the account the agent belonged to has been deleted or dismantled, not just misconfigured.

What to do: This is usually the expected outcome after offboarding a company or partner. If a device was added to the uninstalls list by mistake (for example, a company was deleted and later needed to be restored), contact CloudRadial Support — the uninstalls list is maintained internally and the record needs to be cleared on our side before the agent can be re-deployed to that device.

• Not every check-in problem causes an uninstall. If a partner is simply on hold, if a device's security key doesn't match, or if the specific endpoint isn't recognized, the agent is left in place and simply skipped for that check-in.
• Once a device is on the uninstalls list, the uninstall command is delivered on the next check-in and CloudRadial records that it was sent, so the action is not repeated indefinitely.
  Known Issues

Windows Defender and Other Malware Protections

Since the agent runs with full administrative rights, accesses disk drives, and reads registry and other system information, it may be flagged as malware. Depending on the protections you have installed, be sure that the following program file is allowlisted:

c:\Program Files (x86)\CloudRadial Agent\CloudRadial.Agent.exe

If you are using Intune, you must create a Windows Configuration Profile policy for Endpoint Protection - Windows Defender Exploit Guard - Attack Surface Reduction and exclude the above file from those protections.