Taking control with Remote Desktop Services Manager from workstation console

When I run Remote Desktop from the console of my computer Windows 7 I get a message saying that if I run this tool from the console some options are disabled as Remote Control and Connect.
Is there any way to enable these possibilities from the console?
Thanks, VOR

Hi,
No, there is no way to enable them for use from the console. These features
require that you be within a Remote Desktop session in order to use them. For RDP 8.0/8.1 sessions the situation is different in that you can now perform a shadow (Remote Control) by launching mstsc.exe with
command line switches even from the console.
-TP

Similar Messages

Remote Desktop Service Manager - configure permissions for Remote Desktop Users to Send Message, Disconnect, Logoff

Hello, dear colleagues.
We are using Windows Server 2012 R2 as Remote Desktop Server. Also use Windows Server 2008 R2 with Remote Desktop Service Manager to control RDS user sessions (Send Message, Disconnect, Logoff, Query Info).
Send Message, Disconnect, Logoff options works only for users in Administrators group.
I can't to configure permissions for Remote Desktop Users, specific user or AD group.
To set permissions I'm running RDS Host Configuration on Windows Server 2008 R2 and connect to Windows Server 2012 R2. Then double-click
RDP-Tcp, Security tab, add specific user account , AD group or configure
advanced permissions
for Remote Desktop Users.
But, as I sad above, these options works only for users in Administrators group. How to make it work for Remote Desktop Users or specific user, AD group?
Thanks.
P.S. If move specific user from Remote Desktop Users group to Administrators group on
Windows Server 2012 R2 - it works.

Hi,
You can prevent administrators from changing the permissions for a connection by applying the
Do not allow local administrators to customize permissions Group Policy setting.
This Group Policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
Apart there is one command with which you can set the permission for that check the related
article. Additionally checkthis
thread for more detail.
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Users not showing in Terminal Server Under Remote desktop services manager and Task Manager

Hi All,
I have a problem here in Terminal Server. I can not see the users logged in to Server but i know users are accessing the files and currently working.
1. From the Task Manager-- Show processes from all users displayed all the processes accessing by users.
2. From the Task Manager-- From Users Tab--No users list at all
3. From the Command Prompt- Query users-- No information
4. From the Remote desktop services Manager-- used with IP/Host name-- Still can not see the users list and processes. So i can not kill the session if needed.
Enviroment:
TS CALS 20 currently accessing 15 users
VM-WARE GUEST: 2008 RS Terminal Services/Remote Desktop services installed
Windows up to date-- Just updated last month
Problem is here for long time. Just couldn't find the time to trouble shoot.
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Hi,
Thank you for posting in Windows Server Forum.
As you have tried many steps, I suggest you to try below command line and power shell command if successful in your case. Please try below command with Admin access:
qwinsta /server:<servername>
To kill a session use rwinsta to delete the session specifying the ID number:
rwinsta /server:computer01 3
Here's the list of command line tools for Remote Desktop Or, you can use PowerShell:
Get-RDUserSession and Disconnect-RDUser
Please check the list of Power Shell command from
this link.
Hope it helps!
Thanks,
Dharmesh

Remote Desktop Services Manager Hangs / Crashes

Hi,
I have windows server 2008 R2 based remote desktop environment. When i access remote desktop services manager to manage domain users session, it hangs / crashes. I am not unable to add any other computer to manage as well. Same was working fine in Windows
server 2003.
Any valuable suggestion????
Regards
Rox_Star

Hi,
As a test, please create a new domain admin user account, log on to the server with it, and then open RDS Manager. Do you see the same issue with the new account?
Thanks.
-TP

Audio service hangs on Windows Server 2008R2 with Remote Desktop Services

