MailBag Friday (#36)

Every Friday, we dedicate this space to sharing solutions for some of the most frequently asked questions posed to our ThinManager Technical Support team.  This weekly feature will help educate ThinManager Platform users and provide them with answers to questions they may have about licenses, installation, integration, deployment, upgrades, maintenance, and daily operation.  Great technical support is an essential part of the ThinManager Platform, and we are constantly striving to make your environment as productive and efficient as possible.



We recently purchased some industrial grade thin clients that aren’t on your XLi Compatibility List and we were able to successfully boot them via PXE and have them managed by ThinManager.  Is it possible to get XLi certification for them? Is it something we can do here? What kind of test you apply to thin client box in order to make it XLi certified?


The XLi certification is a list of units that we know will boot PXE and contain the chips that ThinManager supports. Not everything that works is on the XLi Compatibility List. It is just the list of ones we know work.


I would fill out the Request form for that unit to get it in the system. The address to request that a unit gets added is at

I would also send an email to with the Computer Company. Make, Model, etc., and what you observed about it. This may get it on the list without having a unit in our hands.





I had an error 800006df on a terminal server, which I never saw before and cannot find any information on that error code.  Can you guys point me in the right direction?


These error codes are generated from DCOM. We are documenting the suspected cause, as well as solution on the Error Codes page of our new Knowledge Base.





I recently purchased a ThinManager license and two TK-3500 thin clients.  I haven’t installed ThinManager yet, but I plugged in the 3550’s to poke around.  I’ve configured these before and I distinctly recall being able to press a key during the “system initialization” screen to bring up a configuration screen to enter IP information.  Regardless of what I press during that screen the device always goes to the PXE boot sequence and then fails as it does not find a boot disk.  I poked around your site to see if I could find a document or manual to see if I was missing something, but was unable to locate anything other than a product sheet which isn’t helpful in this situation.  What should I do?


The TK-3550 requires the PXE Server to be enabled in ThinManager.  The below link steps through setting it up and what the different options in the wizard do.

Once that is configured the TK-3550 should get it’s its boot file and connect without issue.




Our plant is currently using Uno-2053-GDA0 modules to interface the VGA and serial signals, over Ethernet, to/from the Advantech touch screens.  Will these modules still work with the new version of Thin Manager?  Will there be any compatibility issues with running the new version of ThinManager on a Windows Server 2008 operating system?


The graphic interface is VGA and the touch interface from the Advantech is connected via serial.  Both signals are transmitted over Ethernet to the server.   The Uno-2053 is still supported in ThinManager Platform 6.  There shouldn’t be any compatibility issues via our compatibility matrix found on the ThinManager Knowledge Base:




To review cost savings of using the ThinManager Platform, visit our ROI Calculator here.

To read about successful ThinManager Platform deployments, visit here.

To see when the next ThinManager 2-Day Training Session is being offered, visit here.

Tom Jordan

V.P. of Marketing - Automation Control Products