Skip to main content
Print

Auto Provisioning

Overview

Auto Provisioning allows zTC devices to automatically discover and connect to zMan Director through zDM without requiring manual entry on the thin client.

This workflow is useful for larger deployments where administrators want devices to register automatically during boot or network connection.


How Auto Provisioning Works

In an auto provisioning workflow, zMan or zDM discovery details are made available through the network.

When a zTC device starts, it can use the configured discovery method to locate the correct management service and begin the provisioning process.

Auto provisioning may use:

  • DHCP scope configuration
  • DNS scope configuration
  • mDNS discovery

At least one discovery method must be enabled for auto provisioning to work.


DHCP Scope Based Provisioning

With DHCP scope based provisioning, management server details are configured in the DHCP environment.

When the zTC device boots and receives network configuration, it can also receive the information needed to begin the provisioning process.


DNS Scope Based Provisioning

DNS scope based provisioning allows the zTC device to discover the management service through DNS.

If multiple discovery methods are enabled, DNS has the highest priority.


mDNS Discovery

mDNS discovery allows zTC devices on the same local network to discover the zDM server without requiring a centralized DNS server.

For mDNS discovery, the zTC device and zDM server should be on the same local network, and the discovery method should be set to Auto.


Provisioning Behavior

Once the zTC device discovers the management service, it attempts to connect and begin registration through the assigned zDM server.

Depending on the provisioning policy, the device may be handled through:

  • Auto Approval
  • Manual Approval
  • MAC Based Approval

Notes

  • At least one discovery method must be enabled: mDNS, DHCP, or DNS.
  • If mDNS, DHCP, and DNS are all enabled, DNS scope takes priority.
  • zDM must be installed, registered, and available before zTC devices can be provisioned.
  • Auto provisioning behavior may vary depending on network configuration and deployment model.
Table of Contents