Using RD Connection Broker / Virtualization Host with Hyper-V Server 2

[captainnapalmse]

I'm trying to configure my Hyper-V Server 2008 R2 setup for use with a VDI environment for testing. Currently, I am running:

1 x HP BL460c Blade with Windows Server 2008 R2 Enterprise running System Center Virtual Machine Manager and Failover Cluster Manager

2 x HP BL460c Blades with Hyper-V Server 2008 R2 on a failover cluster utilizing Cluster Shared Volumes

I have created virtual machines (Windows XP Professional and Windows 7 VMs) on both of the Hyper-V servers. The failover cluster, live migration, VMM, and all the other components I've tested thus far are working properly. The VMs appear to be functioning normally, as well, and I can use them successfully.

As mentioned ebfore, we are currently evaluating Hyper-V for use in a VDI environment. We already have a VMWare View infrastructure for one of our sites, but would like to implement Hyper-V in another location. I installed all of the RD components and have tried the configurations. While the configuration pages look the same, it appears to me that the RD Connection Broker, Virtualization Host, et al, are looking for VMs only on the SC-VMM box.

Is there a way to route incoming connections through the RD connection broker to virtual machines located on the two Hyper-V servers, or does the virtualization only work when using Windows Server 2008 R2 installs with the Hyper-V and Virtualization Host roles enabled?

Thanks in advance for any assistance.

 

[kmcferrin]

In the RD Connection Broker you need to have machines defined as part of your virtualized pool OR assigned to individual users.

You also need RDS running in Redirected Access mode.

How big is your installation? I really like Hyper-V and the idea of using it for VDI, but based on my experience the Microsoft VDI broker does not scale so well once you get a couple hundred VMs in there. It becomes cumbersome to manage them all.

The consulting company where I work is actually recommending to our customers that you use Quest vWorkspace for Microsoft VDI projects. It provides more robust management capabilities than the MS broker does out of the box (though many of those features are rumored to be coming in Windows 2008 R2 SP1 later this year).

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator