Hi Dejan,  The main reasons for having a cluster would be if you have persistently assigned virtual desktops. This might be because you don't have roaming profile capability (which is built into vWorkspace) or your users want to install and personalise the desktops with their own applications, both of which I discourage because it adds value to these virtual desktops and then you need a cluster for HA and you have to think about backups. To me going down this route you end up losing lots of major benefits of VDI.  If your reason is for managing the hyper-v hosts then I would say that you still do not need a cluster, you might find this blog post useful.   Are the three hyper-v hosts only for the virtual desktops? Where are you thinking of hosting the vWorkspace Connection Brokers and perhaps more importantly the database?  Regards  Paul
Hi,  I'm planning on using vWorkspace VDI farm with three Hyper-V servers, 2008R2 or 2012, in a cluster setup with live migration and shared storage. I was wondering if anyone in community has this type of setup and what are the experiences or issue that you came across during deployment?  thanks Dejan
Desktop Virtualization (vWorkspace) Hyper-V 2008R2/2012 Cluster