MailBag Friday (#33)

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 just revised our thinclient naming standard to allow for more descriptive names, but notice the name is “trimmed” in the sessions tab view.  This appears to be consistent with the way Microsoft displays in their Remote Desktop Services Manager interface too.  Do you know if it is possible to change something in the registry so that the full client name is displayed, or are these interfaces limited to the apparent 15  character length?

The 15 character limit is a hard limit imposed by Microsoft. ThinManager does not impose this limit when naming a thin client but due to the hard limit, names greater than 15 characters will be truncated.  What you saw in ThinManager was polled directly from the Remote Desktop Session Host Server. If you want your ThinManager names to coincide with your Remote Desktop Services Manager Names, then you would need to truncate them on the ThinManager side.




I have a P&F Barcode Scanner that connects to a ThinManager Ready thin client. What ThinManager settings are required using ThinManager 4.0?

I want to use the scanner like a keyboard wedge.  The scanner has a serial module that plugs into COM2 on the thin client.  Com2 settings on terminal server match barcode scanner serial settings.  I tried the RDP Serial Redirection Module, but not having any luck.  Any ideas?

If it is a serial device that plugs into a RS-232 port, you need to add the RDP Serial Redirection module, plug the scanner into a COM port on the client, and restart the terminal.  Open the scanner program in the session and point to the correct COM port. The thin client COM port will be mapped so referencing COM 2 will give you the data from the thin client’s COM 2, for example.




I set-up non-standard DHCP where ThinManager assigns the IP address from a range.  It appears that ThinManager retains the IP address and terminal assignment based on thin client box MAC address, which is exactly what I want.  During my testing, I’ve been swapping thin client boxes on the same ethernet cable to test display clients, drive mapping, etc.  Most of the time, when I do the swap, the box is assigned its IP address quickly, but occasionally, I encounter the following error:

PXE-E51: “No DHCP offers were received

The only way I’ve been able to resolve the error is to backup the ThinManager configuration, restore from an earlier backup, then restore the latest configuration back.  I can’t pinpoint any specific event that occurs before the PXE boot stops working.  All firewalls are disabled, as we’re on a plant floor network that doesn’t connect to theinternet.  I have two Dell servers acting as terminal servers and running ThinManager in a mirrored configuration, and I use SmartSession for nearly all of my display clients.  How can we get around this problem?

You can overcome the error by restarting the ThinServer Service:

Start > run > cmd > net stop ThinServer > net start ThinServer 


Note: this will cause a role reversal within ThinManager as the master is determined by the greatest ThinServer uptime. If you want to keep your roles as they are, run the aforementioned commands first on the primary, then on the secondary.




I am currently testing using the WinTMC client on my laptop and keep receiving the following prompt:

Enter Terminal Creation Password

I’ve double checked all the passwords I’ve set on the ThinManager Server but none work.

Any help on this would be great.

Right-click on your server name next to the green thinman icon in ThinManager an select Modify.  Click “next” so that you’re now on the Unknown Terminals page.  If ‘Require Password on Unknown Terminals’ is selected, you can either deselect it or change the password so that you can get that WinTMC terminal connected.




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