Overview

The Schedule feature in zMan Director allows administrators to configure and manage scheduled operations for managed zTC devices.

Scheduling functionality is commonly used for automated device operations, firmware activities, and power management tasks across managed thin client deployments.

---

Scheduled Operations

Depending on deployment configuration and enabled features, scheduled operations may include:

• Power scheduling
• Firmware update scheduling
• Reboot scheduling
• Shutdown scheduling
• Maintenance operations

Scheduling helps administrators automate operational tasks across multiple devices and locations.

---

Power Schedule

Power scheduling allows administrators to define operational schedules for managed zTC devices.

This may include:

• Scheduled shutdown
• Scheduled reboot
• Scheduled suspend operations
• Device availability windows

Power scheduling policies can help reduce power consumption and standardize operational hours.

---

Firmware Update Scheduling

Firmware updates may be scheduled to deploy during maintenance windows or off-hours.

This helps minimize operational disruption during firmware rollout activities.

Administrators can monitor firmware deployment progress through zMan Director task and event monitoring features.

---

Schedule Management

Scheduled operations may be configured at the device or profile level depending on deployment requirements.

Administrators should verify:

• Device connectivity
• Assigned zDM availability
• Firmware availability
• Maintenance window timing

before applying scheduled operations.

---

Monitoring Scheduled Tasks

Scheduled activities may generate operational events and task records within zMan Director.

Administrators can monitor scheduled operation status through:

• Tasks
• Event logs
• Device status monitoring

---

Notes

• Scheduled operations depend on device connectivity and zDM communication availability.
• Some scheduled operations may require the device to remain powered on and connected.
• Firmware scheduling behavior may vary depending on deployment configuration and firmware availability.