Control Deployment Tool should handle VPN Network Scans and Multiple VLANs
When deploying the Control Support/Access client an organization may have multiple Vlans, the tool should be able to reach out to multiple Vlans. The other issue is that you cannot deploy to clients using VPNs.
Wow Connectwise, this is extremely short-sighted to just decline this outright.
A lot of companies are moving to an Azure stack. This means the servers a support staff may control are in Azure, while we want to deploy to on-site devices. These will always exist on two different sides of a VPN tunnel between Azure and the local site. You could give yourself routing issues by having an extended LAN over the tunnel, but if it goes down for any reason, you'll have one side offline (namely the site)
We should have the ability to push to any subnet we want. Let us do the networking. The deployment tool should point where we want it to.