Using Offline Desktops in VMware View 4.6

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.

Using Events in VMware View 4.6

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.

Allowing connection to our VMware View desktops 4.6 from abroad

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.

Using VMware View GPO's 4.6

In this document, we'll look at the policies that we can apply at the Active Directory level to our VMware View environment, since we have various administrative templates to be able to manage the agents, clients, Servers, common configuration and especially if we need to optimize the PCoIP protocol. The document shows all the existing GPO's to be able to centrally manage our VMware View 4.6, Of course, in English 😉

Installing and Configuring VMware View 4.6 Connection Server Standard

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.

What's New in VMware View 4.6

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!

Forcing a MAC address on a VMware VM

Sometimes we have the need to change the MAC address in a virtual machine, usually when we want to keep the MAC that we had on a physical computer or for reasons of applications that control it (license servers..). In this document we will see how to force a MAC address on a VM since VMware will allow us only the next range: 00:50:56:00:00:00 – 00:50:56:3F:FF:FF.

Using VMware vMA

In this document, we'll look at the VMware virtual appliance called VMware Management Assistance (VMware vMA), is based on a CentOS distribution 5.2 with vCLI, CIM, Java JRE, vSphere SDK for Perl and vSphere SDK for Java, is a script-based management appliance for our virtual environment.. VMware vMA is a great utility to replace the Service Console and be able to manage our ESXi or vCenter hosts more easily and centrally through scripts/tasks, We can configure it as a log server, Backup, ESX distribution via PXE…