- 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.
- 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 SP12592687 Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1
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.
Hotfix informationTo resolve this issue, install this hotfix. Then, after you restart the computer, you have to run the following cmdlet to set custom properties on the Windows 7 SP1-based virtual desktop collection:
Set-RDVirtualDesktopCollectionConfiguration -CollectionName "[ collection name ]" -CustomRdpProperty "connection type:i:6`nnetworkautodetect:i:0`n[ custom properties ]"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.
PrerequisitesTo apply this hotfix, you must be running Windows Server 2012.
Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Article ID: 2863663 - Last Review: Aug 30, 2013 - Revision: 1