This guide walks through installing Hudu Radar silently, which automatically configures the Hudu Radar Service. A silent install lets IT teams deploy Radar through Remote Monitoring and Management (RMM) tools without manual intervention, including deploying separate collectors to each site of a company.
By installing Hudu Radar silently, you automatically agree to Hudu's Terms and Conditions.
Visit Radar Multi-Collector Overview and Hudu Radar GUI Install & Setup for additional information on collectors and installing Radar interactively.
Guides
Requirements
- Hudu Radar has been enabled within the Hudu instance.
- The Hudu Radar installer has been downloaded from the Hudu instance.
- Hudu 2.46.0 or later and Hudu Radar 2.1.0 or later to run more than one collector per company.
- Minimum OS: Windows 10, Windows Server 2016.
We recommend having an admin set low device requirements so that all discovered devices are sent to Hudu.
Planning your collectors
A collector is a Hudu Radar installation for one site under a company. One collector is enough when a single device can reach every network you want to scan for that company. Deploy an additional collector when the company has separate physical locations or non-routable networks that the existing collector can't reach.
When deploying through an RMM, target one device per site, ideally a secure server or management device.
Hudu Radar is licensed per collector. Each active collector counts toward the Radar licenses on your account.
Installing the application
- Upload the downloaded Hudu Radar installer to your RMM tool. Syncro is used in this example. We recommend the MSI installer when running Radar as a service.
- Create a new script.
- Add the uploaded installer to the script as a required file in a known, existing location, such as
C:\Windows\Temp. Select PowerShell or Batch as the file type, and select Run as system.
- In Hudu, open the company you want to connect and go to IPAM. Click Activate Hudu Radar. A Hudu Radar section is added to the company's left sidebar.
- Select Hudu Radar in the left sidebar. Under Step 2: Get Radar code, click View Radar Code.
- Copy the setup code. Make sure it is an authenticating setup code (Use Hudu Radar as a service checked). A non-authenticating code causes the service to exit.
Either type of setup code can be used to set up the Hudu Radar app, but the app always requires user interaction to authenticate.
- Add the following command to the script and run it on the target device:
msiexec /i C:\Windows\Temp\hudu-radar.msi /qn RADAR_CODE=[setup code] -
/i– install. -
C:\Windows\Temp\hudu-radar.msi– full path to the installer. -
/qn– quiet install. -
RADAR_CODE=– setup code from Hudu.- To scan multiple, enter as a comma-separated list – Wi-Fi, Ethernet0.
- If one or many names contain spaces, wrap the list in quotes.
To use the EXE installer instead:
"path\to\installer" /verysilentInstall parameters are the same in Hudu Radar 2.1.0 whether a company has one collector or several. A collector name isn't needed at install. The service registers itself as a collector the first time it starts.
Scanning
During a silent installation, network scanning runs solely from the Hudu Radar Windows service, which starts automatically once the install completes. Networks are created automatically, and any devices that meet the requirements are added as IP addresses and assets in Hudu, provided asset layout mapping is complete.
Adding another collector to a company
A company can have more than one collector, such as one at each site. When a company has more than one active collector, a collector picker appears in the company's Hudu Radar section, and the devices, networks, adapters, credentials, and scans shown are limited to the selected collector.
Visit Radar Multi-Collector Overview for additional information on setting up multiple collectors.
Already scanning more than one site with a single collector? Visit Migrating Existing Adapters into Collectors before updating Radar to avoid duplicate adapters.
Network maps with multiple collectors
Each collector builds its own network map from the networks and devices it discovers. In the company's IPAM → Map section, the maps from all active collectors are shown together, with each network labeled by the collector it belongs to.
Uninstalling a collector
Uninstalling Hudu Radar from a device marks that collector as inactive in Hudu. Inactive collectors no longer appear in the collector picker. If Hudu Radar is reinstalled on the same device, the collector is reactivated.
FAQ
No. When running silently, Hudu Radar always uses the admin defaults unless they are changed manually in the Hudu Radar app.
No. Credentials must be managed from the Hudu Radar app.
No. A collector only needs to be installed on a single device per site, not on every workstation. Multiple collectors per company are supported, so if a company has multiple locations or networks that can't be reached from one device, deploy one collector to each of those sites.
MSPs typically install collectors on a secure server or management device that only the MSP controls. As a best practice, if Radar is installed on a domain controller or other privileged system, end users should not have access to that device. Access should remain restricted to those who have access to your Hudu instance.
Troubleshooting
The most common cause is the Hudu Radar service not running continuously.
- Check that the service is running in the Windows Services window. If it isn't, try starting it manually. If it stops immediately, the service most likely exited with an error.
- Check the error log. Open
HuduRadarService.outin the install or service folder. The last logged error should show what is preventing the service from running.
Most configuration issues can be resolved by running the first scan from the Hudu Radar app. After the first scan, close the app and manually start the Hudu Radar service. It should then run continuously.
Every collector must run Hudu Radar 2.1.0 or later. Older versions stop scanning and syncing until updated. Redeploy the latest installer to that collector's device.