Hello!
I have some terminal servers on Windows Server 2008R2. Users have the ability to use web browsers (IE, Firefox) with the included Flash Player, IM clients / Internet
telephony (Skype, ICQ), Windows Media Player, Office, and a specific internal software (works with MS SQL). I have the following problem: the Windows audio service hangs up that leads to hangup of all programs which use it, such as: any sites in Internet with
a flash content (in all browsers), ICQ, Skype.Even logging out the session hung when tried to lose a sound. It's impossible to stop or restart service from the services.msc the service just hang with status "restarting". To stop service I terminate svchost
process. As soon as the audio service is stopped - all programs start to work correctly (certainly without a sound). This problem appeared not suddenly - periodic hangups of programs on servers were marked long ago (more than half a year), but not directly
were connected to audio service, especially there were they rather rare (on the average once a week - two) and were corrected by server reset. The error message:
Error container , type 0
Event name: AppHangXProcB1
Reply: No data
Ident CAB: 0
Problem signature:
P1: iexplore.exe
P2: 9.0.8112.16446
P3: 4fb57c8f
P4: 77c1
P5: 131200
P6: svchost.exe:AudioClientRpc
P7: 0.0.0.0
P8:
P9:
P10:
shall suggest an idea about a sound service, but in Event Viewer has no Windows Audio events.
Recently I updated Skype to the last version 6.0.66.120. Before was 4.2.35.155 because versions 5хх on Windows2008R2 with the Remote Desctop Services actually don't
work, if users at the server more than one or two. We checked the sixth version by the test machine with the terminal environment and very were delighted to its normal working capacity. However after installation of this client on production servers it appeared
that hangups of programs on servers began to occur on the average time at an o'clock in case of an average daily load (about 20 users on one server). If you have worked one or two users, problems weren't watched. Internet search led me to the support page
Skype, where the Windows 7 x64 user faced a similar problem in the fifth version of the program. But the solutions proposed by the support team does not help me. In addition, I found the advice to disable enhancements in the properties of the playback device,
but it is impossible for the "Remote Audio" device.
At the moment, on servers where I updated the Skype, I disabled the audio service. If within a reasonable time, I do not find a solution, I will have to revert
to an older version of Skype, but I would like to solve the problem completely.

