Is it possible to get Remote Desktop Services running when in Sysprep Audit mode in 2012r2?

Hi,
I'm setting up some images for 2012r2 and personally like to be able to access the machines via RDP. I have broken out of the OOBE by pressing
CTRL+SHIFT+F3, however, even though RDP is enabled (System --> Remote Setting) and running (Services --> Remote Desktop Services),
when I run 'netstat -a', I cannot see any process bound to port 3389, as such I cannot connect. Have restarted the services just in case, but no dice.
I most the other OS setups (Windows 7, 208R2) this is fine (assuming you update either the password in audit mode or enable RDP login with a blank password), but the fact that nothing is listening
on 3389 means that no matter what I do, I will not be able to connect.
Is there any reason why this is the case?
Cheers
Chris
Chris

Hi Chris,
Thank you for posting in Windows Server Forum.
Can you ping successfully the respective server?
Initially check whether there is any firewall rule set which is blocking your connection. Please try to change the RDP port from following registry key and verify whether you can get access.
To change the port assigned to RDP:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On the Remote Desktop server, open Registry Editor. To open Registry Editor, Start Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Remote Desktop server\WinStations
Note: RDP-TCP is the default connection name. To change the port for a specific connection on the Remote Desktop server, select the connection under the WinStations key.
1. In the right-pane, double-click the PortNumber registry entry.
2. Type the port number that you want to assign to RDP in the
Click OK to save the change, and then close Registry Editor.
For more information you can refer following article (Point 2: You may have a Port assignment conflict).
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
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]

Similar Messages

Is it possible to get Remote Desktop to work from my Surface 2 to a local PC running Vista?

Is it possible to get Remote Desktop to work from my Surface 2 to a local PC running Vista?
I keep getting "cannot find PC" entering IP or PC name
but as a test I have set up my PC to do web hosting, and I can browse to the IP address using desktop IE and see my local web pages.
I've just found a reference that says it has to be Business Vista.
Why would Microsoft put such a STUPID restriction in?
I think this Surface thing is going to go back if so.
What about Win8 64 Pro? Will that work?

Hi,
Thank you for posting in Windows Server Forum.
Yeah, windows 8 pro can connect to surface 2. There is detailed article guide for it, please check below link.
Your Complete Guide to Using Remote Desktop on the Microsoft Surface and Windows 8
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
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]

Cannot Get Remote Desktop Service to Work

On Windows 8.1 Pro 64-bit, we went to Remote tab and enabled Remote Desktop. We entered into the Remote Desktop Users group two users who are local on the box. One of those is local admin and the other is a standard user. When we connect
to this machine by remote desktop and then authenticate, we get a message from Windows that the Remote Desktop Users group needs to be able to login through Remote Desktop Services.
I looked in secpol.msc and the Local Policies | User Rights Assignment | Allow logon through Remote Desktop Services already has the Remote Desktop Users included.
What could be going wrong here that might cause Remote Desktop to disallow authenticated users that match to the Remote Desktop users group?
Will

Hi,
Please check whether two machines are in the same network environment. And make sure if
Remote Desktop Services is running, you can follow these steps:
Press Windows + R keys simultaneously, type services.msc then press
Enter.
Check the status of Remote Desktop Services.
Roger Lu
TechNet Community Support

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

I was running remote desktop on my old mac pro running 10.4.11. Upgraded to new pro running 10.6.7 Can I get remote desktop to run on new computer?

I was running remote desktop on my old mac pro running 10.4.11 Just upgraded to new pro running 10.6.7 Can I get my previous remote desktop to
run on new computer?
Thanks

Are you talking Apple's Remote Desktop software, or Microsoft's?

Need help setting up Remote Desktop Services

This is my first server and I can't get Remote Desktop Services to work. I need to access my Server 2012 machine from my Windows 7 computer. I realize this is probably a trivial task for a server admin of any experience level, but I am utterly confused.
When I try to access https://servername.domainname.local/RdWeb, the webpage is unavailable. When I replace .local with .com, same result. Only when I use https:192.168.1.***/RdWeb it connects.
I log in and click an application. An rdp file is downloaded. I double-click the file. A warning message appears listing the URL of the remote computer (servername.domainname.local) and the gateway server (servername.domainname.com). When I log in from there,
I get the following message:
"Your computer can't connect to the remote computer because the Remote Desktop Gateway server address in unreachable or incorrect. Type a valid Remote Desktop Gateway server address."
Any help is greatly appreciated.

