We’ve posted a new Expert Spotlight! Joe Anderson (DatabaseMX) has been on Experts Exchange since 2006. Learn more about this database architect, guitar aficionado, and Microsoft MVP.
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
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
Asked:
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
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
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
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
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
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.
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.
It does appear that noone has to deal with session IDs at this level, will hope for a vendor fix but not expecting it.
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
Accepted answer: 0 points for HeronTech's comment #a39798972
for the following reason:
Waiting on the vendor to ultimately fix this issue
There isnt a solution available from the experts - but the comments here may prove useful for anyone else having similar problems. ultimately we are still waiting on the vendor to fix how their application deals with remote desktop redirected printing - as this is the only vendor that seems to have this particular issue with redirected session ids greater than 2
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get this solution by purchasing an Individual license!
Start your 7-day free trial.
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