Re: Multiple MSTSC.EXE Processes on WinXPSP2
- From: Bill Bradley <BillBradley@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 7 Dec 2006 10:15:01 -0800
TP,
Thanks. I checked the locations, and, didn't see any TEMP files as you
described, but, did delete anything in my TEMP folder, and, also deleted the
two files in the CACHE folder.
I rebooted my work computer, and, connected three times from another
computer, disconnecting each time. I do NOT have MSTSC.EXE processes running
on my work computer, so, thanks.
I'll monitor this in the coming days, to see if it's trully fixed.
Just to make sure you understand, I connect FROM my home computer TO my work
computer, and ALWAYS disconnect, multiple times. My WORK computer had the
build-up of MSTSC.EXE processes, NOT my home computer. These suggested
deletions were being done on my WORK computer, not the home computer. I hope
that this is what you understood and meant!
Thanks!
"TP" wrote:
Hi Bill,.
mstsc.exe is the Remote Desktop Client. Normally, when you
disconnect from your session the graphical window will close
as well as the client as a whole. Under certain circumstances
the client will remain running with no cooresponding window.
Sometimes the client will be stuck waiting to access a shared
object, for example, the clipboard.
Are you using any virtual channel add-ins to the remote desktop
client, like a universal printer driver, for example?
What settings are you using when you connect to your work
computer, specifically device redirection settings, bitmap caching,
etc?
As a general rule I would recommend occasionally cleaning out
client temp files, persistent bitmap cache, etc. Here is how:
1. Close open programs, especially the remote desktop client.
2. Make sure mstsc.exe is not running. Use task manager to
terminate any instances that are still running.
3. Browse to your temp folder and delete any files/folders
contained within. For reference, the RD client creates folders
similar to _TS43FF.tmp. When browsing, make sure your
folder options are set to show hidden files/folders. Your temp
directory is located here by default:
C:\Documents and Settings\%USERNAME%\Local Settings\Temp
Replace %USERNAME% in the above path with your username.
4. Delete the persistent bitmap cache files. They have an extension of
..bmc, and are located here by default:
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Microsoft\Terminal Server Client\Cache
I am a pretty heavy user of the Remote Desktop Client, both in
features, and in the number of concurrent connections to different
servers. I have the problem you describe occasionally, most
likely due to the bugs in the drive redirection/clipboard functionality.
The majority of the time it is fine though.
-TP
Bill Bradley wrote:
I routinely connect to my work computer from home using the Cisco VPN
and RDP (NOT 6.0!). My usual method is to connect, do what I need,
then disconnect--I never logoff. I may connect several times a day.
I always connect using my Domain credentials, same as I do when I'm
actually at the local console at work.
For some reason, each time I connect, a new instance of the MSTSC.EXE
Process is created. I don't seem to be getting into different
sessions (nor do I see a way to), but, it appears that different
sessions get created. This is unlike connecting to a regular Terminal
Server, where you'd connect into the same session, and, the number of
MSTSC.EXE Processes doesn't increase.
Eventually, there are so many of these processes running, that my
system becomes unresponsive, and I have to reboot, at which time, I
get a prompt to close each Process, one-at-a-time.
I posted earlier about this, and, was told to do the following Local
Policy:
gpedit.msc:
Computer Configuration>Administrative Templates>Windows
Components>Terminal Servers
Restrict Terminal Services users to a single remote session.
Which, I did, but...this has not helped matters.
I am assuming that it is NOT normal to add a new process each time one
connects to an XPSP2 computer, so, are there any ideas as to why this
is happening, and, what I can do about it?
Thanks in advance!
- Follow-Ups:
- References:
- Multiple MSTSC.EXE Processes on WinXPSP2
- From: Bill Bradley
- Re: Multiple MSTSC.EXE Processes on WinXPSP2
- From: TP
- Multiple MSTSC.EXE Processes on WinXPSP2
- Prev by Date: Re: RDP suddenly stops
- Next by Date: Re: RDP suddenly stops
- Previous by thread: Re: Multiple MSTSC.EXE Processes on WinXPSP2
- Next by thread: Re: Multiple MSTSC.EXE Processes on WinXPSP2
- Index(es):
Relevant Pages
|