Live Chat Software by Kayako
 News Categories
(19)Microsoft Technet (2)StarWind (4)TechRepublic (3)ComuterTips (1)SolarWinds (1)Xangati (1)MyVirtualCloud.net (27)VMware (5)NVIDIA (9)VDI (1)pfsense vRouter (3)VEEAM (3)Google (2)RemoteFX (1)developers.google.com (1)MailCleaner (1)Udemy (1)AUGI (2)AECbytes Architecture Engineering Constrution (7)VMGuru (2)AUTODESK (1)storageioblog.com (1)Atlantis Blog (7)AT.COM (2)community.spiceworks.com (1)archdaily.com (14)techtarget.com (2)hadoop360 (3)bigdatastudio (1)virtualizetips.com (1)blogs.vmware.com (3)VECITA (1)vecom.vn (1)Palo Alto Networks (4)itnews.com.au (2)serverwatch.com (1)Nhịp Cầu đầu tư (3)VnEconomy (1)Reuters (1)Tom Tunguz (1)Medium.com (1)Esri (1)www.specommerce.com (1)tweet (1)Tesla (1)fool.com (6)ITCNews (1)businessinsider.com (1)hbr.org Harvard Business Review (1)Haravan (2)techcrunch.com (1)vn.trendmicro.com (3)thangletoan.wordpress.com (3)IBM (1)www.droidmen.com (2)blog.parallels.com (1)betanews.com (6)searchvmware.techtarget.com (1)www.bctes.com (1)www.linux.com (4)blog.capterra.com (1)theelearningcoach.com (1)www.examgeneral.com (1)www.wetutoringnation.com (1)chamilo.org/ (1)www.formalms.org (1)chalkup.co (1)www.mindonsite.com (5)moodle.org (4)moodle.croydon.ac.uk (1)opensource.com (1)1tech.eu (1)remote-learner.net (1)paradisosolutions.com (2)sourceforge.net (7)searchbusinessanalytics.techtarget.com (1)nscs.gov.sg (1)virten.net (1)fastest.com.vn (1)elearninglearning.com (2)www.computerweekly.com (1)youtube.com (2)computer.howstuffworks.com (2)techz.vn (2)techsignin.com (1)itworld.com (7)searchsecurity.techtarget.com (1)makeuseof.com (1)nikse.dk (1)4kdownload.com (1)thegioididong.com (1)itcentralstation.com (1)www.dddmag.com (1)Engenius (1)networkcomputing.com (1)woshub.com (1)hainam121.wordpress.com (1)www.lucidchart.com (1)www.mof.gov.vn (3)www.servethehome.com (6)www.analyticsvidhya.com
RSS Feed
News
Aug
4
RemoteFX vGPU Setup and Configuration Guide for Windows Server 2012
Posted by Thang Le Toan on 04 August 2015 01:23 AM

Windows Server 2012 introduces some significant improvements to RemoteFX™. One feature – RemoteFX vGPU - already present in Windows Server 2008 R2 is the ability to use a physical graphic adapter (GPU) in the Hyper-V host to accelerate the host-side rendering of display content. This guide describes the configuration steps to leverage RemoteFX vGPU in Windows Server 2012. For Windows Server 2012 R2 changes please see the following RDS blog post:RemoteFX vGPU Improvements in Windows Server 2012 R2 

 

 

 


What is RemoteFX?

RemoteFX in Windows Server 2012 is a suite of improvements to the Microsoft Remote Display Protocol (RDP). It optimizes the display experience for remote users, even on constraint networks. Additionally, RemoteFX improves access to peripheral devices attached to the client, e.g. via USB.

The vGPU feature of RemoteFX makes it possible for multiple virtual machines to share a physical graphics adapter. The virtual machines are able to offload rendering of graphic information from the processor to the dedicated graphics adapter. This will decrease the CPU load and improve the scalability for graphic intense workloads that run in the VDI virtual machines.

 


Requirements for RemoteFX vGPU

To off-load graphically intense workloads from the CPU to a physical GPU in Windows Server 2012 the following hardware is required:

 


Checking the requirements

SLAT CPU Support

Before enabling the Hyper-V role on the server, the following tools can be used to find out whether the server CPU supports SLAT:

System info

On an elevated command prompt run the command:

