Overview

Manual Provisioning allows administrators to register a zTC device to zMan Director by manually entering the required zDM server and provisioning information on the thin client.

This workflow is useful when automatic discovery methods such as DHCP, DNS, or mDNS are not available or when the zTC device is outside the local deployment network.

---

When to Use Manual Provisioning

Manual Provisioning may be used when:

• DHCP scope discovery is not configured
• DNS scope discovery is not configured
• mDNS discovery is not available
• The zTC device is on a public or home network
• The device cannot automatically discover the zDM server

---

Required Information

To manually provision a zTC device, the following information is required:

• Server IP or FQDN
• Provision Key / Enrollment Key

The server value should point to the zDM server IP address or FQDN that the zTC device can reach.

---

Manual Provisioning Workflow

The typical manual provisioning workflow is:

1. Confirm that zMan Director is installed and available.
2. Confirm that zDM is installed, registered, and onboarded.
3. Obtain the required provisioning information from zMan Director.
4. On the zTC device, open the provisioning configuration area.
5. Enter the zDM server IP address or FQDN.
6. Enter the Provision Key / Enrollment Key.
7. Apply the configuration from the zTC device.

After the information is applied, the zTC device attempts to connect to zDM and register with zMan Director.

---

Provisioning Result

Once manual provisioning is completed successfully, the zTC device is registered through zDM and becomes available in zMan Director for management.

After registration, administrators can manage the device through zMan workflows such as:

• Device information
• Settings
• Profiles
• Firmware updates
• Certificate deployment
• Power operations

---

Notes

• zDM must be reachable from the zTC device.
• Manual Provisioning requires a valid Provision Key / Enrollment Key.
• If the Provision Key expires or is incorrect, provisioning may fail.
• Manual Provisioning behavior may vary depending on the configured approval policy.
• Network connectivity between the zTC device and zDM should be verified before troubleshooting further.