VMware View4.5-Local Mode; Basics

In View4.0/4.0.1 “Offline Desktop” was experimental. In View4.5 this experimental status has been changed to full support. Also, the name has changed; “View with Local Mode”.

First a short description what Local Mode is. With “Offline Desktop” or “Local Mode” a user is able to “check out” his/her VM. This means a user downloads the VM to his Windows based access device (most of the times this will be a laptop). After the download, the user can disconnects his access device, go home and start his corporate VM again and continue working. Next time the user is back at the office, he can “check in’ the VM. All changes made to the VM between the time of checking out and checking in will be synchronized back into the data center so the central located VM is again up to date.

The first time the whole VM needs to be copied to the access device. This, luckily, is based on Thin Provisioning; when your VM is 10GB on the ESX/vSphere datastore but only is filled with 4GB of data, you need to download 4GB. For the record, after the first full download, all synchronizations are based on changes. When synchronizing, data will be compressed and unwanted files like page files won’t be replicated.

You can set a couple Local Mode policies; allow or deny per pool base, the maximum time a Local Mode VM can  go on without contacting the View server, User-initiated rollback and others.

The checked out VM’s will be encrypted, AES-128 bit by default (256 bit optionally). After a check out, a user would still use the View Client to logon to the locally stored VM, using his Active Directory credentials.

Also, an administrator can initiate delta file replication.

What is new, is the use of a “Transfer Server”. This will be a separate physical server or VM. During the installation of the View Manager software, you will be asked which specific mode you want your server to have: Standard, Replica, Security or Transfer. The Transfer server manages check out/in and replication part. It makes the download/upload of VM’s more scalable. The Transfer server needs storage to store “published” Linked Clone Parent VM’s; Image Repository.

I think for now this is a great addition to the View solution. I am glad it is fully supported in View4.5. Yes, I know “the world” is waiting for a Client Hypervisor but when you think about it, this is pretty good;

-1 Platform for online and offline users, familiar way of connecting and managing,

-No strict hardware requirements like vPro CPU’s,

-You can implement a Bring Your Own Equipment very easily

-Have a great user experience with support for Windows 7 Aeroglass and DirectX 9 with 3D