asked on

Windows Terminal Server 2003

Using Microsoft Windows Terminal Server 2003, under per user licensing mode. We have some generic logins that use the same username to login into the terminal server on different laptops. We use a wireless network for the laptops and sometimes they lose there connectivity to the network for a second or two and the RDP session says "The connection has been lost. Attempting to reconnect to your session..."

The problem is, is when they reconnect instead of going back to their session they were currently on, it starts a new one and essential they lose their work. I don't want to turn on single-session per user or restrict each user to just one session at a time. Is it possible to configure it to reconnect to their previous session when they come back from these momentary network drops?

Krzysztof Pytko

Try to configure a GPO and link to the OU where your users reside

Edit this node

User Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Sessions

there you will find policies responsible for disconnected/closed sessions

You can also try to set up for test on one user those settings using ADUC

Regards,
Krzysztof

kvchmis

ASKER

"Set time limit for disconnected sessions=Enabled" and
"Allow reconnection from original client only=Enabled"

It still has the same behavior of sometimes starting another session instead of using the current one. Is there another setting that I am missing. Also I noticed the on the "Allow reconnection from original client only=Enabled" that it is for Citrix only.

ASKER CERTIFIED SOLUTION

alexsupertramp

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

kvchmis

ASKER

Right I understand that setting "restrict users to one session" to "yes", will probably do the trick; however I have several computers setup with using the same username, so i would have to change them. Most likely just being easier to buy CAL's for devices, but I really don't want to go to all that trouble if there is another way.

alexsupertramp

Ok, everyone is using the same generic username, got it. Well, i'm not sure a different kind of CAL is going to give you a different result either, and I'll say; it's hard to leverage the advantages of Windows Active Directory by giving out one generic user id for multiple users to use simultaneously. you are bound to run into other problems at some point. i have done it before but have learned to avoid it. But, obviously, I don't know your scenario. It you have to, you have to.

A.

kvchmis

ASKER

I need to reallocate the CALs to by device for our senerio. Since unellegant disconnects it is impossible to have open the same session again, unless I limit the user to just one session