10ZiG Technology FAQ

Minimum requirements:

Both the server and console packages require Windows XP with SP2, Windows Server 2003 with SP2, Windows Vista or Windows Server 2008

Microsoft .NET Framework 2.0 and the .NET 2.0 Service Pack 2

MMC 3.0

Compatible with 32-bit and 64-bit Windows

NOTE: Not Compatible with Windows 2003 64-bit

10ZiG Manager Server (Required)

Note: The manager installs on a PC/Server and runs as a service to monitor and act as a PXE server for the thin clients.

When the server is installed an instance of the manager console is installed with it

NOTE: YOU MUST UNINSTALL VERSIONS OLDER THAN 2.0.2.0 PRIOR TO INSTALLING OR YOU WILL NOT HAVE ALL AVAILABLE OPTIONS TO MANAGE WINDOWS EMBEDDED STANDARD 7 THIN CLIENTS!!!!

MgrSrvSetup_v2.0.2.5.exe

Release Notes

The primary server package contains the management service, the MySQL database backend, and the MMC console snap-in GUI. Only one instance of the server package should be installed on a regularly accessible server within your network.

10ZiG Manager Console (Optional)

If needed, the console is installed on a remote PC that will be used to connect to the 10ZiG Manager server to administer thin clients from that remote PC.

MgrConSetup_v2.0.2.5

10ZiG Agent

The agent is installed on the XPe thin client itself. The XTC Agent now supports and is required for WES7 clients, as well as any XPe thin clients to be managed.

XtaSetup_v2.0.1.4

Documentation is accessible through the 10ZiG Manager Server HELP

Back To Top

Where can I download the quick start guide for the older version of the manager?

(old)10ZiG_Manager_Quick_Start

Back To Top

I am using the older manager and when I try to retrieve the configuration from a thin client the program crashes with a term.exe error.

Make certain you do not have a 5250 session name with an underscore in it.

Back To Top

How do I update the firmware on a Linux thin client using the 10ZiG Manager?

Make certain the Image Store path is set in the 10ZiG Manager setup

Copy the image file (.tar) to the image store folder

If the thin client is on the network the 10ZiG Manager service is running it will display in the 10ZiG Manager console.

Right click on the thin client to be updated and select Firmware update.

Confirm the update

Select the .tar file (image file) from the Image Store

A message will be displayed indicating the thin client will be updated and rebooted

At this time, no other message will indicate the status of the upgrade but the upgrade process will be displayed on the thin client itself. Once updated the thin client will reboot and be available again via the 10ZiG Manager Console.

Back To Top

When the unit is completing the PXE boot process and loading the Linux environment I see the following lines on-screen near the end of the boot process;

Eth0 [ followed by Ethernet info]

starting sshd

starting httpd

starting crond

[E17.654459] FAT: Bogus number of reserved sectors

(Note the 6 digit number changes on various reboots)

starting samba

