You might even be able to demonstrate that the VM is indeed better performing in many ways, yet the response might be that they still don’t have enough RAM, CPU, etc. Comparisons between their physical machine and the VM are inevitable, and they may interpret a VM with half the processors and RAM as their physical machine to provide only half of the experience. As VMs become more exposed to the end users (whether they be for VDI, or other user-facing needs), your technical users may become overly curious by what’s “under the hood” with their VM. Those of us who have virtualized our infrastructures are accustomed to this. Virtualization Administrators know that good performance is often a result of a collection of components (storage, network, CPU, hypervisor) working well together through a good design. It’s a weird, but very real aspect of a deployment like this. Don’t underestimate this emotional connection between user and computer. You may have users who complain about their existing computers, but are apprehensive at the notion of it being taken away for something that isn’t tangible. Some embraced it for what it was (an appliance to be more productive), while others chose to be more suspicious. It was interesting to observe how some interpreted the technology. Being able to access a remote system from behind one corporate network to another was as productive as it was cool. From a remote interaction standpoint, the improvements most often showed up where it was really needed remote display over highly latent connections, with convenience of access. Comments like that are a good indicator of success. One of our most frequent users often stated that he simply forgot where the work was actually being performed. Once things were operational, the ease and ubiquity of access to the systems was impressive.
#Install wyse pcoip protocol series
Hopefully this series has helped you gain an understanding as well. I wasn’t entirely sure what to expect, but was determined to get a good feel for what VDI in 2012 could do. I was given the opportunity to try VMware View for a few different reasons (found here). But first, here is a quick recap of what has been covered so far. Well, you’re in luck, because this post is about how View worked, and what was learned from this pilot project. Now that VMware View is up and running, you might be curious to know how it is working.
0 kommentar(er)
