<div>
Found the following &quot;&nbsp;Non console terminal server sessions begin at the number one and increment <u><i><b>dynamically</b></i></u> to the physical limit of the terminal server, or the maximum number of sessions limit defined in the terminal server configuration&quot;<br />
<a href="http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/terminal-server-session-sharing-explained.html" rel="ugc">http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/terminal-server-session-sharing-explained.html</a><br />
<br />
What issues are you having?<br />
<br />

</div>


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 [http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/terminal-server-session-sharing-explained.html]

What issues are you having?



<div>
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.
</div>


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.

<div>
<div class="content wysiwyg-content">
When users connect to terminal sessions, the session ID that gets created is not in any sequence.<br />
&nbsp;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.<br />
<br />
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.<br />
<br />
Can someone tell why the session IDs are genrated in such a way and if there is a way to fix it?<br />
<br />
Thank you!
</div>
</div>


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!

Terminal Session IDs not sequential

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Remote access may refer to the connection to a data-processing system from a remote location, for example through a virtual private network remote desktop software, terminal emulation, or the activation of features of a business telephone system from outside the business's premises.