-
SnapOS
-
-
- Articles coming soon
-
-
-
- Citrix HDX + USB Headset (Call-Center Baseline)
- OS/Firmware Update & Rollback
- Power Management and Session State
- Wi-Fi Roaming & Link Change Mid-Session
- Kiosk / Assigned-Access Auto-Launch
- Barcode Scanner (HID) with Line-of-Business App
- Printing to Local USB & Network Printers
- USB Device Management – Block Storage
- Multi-Monitor & 4K Performance
- Microsoft AVD/RDP + Teams Optimized Video
- VMware Horizon + Smart Card / CAC Login
-
-
-
-
zWAN
-
-
-
-
- Firewall & Layer 7 Application Filtering
- VPN Site-to-Site Tunnel Setup & Connectivity (z40 to Cloud vGR)
- Intrusion Prevention System (IPS) / Intrusion Detection System (IDS) Testing
- DNS Filtering
- DDoS Protection & Logging
- MAC Address Filtering & Geo-fencing
- Application Control & Protocol Blocking
- Authentication & Access Control (zID)
-
- WAN Link Failover & Load Balancing (ACI Mode)
- Dynamic Path Selection & Application-Aware Routing
- SaaS & Internet Breakout Validation
- QoS for Microsoft Teams (Datacenter vGR + Branch z40)
- Tunnel Failover (z40 ↔ vGR) — WAN00 (wired) primary, WAN03 (4G) & WAN04 (5G) backups
- IP Routing & Static Route Steering (z40 Branch)
- VLAN & Layer-2 Bridging
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- IPsec Tunnel not Establishing
- SSL-VPN Tunnel not Establishing
- Mobile Network Issues
- Management Tunnel does not Establish
- DNS not Resolving from Local Network Appliance
- DNS Resolution Issues in Tunnel Configuration
- DHCP Server not Leasing IP to LAN PC
- Debugging EC Events - Unknown Status Issue
- Trusted-MAC Geofencing Issues
- DNS Issues from DC LAN PC
- Troubleshooting LAN Connectivity to Internet via WAN, Remote Branch LAN, or Local Branch LAN
- NetBalancer gateways displaying Faulty/Inactive
- Packet Drop Issues
-
-
zGuardian
-
zAccess
-
StorTrends
Geo Fences
Quick Overview
Geo Fences in zAccess allow administrators to define physical boundaries using geographic coordinates (latitude and longitude). Devices that move outside of the defined radius from a specified location can be automatically denied access to configured applications. This feature is crucial for enforcing location-aware access policies in sensitive or regulated environments.
Create a group name with multiple endpoint devices position (latitude and longitude) or place the location.
Click ADD GEO FENCE

Once the device’s location is set, configure its radius. If the device moves outside this radius, the end user will be restricted from accessing the configured application. This means that if the end user connects from any WAN network, the administrator must configure the radius or grant access to the application accordingly.
Ensure that policies are applied through Rulesets with the appropriate gateway devices assigned.
How to Use This Feature in the UI
- Navigate to Policy Configuration > Geo Fences in the zAccess Director UI.
- Click ADD GEO FENCE.
- Provide a Group Name (e.g., “Headquarters Zone” or “Restricted Campus Area”).
- Enter the Latitude and Longitude coordinates of the target location.
- Specify the Radius (in meters) that defines the boundary around the location.
- Click Save to apply the geo fence. Ensure it is referenced in a ruleset for enforcement.
Concepts & Use Cases
- Location-Based Access Control: Allow or deny application access based on whether a device is inside a trusted geographic boundary.
- Security Enforcement: Prevent data access when devices connect from unknown or high-risk areas.
- Remote Work Governance: Ensure employees connect only from approved work zones (e.g., corporate office, approved co-working spaces).
- Compliance with Geo Restrictions: Enforce region-specific data access restrictions for regulated industries (e.g., healthcare, finance, defense).
Troubleshooting & FAQs
- Why is a device denied access even inside the geo fence?
Ensure the device’s reported location (via OS telemetry) is accurate and matches the coordinates and radius defined in the group. - Can I define multiple coordinates in one geo fence?
No. Each geo fence is based on a single coordinate pair and radius. Use multiple entries for complex coverage. - What happens if the device has no GPS data?
zAccess relies on the endpoint to report location. Devices without GPS may fall back on IP-based geolocation, which is less precise. - Can geo fences apply to wired devices?
Only if the wired device reports location via OS or agent-level configuration.