Windows Roaming Client Deployment using Connectwise Automate

Article author
Fikayo Adepoju
  • Updated

You can use Connectwise Automate to install our Roaming clients to your Windows endpoints in two simple steps:

Step 1

Run the following command to download the DNSFilter roaming client (branded and Whitelabel versions):

Whitelabel version

Invoke-WebRequest -Uri https://download.dnsfilter.com/User_Agent/Windows/DNS_Agent_Setup.msi -OutFile "C:\Windows\LTSvc\DNS_Agent_Setup.msi"

Branded version

Invoke-WebRequest -Uri https://download.dnsfilter.com/User_Agent/Windows/DNSFilter_Agent_Setup.msi -OutFile "C:\Windows\LTSvc\DNSFilter_Agent_Setup.msi"

This will download the agent into the specified LTSvc folder which Connectwise uses. This way, it can run using the local agent and doesn’t have any problems downloading or needing to create another folder.

connectwise-automate-DNSFilter-Step1.PNG

 

Step 2

Next, run the command to invoke the Windows installer to install the agent specifying your site key as shown below:

Whitelabel version

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

Branded version

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

connectwise-automate-DNSFilter-Step2.png

This will cause the agent to be pulled and run from the LTSvc folder.

In about 10-15mins or less, you should see the agent show up in your Connectwise portal.

 

One last thing, you need to remove the machines on which the client is installed from the “TCP - Port 53” monitoring groups. This is to avoid receiving false alarms from Connectwise when it’s periodically checking to see if TCP port 53 is responding.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.