Now that we have released Windows 7 & Windows Server 2008 R2 to manufacturing, we wanted to share our plans to make the Remote Desktop Connection (RDC) 7.0 client available to Windows XP and Windows Vista. RDC 7 will ensure that when connecting to Windows 7 and Windows Server 2008 R2 from an XP or Vista machines you are able to take advantage of the rich, advanced RDP7 features such as Media Player Redirection, True Multi-monitor support, etc
Note: If you use RDC 7.0 to connect to XP or Vista you do not get new Windows 7 features like Windows Media Player Redirection etc. There is no way to get these features when connecting to XP or Vista.
The new RDC 7.0 clients will be available in Q4 CY09 by using the Microsoft Download Center and WSUS and will be available for Windows Vista with Service Pack 1 (SP1), Windows Vista with Service Pack 2 (SP2), and Windows XP with Service Pack 3 (SP3) operating systems.
The following sections describe what the user experience will be when connecting to Windows 7 or Windows Server 2008 R2 from a variety of operating systems using RDP 7, RDP 6.1, or RDP 5.2.
This section describes the set of remote resources available to users from each operating system/client combination.
Access to Remote Desktop sessions
Access to RemoteApp programs
Access to personal desktop by using RD Connection Broker
Access to virtual desktop pools by using RD Connection Broker
Launch applications and desktops from RemoteApp and Desktop Connection on client
Launch RemoteApp programs, virtual desktop, and session-based desktop from RD Web Access
Status & disconnect system tray icon.
User can connect to full remote desktop sessions.
Users can connect to RemoteApp programs rather than a whole desktop. This allows RemoteApp programs to be displayed seamlessly on the user’s local desktop even though they run remotely.
Access to personal virtual desktops by using RD Connection Broker
Users can access to personal virtual desktops when using the new Remote Desktop Virtualization Host in Windows Server 2008 R2. Personal desktops are assigned to users on 1:1 basis and maintain state over time.
Users can access virtual desktop pools when using the new Remote Desktop Virtualization Host in Windows Server 2008 R2. Pooled desktops are shared between multiple users and all changes a user makes are typically rolled back when the user logs off.
Launch applications and desktops from 'RemoteApp and Desktop Connections'
Users can subscribe to all their RemoteApp programs and desktops which are then listed in their local Start menu. The list is automatically updated as items are added or deleted.
Launch application and desktops from RD Web Access
Users can launch RemoteApp programs and desktops from an ActiveX enable browser
Status & disconnect system tray icon
A single system tray icon enables users to see all their remote connections. The user can disconnect all or individual connections using this icon. The icon appears only when launching RDP connections which are associated with a RemoteApp and Desktop Connection feed.
This section describes the user experience when connecting to Windows Server 2008 R2 from each platform/client combination.
Windows Media Player Redirection
Aero Glass Support
Enhanced Bitmap Acceleration
Language Bar Docking
Windows Media Player Redirection enables content hosted in Windows Media Player to be redirected to the client for decoding on the users’ computers. This improves the quality of the video and ensures that video and audio are always in sync. This works for both full Windows Media Player and Windows Media Player controls hosted in Web pages.
You can redirect audio recording devices such as microphones on the client computer. This is ideal for applications like Windows 7 voice recognition and applications that record audio.
True Multimonitor Support
In Windows Vista & Windows Server 2008, Terminal Services supported only monitor spanning. Remote Desktop Services now includes true multi-monitor support for up to 16 monitors. and works for both Remote Desktop & RemoteApp programs. It is not compatible with Aero Glass support.
Terminal Services in Windows Server 2008 did not support Aero Glass remoting for sessions. This is now supported in Windows Server 2008 R2 Remote Desktop Services (but is not compatible with multi monitor support).
Bitmap acceleration improves the remote display of graphics-intensive applications like PowerPoint, Flash, and Silverlight.
RemoteApp allows users to use their docked Language Bar with their RemoteApp applications just like they do with the local ones.
This productive functionality was previously unavailable, and users had to resort to the floating Language bar. To use the RemoteApp docked Language bar users must use a Windows7 client connected to a Windows Server 2008 R2 server.
Easy Print allows users to print to their local printers from remote desktops and programs without needing to install print drivers on the host. Easy Print is now supported when connecting to Windows 7 client.
This section describes the security features available when connecting to Windows Server 2008 R2 or Windows 7 from each platform/client combination.
Per-user filtering of RemoteApp programs
Web forms-based authentication
RD Gateway-based control of device redirection
RD Gateway system and logon messages
RD Gateway Background Authorization & Authentication
Gateway Idle & Session Timeouts
NAP remediation with RD Gateway
RemoteApp programs displayed in RD Web Access can be filtered so that a user will see only the applications to which he or she has access.
Web SSO & Web forms-based authentication
RD Web Access now uses forms-based authentication to improve the user experience. Web SSO ensures that once a user is logged on no additional passwords are required for RD Gateway, RD Session Host servers and RemoteApp programs.
In Windows Server 2008, it was possible for non-Microsoft Remote Desktop clients to override the gateway device redirection controls. In Windows Server 2008 R2 device redirection settings defined in RD Gateway it cannot be overridden.
RD Gateway System and Logon messages
System and logon messages can be added to RD Gateway and displayed to the remote desktop user. System messages can be used to inform users of server maintenance issues such as shutdown and restarts. Logon messages can be used to display a logon notice to users before they gain access to remote resources
Background authentication and authorization requests are performed after a configured session timeout has been reached, sessions for users whose property information has not changed are not affected, and authentication and authorization requests are sent in the background.
RD Gateway Idle & Session Timeouts
Configurable idle and session timeouts with RD Gateway provide better control of users who are connecting through RD Gateway. An idle timeout provides the ability to reclaim resources used by inactive user sessions without affecting the user's session or data. This helps free up resources on the RD Gateway server.
NAP Remediation with RD Gateway
NAP remediation allows you to manage remote clients by updating them with the latest software updates and settings. This helps keep remote clients in compliance with network security policies.
For more information about the new features in Windows Server 2008 R2 Remote Desktop Services, see “What’s New in Remote Desktop Services,” available on Microsoft TechNet (http://go.microsoft.com/fwlink/?LinkId=131925).
Does anyone know when the Calista Technologies will be intergrated in RDP?
As Rex Pulford mentioned above and no one responded to, Windows 7 does not show any indication on the host computer screen to indicate that a remote user is logged on. This leads to a local user, not knowing that a remote session is in progress, logging on and causing the remote user session to be interrupted with no warning. This has been confirmed on multiple test PC's running Windows 7 Professional OEM (both 32 and 64 bit versions).
Is Microsoft aware of this issue, and is it being addressed?
Rex Pulford and Rhodenizer:
Just to ensure the scenario you are talking about: User1 is logged on locally to Machine1 and User2 connects to same machine remotely. Are you saying you do not get a warning? Another way, if User1 is connected to Machine1 remotely and User2 logs on to same machine locally. And you do not get warning either?
I just tested this scenario on Win 7 Ultimate and I get "another user logged on" warning in both the cases. You will get warning as long as two different users are attempting logon to same machine.
Can you please explain your scenario?
Here you could find how to get it running on Windows Server 2003:
We allow SSL via a local proxy server and we want to use this to connect to an external RD gateway server. Is there anyway to configure the 7 (or 6.1) client to use a proxy server (i.e. browser style)?
We are using the OEMBackground registry parameter to set logon wallpaper. This works fine when you’re trying to login to the console like on a physical computer. Even works on Windows 2008 Server R2. BUT when using Remote Desktop we keep getting this green logon screen. Have searched and searched the Internet and have been trying all kinds of different things but no matter what we do, the green screen keeps showing. Windows 7 Ultimate: same thing. We want to demo Windows 2008 R2 Server to our customers but it doesn’t look very impressing with this old fashioned green screen as the first thing they see…. Can’t even change it to black!
It's really easy to install the RDP 7.0 client on Windows server 2003.
Extract the WindowsXP-KB969084-x86-enu.exe with winrar.
Open update.inf with notepad and edit
MinNtServicePackVersion = 768
ThisServicePackVersion = 768
to value 512 and save.
Then you run update.exe and save the update.inf with the restored values of 768 before you get the error message "setup could not verify the integrity of the update.inf." Depending on your machine you might need to be quick.
After saving you can click next and hey there you have RDP 7.0 ready to use in Windows server 2003.
This is probably not the officially best place to ask this question, but I have found it and I'm reluctant to look further.
Does Windows 7 Pro include any RDS cal's?
Can I buy CAL's for RDS for W7 Pro?
Can Windows 7 Professional provide remote desktop connection WITH aero glass. Some sources say no.
Hey there, What if the client only can connect to internet using a proxy server that needs authentication. Is there a way to let de rdp Client authenticate to that proxy server?
Noticed that none of the HP printer drivers have an envelope feeder option. Anyone know if it is safe to install 3rd party printer drivers on 2008R2?
I have a Win7 Ultimate notebook connected to an external beamer, and a Win7 Home Premium netbook. Is it possible to remotely run a presentation on the notebook, so that the presenter's view appears via RDC on the netbook (connected wirelessly) and the audience's view on monitor 2 of the notebook?
We were able to get the 7.0 XP version to install and run on 2003 SP2 using the update.inf change but the change had to be more extensive than noted above. It installed and has worked fine. Here's the before and after section of update.inf that had to be changed.
Before (as it is in the XP version):
NtBuildToUpdate = 2600
NtMajorVersionToUpdate = 5
NtMinorVersionToUpdate = 1
MaxNtBuildToUpdate = 2600
MaxNtMajorVersionToUpdate = 5
MaxNtMinorVersionToUpdate = 1
MinNtServicePackVersion = 768
MaxNtServicePackVersion = -1
ThisServicePackVersion = 768
After (our changes):
NtBuildToUpdate = 3790
NtMinorVersionToUpdate = 2
MaxNtBuildToUpdate = 3790
MaxNtMinorVersionToUpdate = 2
MinNtServicePackVersion = 512
MaxNtServicePackVersion = 512
ThisServicePackVersion = 512
MediaPlayer 11 only plays audio when I'm in multimonitor on my windows 7 hyperv locally on my win 2k8 r2 server. I'm using rdc and not the hyper-v display. If I run mstsc without /multimon but using the same rdp file, I get both audio and video from the same wmv file. Any thoughts?
Who can tell us how to upgrade HP thin clients with Microsoft Windows CE .NET 4.2 to use RDP 7.0 features?
We need bidirectional audio to use VoIP soft phones in terminal sessions in Windows 2008 R2.
Any help is badly needed.