Of course, this may not solve your particular problem, but if you check this out, you will be able to immediately tell if this is your problem.
I recently had a Terminal Server that when people logged in, it just about crippled the server, and it was also extremely slow to log out. It turns out that there can be thousands, or even hundreds of thousands, of HP keys in the following locations in a terminal server environment. They are dynamically added when users log in due to their local printers. Over time, they add up, and can cause great problems. So you can determine if you have the problem by just checking those locations.
HKEY_CURRENT_USER\Software\Hewlett-Packard
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\ Hewlett-Packard
HKEY_USERS\.DEFAULT\Software\ Hewlett-Packard
Even after deleting them, which can be done safely (if you have any doubts, export the key first, then test), eventually the problem will return, so here is my solution:
Create the following registry script in the C:\Windows\system32 directory and name it CleanupHP.reg
Windows Registry Editor Version 5.00
[-HKEY_USERS\.DEFAULT\Software\Hewlett-Packard]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\ Hewlett-Packard]
Create the following registry script in the C:\Windows\system32 directory and name it CleanupHP_User.reg
Windows Registry Editor Version 5.00
[-HKEY_CURRENT_USER\Software\Hewlett-Packard]
Then create the following batch file in the C:\Windows\system32 directory and name it CleanupHP.bat
regedit /s C:\ Windows\system32 \CleanupHP.reg
Create the following batch file in the C:\Windows\system32 directory and name it CleanupHP_User.bat
regedit /s C:\ Windows\system32 \CleanupHP_User.reg
Open gpedit.msc and go to Computer Configuration>Windows Settings>Scripts and add “C:\ Windows\system32 \CleanupHP.bat” to the shutdown scripts.
The go to User Configuration>Windows Settings>Scripts and add the second script C:\ Windows\system32 \CleanupHP_User.bat to the logoff scripts.
For more information:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1302781474639+28353475&threadId=1247687
On Windows 2003 Server or Windows XP, you can install the User Profile Hive Cleanup Service to help close down sessions more quickly when you log out. It closes open file handles, remaps them to the default user, and runs as a service, set to automatic. It
starts and stops itself as needed, but does not run continuously. It is not necessary on Server 2008 and Windows Vista and later as it has since been incorporated into the OS as the “User Profile Service”.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1b286e6d-8912-4e18-b570-42470e2f3582&displaylang=en (Note: The documentation correctly states that version 1.6d will not operate on 64-bit versions, but if you look closely, they are actually up to 1.6g as of this writing, which does support 64-bit.)
I have not yet tested this, but I am hoping that this is also why Microsoft and Windows updates may take so long.
All the best,
Kevin Cotreau
MCSE+I, MCNE