Enable the Allow audio and video playback redirection Group Policy setting
To allow audio and video playback when connecting to a computer running Windows Server 2008 R2, you must enable the Allow audio and video playback redirection Group Policy setting. The Allow audio and video playback redirection Group Policy setting is located
in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection and can be configured by using either Local Group Policy Editor or the Group Policy Management
Console (GPMC).
For more information about Group Policy settings for Remote Desktop Services, see the Remote Desktop Services Technical Reference (http://go.microsoft.com/fwlink/?LinkId=138134).
Is this policy applied? Refer:
http://technet.microsoft.com/en-us/library/dd759165.aspx
Also, have you tried update the audio device driver for this terminal server?

How to set a default printer using vbs on windows 2008 R2 with remote desktop services

Hello
It seems I wasn't in the right places before / threads. BIG Sorry.
Here's the problem: I have this VBScript:
On any computer, the Default Printer "HisBadPrinter"
strPrinterName = "mySuperPrinter"
Set objPrinter = Helper.CreateObject("WScript.Network")
objPrinter.SetDefaultPrinter strPrinterName
In Xp, Windows 7 it work perfect, The default printer is being changed.
But in Remote Desktop on Windows Server 2008 R2 it is not working, with any type of account (Administrator, user, powerUser...) "HisBadPrinter" is always the default printer and it's always printing on it without any error messages.
Help Please.

Ok, here what I have in my ControlPanel > Devices and Printers
Adobe PDF (redirected 3)
Brother HL-4150CDN series on infovm1dc (redirected 3)
Generic / Text Only (redirected 3)
HP Color LaserJet 3800 PCL 5c on infodc3 (redirected 3)
Microsoft XPS Document Writer
Microsoft XPS Document Writer (redirected 3)
PDFCreator (redirected 3)
Now Here what I got when I executed the bit of code :
TS011
Adobe PDF (redirected 3)
TS013
Microsoft XPS Document Writer (redirected 3)
TS012
Generic / Text Only (redirected 3)
TS015
Brother HL-4150CDN series on infovm1dc (redirected 3)
TS016
HP Color LaserJet 3800 PCL 5c on infodc3 (redirected 3)
TS014
PDFCreator (redirected 3)
TS002
DIRECT - Brother HL-2460 (redirected 2)
TS006
PDFCreator (redirected 2)
TS003
Fax (redirected 2)
TS005
Microsoft XPS Document Writer (redirected 2)
TS007
Brother HL-2460 on infodc3 (redirected 2)
TS004
Microsoft Office Document Image Writer (redirected 2)
TS001
Brother HL-4150CDN series on infovm1dc (redirected 2)
XPSPort:
Microsoft XPS Document Writer
There is no printer called "\\ALPHA\HP LaserJet P2015 Series PCL 6".
OK

Install Remote Desktop Services Failed on Windows 2012 Server

I understand RDS is not recommended on DC due to security consideration. However since I want to play it at home, it is not much a concern. Such scenario works fine on Windows 2008 R2. But on Windows 2012, the RDS (session-based, have not
tried VDI, but expect same result) installation always fails and is incomplete on DC.
In \Administrative Tools\Terminal Services, I only have RD Licensing Diagnoser and RD licensing manager. The remote desktop service management service cannot be started (Error code: 0x88250001). Is there any extra configuration needed for RDS
working on Server 2012 DC or before the installation? Thanks.
Update: this issue has been solved in Windows 2012 R2 Server. According to
http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
"Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller. In addition, we published
guidelines for how RD Session Host could be used without the RD Connection Broker."
The guidelines (http://support.microsoft.com/kb/2833839/en-us) primarily apply to Windows 2012 Server.

Asinine. Simply Asinine. Microsoft took it out because of $GREED$.
RemoteDesktop has become so popular, they had to break it to make more money. Thats why they discontinued SmallBusinessServer.   If this practice is so tabooo... Why did MS go the opposite direction with SBS 2011 Premium Cal's? SBS2011
had DC, Exchange, RDS and Sharepoint,SQL, RemoteWebWorkplace, OWA all working in perfect harmony. It is an untrue statement then, that it was "allowed but not recommended"
Now you by Server2012 (core + two virtual) and its not enough for all this.
You need at least another $700 for another sever licence to have it all
and who knows if SQL will run on a DC, or Exchange, or R-DERP server. Another reacherous bridge to cross.
By far, the absloute worse release since Millennium. The product is not ready for production, we broke our rule of waiting until the first SP1 upgrade for this and Exchange 2013. Problems with USB drivers and networking running extreamly slow.
Our 2003 SBS server was at least three times as fast, and this server has SAS and SSD drives running. It can't get out of its own way, and IE10 is the most unstable piece of crap to come out of Redmond. Open wide and swallow - Mother Microsoft
knows whats best for you. YOU WILL EAT OUR SLOP AND LEARN TO LIKE IT.   Server2012 AKA "METRO-SERVER"
Now here I sit after 50 Hours back to back setting up a new R-DERP server 2012, AD, Have my RDP licences in my hand at $100 each, and WTH does Microsoft care if I install it on my DC. ITS MY DC. And the cost savings versus the "risk" was
previously MY decision.
Sure, I can install a couple of Virtual HyperV sessions but they are so tempremental to a power-outage in a small business its not worth it. I have to double up my server hard drive resources, buy a $800 battery backup unit and make sure to attach
the cable, and even then, if that Bi**H does not shut down properly, one bit goes awry in a VHD or VHDX file and you are screwed. Restore from lastnights backup and forget about todays work. Not to mention it will probably take a half day to try
to fix it, then recover it then tell the 30 users they lost a days worth of work.
HYPER-V is for test servers and has no place in a small (micro) business environment. 5-30 users.
Microsoft's solution, buy another server. Need Exchange? Buy another server or take the risky cheapskate route and spin up some VHD's. Might as well put a gun to your head and play russian roulette, at least you know you have a one in six
chance of failure. With MS, its a 100% failure for a dirty shutdown power loss, motherboard blows, memory goes corrupt in a few years, your conventional method of recovery is gone, and you have some upchucked VHD file to try to recover some of TODAYS
data from.
Screw server 2012 forever.
I will sell 2008 and SBS2011 Premium unitl it rots in hell like XP (of which there is NOTHING wrong with for the average, WORD, EXCEL, OUTLOOK and QUICKBOOKS that all SMB's use. Its MS $GREED$ Grab the world by the B**ls and squeeze with all
your might to squeeze every dime you can out of *SMB* because big business is going to run thier 2003 Exchange and 2008 servers into ground before they switch to this garbage.
YOU CANNOT INSTALL EXCHANGE 2013 on DC , OR on R-DERP server.
Go buy another server license and server or MOVE TO THE CLOUD and get fleeced every month.
I have 30 DC/R-DERP/Exchange and SBS2011 Premium servers all running for years in perfect harmony, locked down with security so the users can't even WIGGLE with something they are not supposed to work with. They get their apps, cannot install anything
and all these servers are running just fine behind the firewall and perfectly save. The track record of this combination is 100% stable and is up 24/7/365 with no problems. Do yourself a favor and throw this 2012 into the river, you don't need
any weights because it is LEAD and will sink to the bottom by itself.
Why, you ask? Official is "Its for your protection" The real reason? To sell you more $700 server licences.
Maybe for SMB, we start selling Linux NAS Servers, host the Exchange in the cloud and be hearded like cattle to the Microsoft slaughterhouse. One way or another, you are going to bleed.    A little each month to move to the cloud, or
a small fortune if you want to have it in house. Microsoft wants it to be more expensive to have in house. No more buying a server and running it for six years before you upgrade. They can't have in house servers competing with their cloud,
and small businesses are the low hanging fruit ripe for the pickin'.

License questions on Remote Desktop Services

Hi all,
I have 3 Win2012 Servers installed with Remote Desktop Service enabled and running, and we haven't deployed the Remote Desktop Server Role. As 2 of them are at the remote locations, we will use remote desktop connection to connect
from the server at our office to others for administration and problem solving.
We would like to know under this situation (connect one server at each time), any license is needed to purchase?
Thanks!
BRgds/Edward

this article explains the usage for the /admin parameter:
http://blogs.msdn.com/b/rds/archive/2007/12/17/changes-to-remote-administration-in-windows-server-2008.aspx
I'm not sure if this has changed in WS2012 (I suspect not), but I've not personally spent any time with WS2012 RDS yet.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
or what's the problem,
Mahmoud Sabry IT System Engineer

this issue maybe will be fix by latest version, we still waiting for it
maybe your issue can be fix using this methods
https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
http://shawn.meunier.com/?p=1#comment-43

Remote Desktop Services Error when trying to send a message to a user in the collections

We are implementing RD for thin clients and when I try to send a message to a user I get an error that states,: Unable to send a message to session X on (SERVER NAME.COM). WTS API Failed
Is there a service that needs to be turned on?
Thanks EPK

Hi,
Thank you for posting in Windows Server Forum.
Before sending message please check following considerations.
- You must have Message special access permission to send a message to a user.
- You can send messages only to users whose sessions are in the active or connected state.
- You can send a message to a user session in Remote Desktop Services Manager by using the Send Message action.
Send a Message to a User
http://technet.microsoft.com/en-us/library/cc754124.aspx
Else you can also try below script and check the result.
Send-NetMessage - Net Send / Msg.exe
http://gallery.technet.microsoft.com/scriptcenter/Send-NetMessage-Net-Send-0459d235
Hope it helps!
Thanks.
Dharmesh Solanki

Windows 2008 Remote Desktop Services - Word Spell Check

We are running Windows 2008 servers on our network with remote desktop services (terminal services). We currently experiencing a challenge with Word 2010. The spell check feature is not working, when you try and run it gives an error "Microsoft Word
can't check the spelling or grammar in this document. An error occurred and this feature is no longer functioning properly." After about 5 clicks it comes up with Cannot find the proofing tools for English (Australia). It eventually it works, need to
get it to work the first time. I have searched all around but can't seem to find the answer.

I'd try them over here.
Word
2010 forum on Microsoft Answers
Word IT Pro forum on TechNet
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

How do I remote control a user in remote desktop services in Windows Server 2012?

Hello,
we currently operate in a 2008 R2 environment with the majority of clients connecting to our terminal servers. We use the remote control feature in terminal services manager to connect to a users session when a user phones our helpdesk with
a question / issue.
Just today I've installed 2012 server on a hyper-v virtual machine to have a play with it. I've installed the Remote Desktop Services and noticed this remote control feature is gone. I can still log off or send a message to a user, but I can
no longer remote control their session.
I've seen one or two other posts stating this feature has been removed completely.
So, a couple of questions:
1. How on earth do I "shadow" or connect to a users session now?
2. If I have to go third party to get this functionality back, what's the best software on the market for this and does it support remote connecting of users who have their RDP session span multiple monitors? (2008 R2 doesn't)
3. Will Microsoft ever bring this feature back? as at this stage I doubt we would move to 2012. This is the one feature that is crucial to the day-to-day running of our helpdesk.
Cheers.

A large percentage of our IT support business is through remote management. Most of our large enterprise customers are Terminal Server environment (now called Remote Desktop - why does Microsoft have to change EVERYTHING - how would they feel if I changed
the colour of the sky from blue to red just because I could?).
Last week, after much expense to the customer (and realising that there WOULD be some cosmetic headaches to contend with Server Management) we installed a new "Remote Desktop Server" for them and shifting them from 2003 - a big leap so we discovered.
During deployment it came as a HORRIFIC surprise that we could not remote control user's sessions!
Yes, we ARE to blame for not fully realising the cock-up Microsoft has made for us. We should have fully researched every detail of what changes they made and what they have robbed us of.
Firstly, the removal of the ability to fully manage user's sessions came as a HUGE blow!
The remaining multiple issues that followed (including the hugely cumbersome and SLOW way of accessing user's sessions and the false information that the console was reporting users logged in when they had already logged out) suddenly resulted in us decommissioning
the new 2012 installation in favour of a 2008 R2 installation.
Some may ask; Why not use "Third Party" apps to counteract the issue? Firstly; why spend MORE and why use a third party app that "is as" cumbersome to use just because of a freaking feature that Microsoft deemed a "security risk" - for G.D sake!
We have now been directed by management to convince customers that a move to 2012 is NOT recommended - good choice boss, I love you!
The question is; will Microsoft re-implement this feature and fix Server Management performance/accessibility in a future release before 2008 R2 is no longer available? Probably not - it looks like their stubbornness to forge ahead with their craze mind-set
of transforming their products into something that is now annoying millions (including their bloody push towards everything-cloud which NONE of our customers want anything to do with).
Microsoft! Get us back on to your side and take a step back, take a deep breath and listen to consumers!

To install Remote Desktop Services User CAL on Windows Server 2008 R2 Enterprise Edition with SP1

Dear Sir,
Presently we have installed Windows Server 2008 R2 Enterprise Edition with SP 1. And now i would like to install Remote Desktop Services User CAL on this server. I have 25 digit product key of Windows Server
2008 R2 Remote Desktop Services User CAL (20). Downloaded this product key from our MSDN Subscriptions.
Kindly suggest me how to install (CAL server with product key that i have) and configure remote desktop services on my above existing server also how to point other server with my CAL server.
Thanks

Hi,
1. Install Remote Desktop Session Host and Remote Desktop Licensing Role Services using Server Manager.
2. Open RD Licensing Manager (licmgr.exe), Activate your server, then install your license
3. In RD Session Host Configuration (tsconfig.msc), set the Licensing mode to Per User and Specify your RD Licensing server name (itself). If you want you may configure these two settings via group policy setting instead. The path of the
group policy settings is Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
4. You may point other RDSH servers to your RD Licensing server using RD Session Host Configuration or via group policy as mentioned above.
5. Optionally you may consider installing other Remote Desktop Role Services such as RD Gateway, RD Web Access, RD Connection Broker, etc.
-TP

Can't log on with administrator user by finding the message "The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.

Hi,
Now, my Windows 2008 R2 Enterprise server are running in the domain. It have problem about some one in my team have remote my server with the user administrator while I'm remote it now. It make my session loss. I tried to remote it again but I found
the message at the log on screen about "The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on."
Now, nobody can't remote with administrator user into this server. I have check the application log. I found the error message like this.
++++++++++++++++++++++++++++
Source: Desktop Window Manager
Event ID: 9003
Detail: None The Desktop Window Manager was unable to start because a composited theme is not in use
++++++++++++++++++++++++++++
Source: Microsoft-Windows-Winsrv
Event ID:10002
Detail: The following application was terminated because it was hung: mmc.exe.
++++++++++++++++++++++++++++
Source: Microsoft-Windows-Winsrv
Event ID:10002
Detail: The following application was terminated because it was hung: javaw.exe.
++++++++++++++++++++++++++++
Source: Microsoft-Windows-Winsrv
Event ID:10002
Detail: The following application was terminated because it was hung: Explorer.exe.
++++++++++++++++++++++++++++
Source:Desktop Window Manager
Event ID:9009
Detail:The Desktop Window Manager has exited with code (0x40010004)
++++++++++++++++++++++++++++
Source:Microsoft-Windows-Winlogon
Event ID:6005
Detail:The winlogon notification subscriber <Sens> is taking long time to handle the notification event (Logoff).
++++++++++++++++++++++++++++
In addition, I can log on this server with other user but I can't log off by it's showing the message "please wait for the system Event Notification service". Normally, the problem can solve by reboot the server. But how can be solve this problem
by we do not reboot the server?

Hi,
The cause of unable to remote back to the server seems to be services hung, please try to reset session as the article below guides to see if it works:
Windows Server: Remote Desktop Error: The task you are trying to do can't be completed because Remote Desktop Services is currently busy
http://social.technet.microsoft.com/wiki/contents/articles/28636.windows-server-remote-desktop-error-the-task-you-are-trying-to-do-can-t-be-completed-because-remote-desktop-services-is-currently-busy.aspx
If the issue can always be re-produced, then I would suggest you fully patch the system.
More information for you:
The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on
https://social.technet.microsoft.com/Forums/windows/en-US/c58bfbd5-1d63-47e3-a489-6d8c8778b76b/the-task-you-are-trying-to-do-cant-be-completed-because-remote-desktop-services-is-currently-busy?forum=winserverTS
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

2008 R2 Remote Desktop Services Problems With Older RDP Clients

I recently deployed a new 2008 R2 server to serve as a Terminal Server (Remote Desktop Services) for about 30 people. The new server is replacing a 2003 server. I expected the new machine to be a considerable upgrade and was looking forward to happy people
and less problems. Reality is I am finding several unexpected headaches - discouraging considering the amount of money we have spent on the new machine.
Most of the users connect via HP thin clients, they are the T5510, T5520 and T5530 thin clients. What I have found is performance issues when connecting via these thin clients. I believe the RDP client on these thin clients is RDP 5.5 or earlier. And I do
not believe it is possible to upgrade the RDP client version on the thin clients - I guess they are to be seen as "disposable".
The performance issues are: black blocks appearing when connected - and I have deselected bitmap caching - makes no difference. When typing in certain places the display of the typed characters could not keep up with the user. And lastly I have a weird thing
that just popped up today; where if the user goes to Google it freezes up their entire environment - I cannot even remote control the user/session - why this came up today and was not a problem before I am not sure.
With all of the above issues I have found that the problem goes away or does not exist if I connect to the server using an RDP client on an XP or 7 computer. So I have to conclude the RDP client is the problem.
Does anyone have information on this? Is there anything I can do as far as configuration on the server to allow me to use these older RDP clients? Do I have any alternative other than buying new thin clients?
thanks!

From your description, I also agree that the problem may be in the top RDP client.
1.
HP Compaq t5510 Thin Client:
Operating System: Microsoft Windows CE.NET
RDP Client: Remote Desktop 5.1 Add-On
2.
HP Compaq t5520 Thin Client:
Operating System: Microsoft Windows CE 5.0
RDP Client: Remote Desktop 5.5 Add-On
3.
HP Compaq t5530 Thin Client
Operating System: Microsoft Windows CE 5.0\6.0
RDP Client: Remote Desktop 5.5 Add-On
We can try to optimize two ways.
1.
Upgrading Driver – Network for Thin Client
(1) HP Compaq t5510 Thin Client:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=420576&prodTypeId=12454&prodSeriesId=420575&swLang=13&taskId=135&swEnvOID=1054
(2) HP Compaq t5520 Thin Client:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=500833&prodTypeId=12454&prodSeriesId=500832&swLang=13&taskId=135&swEnvOID=2051
(3) HP Compaq t5530 Thin Client
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01087297&prodTypeId=12454&prodSeriesId=3341951
Upgrading RDP to the latest version of HP Web site.
Let thin clients use to connect to the Remote desktop server with low load.
(1) Open the Remote desktop client in customer’s Thin Client
(2) Click Advanced option. In choose your connection speed to optimize performance area, you can select the low load option. For example, modem(56kbps).
I noticed that you have deselected bitmap caching in Remote Desktop Client options, but makes no difference. You can try again. Then please remember disconnect idle sessions and rational allocation of resources in Terminal Server.
Technology changes life……

Taking control with Remote Desktop Services Manager from workstation console

Similar Messages

Maybe you are looking for