- This topic is empty.
-
Posts
-
The Situation:
I’m trying to use for a public presentation a couple of Wyse S10 clients with an wnos.ini configuration file (RDP) to log on to an local account on an Windows 2003 Terminal Server.The Problem:
When I start the first client everything works great, automatic logon, application starts, …
But when I start the second client, this one takes the Session of the first an the first one shuts down?The local account seems to allow multiple logons, because when I use the Windows Remote Desktop I can log in as the same user a couple of times!
Need some HELP please!
Hi,
This is by design, I would use different accounts and I don’t like have many sessions all as the one user. What I do is auto login as an account based either on the MAC, serial number or terminal name.
Say you call the terminal “bill”, set this is the RDP connect statement:
Connect=RDP
Host=TS_server
username=$TN
password=$MAC
fullscreen=yesNow you create an account with the name Bill on the TS and the password based on the unit MAC. That’s it! autologin units with there own accounts.
I am assuming here this is what you want – not have the user log in,
Cheers,
-TTThe problem is that we need to use a specific software, that uses an account generated by this software, we cannot duplicate!
You can relax the requirement of only one session per user under the Terminal Services Configuration mmc snap-in.
Under “Server Settings” there is a policy that states”Restrict each user to one session”. By default it is set to “Yes”. If you change it to “No” then you can have a user logged in on multiple machines.
That said, this is obviously not a recommended practice.
Best of skill,
-BT.
- You must be logged in to reply to this topic.