Re: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts


Sorry, Russ, but the /console switch only connects if the server
*doesn't* have the two connections already "occupied" (active). It
obeys to the same rules in terms of "connecting to a destination".

Besides me, there's only one admin.
But if you would like to take a look at this scenario:
- The other admin logs on to the server, from his workstation and,
after performing the needed tasks, he leaves the session open in the
background, just in case he forgot something and has to come back to
it.
- I log on to my own session in the server, from another workstation,
and I'm performing some tasks as well. Someone calls me from across the
room, I quickly lock my station and go there to be informed that I need
to go somewhere out of the office. I immediately follow the order, I
just take my laptop and off I go.

Once at the remote site, I figure I need access to some data that I
have in my server user desktop... so I try a remote connect with my
laptop... and it fails... "the two connections limit!", so I call the
other admin and ask him "would you please disconnect your session so I
can log-on from here?", but he's not at the office right now! He
basically did the same as I did! What now? Out of ideas... Well I'm
certainly not going to ask someone from the office to force a power
down in my workstation...

Well and I don't know how often this can happen, but it sure makes me
feel useless when I don't have a solution for simple stuff like this...
:/



For now, here's what I call a middle solution:

Edit, for instance, the Default Domain Controllers Policy:
- Computer Configuration
- Administrative Templates
- Windows Components
- Terminal Services

Set "Restrict Terminal Services users to a single remote session" to
"Enabled".
This will reduce the possibility of reaching the two concurrent active
connections limit (whenever you're able to connect with an already
logged-on user, the current remote session for that user is
"redirected" to the new connection - but the same user will still have
the option of logging on to a different session: the console).

Also, in the "Sessions" sub-folder, there's the option "Sets a time
limit for active but idle Terminal Services sessions", which has an
advantage and a disadvantage:
- Although this option disconnects the session after a given time
limit, but doesn't log it off, preserving unsaved work - which is a
good thing;
- This will break our connections from time to time, and we'll have to
reconnect (if I would configure this setting, I'd leave it with a 15 to
20min time limit, otherwise it wouldn't be useful enough).



If you have any other ideas, please let me know.
Thanks for your support, guys :)

P.S.: I'm also going to take a look at the admin tools (never really
felt the need for it) - will they allow remote control of the server
over the internet? who knows they'll allow the other admin to perform
his tasks, making it unnecessary to use TS at all... Thanks for the
advice so far


--
footswitch
------------------------------------------------------------------------
footswitch's Profile: http://forums.techarena.in/member.php?userid=38931
View this thread: http://forums.techarena.in/showthread.php?t=947176

http://forums.techarena.in

.

Relevant Pages

  • Re: Rmote Access problem
    ... The client could not connect to the remote computer. ... Remote connections ... Re-running CEICW on SBS server: ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote access issues
    ... The remote connection session is disconnected or end is decided by ... when you restart the TS server. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: RDP using RPC over HTTP
    ... Remote Networking Technology Support Site - ... >server as Exchange. ... >The question is can you get the TSWeb to use RPC over HTTP. ... >start an session of RD from there, kind of RD inside RD as you suggested? ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: /remote desktop control suddenly broken - critical
    ... The client computer may not be turned on. ... Remote Desktop connections may not be enabled on the client ... Verify that Remote Desktop is enabled on the computer you are ... connection from another computer on the Windows Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Rmote Access problem
    ... And after you select the task to connect to the server desktop it just stops ... The client could not connect to the remote computer. ... Remote connections ... the network is working. ...
    (microsoft.public.windows.server.sbs)