Posted by: shu in VMware View, Load balancing on
Feb 22, 2012
A load balancer for VMware View is not a requirement in a VMware View infrastructure with less than 2000 users. Even when there are multiple VMware View Connection servers for high availability, a single VMware View Connection server can handle up to 2000 connections so it’s not a big deal that the sessions are not evenly balanced. You do however want to have multiple VMware View Connection servers for high availability and to be able to access multiple VMware View Connection servers from a single point of access. A load balancer provides that functionality but is often expensive and gives additional functionality not needed for smaller deployments, like SSL Offloading. There is however a free “Enterprise-ready” load balancer available from Citrix: Netscaler VPX Express. There is a 5 Mbit throughput limit, but that is not an issue and in this article I explain why.
Posted by: shu in VMware View, Local Mode on
Jan 27, 2012
I’ve been working with VMware View Local Mode for couple of weeks now and I wanted to share my experience. VMware View Local Mode allows a virtual desktop to be downloaded to a laptop or desktop and to be executed locally. The CPU, memory, disk, network and graphics from the local desktop is being used to execute the virtual desktop. No remote display protocol is being used. VMware View Local mode is also part of the Client Side Desktop Virtualization (CSDV) Smackdown, a whitepaper which explains what CSDV is, when to use it and what the possibilities are. This whitepaper will be comparable to the VDI smackdown, only this time it will not be about server-hosted desktop virtualization, but client-hosted desktop virtualization. This whitepaper is expected to be released in Q1 of 2012. In this blogpost I will share my experience with VMware View Local mode, how it works and what doesn’t work.
In my last blog I talked about Obsolete clients in ConfigMgr. This happens during multiple deployments on the same device. There is also a known issue between ConfigMgr in combination with VMware View. Till VMware View v4.0 there was no refresh option possible, so when deleting and provisioning a new VDI desktop, a new object gets created in ConfigMgr collections.
