Configuring Thin Clients to use Redundant ThinManager Servers

From ThinManager Knowledge Base
Jump to: navigation, search

Each ThinManager Ready thin client needs to be configured to boot from both ThinManager Servers when using redundant ThinManager Servers. This differs when using DHCP or a Static IP Address.

Thin Clients Using DHCP

ThinManager Ready Thin clients are set by default to use DHCP to receive an IP address. The thin client also receives the IP address for the ThinManager Server. This is done by configuring Option 066 in the DHCP Server Program.

DHCP Server Options
DHCP Server Options

Open the Windows DHCP Server Program and find the DHCP Options. Scroll to Option 066 - Boot Server Host Name and add the IP address of the the redundant ThinManager Servers in the Data Entry field, separated by a space. This will pass the IP addresses of the ThinManager Servers to the thin client, enabling it to boot from either.
The thin client will try the first, or primary ThinManager Server. If it can't connect to it, it will time-out and try the second ThinManager Server listed.

Thin Clients Using Static IP

The Static method uses IP addresses that are entered on the unit instead of being assigned by a DHCP server. Set the static IP address by booting the thin client and interrupting the boot process by pressing the spacebar when prompted.

Press Any Key to Configure Message
Press Any Key to Configure Message

The thin client will display a IP Configuration Menu.

Default IP Configuration Menu
Default IP Configuration Menu

Select the A key and type the IP address for the thin client and press the Enter key..

IP Configuration Menu
IP Configuration Menu

Once the client has an IP address entered, the other menu items are available.

  1. Terminal IP Address - This should be a unique address for the terminal.
  2. Primary ThinManager Server IP Address - This should be the unique address for your main ThinManager Server.
  3. Secondary ThinManager Server IP Address - The Secondary ThinManager field allows the terminal to use two ThinManager Servers. If the terminal cannot connect to the Primary ThinManager Server, it will connect to the Secondary ThinManager Server to receive its configuration. If you are not using a Secondary ThinManager Server, set the IP address to 0.0.0.0.

Enter the IP address of the Primary ThinManager Server after typing B and enter the IP address of the Secondary ThinManager Server after typing C. Type S to save when finished.
The thin client will try the Primary ThinManager Server when it boots. If it can't connect to it, it will time-out and try the Secondary ThinManager Server.

Personal tools
Namespaces

Variants
Actions
Navigation
Events
Toolbox