The reason they chose to go this route was that the FRX client did not run on 2008 R2. So if we went with classic terminal services they would have had to use a 2003 Terminal Server, which we saw no reason to go back to now that they have licensing for 2008 R2 RDS.
In the end they will stand up 10 (or so) XP VMs, that will work as pooled VMs. They will also take advantage of RemoteApp for Hyper-V as a way to give access to the FRX client application. Here are my quick setup notes for the pooled VMs running XP (steps are done in order!)
For this example, I started with a base of an XP VM, fully patched, SP3, and added to a domain.
- Make sure Hyper-V Integration Services are installed on the VM
- RDC 7.0 Update for XP SP3 KB969084: http://www.microsoft.com/downloads/en/details.aspx?FamilyId=72158b4e-b527-45e4-af24-d02938a95683&displaylang=en
- Enable CreddSSP: http://support.microsoft.com/kb/951608, reboot
- Install KB961742: http://support.microsoft.com/kb/961742 , reboot
- Run this reg key update to allow RemoteApp for Hyper-V (paste it into notepad and then save the file as: fDisabledAllowList.reg, then run it):
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TsAppAllowList]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TsAppAllowList\RemoteDesktops]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TsAppAllowList\RemoteDesktops\TSRemoteDesktop]
- Run script: http://gallery.technet.microsoft.com/scriptcenter/68462b23-0890-4dbd-95b6-8de5763e4f68
- Make sure Firewall exceptions were made (by the script) or the firewall is turned off.
- Add appropriate Users Group to the local Remote Desktop Users group (enable remote access for this group) Also add any other admin type user or admin group that you want to have remote access.
- Create RDP file (set the computer name to be the name of the redirector) and then edit these lines to match:
- Then add the following lines (this test opens Notepad, so customize to your environment):
RemoteApplicationName:s: Remote Notepad Test
Prompt for Credentials on Client:i:1
- Save the RDP File.
- Set this policy on the OU:
Computer Configuration | Policies | Admin Templates | Windows Components | Remote Desktop Services | Remote Desktop Session host | Session Time Limits | Set The time for disconnected sessions
- Reboot the XP VM so the GPO takes effect.
- Shut down the VM - make sure it shuts down cleanly!.
- Take a snapshot in Hyper-V
- Rename the snapshot: RDV_Rollback
- From a test client , test RemoteApp for Hyper-V, and access to the pool from RD Web Access.
- If you sign your custom made RDP files, then make sure the client you test from trusts the CA cert used to sign the signing cert.
- If you use RD Web Access, make sure the client you test from trusts the CA cert used to sign the SSL cert that the website uses.