GOOD, como hemos visto hasta ahora, VMware Mirage se aplica siempre sobre equipos con un S.O. previamente instalado. Pero tendremos una utilidad parametrizada que nos permitirá crear un pendrive USB con un Windows 7 ya listo con el cliente de Mirage preconfigurado, esto será de suma utilidad cuando tengamos que provisionar equipos para usuarios nuevos, o que hayan perdido/robado su equipo, etc…
Una vez ya tengamos nuestros escritorios centralizados, si tenemos en la organización Windows XP y queremos migrar nuestros equipos a Windows 7 de una forma totalmente rápida y automatizada, manteniendo además las configuraciones de los usuarios, así como sus aplicaciones y además aprovisionandole nuevas apps, podremos aprovecharnos de VMware Mirage!
Well, once we have deployed the VMware Mirage environment on our infrastructure following the steps in the previous document, It's time to start. In this document, we'll look at how to centralize desktops, How to access your backups & restore a file and finally how to apply corporate images on centralized desktops & update their application layer.
In May of this year, VMware acquired the Wanova company, at VMware World Showcased Mirage, a software that will help us centralize and simplify the management of desktop images, both physical and virtual. Being able to have Windows images with corporate applications and deploy them to customers in a simple way, as well as any updates to the images.
One of the new features of vSphere 5.1 was the introduction of vSphere Data Protection (since vSphere Data Recovery is discontinued), a new virtual machine backup and recovery software for our vSphere virtual infrastructure 5.1. Like VMware Data Recovery uses VADP (vSphere API for Data Protection) with CBT (Changed Blocks Tracking), but it also uses EMC Avamar's variable block-level deduplication to optimize copies and restores. Provide deduplication together to all appliance tasks and VMs. It is fully integrated with the vSphere Web Client and will provide the possibility of file recovery to end users.
In this scenario we will update a vSphere environment 5.0 to the latest version manually, without Update Manager, we will first update our vCenter Server Appliance to the new version, then the ESXi hosts and finally the virtual machines.
This document will be useful in reducing the size of our VMware vCenter database, it will also be necessary when it reaches the limits if we have it in a SQL Express, since the services will not start and therefore we will have errors in the registry that will indicate it to us.
In this document, we'll look at deploying VMware Horizon Application Manager, which is a web portal where we will have two interfaces, one for management and one for our users, where we can present our ThinApp applications. Relying on a SaaS cloud service (Software as a Service) users will be able to open the ThinApp applications they need in a very simple way. Also with the recent version of VMware ThinApp, we will be able to integrate our packages more easily with the Horizon App Manager portal.
From VMware LABs, we will be able to download ThinApp Factory to automate the process of creating ThinApp packages in our environment. ThinApp Factory is nothing more than a Debian virtual appliance that can be deployed on vSphere 4.1 (or higher) which has a Tomcat-based web interface. We will be able to upload installers and then automatically transform them from different MV templates and directly generate the necessary ThinApp packages, which we will then distribute to our users.
One of the new capabilities in VMware View 5 is the management of user profiles with VMware View Persona Management, Through a series of policies we will optimize the configuration of network user profiles, a good alternative to Microsoft roaming profiles,
Do Tailor-made training
Windows Server – VMware vSphere – Citrix Virtual Apps & Desktops – Centreon
|
|
¡Let's work together!
|
 |
We are a consulting firm that cares and pampers
|
 |
|
With quality and added value
|
 |
