An overview of ThinManager's content delivery system and thin clients, including OnLogic's TM-Ready systems, update considerations, and compatibility.
ThinManager Introduction
In the rapidly evolving landscape of edge computing, efficient device management and orchestration are paramount. ThinManager is a robust content delivery system designed to streamline the deployment and management of edge applications, addressing challenges of scalability, heterogeneity, and rapid deployment inherent in these environments.
It functions by distinguishing between Sources (content generators like Remote Desktop Servers, Virtual Servers, Workstations, or IP Cameras) and Content (the actual data delivered to users). ThinManager is capable of delivering a wide variety of content from these diverse sources.
Crucially, ThinManager doesn't just deliver content; it allows precise access control per device, user, and location, enabling effective management of content access. Endpoint devices can range from standard Android, iOS, or Windows devices running a ThinManager application to specialized thin clients.
What are Thin Clients?
Put simply, Thin clients are terminals without hard drives that connect to a server, offering several advantages over typical clients:
No Installation or Configuration: They don't require software installation, configuration, or updating, as all connected clients use the same application installation from the server.
Lower Cost & Maintenance: Reduced storage costs and simpler maintenance, as managing a few servers is easier than hundreds of distributed systems. Operating systems and storage drives are common failure points.
Automatic Failover: Thin clients can connect to multiple terminal servers. If one server fails, the client automatically switches to another designated server. They can even run two sessions simultaneously, instantly switching upon failure.
To learn more about ThinManager and obtain training on the details, you can visit
The TM line from OnLogic comes pre-configured with a custom BIOS that boots directly to the Rockwell Automation’s ThinManager boot ROM. OnLogic is responsible for any hardware issues, while the Rockwell team can help with anything pertaining to the software, configuration, or setup.
For help with software or configuration issues,
With the release of ThinManager Version 11, Rockwell Automation’s ThinManager software no longer boots from Legacy Boot Mode in the system BIOS. ThinManager now boots using UEFI Mode. In addition, Intel does not support Legacy Boot Mode on newer generation processors.
As a result, only the following OnLogic products support versions of ThinManager older than Version 11:
It is highly recommended by both Rockwell Automation and OnLogic that customers use the most up to date stable release of ThinManager.
Software updates frequently bring valuable new features and enhanced security to users, but they can also bring headaches to IT and OT teams who need to implement the changes. As a result, organizations may remain on a legacy version of a given software package for extended periods. However, inevitably, there ultimately comes a time when it no longer makes sense for organizations to support legacy versions of software.
ThinManager Software Updates
With the release of ThinManager version 11 in 2018, ThinManager switched to utilizing instead of a Preboot eXecution Environment (PXE). Users on legacy versions of ThinManager require hardware that supports PXE. However, only systems with Intel 4th generation Intel Atom processors (Bay Trail) and older support that feature and thus support ThinManager v10 or older.
These older platforms are reaching the end of their lifecycle and, as such, we are discontinuing them. We are here to help you understand what that means for your deployments and the benefits of migrating to a newer version of ThinManager.
ThinManager Update FAQ
What are the benefits of upgrading to newer versions of ThinManager?
Along with new features such as event-based delivery, REST API configuration, and container virtualization, the most important feature of the latest versions of ThinManager is DCOM Hardening patches to help protect your system against intrusions.
The biggest issue with legacy software is that without security patches, your system is left vulnerable to known exploits. ThinManagers version 10 and older no longer receive security patches making migration a priority.
As always, our team is available to answer any questions that you might have about our ThinManager-ready thin clients.
The following sections give an overview of common hardware troubleshooting steps for each TM system.
TM250
For information on the TM250 ThinManager Ready platform, please visit the ML350G-10 page.
TM200
For information on the TM200 ThinManager Ready platform, please visit the ML210 series page.
TM260
For information on the TM260 ThinManager Ready platform, please visit the HX300 series page.
TM430
For information on the TM430 ThinManager Ready platform, please visit the TC401 / TN101 page.
TM300
For information on the TM300 ThinManager Ready platform, please visit the DC-1100 page.
TM700
For information on the TM700 ThinManager Ready platform, please visit the CL100G page.
TM110 / TM710
For information on the TM110 ThinManager Ready platform, please see the CL200 page.
For information on the TM710 ThinManager Ready platform, please visit the CL250 page.
TM610
For information on the TM610 ThinManager Ready platform, please visit the MC610-50 page.
What should I upgrade first, my hardware or my ThinManager software?
You will need to upgrade your ThinManger Server first. OnLogic ThinManager Ready Clients that use legacy PXE boot are compatible with the latest versions of ThinManager. You will then have the ability to use newer OnLogic ThinManager Ready Clients that use UEFI boot.
I have OnLogic hardware that I used with earlier versions of ThinManager. Will it still work with newer versions of ThinManager?
If you are using a system from OnLogic such as the TM700 with a legacy ThinManager version between v6-v10, it will still work with the newest versions of ThinManager.
If you are using a firmware version older than v6, you should contact ThinManager for support.
I am unable to upgrade my ThinManager software. When is OnLogic discontinuing systems that support my legacy software?
The TM700 will remain available until February 2024. The last opportunity to purchase other legacy ThinManager Ready Clients including the TM200, TM300, and TM400, is June 28, 2023.
OnLogic powered by ZEDEDA simplifies and accelerates edge computing. Integrating industrial-grade hardware with cloud-native edge orchestration software helps you overcome complexities of deployment
EVE Revision Updates
Systems shipping after 20 June 2026 are pre-imaged with EVE 16.0.1
Systems shipping after 28 Feb 2026 are pre-imaged with EVE 16.0.0
Systems shipping prior to 28 Feb 2026 are pre-imaged with EVE 14.5.1
OnLogic Powered by ZEDEDA Hardware
To view all hardware that is certified and powered by ZEDEDA, simplifying deployment, please see below:
Help Center
For help with ZEDEDA and EVE-OS, please see below
Getting Started
New system? For help getting started with ZEDEDA and EVE-OS, please see below
Want to learn more about Orchestration and Cloud Native App deployment at the edge? View the ZEDEDA Edge Academy Learning Path Below:
Ignition Edge Quickstart
Get started with Inductive Automation's Ignition Edge, including first-time setup and verifying your installed version.
What version of Ignition Edge do I have installed?
From the Gateway Webpage. Navigate to Config > Modules, you will see a list of all modules. The version will be displayed in its own field.
Refer to the Ignition Manual Page “” for more information
Guide to setting up OnLogic AWS Greengrass Compatible IoT Edge Gateways for edge-to-cloud deployments, including hardware, software, and Greengrass component setup.
1- Revision History
Document Version
Date
Changes
1.0
2.16.24
Initial Version
The OnLogic AWS Greengrass Compatible IoT Edge Gateways are designed to simplify deployment of embedded PCs for your AWS Edge projects. Using a Fanless PC increases equipment reliability and decreases downtime at the edge. OnLogic AWS Greengrass Compatible devices come tested for compatibility with to easily integrate into your AWS IoT applications.
Datasheets are available for your OnLogic AWS Greengrass Compatible IoT Edge Gateway on its’ product page under the download section. All list of systems is provided here:
Cl200 Small Form Factor Series
ML100 Industrial Edge NUC Series
Each OnLogic Gateway includes the computer itself, depending on chosen accessories the following may be included. Accessories may be purchased separately on onlogic.com where stated.
Mounting Hardware (Available for individual purchase)
Accessory Phoenix Connectors for DIO/AIO/GPIO/CANBUS, Power Terminal Block, Serial Cables
AC Power Adapter, if selected (Available for individual purchase)
OnLogic PCs for AWS IoT Greengrass are designed to integrate into your edge compute applications and as such are only a part of the solution. An IoT solution should include:
Data collection devices such as sensors and PLCs to connect to local equipment
Cloud resources to run your application in the AWS Cloud which includes any associated AWS cloud services that you need such as AWS IoT Sitewise, AWS IoT Core, AWS Lambda among others.
To take advantage of advanced features such as Microcontroller (MCU) access to control DIO, CanBUS, GPIO, automotive ignition timings (on applicable systems). Please consult OnLogic product support pages for the applicable systems for a full guide and links to Git repositories (where applicable).
The following link to individual product support pages:
Cl200 Small Form Factor Series
Helix Industrial Computers Series
For an in-depth guide on a product by product basis, visit the OnLogic support page for the product you purchase or consult the product manual. In general:
To get started remove the PC and power supply (if you purchased one) from the box. If you have a system with a pre-wired AC power adapter you can plug that into a wall outlet. If you selected a system with a terminal block you may need to wire the system into your DC power supply or an AC power adapter.
In order to set up the system you’ll need a keyboard, mouse, and display in order to perform the first time setup. Start the system by pressing the power button (if you selected auto-power on your system will start when plugged in).
If you selected a pre-install operating system from OnLogic such as Ubuntu or Windows you will be prompted to create a user account or login to an existing account. If installing your own operating system, follow your preferred provisioning method.
Ensure you are using a PC that is rated for your environment: operating temperature, input voltage, shock, vibration
Ensure to adhere to any certification requirements for IT equipment: Class 1 Division 2, UL Requirements, etc.
Use a weather resistant enclosure when appropriate to shield IT equipment from ambient conditions
Users that have these expertise should expect device setup to take less than 15 minutes for your device to be ready to connect to your existing AWS IoT Console depending on network availability.
As the OnLogic solution does not include any production environments in AWS cloud as such the user is responsible for setup, deployment, and maintenance of their AWS applications and following AWS best practices to ensure operational excellence and security. OnLogic AWS Greengrass Compatible IoT Edge Gateways can be used in any AWS Region or Availability Zone that supports Greengrass. Please ensure to adhere to any importation requirements if deploying outside the United States or European Union as there may be additional regulatory requirements for IT equipment.
To learn more about AWS IoT Greengrass, see and.
Refer to the online documentation detailing the needed for AWS IoT Greengrass. Follow the instructions in the following sections:
Follow the online guide to . Refer to the instructions in the following steps:
. For development environments, you can use the option “Use long-term credentials from an IAM User”. An example of how to do this is shown below:
export AWS_ACCESS_KEY_ID=<the access key id for your user>
export AWS_SECRET_ACCESS_KEY=<the secret access key for your user>
Follow the instructions online under the section to create a simple component on your device.
Follow the instructions online at to upload your component to the cloud, where it can be deployed to other devices as needed.
Follow the instructions online at to deploy and verify that your component is running.
OnLogic does not offer technical support for software issues related to AWS services. Contact your technology integration resources or partner to help resolve software issues. Due to the number of different systems OnLogic offers we have a to answer commonly asked questions and offer preliminary troubleshooting information.
For Hardware support you can contact the OnLogic support team at or 802-861-2300 ext. 2 (8:30 AM to 5:00 PM EST). For responses via email and voicemail we strive to respond the same business day. If received after normal business hours we will respond in the order that they were received. Once an RMA is received normal turnaround when parts are available is 5 business days
All OnLogic systems come with a standard 2 year warranty (unless otherwise stated). For additional information the following resources are available:
