Not sure where to post this; hopefully someone will see it here!
In any case, according to many posts I've seen around, beginning with 2003 server, the old idlewinstationpoolcount registry optimization is no longer necessary, as the idle count is dynamically managed. What I was wondering is if there is anything out there from MS on this for server 2003?
If I do chenge the registry entry on a 2003 server, what is the effect? Nothing? Worse performance? This is really a part of my attempt to put together a detailed list of optimizations cobbled together from multiple sources, along with simple explanations for each one. I am trying to make certain which settings are no longer used and why, and I'm hitting a wall on this one.
Assistance would be greatly appreciated...
Ben Towers
To quote MS:
"The IdleWinStationPoolCount value controls the number of idle sessions created by the server during startup. Each idle session loads an additional instance of Winlogon.exe and Csrss.exe in memory. This can consume more than 2 megabytes (MB) of memory per session"
The number is more like 10 MB, but it's a drop in a bucket. The only value in having idle sessions ready to go is that it may slightly reduce logon times, especially when the server is handling dozens of simultaneous logon requests. I haven't played with this setting before, but I suspect it won't speed things up much (W2K3 might even ignore it).
This article is worth a read:
http://www.thomaskoetzing.de/index.php?option=com_docman&task=doc_download&gid=135
Alan Osborne
President (MCSE, CCNA, VCP, CCA)
VCIT Consulting - Citrix/Terminal Services Remote Desktop Solutions for SMB
VCIT website My Blog