Hi,  Features lost when using VMware instead of HyperV: You'll lose "HyperCache" HyperCache uses RAM to cache the most common disk IO for a HyperV template. This speeds up the VM due to fewer real read/writes from the disks. When working effeciently, this is a big performance boost. Especially if your physical disks are slow.  Your question "I’m going to face different challenges such as Pooled VDI on Hyper-v using disk referencing where the parent setup intend and the child VMs are linked to small disk file? Is this still the case with VMWare..?"  Yes, VMware has "Linked Clones" this works in a very similar way. eg, Parent VM (That you use as a template) Child VMs (That you use as VDI) the Child VM works in the same way as a snapshot, it only records the changes so the disk size can be very small.  You could always leave your SQL where it is.  However, if you search the KB we have a good migration guide.   Thanks, Andrew. 
Hi, Due to Hyper-v complication in CSV setup and due to my ability to try understanding those complication, while on the other hand I don’t call myself as an expert in VMWare vSphere but I do have decent amount of hands-on experience in VMWare product since ESX version 2.5. When it comes to troubleshooting cluster issue on VMWare, maintenance, etc etc… All this kind of troubleshooting won’t impact other hosts in the cluster. Unlike with Hyper-v which gave me a great nightmare. VMWare virtualization platform provides the same concept as Hyper-v Virtualization platform, with enhanced feature, less cost, less reliability and stability as well as complex in to setup and troubleshoot in comparison to ESXi. It’s just my opinion, others has his own opinion and justification but that’s not the argument. My arugment is, while I’m fully understanding how vSphere works let me stick with it rather than wasting time in understanding a new product that provides same concept (Virtualization). That’s that main reason why I wanted to move my vWorkspace VDI environment to the VMWare setup, but the main questions are and before I detailed down the steps and the approach options, I would like to hear from others in relation to vWorkspace features in conjunction to Hyper-v vs VMWare setup. I’m going to lose any real features that I don’t live with it unless I have Hyper-v setup? I’m going to lose VDI performance when it comes to user experience? I’m going to face different challenges such as Pooled VDI on Hyper-v using disk referencing where the parent setup intend and the child VMs are linked to small disk file? Is this still the case with VMWare..?   Current Setup:  Before I jumped to the migration path I would to go with, I will introduce the VMWare Servers to host couple of VDI machines managed by vWorkspace which is setup on Hyper-V servers. I will see how that goes in terms of performance, user experience, user profile redirection, template creation and provisioning along with its customization… I can see the best approach for this Migration Option is the following, please feel free to add any point.  1.      Create VMs for vWorkspace roles in VMWare Setup, joined to the domain, patches etc etc.. 2.      Add all VMs part of Backup Jobs. 3.      Setup each Role of vWorkspace on VMWare VMs;  a.      Broker03 b.      Web03 c.      App03 with RDSH Role, make sure to install the RDSH Terminal Services Roles, and install Licenses and activate them. Install other Apps and Point them within the Managed Application Group. d.      File Server03 with DFS (User Profile Server), make sure DFS replication works correctly.. Configure vWorkspace Silos. (It seems vWorksapce limitation can’t point more than on DFS server in the Silos… Checkbox instead of ComboBox selection) J e.      SQL03 2012 R2 Standard in Cluster Mode. Will make sure the clustering failover works on VMWare setup. 4.      Will make sure the Golden Image template, provisioning works perfect. 5.      Will configure managed Applications and assign them to test users.  6.      Will make sure My Documents GPO redirections works. s 7.      Will make sure the test account is pointed to the correct User Profiles parameters in vWorkspace to make sure the user gets whatever has been created on Hyper-v VMs.  Disconnect Hyper-v Web Servers                 If all of the above works, introduce another VMWare VMs part of the existing vWorkspace Setup and test failover.  Decommission of old servers.  Is it just simple uninstall and it going to delete itself from the database of vWorkspace..? Or is there a special precaution that I must take care of…?   Much appreciate your input. Regards,         
Migrating vWorkspace from Hyper-v to VMWare