Automation Controls Toolbox
automationcontrolstoolbox.com
Knowledge Base

ThinManager

ThinManager terminal boot

A boot and connection checklist for ThinManager terminals, covering PXE, DHCP options, TFTP, firmware packages, RDS targets, DNS, firewall paths, and redundancy evidence.

Product
ThinManager terminals and servers
Level
Intermediate
Read time
13 min
Reviewed
2026-06-30

Safety first

  • Coordinate with operators before rebooting terminals that are active HMI stations.
  • Do not disable firewalls broadly as a permanent fix. Use rule-based allow lists for required traffic.
  • Do not change DHCP scope options in a shared production VLAN without confirming which devices rely on that scope.
  • Treat RDS and FactoryTalk View SE sessions as production operator interfaces. Avoid forcing logoff without approval.

Common symptoms

  • Terminal never receives an IP address.
  • Terminal receives an IP address but does not download firmware.
  • Terminal reports no bootable device or loops during boot.
  • Terminal downloads firmware but cannot retrieve configuration.
  • Terminal reaches ThinManager but cannot launch the display client or RDS session.
  • A terminal works on one VLAN or switch but not another.

Quick checks

  • Identify whether the terminal is PXE booting, UEFI PXE booting, or using stored firmware.
  • Record the terminal MAC address, assigned IP, VLAN, switch port, ThinManager server IP, and firmware package selected.
  • Check whether DHCP Option 066 points to the ThinManager server and whether Option 067 matches the expected boot file for the boot mode.
  • Verify TFTP and ThinManager property/configuration traffic are allowed between terminal VLAN and server VLAN.
  • Confirm the terminal profile, terminal group, display client, RDS server, and login method are assigned correctly.
  • For RDS display issues, verify DNS, RD Gateway/RDS reachability, certificates, and published RemoteApp/AppLink configuration.

Field procedure

Follow the sequence before changing parameters, replacing hardware, or cycling power.

1. Split boot into four stages

  1. 1Network identity: terminal link, VLAN, DHCP lease, IP, subnet, gateway, and DNS.
  2. 2Boot loader and firmware: PXE/UEFI mode, DHCP boot options, TFTP download, firmware package, and terminal model support.
  3. 3ThinManager configuration: terminal contacts the ThinManager server, receives its profile, modules, display clients, and failover settings.
  4. 4Session delivery: terminal launches RDP, RD Gateway, AppLink, View SE client, or other display content.

2. Validate PXE and DHCP

  1. 1Check switch port link, VLAN, DHCP relay/helper address, and whether the DHCP lease is issued to the terminal MAC address.
  2. 2If using a standard DHCP server with boot options, verify the ThinManager server value and boot filename for the terminal firmware mode.
  3. 3Confirm whether UEFI PXE requires a different boot filename than legacy PXE in the site standard.
  4. 4Check for another PXE server or stale DHCP option that could answer first.
  5. 5Use a packet capture or switch DHCP snooping data when the terminal claims no DHCP or no boot server.

3. Validate firmware and terminal configuration

  1. 1Confirm the terminal model is supported by the selected firmware package.
  2. 2Check whether the terminal is assigned to the correct profile or terminal group.
  3. 3If the boot reaches ThinManager and then hangs, focus on configuration delivery, ThinServer service, firewalls, and redundant-server synchronization.
  4. 4If the terminal repeatedly reboots after firmware download, compare firmware package, BIOS/UEFI settings, and terminal hardware revision.
  5. 5Confirm the ThinManager server has enough resources and that ThinServer is running under the expected account.

4. Validate RDS and display client launch

  1. 1Confirm the assigned Display Server or RDS Server Group is online and accepts the terminal's connection path.
  2. 2Verify DNS resolution for RDS/RD Gateway names when hostnames are used.
  3. 3Check RDS licensing, published RemoteApp/AppLink requirements, user permissions, and session collection policy.
  4. 4If a gateway is used, verify certificates and required RD Gateway ports.
  5. 5Test with a known-good terminal profile only after exporting or documenting the original profile.

Diagnostic groups

Use these buckets to separate evidence and avoid chasing unrelated symptoms.

No DHCP or wrong IP address

Terminal does not receive an address, gets an address from the wrong scope, or boots only on a local unmanaged switch.

