US English (US)
FR French
DE German
ES Spanish
IT Italian
NL Dutch
JP Japanese

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

  • Contact Us
English (US)
US English (US)
FR French
DE German
ES Spanish
IT Italian
NL Dutch
JP Japanese
  • Home
  • CyberFOX DNS Filtering
  • Roaming Clients
  • Deployment

Deploying Desktop Client via RMM tools

Written by Owen Parry

Updated at February 26th, 2026

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

  • AutoElevate Knowledgebase
    New to AutoElevate? START HERE General & Troubleshooting Managing Rules Integrations Announcements FAQ Sales & Marketing
  • Password Boss Knowledgebase
    Using Password Boss Business Administration Password Boss Partner Documents
  • CyberFOX DNS Filtering
    Getting Started Filtering Policies Company and Location Setup Roaming Clients Reporting and Logging Troubleshooting
  • Marketing Toolkit
    MSP Marketing & Education Toolkit
  • Changelogs for Autoelevate and Password Boss
  • CyberFOX Product Roadmap
  • Current Status
+ More

Table of Contents

Deploying Roaming Client or Agent via RMM Tools Download the Latest Client Location Specific Installers Deploy the Generic installer with the command line option. Deploy the Location-Specific installer with the command-line options. Deployment via PowerShell Script Deployment via Intune

Deploying Roaming Client or Agent via RMM Tools


This article provides step-by-step instructions for deploying the Cyber Fox DNS roaming client or agent using Remote Monitoring and Management (RMM) or other deployment tools. Follow these guidelines to ensure a smooth and efficient deployment process.

 

Download the Latest Client


Download the latest client from the following link:

  1. A Generic Installer that you will supply the location key via the command line: Generic Installer  
     
  2. The Specific installer that you download from the company, location, or device on the portal that should look like: dns_client_[companyidhere].exe
     

Location Specific Installers

If you are downloading the location-specific installer, ensure that the executable is downloaded per client site and do not change the name of the executable. The location key in the name will be used to assign it to the correct location without any command line requirements.

 

 

Deploy the Generic installer with the command line option.


Use the following command to deploy the client via your RMM tool of choice:

dns-latest.exe /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTART /COMPANY_ID=[company id]

Command Line Options Explained

  • /SP-: Suppresses the “Do you wish to continue?” prompt.
  • /SUPPRESSMSGBOXES: Suppresses message boxes during installation.
  • /VERYSILENT: Eliminates any need for user interaction during the installation process.
  • /NORESTART: Suppresses any need for a restart after the installation is completed.
  • /COMPANY_ID=[company id]: Supply the location company ID to the installer.

If your RMM supports variables, you can insert the company ID as a variable for wider deployments using a single deployment script. 

 

Deploy the Location-Specific installer with the command-line options.


Use the following command to deploy the client via your RMM tool of choice when using the client's location-specific installer file:

dns_client_[CompanyIDhere].exe /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTART

Command Line Options Explained

  • /SP-: Suppresses the “Do you wish to continue?” prompt.
  • /SUPPRESSMSGBOXES: Suppresses message boxes during installation.
  • /VERYSILENT: Eliminates any need for user interaction during the installation process.
  • /NORESTART: Suppresses any need for a restart after the installation is completed.

If you use the location-specific installer without any command line options during deployment, the end user will be prompted with a dialog box to continue the installation. We highly recommend installation using the above command line options to install silently. 

 

Deployment via PowerShell Script 


See PowerShell KB Article

 

Deployment via Intune


See Intune KB Article

agent deployment installation client desktop powershell

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Deploying CyberFOX DNS Via Powershell
  • Deploying CyberFOX DNS Filtering Using Group Policy (GPO)
  • Deploy CyberFOX DNS Filtering Client Using Microsoft Intune
  • Uninstalling the CyberFOX DNS Roaming Client
Request a Demo
  • Get Pricing
  • Start Trial
  • Contact
  • Support Center
  • Login
Solutions
AutoElevate
  • AutoElevate Overview
  • Remove Admin Privilege
  • Just-in-Time Admin
  • Blocker
Password Manager
  • Password Manager Overview
  • Features
DNS Filtering
  • DNS Filtering Overview
MSPs
IT Departments
  • Overview
  • State and Local Government
  • K-12 Education
  • Manufacturing
  • Higher Education
Resources
  • Resource Center
  • Group Demos
  • Events
  • The Simple 7™
Company
  • About
  • Leadership
  • Culture & Values
  • News & Press
  • Awards
  • Partnerships
  • Referral Program
  • Trust Center
CyberFox Logo

CALL US (813) 578-8200

© 2025 CYBERFOX LLC ALL RIGHTS RESERVED | Privacy Policy | Terms of Service | Sitemap


Knowledge Base Software powered by Helpjuice

//-------------------------------------------------------------------- // RESOLVE DESTINATION URL //-------------------------------------------------------------------- function resolveRedirect(path) { if (STATUS_SLUGS.includes(path)) { return "https://status.cyberfox.com"; } if (REDIRECTS.hasOwnProperty(path)) { return REDIRECTS[path]; } return null; } //-------------------------------------------------------------------- // CLICK HANDLER (Capture Phase) //-------------------------------------------------------------------- document.addEventListener( "click", function (e) { var link = e.target.closest && e.target.closest(LINK_SELECTOR); if (!link) return; // Let modified clicks behave normally (open in new tab, etc.) if (e.metaKey || e.ctrlKey || e.shiftKey || e.altKey) return; // Only left click if (e.button !== 0) return; var href = link.getAttribute("href") || link.href; if (!href || href.startsWith("#")) return; var path = normalizePath(href); var target = resolveRedirect(path); if (!target) return; // Intercept click BEFORE Helpjuice SPA/PJAX e.preventDefault(); e.stopPropagation(); if (e.stopImmediatePropagation) e.stopImmediatePropagation(); window.open(target, "_blank", "noopener"); }, true // capture ); //-------------------------------------------------------------------- // KEYBOARD ACCESSIBILITY (Enter / Space) //-------------------------------------------------------------------- document.addEventListener( "keydown", function (e) { if (e.key !== "Enter" && e.key !== " ") return; var link = document.activeElement.closest && document.activeElement.closest(LINK_SELECTOR); if (!link) return; var href = link.getAttribute("href") || link.href; if (!href || href.startsWith("#")) return; var path = normalizePath(href); var target = resolveRedirect(path); if (!target) return; e.preventDefault(); e.stopPropagation(); if (e.stopImmediatePropagation) e.stopImmediatePropagation(); window.open(target, "_blank", "noopener"); }, true ); })();
Expand