• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 977
  • Last Modified:

Terminal Session IDs not sequential

When users connect to terminal sessions, the session ID that gets created is not in any sequence.
 For eg. if I'm first and only user on terminal server in the morning at the office, I should get a session ID of 1, but I would get something else, and consecutive users get assigned random IDs instead of sequential.

We've been having problems with very slow performance inside terminal sessions, event logs not leaving any kind of errors, so we are looking into these anamolies.

Can someone tell why the session IDs are genrated in such a way and if there is a way to fix it?

Thank you!
0
m2chaudh
Asked:
m2chaudh
  • 2
1 Solution
 
Cris HannaCommented:
Found the following " Non console terminal server sessions begin at the number one and increment dynamically to the physical limit of the terminal server, or the maximum number of sessions limit defined in the terminal server configuration"
http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/terminal-server-session-sharing-explained.html

What issues are you having?

0
 
m2chaudhAuthor Commented:
I have done some digging and here is the main issue causing the session ID’s.
Tserver 2003 and Tserver 2000 has a known issue with ghost printers.
This happens when users log off and their virtual printers do not get removed.
We have a utility running on our customers with these servers to help clean them up.  
It is called HIVE cleaner and you have it running.

When there is a ghost printer left behind from a session the next session can not use that session number.

It is not of great concern, it does not mean that the user is still fully running, just that the counter has not been reset.
Sort of like the take a number at the butcher counter.
If there is a ghost printer the butcher lady can not replace the roll and then just keep going up.

Since your Tserver is 2003 & older and it will be replaced with a Tserver 2008R2 with way more features in the next year or so I would not worry.

The only way to stop it is to not allow client side printer mappings.
This also means we can not print to our local printer anymore.

The printing in Tserver 2008 and Tserver 2008R2 has been completely rewritten to support better local resource management.
0
 
m2chaudhAuthor Commented:
Found this to be viable answer to my problems, real problem was network congestion, therefore I was trying to close loose ends with the idea to discover the real culprit, but this isnt one of them.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now