Likely causes

  • Wrong VLAN or access port configuration.
  • Missing DHCP relay/helper address.
  • DHCP scope exhausted or wrong reservation.
  • Duplicate DHCP or rogue PXE response.

Checks

  • Check switch port VLAN, link speed, MAC table, and error counters.
  • Check DHCP lease table by terminal MAC address.
  • Confirm DHCP relay from the terminal VLAN to the DHCP server.
  • Packet capture DHCP discover/offer/request/ack if switch evidence is unclear.

Corrective actions

  • Correct VLAN or DHCP relay configuration.
  • Fix reservation or scope exhaustion.
  • Remove rogue DHCP/PXE response before changing terminal settings.
  • Document the MAC, lease, VLAN, and switch port.

PXE starts but firmware does not download

Terminal gets an IP address but stalls at boot filename, TFTP, firmware download, or a stage-1 style failure.

Likely causes

  • Wrong boot filename for legacy or UEFI mode.
  • TFTP blocked between terminal and ThinManager server.
  • Firmware package does not match terminal model.
  • Multicast setting or network filtering conflicts with firmware transfer method.

Checks

  • Verify DHCP boot server and boot filename values.
  • Check UDP 69, UDP 4011 where applicable, UDP 4900, and multicast-related rules if multicast is enabled.
  • Confirm firmware package selected for the terminal make/model.
  • Try the terminal on a known-good switch port in the same VLAN before changing server config.

Corrective actions

  • Correct DHCP options for the boot mode.
  • Allow required TFTP/PXE traffic through host firewall and network firewall.
  • Select a supported firmware package for the terminal.
  • Disable or correct multicast firmware delivery only after verifying site design.

Configuration download or profile assignment fails

Terminal contacts the server but cannot retrieve its configuration, lands in the wrong profile, or prompts unexpectedly.

Likely causes

  • Terminal MAC assigned to the wrong terminal entry.
  • ThinServer service issue or wrong service account.
  • Configuration traffic blocked between terminal and server.
  • Redundant ThinManager servers not synchronized.

Checks

  • Search ThinManager for the terminal MAC address and profile assignment.
  • Check ThinServer service state and server resource health.
  • Verify TCP 2031/property traffic path.
  • Compare primary and redundant ThinManager server configuration and synchronization status.

Corrective actions

  • Correct terminal profile assignment or group membership.
  • Restore ThinServer service health.
  • Open the specific required firewall path instead of disabling firewall broadly.
  • Resolve redundant-server sync before failing terminals back and forth.

RDS or display client launch fails

Terminal boots into ThinManager but the operator session, AppLink, View SE client, or remote desktop does not open.

Likely causes

  • RDS host offline or not in the assigned group.
  • DNS cannot resolve RDS or RD Gateway hostnames.
  • RemoteApp/AppLink is not published or allowed.
  • RDS licensing, certificate, or user permission issue.

Checks

  • Test RDP to the target from the ThinManager server or approved test host.
  • Verify DNS resolution using the same name configured in ThinManager.
  • Check RD Gateway and RDS event logs.
  • Confirm display client assignment and failover/load balancing targets.

Corrective actions

  • Correct DNS or RD Gateway settings before editing terminal profiles.
  • Add or fix the published RemoteApp/AppLink target.
  • Repair RDS licensing or user permissions.
  • Document the working RDS target and update redundant entries consistently.

Evidence to capture

  • Terminal make/model, MAC address, firmware package, boot mode, assigned terminal profile, and group.
  • DHCP lease, scope options, relay/helper address, VLAN, switch port, and boot filename.
  • ThinManager server version, ThinServer service state, redundancy partner state, and server resource usage.
  • Firewall rules or packet capture showing DHCP, PXE, TFTP, property/configuration, RDP, and RD Gateway traffic.
  • RDS server, RD Gateway, DNS name, certificate status, and display client assignment.

Escalate when

  • Terminal is an active operator station and rebooting or profile changes would remove process visibility.
  • DHCP scope or firewall changes affect shared production VLANs.
  • Redundant ThinManager servers disagree and no current backup exists.
  • RDS licensing or domain policy ownership is outside the controls group.
  • Firmware compatibility is unclear for the terminal model and ThinManager version.