Renaming the Thin Client Results in a Reboot Loop

This is relevant for IGEL WES version 3.12.xxx or lower. With IGEL WES version 3.13.100, the problem has been solved.

Symptom

If you rename a thin client while it is registered in an AD (Active Directory) domain, the thin client will try rebooting over and over again. Short before the boot process is aborted, the message Reset domain status apears on the screen.

Solution - If the Thin Client Is in the Reboot Loop

You can reset the new terminal name temporarily during the bootup phase:

  1. Open the UMS.
  2. Double-click your thin client and go to Network > LAN Interface.
  3. Delete the entry in the Terminal Name field.
  4. Click Save.

    On one of the several reboots, the thin client will eventually receive the updated settings from the UMS and boot up normally.

    The new terminal name is restored locally.

    The new terminal is not visible in the Setup yet, but you can check it under Control Panel > System > Computer name, domain, and workgroup settings.

    The name within the AD is not changed.

Preventing the Reboot Loop

  1. Open the UMS or the thin client's local Setup.
  2. Go to Security > Active Directory.
  3. Deactivate Use IGEL Setup for configuring Active directory setting to remove the thin client from the AD domain.

    The thin client logs out of the domain and reboots.

  4. When the thin client is up again, go to Network > LAN Interface.
  5. In the Terminal Name field, change the terminal name.
  6. Click Save or Ok.

    The thin client reboots.

  7. Go to Security > Active Directory.
  8. Activate Use IGEL Setup for configuring Active directory setting to join the thin client into the AD domain.

    The thin client logs in to the domain and reboots.

IGEL's Terms & Conditions apply.