C:\systeminfo.exe

At the very end of the output information this text should appear on a system with SLAT capable CPU:

 

Coreinfo

The free tool can be downloaded from the Sysinternals pages on Technet (http://technet.microsoft.com/en-us/sysinternals/cc835722.aspx  ). It has to be run before installing Hyper-V on an elevated command prompt.

C:\coreinfo.exe –accepteula –v

If the CPU meets the requirements, both lines are marked with a star symbol (*).

DirectX 11 compatible graphic adapter

Hardware vendor web page

In order to verify whether the GPU is DirectX 11 ready you can use the web page of the manufacturer of the graphic adapter.

 

Microsoft Windows Server Catalog

To leverage RemoteFX vGPU in an enterprise environment it is recommended to use a graphic adapter listed on the Windows Server Catalog. Windows Server 2012 certified GPUs are listed here  .

 

DirectX Diagnostic Tool (DXDiag.exe)

Run this command at an elevated command prompt:

C:\dxdiag.exe

The DirectX Diagnostic Tool will be displayed. Check the line “DirectX Version” for DirectX 11.

In addition to that, please verify the Feature Level information at the "Display" tab of DXdiag. The GPU Feature Level has to be at least 11.0 for RemoteFX vGPU in Windows Server 2012.

 

WDDM 1.2 compatible driver

Use the DXdiag tool to verify driver for the graphics adapter on the Windows Server 2012 is Windows Device Driver Model (WDDM) 1.2 compatible (NOTE: ensure you are logged on to the physical server, do not use a Remote Desktop connection since it will not display the graphics properties):

 


Installation and configuration of RemoteFX vGPU

  1. Install Windows Server 2012 on the server.
  2. Verify SLAT-support of the CPU using Systeminfo or Coreinfo.
  3. Install Windows Updates.
  4. Install the latest available display driver which at least supports WDDM 1.2 and DirectX 11 from the manufacturer of the graphic adapter.
  5. Verify DirectX 11 with Dxdiag.
  6. Verify the Windows SKU running inside the virtual machine is “Windows 8 Enterprise” or “Windows 7 Enterprise“, which is required for RemoteFX vGPU support.
  7. Install Hyper-V Role using Server Manager and reboot the server.

  8. Install the Remote Desktop Virtualization Host Role using Server Manager or use the Remote Desktop Standard Deployment Wizard for a full setup of all Remote Desktop Services Roles. For the isolated installation of the role you have to select “Roles- and Feature based installation“. After the role setup is completed, the server must be restarted.
  9. Open Hyper-V Manager and select the physical GPU support in Hyper-V Settings.

  10. Add or import the Windows 8 Enterprise or Windows 7 Enterprise virtual machines onto the Windows Server 2012 virtual machine.
  11. Add the RemoteFX 3D Graphics adapter to the Window 8 Enterprise or Windows 7 Enterprise virtual machine by navigating to the virtual machine settings and select “Add Hardware”.
  12. Select “RemoteFX 3D Video Adapter” and click “Add”

  13. Navigate to the properties of the added “RemoteFX 3D Video Adapter” and configure the maximum number of monitors and resolution that will be used by the Remote Desktop clients that will connect to this virtual machine.

  14. Commit the changes to the properties of the virtual machine and launch the virtual machine to configure the Windows 8 or Windows 7 Sp1 Enterprise client.

     

      Note
    Certain steps must be applied to allow Remote Desktop Connections for Windows 7 with SP1 Enterprise client

     

    1. Hyper-V Integrated Services must be updated
    2. Allow Remote Desktop to communicate through Windows Firewall

    3. Optional: Add the local Administrator account to the Remote Desktop Users Group. This enables the local Administrator remote access. Any Domain Administrators added to Administrators Group will have access by default.
    4. When using Remote Desktop Connection, change the Performance Experience to LAN. This enables the RemoteFX Adapter to function correctly in the virtual machine

    5. After the virtual machine restarts, you will see a black screen on the virtual machine console with the message “Video Remoting was disconnected. The virtual machine is using the 3D video adaptor, which is not supported by the Virtual Machine Connection console.” This is expected, and you will not be able to log on to the virtual machine from the Virtual Machine Connection. You will be able to remotely log on to the virtual machine by using an account that is a member of the Remote Desktop Users group on the virtual machine.

  15. After configuring the virtual machine, check the Device Manager in the virtual machine to verify that the “Microsoft RemoteFX Graphics Device – WDDM“ is recognized as a display adapter when using the Remote Desktop Client to connect

  16. DXDiag can also be used to verify the display adapter. Within the virtual machine using a Remote Desktop Session, launch the DXDiag tool and confirm on the display tab that in fact the “Microsoft RemoteFX Graphics Device – WDDM” has been enabled.

  17. RemoteFX vGPU is now configured and the virtual machines can be leveraged in a VDI Deployment.

 

  Note
RemoteFX vGPU can only be leveraged with Windows 8 and Windows 7 with SP1 Enterprise clients. Virtual machines with Windows Server 2012 acting as Remote Desktop Session Host (session virtualization) cannot use RemoteFX vGPU. An overview of all supported features for the various operating system platforms is provided in the blog article:http://blogs.msdn.com/b/rds/archive/2012/11/26/remotefx-features-for-windows-8-and-windows-server-2012.aspx 

To use RemoteFX vGPU in an enterprise environment with several virtual machines it is recommended to use a professional graphics adapter that is certified for Windows Server 2012, listed  in the Windows Server Catalog. Only these graphics adapters offer the required scalability and specially tested drivers for those scenarios. As illustrated in the screenshots, consumer graphics adapter AMD Radeon HD6870 was used to demonstrate the installation and configuration. This is only recommended for test and demo purposes.

 

Finally, it is important to use the scenario-based deployment option in Server Manager to setup and configure a Remote Desktop Services infrastructure. Only this option will install the other required roles like RD Licensing, RD Web Access and RD Connection broker to enable end user access to the virtual machines.

Have fun with RemoteFX and the Remote Desktop Services in Windows Server 2012!


Frequently Asked Questions

What are the requirements to use RemoteFX graphics acceleration by using the vGPU?

  • Hyper-V running on Full Installation of Windows Server 2008 R2 SP1 or Windows Server 2012
  • DX11 vGPU with WDDM v1.2 driver
  • SLAT-Capable processor
  • Remote Desktop Virtualization Host role service must be installed (to enable RemoteFX vGPU)
  • Hyper-V must have Physical GPUs enabled for use with RemoteFX vGPU
  • The virtual machine must have the “RemoteFX 3D Video Adapter” added
  • The Windows SKU running inside the virtual machine must be “Windows 8 Enterprise” or “Windows 7 Enterprise”

 

How can I determine if my system has a SLAT supported processor?

To use RemoteFX/vGPU with Hyper-V a SLAT supported processor must be present.

1) The CoreInfo utility from Sysinternals.com can be used to verify the processor is SLAT supported:http://technet.microsoft.com/en-us/sysinternals/cc835722 

2) Open the command prompt as an administrator on the server host

3) Run the following commands:

Pushd \\live.sysinternals.com

  • A temporary drive letter will appear

Coreinfo –accepteula –v

  • The output should return results for the following: Hypervisor, and EPT. The EPT parameter should have a “*” indicating it supports Intel extended page tables (SLAT)

 

What types of vGPU are supported with RemoteFX?

When running Windows Server 2012 with the RemoteFX vGPU, the host must have a DX11.1 (WDDM 1.2) capable graphics card and driver. DX9 / DX 10 only capable GPUs are no longer supported for use with the RemoteFX vGPU on Windows Server 2012.

Note: The above statement applies to both Windows 7 with SP1 virtual machines and Windows 8 virtual machines that leverage the RemoteFX vGPU on Windows Server 2012. See the following blog article for more information including links to list of supported cards from Nvidia and AMD:http://blogs.msdn.com/b/rds/archive/2012/06/13/richvgpu.aspx 

 

Can I use multiple types of GPUs?

No, if more than one GPU is installed, the GPU’s need to be identical. The GPU must have sufficient dedicated memory that is separate from system memory.

What versions of Windows are supported inside a virtual machine to use the vGPU?

Not every version of Windows enables use of the vGPU, even if the vGPU is enabled in Hyper-V for the given virtual machine you are connecting to. Ensure that you are running Enterprise version of Windows client.

