There are a number of ways in which an administrator can publish RemoteApp programs and virtual desktops in Windows Server 2008 R2. The following contains a brief, high-level overview of the publishing options you have, depending on the size of your deployment.
If your deployment requirements are:
In this scenario, you can publish RemoteApp programs and remote desktops in the same way you published them in Windows Server 2008.
On the Remote Desktop Web Access (RD Web Access) Configuration tab:
· Select the “One or more RemoteApp sources” option.
· In the Source name box, type the RD Session Host server name (or if you have a server farm, type the RD Session Host farm name).
This is a new feature in Windows Server 2008 R2, wherein you can specify multiple RD Session Host servers delimited by semicolons in the Source name field.
On the RD Web Access Configuration tab:
This is a new feature in Windows Server 2008 R2, wherein you can point the RD Web Access server to a Remote Desktop Connection Broker (which has the Centralized Publishing service running as part of it), which in turn aggregates the published RemoteApp programs from multiple RD Session Host servers, the assigned personal virtual desktop for the user request from AD, and the published virtual machine farms.
For the detailed steps on deploying personal virtual desktops by using Remote Desktop Web Access, please refer to the step-by-step guide here.
For the detailed steps on deploying virtual desktop pools by using Remote Desktop Web Access, please refer to the step-by-step guide here.
PingBack from http://www.windowsaffinity.com/?p=1971
This second new feature represents yet another glaring omission in Windows Server 2008 RTM, and its resolution means that environments of size can begin considering RDS (TS) for large and dissimilar farms. Essentially, with the original version of TS
I'm looking at implementing this on Server 2008 R2 with HyperV hosted instances of Windows 7 - that's all done - but it seems there is something that's not that intuative to add these instances into a Virtual Pool and assign to an AD groupd for deployment?