Re: Second terminal services user throws off first one

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi John,

There is no risk of database corruption due to one user taking over an existing session. The reason is because the session stays the same while only the PC viewing/interacting with it changes. It *is* a source of inconvenience and/or confusion to users, however.

One suggestion would be to set Restrict each user to one session to No in Terminal Services Configuration, and then use LockSingleUser2 during logon to check if there is already an existing session, and if yes display a message and then logoff.

You can find LockSingleUser2 using google.

Thanks.

-TP

John Gray wrote:
Thanks to both of you for your responses!

Perhaps I should give more detail to explain why my view as expressed
in my post applies, even though it may not result in a solution to my
liking.

I have set up two domain/terminal server logons because we have just
two (fairly expensive) terminal server licences to use a database
written by a third party, which happens to be hosted on the Terminal
Server. Locally the licensing is by PC; in the Remote Desktop
environment it is by TS Profile. So a small number of remote users
(six) has the potential to connect to this database, but only where
one user can use the first available logon, and a second user can use
the second available logon. The other four potential users would
have to access it at a different time, when one of the logons is not
then in use. It is quite possible that a user will attempt to log on
using a logon id already in use - thus cancelling the original session
and possibly causing server database corruption as the running copy of
Access (for this is the database) finds that the bottom has dropped
out of its world.

So unless I can guarantee by some automatic, non-human, method that
nobody will be able to log on with one of the two possible userids
when it is already in use, I run the risk of 'database unhappiness'
occurring.

It seems that Terminal Server is here conspiring with itself to give
the worst possible result for my situation...

John Gray
.

Relevant Pages

  • Re: Horizontal scaling - advice needed
    ... the session can be unambiguously proxied to the right backend server, ... To start with have a single database machine. ... Full database clustering is challenging, but if your site is making you lots ... For transient session state, ...
    (comp.lang.ruby)
  • Re: Sanitizing user input
    ... But if you have the different applications on different virtual hosts, you don't need to change the session id. ... A flower shop ... can afford only one server, ... And for security, a script which needs only "read" access to a database, ...
    (comp.lang.php)
  • Re: Reporing service failure
    ... I understand that when you tried to configure your database for your SQL ... Server Reporting Services, you encountered the logon failure error. ... And then configure your SSRS databases via Reporting Services Configuration ...
    (microsoft.public.sqlserver.security)
  • Re: Viewing a remote session
    ... > He mentions connecting to the server via RDP sessions. ... > software for remote control or remote support. ... When I logon to the server using RDP and their ... >>> find their session, right-click the session, and select 'remote ...
    (microsoft.public.windows.server.sbs)
  • Re: Lisp Web Development and Application State
    ... the hook for you to map back to wherever on the server you stored ... this can extend so far as to store *all* of the state ... a session or hack together a continuations/closures system that stores ... Write the "state" to the database in a single field. ...
    (comp.lang.lisp)