Follow this post to install the Windows Roaming Client using ConnectWise Automate. We recommend using ConnectWise Support if you run into any issues.

The Site Secret Key from the DNSFilter dashboard is required to complete the installation.

1. Download the DNSFilter Roaming Client using the Standard or legacy Whitelabel commands below. This downloads the agent into the specified LTSvc ConnectWise folder without the need to create another folder. 

   ✍️ Replace 3.6.10 in the URL and filename with the current Roaming Client version. The current version is available in the dashboard by navigating to Deployments, selecting Roaming Clients, and selecting Install Roaming Client.

   Standard agent x64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNSFilter-Agent-Setup-x64-3.6.10.msi" -OutFile "C:\Windows\LTSvc\DNSFilter_Agent_Setup.msi" 

   Standard agent ARM64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNSFilter-Agent-Setup-arm64-3.6.10.msi" -OutFile "C:\Windows\LTSvc\DNSFilter_Agent_Setup.msi" 

   Legacy Whitelabel agent x64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNS-Agent-Setup-x64-3.6.10.msi" -OutFile "C:\Windows\LTSvc\DNS_Agent_Setup.msi" 

   Legacy Whitelabel agent ARM64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNS-Agent-Setup-arm64-3.6.10.msi" -OutFile "C:\Windows\LTSvc\DNS_Agent_Setup.msi"

2. Replace site-key with the Site Secret Key in the command below:

   Standard agent:
   msiexec /qn /i "C:\Windows\LTSvc\DNSFilter_Agent_Setup.msi" NKEY="<site-key>" 

   Legacy Whitelabel agent:
   msiexec /qn /i "C:\Windows\LTSvc\DNS_Agent_Setup.msi" NKEY="<site-key>"

3. Run the command. This pulls and runs the agent installer from the LTSvc folder. After the install finishes (about 10-15 minutes) the agent will populate in the ConnectWise portal 
4. Remove the agent devices from TCP - Port 53 monitoring groups to avoid false alarms from ConnectWise when it checks the port.

5. Optional: use unversioned installer links.

   If the deployment script should always pull the current Stable release without updating the URL, replace the versioned links in step 1 with the unversioned equivalents below. Allow up to 24 hours after a Stable release for the unversioned file to reflect the new build.

   Standard agent x64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNSFilter_Agent_Setup.msi" -OutFile "C:\Windows\LTSvc\DNSFilter_Agent_Setup.msi" 

   Standard agent ARM64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNSFilter_Agent_Setup_arm64.msi" -OutFile "C:\Windows\LTSvc\DNSFilter_Agent_Setup_arm64.msi" 

   Legacy Whitelabel agent x64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNS_Agent_Setup.msi" -OutFile "C:\Windows\LTSvc\DNS_Agent_Setup.msi" 

   Legacy Whitelabel agent ARM64:
   Invoke-WebRequest -Uri "https://downloads.dnsfilter.com/User_Agent/Windows/DNS_Agent_Setup_arm64.msi" -OutFile "C:\Windows\LTSvc\DNS_Agent_Setup_arm64.msi"

   Each unversioned installer has a matching checksum file. The checksum filename is the installer filename plus .sha256sum.asc (for example, DNSFilter_Agent_Setup.msi.sha256sum.asc). A deployment script can download the checksum file, compare the hash to the one from its last run to detect whether a new build is available, and verify the installer after downloading.