Hi,
The ideal method for managing a server from a client computer is achieved by installing the RSAT tools (remote server administration tools).
http://www.microsoft.com/en-us/download/details.aspx?id=39296
What these tools do is to actually install Server Manager on your client computer. However, you will need a Windows 8.1 computer to install the tools in the link above. They won't install on Windows 7. Note: The RSAT tools are available for Windows 7 but
you can only manage 2008 R2 and earlier with that version of RSAT. The RSAT tools are sync'd with the release of client and server versions.
RSAT does need a direct connection between the client and the server (as far as I know), so you can't manage your intranet server from the public Internet this way unless the server has a public IP address or - more ideally you have a VPN server set up to
access your internal network.
As Tim mentions, you can configure routers with 'port forwarding' to connect via RDP from outside your private network to the inside. If you log into the router you should see this option but it does require some understanding of what you are doing.
In this case, you would need to connect to the router's external (public) IP address. You should be careful however enabling access into your private LAN from the outside as this does open you up to some security risks.
Another option for you is to use a 3rd party solution such as logmein or teamviewer although in my opinion these are less than ideal methods.
-Greg

Remote Desktop Services Role on a Virtual Machine (VM) Requirements

Does MS recommend installing RDS Role on Hardware or Virtual Machine? I have a use case where I have about 35 people that will be using the Internet Explorer and possibly run additional piece of software. I'm having trouble determining if the RDS Role on
Virtual Machine will be able to sustain the load of so many users. Should the same performance metric used in hardware selection be appropriate to apply for Virtual Machines. We are using VMware on pretty powerful DELL hardware, which is also hosting
120 existing VMs as of now. So my questions is would VM with 4 CPU's, 8GB of RAM, 80 GB Virtual Disk and 1 GBPs NIC would be handle the job?

Hi,
Thank you for posting in Windows Server Forum.
There is no any particular requirement to run RDS on physical or virtual machine. But if you want to install RD Virtulization role then you need to see that Hyper- V role installed because “when the RD Virtualization Host role service is installed, Server
Manager checks to see if Hyper-V is installed. If Hyper-V is not installed, Server Manager will install it”. And Hyper-V role cannot be installed on virtual machine so for that you need to install on Physical machine. Other all RDS role can be installed
on virtual machine also.
Install the Remote Desktop Virtualization Host Role Service
In addition, please check below articles.
1. Remote Desktop Services: Server and client requirements
2. RDS Hardware Sizing and Capacity Planning Guidance.
Hope it helps!
Thanks,
Dharmesh

Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer

Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer, And when Installing network printers from the domain controller it reports it cannot connect to printer. I can ping all
network devices. I can connect to the internet.
On boot I get a netlogon 5719 error followed by service control manager errors 7023,7001 and a group policy error 1129.
Clients can connect to the remote application and RDP operates to connect to the server internally and externally.
The domain controller is another server 2008r2 box. I have scoured the internet but have not found any solutions that work yet.

Hi,
After referring to your post, it can be identified that the issue which you are facing is mostly due to some network issue in your environment. Please recheck your network connection issue between computer and domain controller.
Can you able to ping with IP address and also with fully qualified name of a domain controller in the users' and computers' domain. If it fails states that name resolution issue with computer and domain controller. Are you using MS DHCP Relay agent then there’s
available Hotfix for the particular Event ID. Please go through this KB 2459530 to fix the error event ID.
As per the net logon error 5719 which you are facing states that the client component of Netlogon was unable to locate a DC for the domain it was trying to perform an operation against. Below is one of the reason. If this is being logged on a DC and the event
refers to the DC's own domain, something might be preventing the client component of Netlogon from starting a network session (to itself or to another DC in the domain). The following event 7001 & 7023 states start & stop operation service. Please
go through beneath article for more details.
1. Event ID 5719 is logged when you start a computer
2. Netlogon 5719 and the Disappearing Domain [Controller]
3. Event ID 1129 — Microsoft-Windows-GroupPolicy
Hope it helps!
Regards.

Cannot run more than one instance of a remote app in remote desktop services Server 2012

