Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.
COURSE of the MONTH
15 days, 6 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Terminal server user - restrict to specific session
Posted on 2013-12-29
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
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
5
2
9 Comments
Active today
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
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
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
Active today
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
Featured Post
Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP, Windows Server…
- Ransomware
- Experts Exchange
- Windows XP
- Windows OS
- Windows Server 2008
- Windows Server 2003, Security
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions.
Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders.
Click on Start and then select Computer to view the available drives on the se…
Suggested Courses
Course of the Month15 days, 6 hours left to enroll
771 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.