Hi,
When I'm using Terminal Services, often when I do a ctrl-c and copy some text on the remote server, the cpu meter in taskmgr is PEGGED for about 5 minutes. I'm not copying a massive database table, I'm talking about selecting a 5-word sentence and copying that. (This is on a LAN, 100mbps)
I had originally thought it was just coincidence--that some other user just happened to start some huge process the very second I hit ctrl-c, but I've ruled that out. It doesn't happen every time, but it's happened enough that I know it's definitely the ctrl-c/ctrl-v that pegs the cpu. Several times, the MSTSC window has gone dead and I had to log on as admin in another session to kill the first--since I couldn't even kill the MSTSC window in the client--not even via the client's taskmgr!
Is there a known issue with this, or are the keyboard shortcuts, like ctrl-c, remapped to something else that would cause this? Thanks,
--jsteph
When I'm using Terminal Services, often when I do a ctrl-c and copy some text on the remote server, the cpu meter in taskmgr is PEGGED for about 5 minutes. I'm not copying a massive database table, I'm talking about selecting a 5-word sentence and copying that. (This is on a LAN, 100mbps)
I had originally thought it was just coincidence--that some other user just happened to start some huge process the very second I hit ctrl-c, but I've ruled that out. It doesn't happen every time, but it's happened enough that I know it's definitely the ctrl-c/ctrl-v that pegs the cpu. Several times, the MSTSC window has gone dead and I had to log on as admin in another session to kill the first--since I couldn't even kill the MSTSC window in the client--not even via the client's taskmgr!
Is there a known issue with this, or are the keyboard shortcuts, like ctrl-c, remapped to something else that would cause this? Thanks,
--jsteph