All,
I installed "Remote Desktop Services (RDS) Quick Start Deployment for RemoteApp, Windows Server 2012 Style" using the instructions here http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.aspx
I need to set up an image viewing program (Olyvia) to allow students using Macs and iPads access to this windows only application in order for them to get their work done. We may have 12 or more students accessing and trying to run the Olyvia application
at any one time.
All works good, except that I cannot run the Olyvia application (setup as a remoteapp program) more than one instance at a time. That is, when I start up "olyvia" on a Mac, it works great. If I leave it up and running, and then try
and start up "olyvia" on an iPad (using different accounts), I get the following error message:
"Cannot run more than one instance of this program simultaneously. Either the program is already running, or it has not been terminated completely."
I need to understand the root issue.
1. Is this a licensing issue? So, I need to add some CALs to the RDS server?
2. Is this a application issue with "olyvia"? So, no matter what I do, it is not going to be able to be used by more than one person at a time when configured as a remoteapp?
3. Did I not "publish" the application correctly?
4. Is this happening because I followed the "quick start" guide?
Appreciate any help I can get on this. We have no problem getting CALs, I just need some help with the root issue.
Thanks,
Geoff Weatherford
CVMBS, CSU

Hi Geoff,
Each application uses different techniques for determining if multiple instances are running. If you can determine what method it is using then perhaps you could use App-V or other virtualization software.
In the best case you really should direct your question to the maker of Olyvia. The reason I said that is they specifically designed their software to prevent multiple instances, so the first question is, why? Is it related to Licensing?
Compatibility? If you knew the specific reason(s) why they are doing it and the technique used then at the point using a virtualization technique may be the best option.
-TP

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!

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'.

High availability SQL Server requirements for Remote Desktop Services in Windows Server 2012

Good night,
Thanks for reading this question, I do not write much English.
I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf, I searched in different microsoft link but I have not received a response.
Kindly appreciate your cooperation and attention.

Hi Alejandro,
I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf
If you want to know the size requirements of .mdf abd .ldf files, since they are parts of SQL database, I suggest you refer to SQL forums below to get more professional support:
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlgetstarted
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home
In addition, here are some articles regarding RDS deployment for you:
Remote Desktop Services Deployment Guide
https://technet.microsoft.com/en-us/library/ff710446(v=ws.10).aspx
Remote Desktop Services (RDS) Quick Start Deployment for RemoteApp, Windows Server 2012 Style
http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.aspx
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]

Questions in regards to server 2012R2 Remote desktop Service deployment and GPO

Hi Everyone
We have a business requirement moving to 2012R2 RDSH server. I have installed a 2012R2 member servers and enabled Remote desktop licensing role. I have activated the licenses. the servers is in operational
I have deployed 3 windows 2012R2 member server "RDS1" , "RDS2" and "RDS3".
on RDS1 I ran Add roles and Feature Wizard > Remote Desktop Services installation > Quick Start >Session based desktop deployment to complete the installation.
On RDS1 Server Manage Dashboard Page Select Remote Desktop Services > Overview. Under RD Licensing I added my 2012R2 license server "2012r2-tslic". Go to task. Edit deployment properties RD license mode to per device and click OK.
Reboot RDS1
Check RD Licensing Diagnoser everything is clear
On RDS2 I did the exact same thing ran Add roles and Feature Wizard > Remote Desktop Services installation > Quick Start >Session based desktop deployment to complete the installation.
But With RDS2 I move this server to an OU that link to a GPO with RD licensing details. after reboot the servers check RD Licensing Diagnoser I can see 2012r2-tslic specified as the license servers.
Based on this document
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx Are you suppose to configure RD license server via Remote desktop Service deployment ? Not GPO ?
Here are my questions
We currently have ten 2008r2 terminal servers in a NLB cluster. each RDSH server have in house application installed on each one of them. User connect to the 2008R2 RDSH servers via RDP connection. we have a restricted GPO apply to those
RDSH servers. user cannot do anything on RDSH servers apart from running the application and use excel. On the remote desktop session host configuration we have enable settings like end a disconnected session , Active session limit ,
remote control users session , LPT port redirection.
We push out RD license server detail via GPO to the terminal servers
Can I use our existing GPO apply the licensing server settings , desktop restriction setting to the 2012R2 RDHS servers or we should be using Remote desktop Service deployment to do the job ? If that is the case how would you transfer the
current 2008r2 environment to 2012 using Remote desktop Service deployment. is that mean I have to manually configure 1 by 1.
Please help
Many thanks

Hi,
Please see my response to you in the other thread. Please contact me via email and I will go over the basic planning and deployment steps with you which will help clear things up and get you started off on the right foot.
You should only run through the wizard and create a RDS deployment once. Then you add the various servers (RDSH, RD Licensing, RD Gateway, etc), set Deployment properties, etc.
Thanks.
-TP

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

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……

Is it possible to get Remote Desktop Services running when in Sysprep Audit mode in 2012r2?

Similar Messages

Maybe you are looking for