You install the Hyper-V role and Remote Desktop Session Host role on a computer that is running Windows Server 2012.
You create a Windows 7 Service Pack 1 (SP1)-based virtual machine on the computer.
You do not have the updates that are described in Microsoft Knowledge Base (KB) articles 2574819 and 2592687 installed on the virtual machine.
You enable the RemoteFX virtual graphics processing unit (vGPU) on the virtual machine.
You configure the computer to use Remote Desktop Connection Broker (RD Connection Broker) to provide access to the virtual machine for users.
You connect to the virtual machine from a Windows 8-based client computer by using RD Connection Broker.
In this scenario, the user experience that is improved by the Microsoft RemoteFX feature is not enabled on the virtual machine.
If you connect to the virtual machine directly, the RemoteFX user experience is enabled on the virtual machine.
For more information about KB 2574819 and KB 2592687, click the following article numbers to view the articles in the Microsoft Knowledge Base:
2574819 An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1
2592687 Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1
This issue occurs because RemoteFX is optimized to only support local area network (LAN) connections in Windows 7 SP1. In other words, you have to use a LAN connection to establish a RemoteFX vGPU Remote Desktop Protocol (RDP) session to a Windows 7 SP1-based virtual machine.
The RemoteFX Network Auto-Detect feature is introduced in Windows 8 and Windows Server 2012 as a new feature. By default, the feature is enabled on a Windows 8-based or Windows Server 2012-based computer. When you start an RDP session from a Windows 8-based client computer, the "Detect connection quality automatically" setting is selected by default. Therefore, the session cannot be recognized as a RemoteFX vGPU RDP session by a Windows 7 SP1-based virtual machine.
Note If any other custom property exists, the custom property has to be indicated by adding it to the [custom properties] parameter, and the collection name has to be specified in the [collection name] parameter according to the custom environment.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must be running Windows Server 2012.
To use the hotfix in this package, you do not have to make any changes to the registry.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notes
Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
6.2.920 0.16 xxx
Windows Server 2012
6.2.920 0.20 xxx
Windows Server 2012
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012