You can use one of these options to verify you are running enterprise version:

  • Navigate to licensing options / system info
  • Open a command prompt and run the the “Systeminfo” command, one of the returned parameters (“OS Name”) will show the version of Windows you are running.

 

How can I determine the RemoteFX vGPU is utilized in a RemoteFX/RDP session?

  1. Confirm the device connecting supports RDP 7.1 (RemoteFX Codec) or RDP 8.
  2. Confirm the virtual machine is configured to use RemoteFX with the vGPU:a. On the Hyper-V host system launch the Hyper-V Manager and go to “Hyper-V Settings” (right click on the host).

    b. Confirm the Physical GPU is present and the “Use this GPU with RemoteFX” is enabled.

    c. Navigate to the Windows 8 virtual machine. Then navigate to the properties of the virtual machine and confirm the “RemoteFX 3D Video Adapter” is in the hardware list. If it is not in the list, use the “Add Hardware” option to add the “RemoteFX 3D Video Adapter” to the virtual machine.

  • In the Windows 8 virtual machine itself confirm the “Microsoft RemoteFX Graphics Device – WDDM” video adapter is there:

  • When connecting to the session confirm if RemoteFX/vGPU is enabled in the virtual machine you are connecting to review the Windows Eventlog on the Windows 8 virtual machine:
  1. Launch eventvwr.exe.
  2. In the eventviewer look for the following in the tree on the left:

    “Applications and Services Logs” > “RemoteDesktopServices-RdpCoreTS” > “Operational”

  3. In the listview in the middle look for event ID 34:
  4. The detail of the event should show “Remote Desktop Protocol will use the RemoteFX host mode module to connect to the computer.”:

  5. If you see event ID 33 then it means the vGPU is not enabled, for example when connecting to a virtual machine running RDSH.
  6. For an RD Session Host on Windows Server 2008 R2 the RemoteFX RDP 7.1 Codec can be forced using the following online documentation: http://technet.microsoft.com/en-us/library/ff817595(v=ws.10).aspx

Are there any performance tests I can run to show the benefit of vGPU?

From a performance point of view you can use the following example to compare the Frame rate between a virtual machine without vGPU enabled in Hyper-V and virtual machine enabled with vGPU:

  1. Fishbowl (for example set 100 fish and compare side by side with virtual machine that does not have vGPU enabled)

    http://ie.microsoft.com/testdrive/Performance/FishBowl/Default.html 

  2. Particle Acceleration

    http://ie.microsoft.com/testdrive/Performance/ParticleAcceleration/ 

 

I don’t see a difference between the vGPU and non-vGPU virtual machine?

When you do not notice any difference between a virtual machine with vGPU enabled and a virtual machine without vGPU enabled then confirm the following:

  1. Which version (Enterprise or Pro) of windows 8 is the vGPU enabled virtual machine running? The RemoteFX vGPU hardware acceleration is only supported on the Enterprise version of Windows.
  2. RD Session Host does not support the vGPU, however with RD Session Host you will still have the benefits of software emulation of the GPU on the Windows Server 2012 RD Session Host server.

 

What performance counters are available to determine RemoteFX performance issues?

The following performance counters are available for RemoteFX Graphics on Windows 8 / Windows Server 2012:

  1. RemoteFX Graphics:

    a) Average Encoding Time

    b) Frames Skipped/Second – Insufficient Client Resources

  2. RemoteFX Network:

    a) Insufficient Network Resources b) Insufficient Server resources

If the bottleneck is encoding speed, 1a and 2b will be high. If the bottleneck is bandwidth, 2b will be high. If bottleneck is client speed, 1b will be high.

 

  Note
That Frames-per-Second measured inside a virtual machine may in-itself not be a good measure as there are other factors like bandwidth, server resources which may all play a factor.

 

I am seeing a blank screen when connecting to a Windows 8 Enterprise virtual machine with vGPU enabled?

Verify the server running Hyper-V is running the same version / build as the version running in the virtual machine. For example if the Windows 8 virtual machine is running build 9200 and the RD Virtualization Host server a prerelease build 8400 then the Hyper-V drivers are not compatible and a black screen will displayed. Ensure the same build is used to resolve the problem. Also check if you are running the enterprise SKU that has support for RemoteFX vGPU (e.g. either Windows 8 Enterprise or Windows 7 Enterprise with SP1).

 

