When you are using virtual appliances (VAs) for Internal Network or Active Directory (AD) visibility and granularity, the behavior of the Cisco Umbrella roaming client changes. VAs act as DNS forwarders and send all public DNS requests to Umbrella and forward internal DNS requests to the network's internal DNS servers.
If a computer running the Umbrella roaming client enters a network with VAs set in DHCP's DNS settings, the Umbrella roaming client does the following:
- Disables itself. The Umbrella roaming client is running but enters a "standby" state
- The DNS servers revert to what is provided by the VAs
- Reporting in the Umbrella dashboard will show the Internal Network IP or Active Directory identity of the user or computer and not as the Umbrella roaming client hostname.
Umbrella roaming client-specific policies will not be enforced until you roam onto a network without VAs.
This state is reflected in the Deployments > Core Identities > Roaming Computers page. A roaming computer protected by a VA is green and states that it is protected by a VA.
Updated 3 years ago