ARGUS


Thinlabs Quad Core products (TL1000, TL2300, TL2400, TL85xx, TL86xx) support Windows 10.

Thinlabs Dual Core products (TL2100, TL2200, TL6000, TL8300, TL8400) do not support Windows 10.

-------------------------------------------------------------------------------


Thinlabs systems have two default user accounts (user / password),
Administrator / Administrator and User / User, respectively.

Devices by default automatically log onto the User account.

VNC Password: Admin

It is highly recommended to change default passwords immediately to keep your IT environment secure.

--------------------------------------------------------------


Serial numbers of Thinlabs All-In-One Systems and Box Modules are 12 digits in length; serial numbers of ADITI Lithium Ion Batteries are 6 digits in length.

Certification stickers with serial numbers are located on the back of box client modules.

On integrated thin clients, there is a certification sticker on the back of the system;
newer models also have a 2nd serial number sticker either on the left side bezel or on the bottom of the bezel.

If the certification sticker has been destroyed, contact Thinlabs Support.

--------------------------------------------------------------


Verify the boot option settings are correct in the BIOS (TL23, TL24, TL85, TL86 models).

  • Press DEL to enter BIOS.
  • At the Save & Exit menu,
    select Load Optimized Defaults
  • At the Boot menu,
    under Boot Option #1,
    select Windows Boot Manager (P1: [device name])
  • Press F4 and select Yes to Save & Exit Setup.

Registered Thinlabs users can check the status of a product by Serial Number or Invoice Number
on our Warranty Lookup page.

Select either Serial Number or Invoice Number.
Enter the corresponding information and click Lookup.

--------------------------------------------------------------

-----

THINLABS WARRANTY AND SUPPORT IS LIMITED TO MANUFACTURING AND HARDWARE DEFECTS ONLY. Review our on-line support options, including our FAQs and Downloads first.

-----

If OEM Software does not complete a successful boot process:

  • NOTE: It is the responsibility of OEM support personnel to provide recovery media and instructions to end users.
  • Thinlabs can offer this service for OEM customers with a valid support contract.
  • After the initial system BIOS post, if OEM software (regardless of operating system) either (1) fails to load completely or (2) continuously reboots, try reloading the operating system.

OEM Software Touch screen problems:

  • When using a proprietary OS, verify that X and Y coordinates are not hard-coded so that the touch screen calibration utility can properly detect and set coordinates.  If coordinates have been hard-coded, update settings in the software as required for the specific unit.
  • If, after trying the above to remedy any issues, the thin client is still not working, please request an RMA for further support.

-----

Thinlabs reserves the right to charge standard out-of-warranty service fees when:

  • units returned fail to exhibit any problems as reported;
  • problems resolved are not manufacturing and hardware related; or
  • any problems with the thin client could have been remedied utilizing the available on-line support options provided.

--------------------------------------------------------------


This may be seen on systems with 2 GB RAM if the paging file is set to Disabled when installing resource-intensive applications. See the how-to document on Windows 7 - Memory Optimization for information on how to correct this error.

--------------------------------------------------------------


Thinlabs systems have two default user accounts (user / password),
Administrator / Administrator and User / User, respectively.

Change default passwords prior to deploying systems in the field.

Devices are set to auto-logon to the local User session by default.
If you change the password or create another user, you can set the units to autologon by:

On WES 2009 (XPe):

  • Start Menu | Setup Panel | Utilities | TweakUI
  • Scroll down the menu list on the left, select Auto Logon, and set new login credentials.
  • Commit changes to the EWF using EWF Manager
    (you can also change autologon settings remotely using Thinlabs Device Manager)
On WES 7 (W7e):
  • From the Start menu search box, search forcmd
  • Right click on cmd.exe and select "Run as Administrator"
  • Type the cmd "control userpasswords2" and press <Enter>.
  • The "User Accounts" applet should open.
  • Uncheck the box "Users must enter a username and password to use this computer" and click <Apply>.
  • When prompted, enter the credentials for the user session that requires to auto logon when unit boots.
  • Commit changes to the EWF using EWF Manager.
    You can also change the autologon setting remotely using Thinlabs Device Manager)

--------------------------------------------------------------

  • Disable LLDP Snooping
  • Ensure the port is set to deliver 30W or higher

--------------------------------------------------------------


General:

  • Check the internet connection to ensure it it functioning.
  • Check the switch or router to ensure it is working - check the network ports to ensure they are working.
  • If attempting to access a specific website via the Internet, check to see if another website can be accessed through the internet browser.
  • If attempting to PING another IP address on the network, check to see whether that IP address can be accessed from another client.
  • If network access is controlled by a central MAC address database, ensure that the correct MAC address of the device in question is included in the database.

Hard wired Ethernet connections:

  • If using Static IP:  ensure that there are no duplicate IPs on the network.
  • If using DHCP:  check the network port by connecting a portable notebook computer at the same network jack, or;
  • Check the system at another station to ensure it is not a network port problem.
  • Check the CAT-5 network cable.
  • If using PoE:
    • Make sure the network cables are firmly connected from the PoE switch to the internal PoE splitter and/or PoE injector.
    • Make sure the network patch cable is firmly connected on the computer from the internal PoE splitter to the LAN port of the motherboard.

Wireless connections:

  • Check to see if external wireless antenna is connected and threaded properly into the connector.
  • Try swapping an antenna from a working device.
  • Check that the wireless access point is online and accessible through other wireless clients.
  • Ensure that the correct SSID / Passphrase is entered in the wireless settings on the thin client.
  • If using a Windows XP Embedded device:
    • Verify or update wireless configuration on the client
    • Commit changes to the system using XPe's Enhanced Write Filter Manager (EWF) and reboot the system.

--------------------------------------------------------------

Pages