I've been working with VMware View for a number of years, designing, implementing, fixing and upgrading it's various different versions released along the way.
VDI is an area of virtualisation I have grown to really enjoy. It represents more of a challenge than your normal server/DR virtualisation project can offer because there are so many more considerations. Not only that but the end result of your design and implementation is judged by the end users using this environment on a daily basis, if they're not happy, you will soon know about it.
So as a consultant travelling around and seeing various different companies and designing View environments based on more often than not quite lacking information about how they work, the most important take away I have had is ensuring the View environment itself and the infrastructure is configure correctly as a starting point. I will cover other aspects such as users and specific configurations in future posts, here I want to cover the core infrastructure best practices.
What I'm essentally going to divulge is some of my own tips, not too much that my years of knowledge are given away for nothing or essentially my livelyhood now that I'm a contractor. But some useful information to people who understand the concepts around each point mentioned below. enough perhaps make an improvement in their own VDI project or current View environment.
Now the information itself was created some years ago and I've checked through it and it still stands correct today. As you may see this was a PowerPoint presentation consisting of bullet points. What I've done is delivered this as a full day session on VDI/View best practices to a technical audience, expanding and taking questions on the points made in the slides, and the feedback was great!
One final note, if you blindly copy any part of this please kindly quote the source (I will find you)!
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.