?
Solved

Update for Windows 2008 R2 RDS for HD client support

Posted on 2015-01-26
15
Medium Priority
?
252 Views
Last Modified: 2015-02-01
I had a problem around 6 months ago connecting via remote desktop to a Win 2008 R2 session host using a Windows 7 HD client.

Connection kept freezing - there was not an issue when using a non-HD client.

I was able to locate an RDS update that resolved this issue - but I did not make a note of the KB number and now have the same issue on a different server.

Anybody have any idea which update it was as I can't find it - have been through all the updates installed on the server around about the time it was installed 6 months ago but cannot find anything related.
0
Comment
Question by:devon-lad
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 5
  • 4
  • +1
15 Comments
 
LVL 83

Expert Comment

by:David Johnson, CD, MVP
ID: 40571478
what is an HD client?
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40571820
I'm assuming he means HD as in High Definition perhaps?

@devon-lad: Are you perhaps referring to the RDP 8.0 update? http://support.microsoft.com/kb/2592687

Current release of RDP is actually at 8.1: http://support.microsoft.com/kb/2923545
0
 
LVL 38

Expert Comment

by:Mahesh
ID: 40572410
with RDP 8.0 update in above link Remote-FX capabilities are enhanced
I think you are referring to this update as update for HD client to improve user experience
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 1

Author Comment

by:devon-lad
ID: 40572417
VB ITS / Mahesh - As far as I remember I had to update both the client and the server.  Is it just a case of installing the RDP update on both the client and server?
0
 
LVL 24

Assisted Solution

by:VB ITS
VB ITS earned 1200 total points
ID: 40572422
Yep, just install on both the clients and the server. Make sure both ends have at least Service Pack 1 installed as it's a requirement.

If you're talking Remote FX though then that's a whole different ball game altogether...
0
 
LVL 38

Expert Comment

by:Mahesh
ID: 40572443
RDP 8.0 client has both server and client side component
The RDP 8.0 update includes both the RDC 8.0 client and the RDP 8.0 server-side protocol components
http://support.microsoft.com/kb/2830477
U should install this update on server and client side both
0
 
LVL 1

Author Comment

by:devon-lad
ID: 40572448
Have just checked and all clients are on 8.1 - problem server is on 7.1.  Previously problematic server is on 8.0.

So it must have been the 8.0 update I'd previously installed on the server.

Presumably best to go with 8.1?
0
 
LVL 38

Expert Comment

by:Mahesh
ID: 40572454
U can go with 8.0 1st and then you can update it to 8.1 if required because 8.1 do not has server side component
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40572489
@Mahesh there is a RDP 8.1 update for 2008 R2: http://www.microsoft.com/en-us/download/details.aspx?id=41984
0
 
LVL 38

Assisted Solution

by:Mahesh
Mahesh earned 800 total points
ID: 40572490
I know that
Here is information in http://support.microsoft.com/kb/2830477 with RDP 8.1 update

Co-existence with the RDP 8.0 update
This update does not include Remote Desktop Protocol 8.1 server-side components for Windows 7 virtual desktops. In other words, this update includes only the new client. Therefore, the update applies only to computers that will be used as client computers. The RDP 8.0 update includes both the RDC 8.0 client and the RDP 8.0 server-side protocol components for Windows 7 SP1 virtual desktops. If you want to have both the RDP 8.0 server-side components and the RDC 8.1 client installed on the same computer, you must first install the RDP 8.0 update and then later install this update.
0
 
LVL 1

Accepted Solution

by:
devon-lad earned 0 total points
ID: 40572740
Ok, just for clarity for future readers...

RDP 8.0 needs to be applied from http://support.microsoft.com/kb/2592687 on both the client and the server when using HD display on the client computer.

RDP 8.1 can further be applied but this does not include the required server components to support HD that are in the 8.0 update.  So installing 8.1 only would not fix this specific issue.

Is that right?
0
 
LVL 24

Assisted Solution

by:VB ITS
VB ITS earned 1200 total points
ID: 40572754
That only applies for Windows 7 Virtual Desktops, which the author does not use. He states in his original question that he is connecting to a 2008 R2 Remote Desktop Session Host.

The RDP 8.1 update article for Windows 7 + 2008 R2 from Microsoft states the following improvements:
Fixes connection reliability issues.
Provides better error messages for connection failures.
Resolves a time-out issue in which a connection to a virtual machine hosted in Microsoft Azure disconnects after being idle for more than 4 minutes and requires re-authentication.
Link: http://support.microsoft.com/kb/2923545

To answer your question above devon-lad yes it appears the 8.1 update does not do much to improve performance when connecting to 2008 R2 servers. If you are connecting to Server 2012 R2 machines though then there are definitely improvements there but I digress.

Can you please confirm if the RDP 8.0 update has addressed your original issue?
0
 
LVL 1

Author Comment

by:devon-lad
ID: 40572766
Yes, the 8.0 update installed onto the server fixed it - clients already had 8.1
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40572775
Great! I think it's safe to close this question now and move on with our lives :)
0
 
LVL 1

Author Closing Comment

by:devon-lad
ID: 40582253
Have accepted my own post summarising your suggestions to make it easier for others.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question