Introduction

zMan Director is a centralized management server for remote management of zTC Thin Clients. It provides device information, power management, profiling, and device settings.

System Requirements

zMan Director Host

• Storage: 256GB SSD
• Memory: 16GB RAM
• CPU: 4 Cores (Minimum)
• OS: Ubuntu 22.04 LTS (Physical or Virtual Machine)

Installation

Prerequisites

Ensure the following packages are installed on Ubuntu 22.04:

    sudo apt-get install net-tools
    sudo apt-get install openssh-server
    sudo apt install p7zip-full
    

Configuration

1. Copy zManDirector-xxx.7z to the installer host using WinSCP.
2. Extract the file:

   7z x zManDirector-xxx.7z

3. Navigate to the extracted deployment/setup/ folder.
4. Edit master.yml with valid server details:

   nano deployment/setup/master.yml

   

Update Credentials

Modify default credentials in vars_main.yml:

nano deployment/setup/host-templates/vars_main.yml

zMan Deployment for Public IP

To host zMan Director on a public network, configure the external IP in master.yml.

Required Firewall Ports

Ensure these TCP ports are open:

• 443
• 7080
• 8082

Installation Steps

sudo ./pre_req.sh 
sudo ./setup.sh standalone

Access zMan UI at: https://<zMan-IP>/zman-tenant

Uninstallation

To uninstall, navigate to the deployment/setup folder and run:

sudo ./setup.sh standalone cleanup

Server Configuration

Onboarding zDM Server

Once installed, the zDM server will appear under Server Configuration → zDM Management. Click Onboard to register.

Importing zTC and Associating with zDM

• Import via CSV: Upload a CSV file containing zTC IDs and locations.
  
  
• Manual Addition: Add zTC devices individually.
  
• Assign zDM: Assign zDM to zTC devices.
  
  

Device Provisioning

• • Auto Provisioning: Configure DHCP with Management Portal Access URL.
  • Manual Provisioning: Enter the Provision URL and Access Key in the zTC UI.

Dashboard View

The dashboard provides an overview of:

• Device Status
• Firmware Versions
• Task Progress
• Profiles

• Overall View
  The overall view serves as a centralized view for collecting and presenting information related to all devices and their associated status. This view acts as a comprehensive hub where all device-related data and other pertinent status details are gathered and visually represented for convenient access and assessment./li>

• Location
  The location-based view functions as a specialized perspective that organizes and presents device-specific data and relevant status information based on their respective locations. This view serves as a focused interface where all device-related information, specific to their physical positions or designated areas, is systematically collected and prominently displayed for easy access and assessment.

• Group
  The dynamic group-based view offers a tailored perspective that dynamically organizes and presents device-specific data and pertinent status information based on their membership in specific groups or categories. This view acts as a flexible interface where all device-related information, as categorized by dynamic group assignments, is automatically collected, and presented for convenient access and real-time evaluation.

zID Configuration

zID is the identity provider for zMan Director. It enables integration and synchronization with Active Directory (AD) controllers.

Device Management

9.1 Edit Location

Modify the device location, including latitude and longitude, for better tracking.

9.2 Device Information and Settings

9.2.1 Information

Displays detailed device information such as:

• Overview
• Processor details
• Installed software
• Network configuration
• Real-time metrics (updates every 20 seconds)

9.2.2 Settings

Allows administrators to configure device-level settings such as display, audio, input, and network settings.

9.2.3 Remote Debug

Administrators can remotely troubleshoot zTC devices using:

• Syslog Configuration: Configure logging settings.
• Debug Shell: Securely connect via SSH for advanced diagnostics.

9.3 Power Options

Administrators can perform the following actions:

• Shutdown: Powers off the device; requires a manual restart.
• Reboot: Restarts the device remotely.
• Suspend: Puts the device into a low-power state (Wake-on-LAN must be enabled).
• Factory Reset: Resets the device to default settings; re-registration with zMan is required.

9.4 De-register

Removes a zTC from zMan Director. If the device comes back online, it must be manually re-registered.

10. Device Settings

10.1 Profiles

zMan supports creating profiles for various VDI protocols, which can be applied to individual or grouped zTCs:

• Citrix
• VMware
• Microsoft (with Auto-login support)

10.2 Settings

10.2.1 Display

Configure screen resolution, multi-monitor support, and display modes.

10.2.2 Audio

Adjust volume, microphone levels, and mute/unmute options.

10.2.3 Input Device

Modify mouse speed, button swapping, and keyboard configurations.

10.2.4 Power Management

Enable or disable Wake-on-LAN and Wake-on-USB features.

10.2.5 Date and Time

Set the time zone and configure synchronization with an NTP server.

10.2.6 Syslog

Configure syslog server settings to collect and store zTC logs.

10.2.7 Wi-Fi

Configure Wi-Fi SSID, security settings, and connection preferences.

10.2.8 SCEP

Enable Simple Certificate Enrollment Protocol (SCEP) for automated certificate management.

10.2.9 Proxy

Set up proxy settings to control internet access and enhance security.

10.2.10 VDI & Browser

Define preferred Virtual Desktop Infrastructure (VDI) protocol and browser settings for zTC devices.

Certificate Deployment

This section lists the certificates uploaded via the repository management system. These certificates can be applied to individual or grouped devices.

Power Schedule

Administrators can create schedules for power operations such as:

• Reboot (Immediate only)
• Shutdown
• Suspend

Scheduling options include:

• Immediate
• Run once (set date and time)
• Recurring (daily or weekly with selectable days)

Applications

Thin clients send a list of supported applications upon registration. Administrators can enable or disable applications for groups or individual devices.

Firmware Update

Firmware updates can be managed via:

• Amazon S3 Cloud
• MinIO (internal S3-based storage)

Using MinIO

1. Log in to MinIO at https://<zMan-IP>:7080/minioconsole/login.
2. Create a bucket and set the access policy to 'public.'
3. Upload the firmware image and manifest file.

Example manifest.json format:

{
  "model": "zTC3150L",
  "version": "1.2.620",
  "images": [
    {
      "from": "*",
      "to": "1.2.621",
      "path": "https://<zMan-IP>:7080/minio/ztc-fw/1.2.620.ima",
      "checksum": "317287ff3bd36a9e859a5be999ae014f"
    }
  ]
}

Adding Firmware to zMan MSP Admin

Copy the manifest file URL from MinIO or Amazon S3 and add it under the Firmware menu in the zMan MSP Admin UI.

Example URLs:

• https://<zMan-IP>:7080/minio/ztc-fw/manifest.json
• https://xxxx.cloudfront.net/zTC3150L/1.x.xxxx/manifest.json

Performing Firmware Updates

Firmware updates can be applied to individual or grouped devices immediately or scheduled for later execution.

Repository Management

Internal File Repository (MinIO)

zMan Director includes a built-in MinIO file repository, allowing administrators to upload security certificates for deployment.

Supported Certificate Formats

• .cer
• .pem
• .der
• .crt
• .p12

Analytics Operations

Tasks

When applying profiles, firmware updates, or settings, a task is created to track progress and results.

Event Logs

All zMan operations generate event logs, categorized as:

• Information
• Error