What monitor configurations are supported when connecting to a Windows 8 Pro or Windows 7 with Service Pack 1 virtual machine with RemoteFX vGPU enabled?

Maximum monitor resolutions in Windows 8 Enterprise or Windows 7 Enterprise with SP1 virtual machines:

Maximum resolution

Supported maximum monitors per RemoteFX vGPU Enabled virtual machine

Windows 7 Enterprise with SP1 on Windows Server 2008 R2 SP1 Hyper-V or Windows Server 2012

Windows 8 Enterprise on Windows Server 2012 Hyper-V

1024 x 768

4

8

1280 x 1024

4

8

1600 x 1200

3

4

1920 x 1200

2

4

2560 x 1600

-

2

Monitor resolutions that can be in landscape and portrait modes:

Resolutions

640 x 480

1280 x 800

1600 x 1200

2048 x 1536

800 x 600

1280 x 1024

1600 x 1050

2560 x 1440

1024 x 768

1366 x 768

1920 x 1080

2560 x 1600

1280 x 720 1440 x 900 1920 x 1200  

1280 x 768

1400 x 1050

2048 x 1080

 

 

Physical GPU in Windows Server 2012 Hyper-V settings is unavailable post domain join?

When a Windows Server 2012 Remote Desktop Virtualization Host is added to a domain and the default domain policy is applied, the option to select a physical GPU used for Remote FX (within Hyper-V settings) is unavailable. There is a known issue which has been addressed in Windows Server 2012 R2. For more information on the root cause and how to address on Windows Server 2012, please see KB2878821  .


Read more »



Aug
4
RemoteFX on Windows Server 2012 R2
Posted by Thang Le Toan on 04 August 2015 01:14 AM

Scenario

In this guide, we will show how to setup and configure RemoteFX for a Hyper-V host running Windows Server 2012 R2. The host is used for testing and development purposes, it is not member of a domain. (In this guide, the name of the host machine we are configuring will be “Black”.)

Especially we are interested to have a synthesized DirectX 11 capable graphics adapter in our virtual machines. This is known as the RemoteFX vGPU feature.

The host machine has a Core i7 processor (Haswell generation). Graphics adapter is a NVIDIA Quadro K620. So the hardware meets the requirements for RemoteFX and we will not bother with discussing details of hardware requirements.

Let’s start with setting up the host machine.

Add the Hyper-V Role

  1. After the basic setup of Windows Server 2012 R2 Datacenter, ask Windows Update to install all available updates. Also be sure that the latest available display driver is installed.
  2. Then the Hyper-V role needs to be added. In Server Manager, choose Add Roles and Features from the Manage menu. Choose a Role-based or feature-based installation. Then select the local server to add the role to.
  3. Add the Hyper-V role. Confirm to also add all required features suggested by the wizard and let the wizard finalize the job.1
  4. As usual, after adding the Hyper-V role the Hyper-V Manager will be available.2

Add the Remote Desktop Virtualization Host Role Service and the Remote Desktop Licensing Role Service

For RemoteFX to work, the Remote Desktop Virtualization Host role service must be up and running on the Hyper-V host machine.

Also a Remote Desktop Licensing Server must be available in the network. The RD Virtualization Host needs the RD Licensing Server to confirm the availability of Remote Desktop Client Access Licenses.

Since our installation is for development and testing, we will set up the licensing server on the same machine as the Hyper-V host.

  1. In Server Manager, choose Add Roles and Features from the Manage menu. Choose aRole-based or feature-based installation. Then select the local server to add the role to.
  2. Add both the Remote Desktop Licensing role service and the Remote Desktop Virtualization Host role service. Confirm to also add all required features suggested by the wizard and let the wizard finalize the job.3
  3. Now the Remote Desktop Licensing Manager and the RD Licensing Diagnoser will be available.

4

Install Remote Desktop Licenses

