SP1 for Windows 7 / Server 2008 R2 brought about 2 new features. Installing them on a standard Windows Server 2008R2 is well document, but requires jumping over some hoops in Hyper-V. Here’s the steps to get it working from scratch, assuming you meet the requirements.
0. Do the following checks before you continue:
a. Ensure that your Windows 7 VM is either Ultimate or Enterprise. (Professional did not work for me)
b. The management PC is connected to your Hyper-V host via LAN
c. Your Hyper-V host has met the necessary CPU / RAM / GPU requirements with drivers installed.
d. You can connect to Hyper-V host via MSTSC
[Update] e. You need at least an i7 Processor which supports Second Level Address Translation. Failure to meet this requirement results in the following error at step 13.
1. Install SP1 on Hyper-V Host.
2. Install SP1 on Windows 7 Client VM.
b. Load up the Integration Disc Image.
c. Update/Repair Hyper-V Integration tools.
e. Ensure that Remote Desktop – RemoteFX(TCP-In) is permitted by the firewall.
f. Ensure that you can access the VM via Remote Desktop. (i.e. via mstsc, with RDP services enabled, firewall set)
g. Shutdown VM.
3. Install SP1 on the PC as you need RDP 7.1 later.
4. On the Hyper-V Host, start Powershell by typing:
[Update] If Hyper-V complains that Powershell is not a valid command, it means that you have not enabled Powershell. Do the following:
- C:\> DISM /Online /Enable-Feature /FeatureName:NetFx2-ServerCore
- C:\>DISM /Online /Enable-Feature /FeatureName:MicrosoftWindowsPowerShell
- Reboot Hyper-V.
5. On the Hyper-V Host, enable RDS-Virtualization by typing in Powershell:
PS C:\> Import-Module ServerManager
PS C:\>Add-WindowsFeature RDS-Virtualization
[Update] If Powershell complains that “ServerManager” was not loaded, rectify it by:
- C:\>Dism.exe /Online /Enable-Feature /FeatureName:ServerManager-PSH-Cmdlets
6. On the Hyper-V Host, enable RemoteFX Embedded Video Capture by typing:
C:\>dism /online /enable-feature /featurename:Microsoft-Windows-RemoteFX-Host-Package
[Update] It is not necessary to restart after this.
C:\>dism /online /enable-feature /featurename:Microsoft-Windows-RemoteFX-EmbeddedVideoCap-Setup-Package
[Update] It is necessary to restart after this.
Partial Source: http://technet.microsoft.com/en-us/library/ff817602(WS.10).aspx
[Update] If upon reboot, you do not see Hyper-V login screen, fear not. Log in to Hyper-V via MSTSC, and install your Graphic Card driver from NVIDIA or AMD:
C:\>pnputil –i –a <path to driver.inf>
8. Start Hyper-V Manager and point to your Hyper-V Host.
[STOP] Before proceeding, HAVE YOU DONE 2e, 2f and 3?
9. Right-Click on your Windows 7 Client VM, select “Settings”.
10. From the left menu, select “Add Hardware”. You should see the “RemoteFX 3D Video Adapter” enabled.
11. Setup your display settings, then click OK.
12. Start the VM.
13. Connect to your VM via MSTSC.
If you try to connect to the VM via the Hyper-V Console, you’ll get an error message saying something like “RemoteFX is enabled and you can’t use the Hyper-V console to manage it”
Of course, this message can be used to check if RemoteFX is indeed running.
[Update] Having some “Unable to start synthetic 3D video driver” on a separate VM. Will update once I fix a fix.
[Update] RemoteFX requires at least an i7 processor supporting SLAT.
14. To tweak the quality / response of the RemoteFX connection, head over to http://www.vdicloud.nl/?p=234 and search for “Group Policy Editor Console”
Just for reference, here’s the specs of my test system:
ASUS X58 Sabertooth Motherboard
Kingston DDR3 PC1333 6 x 4GB
Intel i7-960 Processor
ASUS EN8400GS Graphics Card (installed driver via pnputil)
Hitachi 7200 RPM HDD 2 x 1TB on RAID 1
Phew, that’s quite some work! Next, I’ll follow up with USB Redirection and Dynamic Memory. Hoping it is easier than this~!
Let me know how these instructions work for you. Good luck!
[Update] Now I need to go con someone to swap and i7 with my Core 2 E8400.