How can we help?
-
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
-
- 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
-
-
zTC
-
-
-
-
-
- Citrix HDX + USB Headset (Call-Center Baseline)
- VMware Horizon + Smart Card / CAC Login
- Microsoft AVD/RDP + Teams Optimized Video
- Multi-Monitor & 4K Performance
- USB Device Management - Block Storage
- Printing to Local USB & Network Printers
- Barcode Scanner (HID) with Line-of-Business App
- Kiosk / Assigned-Access Auto-Launch
- Wi-Fi Roaming & Link Change Mid-Session
- Power Management and Session State
- OS/Firmware Update & Rollback
-
-
StorTrends
-
zAccess
-
zGuardian
You are here:
Print
Onboarding & Assigning zTC Devices
0 out Of 5 Stars
| 5 Stars | 0% | |
| 4 Stars | 0% | |
| 3 Stars | 0% | |
| 2 Stars | 0% | |
| 1 Stars | 0% |
Onboarding & Assigning zTC Devices
Summary
Import or manually add zTC endpoints into zMAN, then assign them to a registered zDM Server for provisioning. Once assigned, devices appear under Active Clients for further configuration.
Prerequisites
- At least one zDM Server in **Registered zDM**
- CSV file of zTC_IDs (MAC), plus optional location, latitude, longitude
Importing Multiple zTCs
- In zMAN UI, go to **zTC Clients → Import zTC**.
- Download the sample CSV; populate each row with:
- ZTC_ID: LAN MAC address
- Location: site name (optional)
- Latitude/Longitude: geographic coordinates (optional)
- Upload the filled CSV.
- Devices without location data appear under the **Unassigned** tab.
- Successful imports list under **Unassigned** until assignment :contentReference[oaicite:8]{index=8}.
Adding a Single zTC
- Navigate to **zTC Clients → Add Thin Client**.
- Enter the device’s ZTC_ID (MAC) and optional metadata; click **Add**.
Assigning to zDM
- Under **zTC Clients → Unassigned**, select one or multiple devices.
- Click **Actions → Assign zDM Server**, then choose the target zDM entry.
- Upon successful provisioning, devices move to the **Assigned** tab :contentReference[oaicite:9]{index=9}.
Provisioning Methods
- Auto provisioning (DHCP-based):
Add DHCP Option with Management Portal URL and Access Key on your DHCP server; zTC auto-requests provisioning on boot :contentReference[oaicite:10]{index=10}. - Manual provisioning:
On the zTC, open **Management Server Configurator**, select Manual, and paste the zMAN **Provision URL** (e.g.https://<zMan-IP>/zman-tenant/) and **Provision Key** (found under **Server Configuration → API Access Key**) :contentReference[oaicite:11]{index=11}.
Post-Provisioning
- Provisioned devices appear under **zTC Clients → Registered**; from here, apply profiles, settings, firmware, and power actions.
- If a provisioned device goes offline, tasks defer until it reconnects, then resume automatically :contentReference[oaicite:12]{index=12}.
Was this article helpful?
0 out Of 5 Stars
| 5 Stars | 0% | |
| 4 Stars | 0% | |
| 3 Stars | 0% | |
| 2 Stars | 0% | |
| 1 Stars | 0% |
5
Table of Contents