Now let us install some Remote Desktop CALs. (A MSDN subscription is a good way to get RD CALs.)

  1. Start the Remote Desktop Licensing ManagerConnect to the machine the Remote Desktop Licensing service is running on, i.e. to the local machine in our scenario.
  2. Open the Properties in the server node’s context menu. Connection method should beAutomatic connection. Also type in the Required Information (your name, your company, and your country).5
  3. Now choose to Install Licenses in the server node’s context menu. The Install Licenses Wizard opens up.
  4. Choose the appropriate License program. In our example, we choose License Pack (Retail Purchase) which is what you typically get from a MSDN subscription.6
  5. Provide the required license information (depends on the chosen license program).7
  6. Let the wizard finalize its job to install the licenses.8
  7. The Remote Desktop Licensing Manager indicates that the task succeeded.

9

Configure the License Server for the Remote Desktop Virtualization Host

  1. Open up the RD Licensing Diagnoser. The Licensing Diagnoser tells us that our Remote Desktop Session Host Server cannot find a RD Licensing Server. We didn’t set up a RD Session Host Server but a RD Virtualization Host Server, but anyway.10
  2. The RD Virtualization Host Server locates the RD Licensing Server via group policies. Since our server is not member of any domain we use a local group policy. So open up gpedit.mscand navigate to Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing.11
  3. Open up the Use the specified Remote Desktop license servers policy setting. Enable the policy setting and type in the name of the license server to use.12
  4. Then open up the Remote Desktop licensing mode policy setting. Enable the policy setting and specify the licensing mode Per Device. (Remember that we installed Per Device licenses.)13
  5. With these policy settings the RD Licensing Diagnoser is happy now.

14

Choose the GPU to be used with RemoteFX

Now that the Remote Desktop Virtualization Host role is installed a RemoteFX 3D Video Adapteris available which can be added to virtual machines.

15

But first we need to associate the RemoteFX 3D Video Adapter with an appropriate physical GPU.

  1. In Hyper-V Manager, open up Hyper-V Settings.16
  2. Choose the appropriate GPU to be used with RemoteFX.17

Windows 8.1 as Guest

First we evaluate RemoteFX with Windows 8.1 as a guest in a virtual machine. The client from which we will connect to the VM is also running Windows 8.1.

Using the RemoteFX 3D Video Adapter in a virtual machine requires Windows 8.1 Enterprise as guest operating system. For Windows 8.1 Pro or Core the RemoteFX 3D Video Adapter will not be offered as available hardware to add.

Also be sure that you configure a Generation 1 VM. Generation 2 does not support RemoteFX.

18

  1. Set up a Generation 1 virtual machine with Windows 8.1 Enterprise and ask Windows Update to apply all available updates.
  2. In Hyper-V Manager, you should configure Integration Services to include Guest services(which are not included by default).19
  3. Windows 8.1 with all available updates has the latest integration services installed to work with Windows Server 2012 R2 as a host. So you do not need to update the Integration Services in the VM.20
  4. Add the RemoteFX 3D Video Adapter to your VM and configure the adapter according to your needs.21
  5. Connect to the VM by a Remote Desktop Connection from a Windows 8.1 client. (Note that connecting to our RemoteFX enabled VM by a Virtual Machine Connection is also supported.)
  6. RemoteFX can be verified by checking the display adapter in the VM’s Device Manager.Microsoft RemoteFX Graphics Device – WDDM indicates that RemoteFX is available.22
  7. Executing dxdiag.exe from the Run dialog shows the VM’s supported DirectX features levels, the WDDM driver model, and the amount of graphics memory available.23
  8. The VM’s event log will also contain diagnostic information about the remote desktop connection and the feature support negotiated between the VM and the client. In Event Viewer, open up Applications and Services Logs\Microsoft\Windows\RemoteDesktopServices-RdpCoreTS\Operational. Event ID 34 Remote Desktop Protocol will use the RemoteFX host mode module to connect to the client computer indicates that RemoteFX vGPU is enabled.24

Windows 7 with Service Pack 1 as Guest

Now we evaluate RemoteFX with Windows 7 with Service Pack 1 as a guest in a virtual machine. Again the client from which we connect to the VM is running Windows 8.1.

Using the RemoteFX 3D Video Adapter in a virtual machine is working with Windows 7 Enterprise or Windows 7 Ultimate as guest operating system. (I did not evaluate other Windows 7 SKUs.)

