<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Terminal Server and PTEs</title><link>http://blogs.technet.com/b/askperf/archive/2012/06/12/terminal-server-and-ptes.aspx</link><description>Good morning AskPerf! One of our large call generators that we still see is with PTE depletions on Windows Server 2003 Terminal Servers (x86). Scaling your W2K3 Terminal Server can be challenging as the load increases with additional users and the limits</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Terminal Server and PTEs</title><link>http://blogs.technet.com/b/askperf/archive/2012/06/12/terminal-server-and-ptes.aspx#3507379</link><pubDate>Wed, 04 Jul 2012 08:32:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3507379</guid><dc:creator>Ratnesh</dc:creator><description>&lt;p&gt;Critical information in simple words. The limitation and optimized utilization of the resources will let you know whats going in and out of the System. Thanks for the article.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3507379" width="1" height="1"&gt;</description></item><item><title>re: Terminal Server and PTEs</title><link>http://blogs.technet.com/b/askperf/archive/2012/06/12/terminal-server-and-ptes.aspx#3503385</link><pubDate>Tue, 12 Jun 2012 11:19:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3503385</guid><dc:creator>Miroslav Reisinger</dc:creator><description>&lt;p&gt;In some cases, it is also good to look at &amp;quot;SystemPages&amp;quot; value under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management. Default should be 0, but i had one case in the past where this was set to a number like 50000 by someone on both nodes in one Itanium cluster. When running under load, system was not able to create any new threads, perform failover etc.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3503385" width="1" height="1"&gt;</description></item></channel></rss>