Con VMware View Composer conseguiremos distribuir escritorios a los usuarios a partir de una misma imagen para todos, sin tener que andar clonando una máquina virtual origen, or have one full virtual machine per user, This is, los escritorios que generemos a partir de esto no tendrán un disco duro virtual, If not a link’ to a replica of the original virtual hard drive. With this we will achieve impressive storage savings, For example, if we design that our Desktops we want them to have 20Gb of disk, You don't need to allocate that amount to each VM, if, for example, we are going to distribute 50 Desks: 50MV x 20Gb = 1TB of space for VDI or VMware View environment only, as this does not make much sense, VMware View Composer is used to deploy Desktops from a single image, these new Desktops will occupy only their swap memory plus space (optional) What […]

Today we'll look at how to have VMware View desktops offline 4.6, for this we will need a VMware View server 4.6 Connection Server with the Transfer Server role. This server will simultaneously allow up to 20 Desktop Transfers (We can assemble another one for more capacity, High availability or balancing). With this we will be able to allow our users to work offline by downloading the desktops (by composer) on your laptop and when you are back online, upload that desktop back to the VMware View environment.

En caso de necesitar una gestión de eventos en el entorno VMware View 4.6 deberemos configurarlo de forma manual, con el fin de almacenar los LOG’s de nuestro entorno VDI y poder obtener más información en caso que tengamos problemas. En este breve documento configuraremos los eventos de VMware View 4.6 contra una base de datos SQL Server.

By default, PCoIP connections are direct between the VMware View client and the final virtual desktop (where the View Agent resides), this from the version 4.6 changes allowing you to connect through a server that acts as a reverse proxy as it does not ensure the connectivity of the UDP frames that are sent if you do not redirect PCoIP through the Security Server. This Security Server will allow us to connect from the outside without VPN's and without having to open PCoIP to each virtual desktop, since he will be in charge of connecting to the Connection Server and the Connection Server to the virtual desktop.

In this post we will look at the installation of the first server in a VMware View environment 4.6, will be our first connection broker or VMware View Connection Server (Standard), this will be the one that authenticates users through Active Directory and redirects client requests to the appropriate desktop. In case we need a balance of connections we can add a VMware View Connection Server (Replica) or as many as we need, the configuration of these is stored embedded in the LDAP directory and replicated between the servers.

The past 24 de febrero VMware lanzó la esperada versión 4.6 de VMware View que trae una serie de mejoras, problemas arreglados (relacionados con el teclado, corregidos más de 160 bugs…), soporte para el SP1 de Windows 7/2008 R2. VMware View 4.6 se puede montar a partir de VMware Infrastructure 3 version 3.5 Update 5 (or higher) y VirtualCenter Server 2.5 Update 6 o en vSphere 4.0 Update 2 o en vSphere 4.1. Estas son las principales novedades que trae VMware View 4.6: – Soporta uso de smart cards que usen PKCS#11 o con Microsoft CryptoAPI. – Soporte de PCoIP en los VMware View Security servers (sólo bajo Windows 2008 R2) mediante PCoIP Secure Gateway podremos conectarnos ya sin necesidad de VPN’s a nuestra infraestructura virtual desde el exterior. – Redirección de USB’s soportada!