Hi,
(Would like to cross post this to RD forum, but perhaps better suited here?)
We're currently prototyping up a multi-tenant (note!) whole desktop (VDI) hosting infrastructure using a domain joined cluster of Hyper-V Server 2008 R2 machines. We have established test Win7 VDI pools that are hosted on the Hyper-V clusters (running as Virtualization Hosts). Forefront TMG front ends the infrastructure at the edge, and the current architecture contemplates assigning each tenant a discrete VLAN and domain with optional Exchange Server, SharePoint, etc.
The issue we've up against involves the following: since it is necessary to domain join the Hyper-V Virtualization Host servers to the same (tenant 'owned') domain as the pooled desktops, the server with the RD Connection Broker role installed, etc, how can we effectively share the Hyper-V cluster among several tenants? In other words, the current RD VDI architecture appears to necessitate dedicated Hyper-V clusters on a per domain basis. It's worth noting that this is not an issue with session virtualization (the RDH role), since there is no explicit relationship between the RD Host server and the underlying Hyper-V host in this case.
Am I missing something, here, or are these limitations real and unavoidable?
Please let me know if further clarification is required, and I look forward to your replies.
Thanks,
Andrew