(couple of lines for for discovery and runlevel0

10Zig Login:

Is this a problem or a sign of something gone wrong?

The message that appears “FAT: Bogus number of reserved sectors“ should not cause concern as it just reflects the how Linux sees the FAT partition that we create with Windows when we build our master images.

The error does not affect backup or restoration.

Back To Top

Why don't my Linux or CE thin clients PXE boot after I set them to PXE in the 10ZiG Manager?

Do to BIOS limitations, each of the Linux and CE thin clients must be set to PXE boot in the BIOS.

Back To Top

Where can I download the older version 2.0.40 of the BOSmanager?

BOSmanager 2.00.40

Back To Top

Can I PXE boot to the 10ZiG Manager using the wireless connection?

No, PXE is part of BIOS and the BIOS only knows about the built in NIC.
Back To Top

What ports are used by the 10ZiG Manager?

The 10ZiG Manager communicates with the thin clients using remote procedure call (RPC) and Active Directory relies on remote procedure call (RPC) for replication between domain controllers thus resulting in a conflict if on the same server.

Network Ports and Purpose

TCP 3306 - Used by the local MySQL service hosting the Manager database.

TCP 11132 - The Manager Console retrieves information from the Server via this port.

TCP 11133-11147 - A Manager Console will register one of the ports in this range, usually 11133, with the Server to receive various notifications.

Client Discovery and Communication Ports

UDP 52500 - Broadcast discovery port for Windows (XTC Agent) and Linux 9 thin clients.

TCP 52510 - This RPC port is used by Manager Server to perform remote operations and queries on Windows (XTC Agent) clients.

TCP 52511 - This RPC port is used Windows (XTC Agent) clients to notify the manager server when they come online or are going offline.

TCP 80/443 (HTTP/HTTPS) -These Web ports are used by Manager Server to query information from and perform operations on Linux 9 (LTC Agent) clients.

UDP 1680 or TCP 1680 - Depending on whether TCP discovery is enabled, one of these ports is used to discover of Linux 8 and Windows CE thin clients.

TCP 21(FTP) - The port is used by Manager Server to query information from and perform operations on Linux 8 (Browsed Agent) clients.

TCP 8001 - The Manager Server publishes firmware update packages for Linux clients on this port.

PXE Boot Ports

UDP 68 (DHCP/BOOTP)- The Manager Server responds to DHCP/BOOTP requests from this port for PXE-Booting clients for image deployment/recovery.

UDP 69 (TFTP) - When PXE-Booting, the PXE configuration and boot image are transferred to the client via TFTP

Back To Top

What is the difference between the Clone System Image - Deploy System Image and Backup and Restore?

An explanation of the Cloning/Deploying and Backup/Restore and their differences:

Cloning is the process of creating a re-deployable Windows image.

The administrator initiates the clone from the Manager’s Thin Client view after selecting the source device.

For a WES7 device, the administrator is guided through a Sysprep wizard for additional customization, but for XPe , the Manager explains that FBReseal will be performed.

The administrator is prompted for the name to which to save the image.

The source is set to PXE boot, and the Manager remotely initiates “FBReseal” for XPe or “Sysprep” for WES 7 devices. Both FBReseal and Sysprep remove/reset specific system settings to allow the backed-up image to regenerate identification information for uniqueness when the prepared image is booted the next time. However, the Manager offers some customization options for Sysprep where with FBReseal the same options need to be configured directly on the device before resealing.

Once the system has been resealed or sysprepped, the unit is rebooted.

When Manager has discovered the device which has booted into PXE Linux, the image backup automatically starts.

Once the backup has completed, the source device is set to boot normally and rebooted. The backed-up image is should then be ready for deployment.

The source device will boot back into the Windows operating system where the system identification information is regenerated.

Deploying an image is basically the “automated” process of restoring a previously backed-up image whether it had been cloned or manually backed-up.

The administrator selects the target devices from the Manager’s Thin Clients view and initiates the image deployment.

He or she is prompted to select the image to deploy.

The target devices are set to PXE boot and then rebooted.

Once the devices have booted into PXE Linux and the Manager has discovered them, the image is restored automatically.

After the restore completes, the devices are set to boot normally and rebooted again.

The Backup/Restore option is a manual process in that the Windows device is set for PXE booting and rebooted in PXE Linux.

The PXE Linux-booted device will appear in the Manager’s Image Recovery view, where the administrator can then start a backup or restore via the Manager GUI.

An image backed up with this method is only intended to be restored to the same device as it has not been prepared for redeployment to other devices.

Back To Top

The image will not push out and fails - what might be the problem?

Make certain that use simple file sharing (Recommended) is unchecked in folder options - NOTE: The wording may be different in other versions of Microsoft Windows.

Back To Top

How do I use the hot keys in UltraVNC viewer on a Linux thin client through the 10ZiG Manager?

The 10ZiG Manager uses UltraVNC viewer for shadowing thin clients. This viewer provides various additional features like chat and file transfer. These features can be accessed via hot key sequences that begin with “Ctrl+Alt”, but the key sequence interferes with sending these sequences to the shadowed device.

Therefore, the aforementioned hot keys need to be disabled in order to obtain a terminal console on our Linux devices via “Ctrl+Alt+Shift+0”.

To do so:

Press the “Scroll Lock” key to disable the hot keys. (This enables scroll lock.)

Press the Ctrl + Alt + Shift + 0 to open a console terminal.

Press the “Scroll Lock” key again to re-enable the hot keys. (This disables scroll lock.)

Back To Top

My thin client is on a VPN and I need to PXE to the 10ZiG Manager.

Define the options for the scope or for the DHCP server.

Add option 66 “Boot Server Host Name” and specify the IP address of the 10ZiG Manager server for the value.

Add option 67 “Bootfile Name” and specify “pxelinux.0” for the value.

Back To Top

Where can I find a manual for the 10ZiG Manager?

The manual is the online help in the program itself but you can also view it here:

10ZiG Manager Manual PDF

Back To Top

Can I run the 10ZiG Manager on the same server as my DHCP server?

No, the 10ZiG Manager uses the same listening port as DHCP so there would be a conflict

Back To Top

Can I run the 10ZiG Manager on the same server as my Active Directory server?

No, the 10ZiG Manager communicates with the thin clients using remote procedure call (RPC) and Active Directory relies on remote procedure call (RPC) for replication between domain controllers thus resulting in a conflict if on the same server.

Back To Top

How does the 10ZiG Manager communicate with the XPe thin client?

The 10ZiG Manager uses RPC (remote procedure call) to communicate with the XPe thin client using ports 52500 and 52510.

Back To Top

How can I backup or restore an image on a thin client using a USB thumb drive?

Download the Drive Imaging Utility and Guide below:

TzImgUtil_setup.exe

TzImgUtil.pdf

Back To Top

I have a class A network and have added my IP range but I still don't see any thin clients?

For large networks - in the 10ZiG Mangager Server Settings - Discovery Tab - set the ping timeout to 500 milliseconds instead of the default 250 milliseconds

Back To Top

Is there a way to manage my RDP sessions on Linux thin clients using the 10ZiG Manager?

LTC RDP Manage Plugin Installer Package

This program is an add-on to the 10ZiG Manager

Back To Top

I updated my 10ZiG manager to version 2.0.2.0 and now I am missing options on Windows Embedded Standard 7 thin clients

Two options

Uninstall the 10ZiG Manager program and reinstall.

or

Stop the 10ZiG Manager Service

Navigate to the install path of the 10ZiG Manager server C:\Program Files\10ZiG\10ZiG Manager\mysql\data and delete the folder tenzigmgr

Start the 10ZiG Manager Service

Reconfigure the settings such as IP ranges etc.

Back To Top

I installed 10ZiG Manager on Windows 7 64 bit and now I get a Snap-in error - Font "Arial Does not support style "Regular".

Find arial.ttf (Arial font) and reinstall it in Windows.

Back To Top

I am trying to update my Linux thin client using a tar file in the 10ZiG Manager but it fails.

The update mechansism was broken after build 9.8.1 until a new build 9.8.6 was created.
To update to 9.8.6 you must update using a binary image. Contact Tech Support for location and credentials to download updated image.

To update the image the two are options; restore using the 10ZiG Manager or use a thumb drive created by TzImgUtil.

Update using 10ZiG Manager

Install the 10ZiG Manager and copy the binary file to C:\ImageStore

If the thin client is seen in the 10ZiG Manager, right click on it, select Image Management and then Backup and Restore

The thin client will be moved to the Image recovery tab with PXE set to Yes

If the thin client is not seen by the 10ZiG Manager, click on the Image recover tab and add the MAC address of the thin client using

Change the BIOS settings of the thin client to boot from LAN (BIOS password is 10ZIG)

Boot the thin client and it will PXE boot to the 10ZiG Manager

When the thin client has booted it will be displaying a recovery menu on the display but do not use that menu.
Using the 10ZiG Manager, Image recovery tab, right click on the thin client to be reimaged (it should now indicate PXE YES with a green dot) and select Restore Binary Image

Select the image file to be restored

The 10ZiG Manager will restore the image and indicate a successful restore when complete

Right click on the thin client and deselect the PXE boot option

Reboot the thin client which now has the updated image

Update using a USB Thumb Drive

Download the image utility in Question 18. Note: PDF of directions at the same location

Extract the utility and run the program to make a USB thumb drive bootable for the utility

Make certain you format as fat32 and the USB thumb drive needs to be large enough to hold the boot files and the binary file
Note: This program will erase all files on the thumb drive

Enter the BIOS of the thin client (password 10ZIG) and set the first boot to USB (on some units the option may be USB Zip)

Boot the thin client using the created USB thumb drive

Use the menu on the display to restore the image

Once complete reboot with thumb drive removed to an updated image

Back To Top

I can't start the 10ZiG Manager Service.

Check the Windows application event logs and if the message is as follows:

Event Type: Error
Event Source: 10ZigMgr
Event Category: None
Event ID: 0
Date:
Time:
User: N/A
Computer:
Description: Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.
at Tenzig.Manager.Settings.MgrSettings.get_IP()
at Tenzig.Manager.Server.TC.MgrThinClient..ctor()
at Tenzig.Manager.Server.TC.MgrThinClient.GetInstance()
at Tenzig.Manager.Server.Service.MgrService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

The log file indicates that the manager was unable to obtain the IP address for the selected Network adapter.
Verify the appropriate network adapter is selected via the settings dialog from the Manager service controller tray icon?

If the correct adaptor is selected the 10ZiG Manager’s registry key may have gotten corrupt.

Delete the registry key and rerun the settings applet.

Delete the registry key, “HKEY_LOCAL_MACHINE\SOFTWARE\10ZiG\MgrService”.

Restart the 10ZiG Manager Service Controller.

Back To Top

The 10ZiG Manager does not see my thin clients or they go green and then red back and forth.

The issue may be Multicast Discovery - go into the 10ZiG Manager Server Settings and uncheck Use Multicast Discovery

Back To Top

WOL (Wake On LAN) function is not working - I can shut the thin clients down but I can't power them off.

WOL uses UDP port 0 and sends a small broadcast to wake up the thin client. For WOL to work the network environment must support “direct broadcasting”.

For example: If the manager is at IP 192.168.1.2 and the client IP is 192.168.2.125, the WOL broadcast must be able to get to 192.168.2.255 which is the broadcast address of the client's subnet.

Back To Top

I have a 5120 or a WTC-1000 and BOSmanager never finds it.

Please extract this file AdminMod.zip to the directory C:\Program Files\BOSaNOVA\BOSmanager and rename the current Admin.exe file to admin.old and then rename AdminMod.exe to Admin.exe.

Back To Top

I have a Linux thin client that shows up with the name NONE.

Most likely the name of the thin client has been changed to a name with a space in it - remove the space and it will show up in the manager with the correct name.

Back To Top

How can I copy/move an existing 10ZiG Manager database to another computer?

Preparing the new server:

Install the 10ZiG Manager server package on the new computer. Make note of the installation path, by default on 32-bit Windows is “C:\Program Files\10ZiG\10ZiG Manager” or on 64-bit Windows is “C:\Program Files(x86)\10ZiG\10ZiG Manager”.

During the manager installation, make certain to select the appropriate network adapter and specify the desired path for the network share.

Allow the installation to start the new manager server service or manually start it via the “10ZiG Manager Service Controller” start menu shortcut after installation if necessary.

Once the service has successfully started, which is indicated by a blue 10ZiG tray icon, right-click on the tray icon and select “Stop”. The icon will be grayed-out when the service has completely stopped.

Copy the old database to the new computer:

Locate the old database subfolder within the existing manager server installation path. The default path on 32-bit Windows is “C:\Program Files\10ZiG\10ZiG Manager\mysql\data\tenzigmgr” or “C:\Program Files (x86)\10ZiG\10ZiG Manager\mysql\data\tenzigmgr” for 64-bit.

Copy the “tenzigmgr” subfolder with its contents to the new manager server installation path. i.e. Place the old “tenzigmgr” subfolder into the “C:\Program Files\10ZiG\10ZiG Manager\mysql\data“ folder on the new server allowing the existing files in the destination folder to be overwritten.

Restart the new manager server service by right-clicking on the tray icon and selecting “Start”.

Once the manager server service has started successfully (blue tray icon), the migrated database will have been integrated into the new manager server installation.

Launch the Manager Console via the installed shortcuts or by double-clicking the tray icon, and verify the previous IP range and group settings are OK.

Back To Top

I am getting a "cannot access the ImageStore share" error in the 10ZiG Manager when in recovery mode.

A couple of factors can cause the thin client in recovery mode not to be able to map the “ImageStore” share on the manager server.

If your Manager server is Windows 7 or Server 2008 R2 and is not a domain member, it may necessary to disable “Simple File Sharing” or “Sharing Wizard” which causes the server’s file shares to only require a password. When the thin client is in recovery mode it tries to mount the share, it provides the username and password specified during the manager installation, yet authentication fails.

To disable “Sharing Wizard”:

From Windows Explorer, click the “Organize” toolbar menu, and then select “Folder and search options” to open the “Folder Options” dialog.

Click on the “View” tab.

In the “Advanced settings” list, scroll down and verify “Use Sharing Wizard” is unchecked. If it is checked, click the checkbox to uncheck. (See the attached image.)

Click the “OK” to apply the settings and close the dialog.

Stop and restart the 10ZiG Manager and try the backup again.

If the above is not the case, we can try creating a local user account on the server specifically for accessing the ImageStore share. Once the local account has been created:

Right-click on the 10ZiG Manager tray icon, and select “Image store…”.

Specify the local account name, making sure to specify the server’s computer name for the domain followed by a backslash and then the username. Ie: computername\username

Enter the password in both password fields to confirm.

Click the “OK” button to apply the settings and close the dialog.

Stop and restart the manager server and try the backup again.

Back To Top

I have a WES 7 thin client that is seen in the 10ZiG Manager Console but then it randomly shows as off even though it is still on and working.

On WES7 devices, we should make sure to enable the firewall rule to allow ping (ICMPv4) through so that when or if the Windows Firewall is turned on, the clients will respond to the request.

Please enable the rule, “File and Printer Sharing (Echo Request – ICMPv4-In)” with the following settings:

Profile: All

Enabled: Yes

Action: Allow

Local Address: Any

Remote Address: Any

The other settings can be left as their default values.

To enable this rule on a deployed thin client:

Open the Windows Firewall control panel.

Select the “Advanced settings” item in the left pane.

From the “Windows Firewall with Advanced Security” window, select the “Inbound Rules” in the tree view.

Locate the first “File and Printer Sharing (Echo Request – ICMPv4-In)” rule entry, right-click, and select “Properties”.

On the “General” tab, check the “Enabled” box and make certain “Allow the connection” is checked.

On the “Scope” tab, make certain “Any IP address” is checked for both Local and Remote IP address options.

On the “Advanced” tab, check the boxes for all the profiles.

All the other settings should be left as their default values.

Click the “OK” button to apply and enable the rule; this will take effect immediately.

Back To Top

I have a PXE server in place already so I don't want to use the 10ZiG Manager as a PXE server - how can I use the existing PXE server to push out images to thin clients?

You must be using version 2.0.2.5 (beta) or higher of the 10ZiG Manager.

Copy all the files from the tftp folder from the 10ZiG Manager install folder to the existing PXE server in the published files directory.

Place the image in the general repository directory on the existing PXE server.

Go into the manager server settings (right click on the ICON down near the time on your PC and select settings) - Advanced Tab – Uncheck Enable TFTP server and under the TFTP Host put the IP of the existing PXE server. Boot the thin client in PXE mode and you should be able to restore the image from the existing PXE server.

Back To Top

The PXE process starts correctly but the TFTP does not seem to communicate resulting in an eventual timeout error.

Start the SYSLOG.exe and reproduce the timeout problem

View the SYSLOG and look for the following message:

The log message that indicates this situation appears as follows: 07-04-2011 12:16:37:502 <Error> BootServer [TftpSession::SendPacket] : System.Net.Sockets.SocketException: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.

Based on the SYSLog error message it appears the Maximum Transmission Unit (MTU) size is insufficient for the TFTP transfer when PXE booting. The default MTU value for Ethernet connections is 1500. Please check the system's current settings and adjust accordingly.

From a command prompt window, type “netsh interface ipv4 show subinterfaces” and press Enter to display the current MTU values for the system’s network adapters.

Verify the MTU value for the “Local Area Connection” is 1500.

If this value is insufficient, increase it by typing the following and pressing Enter:
“netsh interface ipv4 set subinterface “Local Area Connection” mtu=1500 store=persistent”

Note: If you have more than one wired LAN adapter, repeat steps 2-3 for the subsequent adapters.

Back To Top

The 10ZiG Manager doesn't seem to be able to determine the online status of WES 7 thin clients.

The 10ZiG Manager needs to be able to ping the thin clients to determine their online status. On WES7 devices, a firewall rule must be enabled to allow ping (ICMPv4) through so that when or if the Windows Firewall is turned on, the clients will respond to the request.

Please enable the rule, “File and Printer Sharing (Echo Request – ICMPv4-In)” with the following settings:

Profile: All
Enabled: Yes
Action: Allow
Local Address: Any
Remote Address: Any

The other settings can be left as their default values.

To enable this rule on a deployed thin client:

Open the Windows Firewall control panel.

Select the “Advanced settings” item in the left pane.

From the “Windows Firewall with Advanced Security” window, select the “Inbound Rules” in the tree view.

Locate the first “File and Printer Sharing (Echo Request – ICMPv4-In)” rule entry, right-click, and select “Properties”.

On the “General” tab, check the “Enabled” box and make certain “Allow the connection” is checked.

On the “Scope” tab, make certain “Any IP address” is checked for both Local and Remote IP address options.

On the “Advanced” tab, check the boxes for all the profiles.

All the other settings should be left as their default values.

Click the “OK” button to apply and enable the rule; this will take effect immediately.

Back To Top