Re: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts
- From: "kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 8 Apr 2008 23:24:31 -0700
footswitch wrote:
Hi there. I'm having this issue with a rather *fresh-install of SBS
2003 (no Service Packs)*.
Before fresh-installing, i had this configured just as I wanted. But
now, I can't seem to find my way through this.
Please, can anybody tell me: how can I limit AND/OR allow to choose
which remote session to login to (since the same user can create two
sessions+console session), when using remote desktop to access SBS
2003, BUT in a way that new connection attempts are still allowed
(automatically replacing active connection(s))?
BASICALLY I'M TRYING TO CONFIGURE IN MY SERVER WHAT WOULD BE THE
WINDOWS XP BEHAVIOR REGARDING REMOTE DESKTOP CONNECTIONS.
This means I currently have two problems.
The server is allowing two concurrent connections. I tried to mess
around with the Terminal Services Configuration to limit that, but
that brought me a "hidden issue" that I didn't have in the past.
Consider the following scenario:
- You remote desktop into your server;
- Connection drops (due to an internet-related problem, for instance),
and you eventually have to leave your current location, so you just
close down the RDP window, expecting to finish your server
mainteinance later;
- *EDIT:* or you just lock the session in some computer you were
using, and suddenly had to leave in a hurry, forgetting to disconnect
the remote session;
- When you try to remote desktop again at a later point, the
connection is almost immediately refused (my laptop OS is in
Portuguese, so I can't really tell what the precise message is, but
it's something like: "This computer couldn't establish a connection
to the remote computer.
Try to connect later. If the problem persists, contact the remote
computer owner or the network administrator.")
*The behavior I'm looking for is something like:*
- Server would accept new connections every time, "kicking" the
currently active connections in the case of a successful login;
- Users would login to active sessions and not to new ones - this
allows to continue the interrupted work.
Thank you in advance for your time and support. If you have any
further questions, please feel free to ask.
Kind regards,
Luis Domingues
(footswitch)
Additional to Russ's post, you can also install the Windows 2003 admin tools
on an XP Pro workstation and remotely connect to terminal services mananger,
logging out or reseting orphaned sessions as needed.
You can limit admin sesssions to one, but IMHO this isn't a good idea. Use
the posted methods as described.
--
/kj
.
- Follow-Ups:
- Re: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts
- From: Russ \(SBITS.Biz\)
- Re: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts
- References:
- Prev by Date: Re: Replace SBS Server
- Next by Date: Re: Small Business Server 2003 in an existing Active Directory dom
- Previous by thread: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts
- Next by thread: Re: Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts
- Index(es):
Relevant Pages
|
Loading
