Windows Roaming Client with Azure VMs

Article author
Chris Todd
  • Updated


In order for DNSFilter Windows Roaming Client to run as expected on Azure Virtual Machines, follow the below configuration steps. 


What Details When Where Screenshots
  1. Add a dedicated network interface with internet access on Azure VM for Win RC (Leave the pre-existing NIC for Azure/RDP access).

To make this Azure VM configuration change, it is required for the VM to be stopped.

In Azure web console or with Azure CLI scripts

Configure NICs
  1. Setup default gateway for second NIC

  2. Rename the NIC for RDP to ‘main'

  3. Set NIC priority order to prevent DNS leak

While the VM is running, but WinRC is not running (either prior to WinRC install, or after stopping the service - see Recovery Method below)

In VM’s OS settings or in Powershell


Install WinRC
  1. Install Win RC and immediately stop Win RC Windows service to prevent network connectivity break

After Win RC installation

This if you face difficultly stopping the service before RDP connectivity stops, intentionally installing with a bad key can help. If you face issues use the Recovery Method below.

In VM’s OS Services window or in Powershell


Configure WinRC
  1. Configure Win RC to ignore NIC for RDP as a VPN

    Add "main" to IgnoreVPNInterfacesNames 

After Win RC installation

In VM’s OS Registry window or in Powershell


Recovery Method

If WinRC is running and has removed RDP to the Azure VM, use Azure Serial Console to stop Win RC Windows service from command prompt.


Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Article is closed for comments.