RE: Loose Mouse on Win2k3 RD MMC

From: Bob Qin [MSFT] (bobqin_at_online.microsoft.com)
Date: 11/24/04 

Date: Wed, 24 Nov 2004 09:08:12 GMT

Hi Dan,

Thanks for your posting here.

Please run msconfig.exe to disable Startup Group and Third party services
on the Windows XP computer. What is the result?

You can refer to the following document for the detailed information:

How to Troubleshoot By Using the Msconfig Utility in Windows XP
http://support.microsoft.com/?id=310560

In addition, please try the following steps to move the hardware
acceleration tab all the way to the left.
You have to do this from the actual console of the Terminal Server and NOT
a terminal server session.

1. Right click on the desktop
2. Choose Properties
3. Choose the Settings tab
4. Click on the Advanced Button
5. Click on the Troubleshoot Tab
6. Slide the Hardware Acceleration button all the way to the left (to None).
7. Click on OK and OK to exit the dialog boxes.

Now please reboot the server.

What is the result now?

Have a nice day!

Regards,
Bob Qin
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
      From: <dfoxley@nospampacificdatavision.com>
      Subject: Loose Mouse on Win2k3 RD MMC
      Date: Tue, 23 Nov 2004 16:49:41 -0800
      Newsgroups: microsoft.public.windows.terminal_services
       
      I have a WinXP workstation with 2 monitors, an ATI Radeon 7000 series
video
      card. When using the RDP MMC snap-in I loose the mouse cursor
eventualy.
      Closing the snap-in a re-establishing the connection to the remote
restore
      the mouse. This usually happens when I am going between servers in
the
      snap-in and as well going to my desktop. This does not happen when
using the
      stand alone Remote Desktop Client. Any suggestions of what I could
do to
      fix this annoyance?
      
      Thanks,
      Dan Foxley