Unlike prior versions, vSphere 5 supports only the ESXi hypervisor architecture, the only thin purpose-built hypervisor that does not depend on a general purpose operating system. If you are currently running ESX 4.x you must migrate to ESXi 5, in order to benefit from the unique capabilities and features of vSphere 5 and ESXi 5.
vSphere 5.0 saw the vSphere Web Client make it's entry but with limited functionality compared to the installed vSphere Client.
However now the tables have turned and with the release of vSphere 5.5 VMware are now pushing the vSphere Web Client as the client to manage vCenter Server.
Only the new features in vSphere 5.1 and 5.5 can be managed via the vSphere Web Client and the old vSphere Client will disappear in future releases (possibly with vSphere 6!).
To be honest I like the idea that I don't have to install the correct version client as I work on so many different customers systems, but I do find the web client slow to respond (like View).
If you are looking for a more technical explanation of persistent vs non persistent desktops and how this applies to VMware Horizon View, please read the following article: Persistent vs Non Persistent Virtual Desktops (Horizon View Technical Explanation)
What is a non-persistent virtual desktop?
Pros: Storage utilisation/costs, desktop update/management, increased security
Cons: User installed applications not possible
A non-persistent virtual desktop does not retain any data on the desktop itself after a logoff or reboot. This includes any data such as user settings, application settings, internet bookmarks and so on. Instead this data is retained using another method such as folder redirection to store user settings in a central location and applied to any desktop they logon to.
Share this blog post on social media:
TweetAll advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.