{"id":1756,"date":"2012-11-09T15:50:00","date_gmt":"2012-11-09T20:50:00","guid":{"rendered":"http:\/\/blogs.thinmanager.com\/thinclients\/?p=1756"},"modified":"2014-09-15T09:03:02","modified_gmt":"2014-09-15T13:03:02","slug":"mailbag-friday-24","status":"publish","type":"post","link":"https:\/\/blogs.thinmanager.com\/thinclients\/?p=1756","title":{"rendered":"MailBag Friday (#24)"},"content":{"rendered":"

\"\"<\/a>Every Friday, we dedicate this space to sharing solutions for some of the most frequently asked questions posed to our ThinManager Technical Support team. \u00a0This 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. \u00a0Great 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.<\/p>\n

 <\/p>\n

 <\/p>\n

We are having an issue with ThinServer.exe eating over 5GB of memory on our system.\u00a0 Are there any known memory leaks or patches that will need to be applied to this version (5.0 build 5000)??<\/em><\/p>\n

 <\/p>\n

 <\/p>\n

There was an issue related to automatic synchronization that would cause that and was addressed in Service Pack 2 for ThinManager 5.0. \u00a0Service Pack 2 can be found here:<\/p>\n

http:\/\/thinmanager.com\/support\/downloads\/service_packs\/ThinManager_50_SP2_Install.exe<\/a><\/p>\n

-TM<\/p>\n

\n

_______________________________________<\/p>\n

 <\/p>\n<\/div>\n

I have encountered a problem where my client application closed and the session remained on the ThinManager screen.\u00a0 I received the following error in the log.\u00a0 <\/em><\/p>\n

“Session ended on server. \u00a0Server initiated disconnect”<\/p>\n

Do you know what would cause this error? \u00a0How do I keep it from happening again?<\/em><\/p>\n

 <\/p>\n

 <\/p>\n

What likely happened was that you had an initial application specified that spawned child processes. When the main application died, the child processes were still alive. Because these child processes were still alive (and not visible), the terminal session remained opened. \u00a0We have a workaround for this called the Watchdog script, which is placed into a .bat file and specified as the initial program:<\/p>\n

-Create a .bat file that contains the following code:<\/p>\n

\n

start “” \/wait “Path\\to\\Program\\executable.exe”<\/strong><\/p>\n

shutdown \/f \/l<\/strong><\/p>\n<\/div>\n

-Setup ThinManager to launch the .bat file instead of the regular executable.<\/p>\n

-Restart thin client (if thin client is currently running)<\/p>\n

-TM<\/p>\n

\n

_________________________________________<\/p>\n

 <\/p>\n<\/div>\n

\n

My interactive shadowing doesn\u2019t appear to be working.\u00a0 I can see the monitor but I can\u2019t interact. \u00a0I am logged in to my ThinManager server as Administrator. \u00a0What should I do?<\/em><\/p>\n<\/div>\n

 <\/p>\n

Go into ThinManager, and under the \u201cRemote View\u201d menu there is a checkbox for \u201cInteractive Shadow\u201d. This setting is saved in the registry under the user profile.<\/p>\n

-TM<\/p>\n

_______________________________________________________<\/p>\n

 <\/p>\n

\n

I have an Arista<\/a> Office Thin Client and a USB RFIDeas<\/a> card reader (RDR-805W2AK0).\u00a0 When the unit boots and loads the RF USB module, a message is displayed that says that the reader is not found.\u00a0 Am I missing something in the configuration??<\/em><\/p>\n<\/div>\n

 <\/p>\n

 <\/p>\n

The RFIDeas pcProx USB module can be used with both the\u00a0RDR-6081AKU and the RDR-80582AK0. \u00a0It is set to the AKU by default and needs to be set to the AK0 in the module configuration.<\/p>\n

\n