asked on 12/30/2013

Terminal server user - restrict to specific session

Hello

We have a particular client running server 2008 R2 on a single server installation with remote desktop services (terminal server) configured

We have an issue (due to poor software support) where if the remote user gets a session ID greater than 2, that the remote printing does not work for the application

Windows printing works fine, its just this particular application that has a problem

Is there a way to specify a session ID for a remote user to always have the same session ID?

For instance we would want 'remoteuser' to ALWAYS have session ID 2, regardless of when other users login to this server remotely

The only other users who connect to this server are ourselves; and it does not affect us as to what session ID we get

Windows Server 2008 Remote Access Microsoft Server OS

Last Comment

HeronTech

2/16/2014

Mahesh

12/30/2013

By default, a terminal server allows you to reconnect to a disconnected session from any computer.
Only option to get same session ID for user is to configure \ restrict users to a single session on terminal server and the user must leaves the session in a disconnected state, so that user will automatically reconnect to that session only next time when connected.

Check below article to enable single session restriction through Terminal server itself or through GPO
http://technet.microsoft.com/en-us/library/cc754762.aspx

Only you need to increase timeout for disconnected sessions, otherwise if session get disconnected, it will create new session with new session ID

I hope this is the setting you are looking for. Correct me if wrong please

Mahesh

HeronTech

12/30/2013

ASKER

I was hoping for a more permanent fix than to leave the one user perpetually connected; and getting the same ID whenever they logon

I had a Microsoft case open and they basically said that its by design, and whoever logs in first gets the lower ids.

It was more if anyone else had come across this and an appropriate solution

Mahesh

12/30/2013

Thanks for confirmation

Really I don't see any option other than above as it is some kind of dynamic behavior and can't be controlled

May be its not the session id which restricting application from printing, root cause might be different and can be addressed by software vendor hopefully

Mahesh

Detlef001

12/30/2013

I don't there can be a different session id for the same , since at every log in the time interval changes. Moreover for "Restrict Terminal Services users to a single session"? Because if you set the group policy, the tsconfig should grey out the setting for the same policy. Since you could also use the tsconfig to set the policy, I am wondering whether the GP really got applied.

HeronTech

1/22/2014

ASKER

Also with a restrict to a single session option, and holding a perpetual session open, this would need to be then logged back in first each time the server reboots, which would also be an issue.
It does appear that noone has to deal with session IDs at this level, will hope for a vendor fix but not expecting it.

HeronTech

2/10/2014

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for HeronTech's comment #a39798972

for the following reason:

Waiting on the vendor to ultimately fix this issue

ASKER CERTIFIED SOLUTION

HeronTech

2/12/2014

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

HeronTech

2/16/2014

ASKER

Waiting on vendors to ultimately fix this issue