Remote Desktop Connection + copy and paste

[ac2006]

Hello,

I know this is a very old issue, but I was hoping someone might have an
updated solution for it. I have several remote users who connect to their
desktops in the office using Remote Desktop Connection. Occationally they
run into the issue where they can no longer copy and paste. I've given them
the work-around.

1. Open Task Manager, highlight RDPClip.exe and click the "End Process" button
2. Click the "Applications" tab, click the "New Task" button, and type the
text "RDPClip.exe"

This works most of the time. When it doesn't I tell them to reboot the
remote machine. As you can imagine the end-users find this work-around very
annoying.

My bigger issue now is, we have some remote users who's machines have a
policy restricting their access to Task Manager. So their only choice is to
reboot.

Any updates on this issue would be great.

 

[Jose]

Hello,

I know this is a very old issue, but I was hoping someone might have an
updated solution for it.  I have several remote users who connect to their
desktops in the office using Remote Desktop Connection.  Occationally they
run into the issue where they can no longer copy and paste.  I've giventhem
the work-around.

1. Open Task Manager, highlight RDPClip.exe and click the "End Process" button
2. Click the "Applications" tab, click the "New Task" button, and type the
text "RDPClip.exe"

This works most of the time.  When it doesn't I tell them to reboot the
remote machine.  As you can imagine the end-users find this work-aroundvery
annoying.

My bigger issue now is, we have some remote users who's machines have a
policy restricting their access to Task Manager.  So their only choice is to
reboot.

Any updates on this issue would be great.

First, try to understand the issue with rdpclip and what is really
happening:

http://blogs.msdn.com/rds/comments/1089729.aspx

Now, you can kill a task from the Start, Run dialogue. For rdpclip,
you could on the remote machine enter:

taskkill /IM rdpclip

and then just enter:

rdpclip

to start it up again.

There does not seem to be a problem if you execute the rdpclip command
more than once - it will not start multiple copies.

There are options to taskkill (taskkill /? or read about it), so you
should do some testing to figure out what is the best option for you.

The tasklist program may also be useful to learn about.

You could create a desktop shortcut to a batch file (or hide the batch
file someplace) to run the two commands with more efficiency whenever
necessary.

 

[Terry R.]

The date and time was Thursday, June 18, 2009 6:35:01 AM, and on a whim,
ac2006 pounded out on the keyboard:

Hello,

I know this is a very old issue, but I was hoping someone might have an
updated solution for it. I have several remote users who connect to their
desktops in the office using Remote Desktop Connection. Occationally they
run into the issue where they can no longer copy and paste. I've given them
the work-around.

1. Open Task Manager, highlight RDPClip.exe and click the "End Process" button
2. Click the "Applications" tab, click the "New Task" button, and type the
text "RDPClip.exe"

This works most of the time. When it doesn't I tell them to reboot the
remote machine. As you can imagine the end-users find this work-around very
annoying.

My bigger issue now is, we have some remote users who's machines have a
policy restricting their access to Task Manager. So their only choice is to
reboot.

Any updates on this issue would be great.

I've haven't experienced this in using RDP.

If your workaround cures it most of the time, why not create a batch
file on the All Users Desktop of the TS and tell the users to copy it to
their workstations? That would be much faster.

Have you tried connecting drives to see if that helps?

Terry R.

 

[ac2006]

I should have mentioned that the user's policy also restricts the run
command.

However, the batch file is a good idea. I also found this, our users are
connecting through a W2K3 TS before connecting to their desktops, so this
might be the ticket.

http://support.microsoft.com/default.aspx/kb/840872

Thank you for your suggestions!

 

[Terry R.]

The date and time was Thursday, June 18, 2009 9:49:01 AM, and on a whim,
ac2006 pounded out on the keyboard:

I should have mentioned that the user's policy also restricts the run
command.

However, the batch file is a good idea. I also found this, our users are
connecting through a W2K3 TS before connecting to their desktops, so this
might be the ticket.

http://support.microsoft.com/default.aspx/kb/840872

Thank you for your suggestions!

I have users use RDP w/W2003 TS and MSO 2003 & 2007 without issue (not
both on same domains). If they're being locked down that tight, I
wonder if there might be a permissions issue somewhere. Do any users
without the restrictions experience the same?


Terry R.

 

[Jose]

The date and time was Thursday, June 18, 2009 9:49:01 AM, and on a whim,
ac2006 pounded out on the keyboard:






I have users use RDP w/W2003 TS and MSO 2003 & 2007 without issue (not
both on same domains).  If they're being locked down that tight, I
wonder if there might be a permissions issue somewhere.  Do any users
without the restrictions experience the same?

Terry R.

I think the OP says it works for a while, or sometimes, but when it is
broken - it is broken until corrective measures are taken
("occasionally").

The MSDN link reinforces this observation and also says you may not
ever have this problem, but if you do, here is what is probably
happening and ways to get it working again.

You could also whomp up a little VB Script to run if the batch file is
too awkward or doesn't work, and there are other options besides the
killtask command - it was just a suggestion!