What is the required firmware update path for 10ZiG thin and zero clients?

When performing a major version upgrade, i.e. from 16.3.x to 16.5.x, you must perform the upgrade using the best practice upgrade path.

From versions 16.1.x, 16.2.x, and 16.3.x, this path would be to first upgrade from your current firmware version to 16.3.35.5, and then upgrade from 16.3.35.5 to 16.5.x.

Upgrade from our legacy 12.x firmware to 16.x is no longer supported, and will require a reimage of the device to the latest firmware.

NOTE: When performing any major version firmware update, is it always required to perform a full factory default after the update process. Do not use the check box in your Manager’s firmware update wizard for this; instead perform a factory default as a scheduled task after the update has been applied to the device.

Once the factory default is performed, you can then apply a configuration template created from the target firmware version to your newly updated devices. Do not attempt to use the configuration templates created on your previous firmware as they will not work and could leave your devices in an unusable state.

I’d like to reimage my 10ZiG thin or zero client without using the 10ZiG Manager. Can you guide me through the process using the .tar firmware file I have?

The simplest way to reimage a single 10ZiG thin or zero client without using your 10ZiG Manager server is to use our USB Imaging Utility. You can download the latest version of the Utility from our Firmware Downloads page here.

For this process you will use a USB drive that is 32GB or smaller. It is recommended to avoid using SanDisk or Kingston drives as they have hidden partitions that will disrupt the imaging process.

The steps to use the USB utility to reimage your 10ZiG client are as follows.

  1. Download and run the USB Imaging Utility to format your USB drive, make it bootable and to install our imaging utility onto it.
  2. After creating the bootable USB, copy the .tar format firmware file to the root directory of the drive.
  3. Insert the USB into the unit and power it on.
  4. When you see the initial 10ZiG splash screen or hear the POST beep, start tapping the ESC key to enter the boot manager (F7 on the 7548qTAA laptop models, followed by the BIOS password 10ZIG in all caps).
  5. Select your USB drive as the boot device and let it boot.
  6. Once booted, you will enter the PXE Recovery Linux environment. From the menu, choose “Install from USB”.
  7. In the file explorer window, select the .tar firmware file and click OK.
  8. Confirm the action when prompted; you will then see the progress bar.
  9. After completion, you will return to the PXE Recovery Linux screen. Choose “Reboot” and hit “Yes” to  confirm.
  10. Remove the USB drive, and the unit will boot up into the new firmware image.

I have upgraded my client’s firmware from version 16.3.x to version 16.5.x and the configuration menu is now blank when I navigate to Configuration > Edit in the 10ZiG Manager console. How can I edit the unit configuration and create new templates?

There was a conversion to XML-based configuration in our 16.5.x branch of firmware. With the new XML format comes the requirement of leveraging the 10ZiG Manager’s Web Console for configuration and management of the clients. The new XML format is not compatible with the legacy MMC console and is unsupported there.

How can I reset a 10ZiG client if it does not appear in the 10ZiG Manager?

From the console of your 10ZiG thin or zero client, press the CTRL, ALT, SHIFT and the zero key in the number line together. If there is a Control Panel password assigned to the client, you will be prompted to enter that password.

Once the password has been entered, the client will present a bash shell similar to a cmd shell in Windows. Type the words “factory all” without the quotes, and press ENTER.

This will factory default the client and then reboot it, allowing the unit to boot in a defaulted state. You can now reapply a configuration template to the device or configure it by hand to return it to service.

What devices can I attach to a PCoiP zero client?

Monitors: Depending on the PCoIP Zero Client model, you can attach up to four monitors.

Analog devices: You can attach analog output devices such as headphones and speakers to the PCoIP Zero Client’s analog output (line out) jack, and analog input devices such as microphones and recording devices to the client’s analog input (line in) jack.

USB devices: You can attach a variety of USB devices to your PCoIP Zero Client. USB human interface device (HID) devices (e.g., keyboards, mice, Wacom tablets) are locally terminated by the client. Non-HID devices (e.g., mass storage devices, some printers, non-isocronous scanners) are automatically bridged. The drivers for many of these devices need to be installed in the host operating system (OS).

What is a PCoiP zero client?

PCoIP Zero Clients are hardware- and firmware-based endpoints that allow users to connect remotely to PCoIP Remote Workstations, workstations running PCoIP Access SoftwareTeradici Pervasive Computing Platform desktops and workstations, Amazon WorkSpaces desktops, and VMware Horizon and VMware Horizon DaaS virtual desktops. Because they do not have general purpose CPUs, local data storage, or application operating systems, PCoIP Zero Clients are ultra secure and easy to manage. PCoIP Zero Clients contain upgradable firmware that allows you to customize your client with various features.

Is a zero client more secure than a thin client?

Slightly. Because a Zero client has fewer applications, there is much less that can be targeted by hackers. However, A Thin client is also quite secure as both use read-only operating systems. Apart from this, as the user does not have access to the local OS in a Zero client, he can not go to any malicious websites that might pose a security risk to the endpoint.

Should I use a thin client or zero client?

Zero clients are slightly faster to boot because there is only one application running, so the boot process tends to be very fast. With a Thin client, you may have multiple applications running so it may take longer. That said, many vendors offer a management tool that allows boot timings to be pre-programmed.

How flexible are zero clients?

Zero clients are made for one application to run at a time. If, for instance, one needs to run both RDS and VMware Horizon from the same endpoint, this would require a Thin client operating system.

What is the difference between zero clients and thin clients?

There is no difference in the form factor between a thin and a Zero client. Generally, these are small devices that weigh a couple of pounds. They are fanless and very quiet. Typically they can be mounted on the back of a monitor to avoid crowding the desk space. Zero clients can also take the form factor of laptops or All-in-One devices (monitor with PC combined). Even former PCs can be made into Zero clients. It really comes down to the operating system that is running on the device of choice. Depending on the device, there will also be varying peripheral options (USB, COM port, wifi, RJ 45, HDMI, Display Port, etc…).

Become a 10ZiG Ready Partner

Apply to become a 10ZiG Ready Partner HERE and let’s start creating great stories together.

Get Your 30-Day
Free Demo

Experience the power of 10ZiG risk-free. No credit card. No obligation.