If a regular user logs on to the terminal server via remote desktop, the winlogon goes to 25% CPU (on a 4 CPU system) and most actions are frozen. It hangs like that for several minutes. This is like what is described in http://support.microsoft.com/kb/324446, but that does not mention SP2 for Windows Server 2003, which this server is at. So, is the fix valid? The problem seems to really only happen when several people are logged on. It doesn't always happen. When I last looked at this by having had process explorer already running, the thread that was consuming all of this CPU was xpsp2res.dll and looking at the stack, the top several mentioned entries were ntkrnlpa.exe. I have a March 2007 version of the ntkrnlpa.exe. Any other ideas?

Anyone? I am having the same problem with Windows 2003 TS / Citrix.