The connection broker will support two kinds of virtual desktops. Since VMM is also intended for managing virtualized servers it might not be the best choice for virtual desktop administration. My guess is that ISVs will offer management tools that will focus on VDI. The Remote Desktop Connection Broker will include “extensive” APIs which allow third party vendors to add management and scalability features. The Windows Server Division Weblog wrote: “Together with Hyper-V and System Center Virtual Machine Manager, the Remote Desktop Connection Broker enables a VDI solution for low-complexity, departmental environments, and a platform for partners who are delivering rich, extensible solutions where heterogeneous client support is a prerequisite, and when enhanced management and scalability is a requirement.” APIs However, it is not clear if one will require VMM in order to use VDI. The article doesn’t mention it explicitly, but I think that VMM will also support VDI.
System Center Virtual Machine Manager (VMM) Whereas the Session Broker allows users to reconnect to a specific server in a load-balanced terminal server farm, the Connection Broker will manage presentation virtualization (terminal services) and desktop virtualization connections. The Connection Broker will replace the Windows Server 2008 Session Broker. This will certainly push Hyper-V adoption. Virtual desktops will run on a Hyper-V host.
0 kommentar(er)
