Hi, I am Alvin Lau, a Software Development Engineer in Test (SDET) from the Remote Desktop Virtualization team. Today I want to talk about how Windows Server 2012 and Windows 8 enable a seamless multimedia experience for all content types on all networks.
Previously, Windows Server 2008 R2 and Windows 7 introduced Windows Multimedia Redirection, which provided a great experience when playing multimedia content by using Windows Media Player (WMP) in a remote session. Since Multimedia Redirection was based on redirecting the native media stream to the client, the experience was great for supported video formats on LAN networks. However, there were a few key shortcomings:
To address these shortcomings, Windows Server 2012 and Windows 8 introduced RemoteFX Media Streaming, which uses host-side rendering techniques (which provide broad video format support) in combination with the industry standard H.264 codec (which benefits online media streaming) to seamlessly redirect video content.
RemoteFX Media Streaming works in 3 simple steps
This is a simplification of all the complexities in the system–but should give you an idea of how it works.
Benefits of RemoteFX Media Streaming
In summary, RemoteFX Media Streaming delivers a smooth playback experience for all video content even on WAN networks.
Take a look at the following video which shows Windows 7 and Windows 8 remote desktops side by side. In both cases the client computer is connected to the remote desktops by using a WAN link with 2 Mbps bandwidth, 250ms round-trip latency, and 0.5% random loss.
Does Windows Server 2012 still support Multimedia Redirection?
Windows Media Redirection still provides the best experience on LAN networks for supported video formats. Windows Server 2012 and Windows 8 automatically detect these conditions and turn on Multimedia Redirection. If these conditions are not met (for example, if the user is on a WAN network), the system automatically switches to use RemoteFX Media Streaming, even for WMP content. The determination of whether or not the user is on a WAN network is made by looking at the end-to-end latency—if the connection latency is above 30ms, Multimedia Redirection will not be used.
RemoteFX Media Streaming is enabled along with the rest of Remote Desktop Services, and no additional configuration is required. This is in line with our core philosophy for RemoteFX in Windows Server 2012, which is to make things simple and have features just work out of the box. However, if a user is connecting to a virtual desktop that has a RemoteFX virtual graphics processing unit (vGPU) installed, the host Hyper-V server must have a non-server core setup due to the fact that media codecs are not available in a server core setup.
Thanks for reading, and I hope you find this post useful. I am looking forward to your feedback.
If you have specific troubleshooting questions, go to the RDS web forum at http://social.technet.microsoft.com/Forums/en-US/winserverTS/threads; many of my fellow product group members and community experts watch and respond to questions on the web forum on a regular basis.
Speaking of the new version of RemoteFX... When will Win7 be updated so it can decode the new versions payload from win8/2012?
The new RemoteFX sure does look good though ;)
Daniel, the schedule for the Remote Desktop Client update to Windows 7 is not yet locked. When we have a locked down plan that we can communicate with reasonable confidence, you'll hear from us on this blog :). In the past WS2008 R2), the down level update was typically made available 2-3 months after the new OS versions availability.
To utilize the H.264 and AAC codecs, I think European users need to install Media Feature Pack for N and KN versions of Windows 8 (www.microsoft.com/.../details.aspx).
@Shanmugam, Thanks for the info! For obvious reason, we wont be able to pilot the new features in anger until this is available...
o.0 pn 09++9988
-i kioxi ;l5545
"However, if a user is connecting to a virtual desktop that has a RemoteFX virtual graphics processing unit (vGPU) installed, the host Hyper-V server must have a non-server core setup due to the fact that media codecs are not available in a server core setup."
So I cannot use the RemoteFX Media Streaming options on standalone Microsoft Hyper-V Server 2012 host? Even when the guest is running Windows Server 2012 Standard?
@MikeH In that case, I believe the RemoteFX Progressive Codec will be used instead (see #2 under RemoteFX Media Streaming works in 3 simple steps). Anyone knows a way of brute force installing the Media Feature Pack on the server core setup? I guess that will possibly make the H.264 codec available on the system hmm...
WMP redirection works - but only if videos get played using the native Windows Media Player.
If I play videos using the Modern UI Player then WMP redirection does not seem to work.
Is this by intention ?
Is there is any way to know that media content is playing through Media Remoting or Media redirection in RDP session?
"Is there is any way to know that media content is playing through Media Remoting or Media redirection in RDP session?"
If you adjust the player window to a small size ,and check that the network utilization is still not decreased, it should be in Media Redirection mode.
If my Win 7 clients (both Win 7 ThinPC and Win 7 Enterprise) have the latest version of the RDP client (6.3.9600 at the moment), is there any way for them to benefit from this Remote FX media streaming from a 2012 R2 RDS host?
To make use of H.264 compression in RemoteFX , your blog says that H.264 decoder is required in the client side.My question is whether H.264 encoder is required to be installed in the server side as well ?