esxcli storage vflash device list
Name Size Is Local Is Used in vflash Eligibility
-------------------- ------ -------- ----------------- ---------------------------------
naa.500a07510d7fe78 457862 true true It has been configured for vflash
esxcli storage vflash module stats get
Num Active VMDKs: 14
I recently noticed an error within the Horizon View events database I had not seen before. This error was in a new environment I was configuring and testing at the time.
The specific error was:
"Failed to perform space reclamation on machine VDI-WIN81-137 in Pool WIN81-POOL1"
The error was occurring ever hour and failing to reclaim disk space from the linked clone virtual desktops. If you have a blackout period configured for specific days and times then the space reclamation process will not run during these times.
It is often standard practice to install the server operating system on C: and then applications and data on additional drives such as E:, F: and so on.
However vSphere Web Client since its 5.0 release though 5.1 and including the latest version at time of writing 5.5 U2, if you install vSphere Web Client to any directory other than the default installation directory you will get the following error when browsing to the vSphere Web Client page.
"HTTP Status 404
The requested requested resource is not available"
VMware Horizon View provides different methods of provisioning and assigning users to virtual desktops. It is important to fully understand what benefits and limitations each method provides so that a solution can correctly be designed. The correct solution may encompass several desktop pools with a mixture of provisioning methods and user assignment.
If you are looking for a less technical explanation of Persistent vs Non Persistent desktops, please read the following article:
There are 2 desktop pool types available, ignoring the terminal services pool, which are; Automated pool and Manual pool.
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.
Following on from creating an RDS Farm within Horizon View Administrator and an Application Pool based on applications hosted an RDS session host, we are going to create an RDS desktop pool.
That's right, you can now have a desktop which is a shared/hosted desktop on an RDS session host (much like Citrix XenApp).
In some use cases a group of staff may not require a full virtual desktop to perform their job. In which case giving them access to a desktop hosted on a shared RDS host would be a more economical solution.
But the access to this shared desktop could be published via the same method access their virtual desktops and using the same PCoIP protocol, which is quite exciting for me and another design option available for those solutions where a group of users just use IE, email, file and print and have a low resource utilisation.
One of the most prominent new features of VMware Horizon View 6, is the ability to utilise Windows Server RDS Hosts to provide server based applications and desktops to users.
This is quite possibly the most desirable feature of recent releases. As a consultant covering both VMware and Citrix solutions, this levels the playing field somewhat in terms of publishing applications (but not entirely) between the two vendors. If anything this will make it more interesting in the next couple of releases as VMware advance this functionality.
So what is all the fuss about? After all you could have created an RDS host with RemoteApp previously and given View users access to these.
The VMware EUC development team has developed a way in which PCoIP can be used as a protocol on RDS hosts, much like Citrix use the ICA protocol. This has required VMware to work very closely with Microsoft to achieve this.
The result is that it's now possible to present applications on an RDS host (or a Collection of RDS Hosts) via VMware Horizon View Administrator. Managing entitlements in the same place and offering these RDS based applications (and desktops) via the same Horizon View Client. All the while using these applications via the same PCoIP protocol as View virtual desktops which should improve the users experience compared to using the standard RDP (RemoteFX protocol).
DirectAccess is a feature of the Remote Access role in Windows Server 2012 and 2012 R2, however it has actually been around since 2008 R2.
The client component of DirectAccess is actually built into Windows 8.x and does not require any additional roles or software installing.
DirectAccess is a remote access solution which can replace traditional VPN (either MS based or otherwise).
Instead of the client having to initiate a VPN connection to the office/datacentre after they logon, DirectAccess automatically connects computers and users to their corporate network if they are connected to the internet.
VMadmin.co.uk is a personal blog with a primary focus on virtualisation within IT, but also covers other related infrastructure technologies.
I've been running VMadmin.co.uk since 2008, when it initially it begun life as a wiki containing my personal configuration tips and notes, which I could access as I travelled. These were not publically available, however I soon decided to open them up to the world and the interest from the audience inspired me to continually add more posts.
At the time of writing this in 2014, (some 6 years on) there are currently 325 posts ranging from how to series guiding through the installation of vSphere, to best practice tips and advice on resolving issues I've personally come across out in the field.
Share this blog post on social media:Tweet
All 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.