| ... | Articles and Whitepapers |
| ... | Downloads |
| ... | Internet Resources |
| ... | Windows Server 2008 R2 Remote Desktop Services |
| ... | Windows Server 2003 Terminal Services |
| ... | About this Web Site |
| ... | Benny's Short Profile |
| ... | Benny's Biography |
| ... | Presentations 2010, 2009, 2008, 2007, 2006, 2005, 2004 and earlier |
Posted by Benny Tritsch on November 25, 2004 – updated on January 31, 2005
[Introduction] [Test Setup] [Testing Methodology] [Analysis 1] [Analysis 2] [Analysis 3]
The last test covered Windows 2000 Server. It illustrated the drastic internal system differences between Windows Server 2003 and Windows 2000 Server. The same hardware platform was used as in the previous tests, but the system was already in saturation after 45 test users were logged in.

A very good indicator for the performance deterioration seemed to be the Processor Queue Length. It was growing to an absolutely incredible value of 350. The system was almost at a complete stop and never recovered before the test users were logged out again.

This test showed in an impressive way that Windows 2000 Server was not ready for high-end hardware platforms when Terminal Services were involved. Windows Server 2003 changed this substantially. However, we still cannot recommend using hardware platforms with more than four CPUs in a Terminal Server infrastructure.