Also be sure that you configure a Generation 1 VM. Generation 2 does not support RemoteFX.

  1. Set up a virtual machine with Windows 7 with Service Pack 1 Enterprise. Before installing any further updates check the version of the Remote Desktop Protocol by opening up theAbout dialog of the Remote Desktop Connection application. The supported RDP version is 7.1.25
  2. Now ask Windows Update to install all available updates. Check the supported RDP version again. It is 8.1 now. So the RDP 8.1 update for Windows 7 SP1 has been installed by Windows Update. But note that as soon RemoteFX will have been enabled the RDP version effective in use when clients connect to this VM will fall back to 7.1.26
  3. In Hyper-V Manager, you should configure Integration Services to include Guest services(which are not included by default). Do not yet add the RemoteFX 3D Video Adapter to the VM. We will do it later.27
  4. We need to update the Integration Services installed in the VM. So insert the Integration Services Setup Disk into the VM and install the latest version.28
  5. When trying to connect to a RemoteFX enabled Windows 7 VM with Virtual Machine Connection, i.e. from Hyper-V Manager without using RDP, you will find out that Virtual Machine Connection is not supported. You must use a Remote Desktop Connection. This is different from a Windows 8.1 VM with RemoteFX where you can connect with Virtual Machine Connection.29
  6. Since a RDP connection is the only way to interact with a RemoteFX enabled Windows 7 VM be sure that the VM has a network adapter and that remote access is allowed in the VM.30
  7. Add all users who should be granted Remote Desktop access explicitly to the Remote Desktop Users group. Do not rely on the dialog claiming that members of the Administrators group can connect even if they are not listed.31
  8. Since Windows 7 Service Pack 1, inbound RemoteFX connections to a VM are blocked by the Windows Firewall by default. There is a group of firewall rules we need to enable to allow RemoteFX. Inside the Windows 7 VM, open up Windows Firewall with Advanced Security. In the Inbound Rules tab, enable all rules belonging to the group Remote Desktop – RemoteFX.32
  9. Now add the RemoteFX 3D Video Adapter to your VM and configure the adapter according to your needs.33
  10. Start the VM, make the first connect with Virtual Machine Connection, wait for the driver installation to finish, then restart the VM.34
  11. Remember that after the restart you can no longer connect to the VM with Virtual Machine Connection. You must use Remote Desktop Connection instead. When connecting with Remote Desktop Connection, be sure that the user name contains the machine name of the VM.35
  12. When connected to the VM, RemoteFX can be verified by checking the display adapter in the VM’s Device ManagerMicrosoft RemoteFX Graphics Device – WDDM indicates that RemoteFX is available.36
  13. Running dxdiag.exe does not show the DirectX feature level clearly but in a Windows 7 VM with RemoteFX it is DX9 even if the physical graphics adapter supports DX11. (A Windows 8.1 VM with RemoteFX supports up to DirectX feature level 11.1 if it is supported by the physical graphics adapter, too.)37
  14. In Event Viewer, open up Applications and Services Logs\Microsoft\Windows\RemoteDesktopServices-RdpCoreTS\Operational. You might not find the expected event ID 34. Instead event ID 33 is present.38
  15. In addition, you will find a warning with event ID 5 in the Admin log claiming that the client does not support RemoteFX.39
  16. When a Windows 8.1 client talks to a Windows 7 SP1 VM via RDP the Remote Desktop Protocol 7.1 will be used which is less optimized to work over WAN or WLAN connections. Close the connection, i.e. log off. To improve the RemoteFX experience, on the Experiencetab of the Remote Desktop Connection client application choose LAN (10 Mbps or higher). Then connect again. Now at least the warning in the Admin log should have been gone.40

Comparison: Windows 8.1 vs Windows 7 SP1

The table summarizes the features supported by a Windows 8.1 VM and a Windows 7 SP1 VM. As always in this guide, it is assumed that the VM is hosted by Windows Server 2012 R2 and that RemoteFX vGUI is enabled.

When talking about the effective RD protocol version in use we assume that we connect to the VM from a client machine with Windows 8.1.

VM Operating System SKU Required Max DirectX Feature Level Supported RDP Version in use Virtual Machine Connection Supported Enhanced Session Mode Supported Generation 2 VM Supported
Windows 8.1 Enterprise 11.1 8.1 yes no no
Windows 7 SP1 Enterprise, Ultimate 9 7.1 no no no

 


Read more »




Help Desk Software by Kayako