Archive for the ‘Migration’ tag
VMware has released a new version of Horizon Mirage. The new version includes new features and bug fixes.
- Optimized storage disconnection handling
- SSL configuration option for Mirage Server installation
- CE Calculator
- Branch Reflector Enhancements
Tim has published a bit more information on his blog.
VMware has published a new version of Horizon Mirage with a few new features integrated.
- Endpoint centralization – Performance improvement when a large number of endpoint centralizations are performed, by reducing the number of IO operations required from the storage.
- Vista OS support – Horizon Mirage supports the disaster recovery use case for Vista, and Vista to Windows 7 migration.
- New help desk Web console – Help desk users can troubleshoot and fix endpoints using a Horizon Mirage Web interface.
- Client and file portal localization – The Horizon Mirage client and file portal now supports: French, German, Japanese and Simplified Chinese.
- Windows 7 in-place migration encrypts endpoints with Sophos 5.5 software – There is no need to decrypt endpoints during an in-place Windows 7 migration.
- Aligned Mirage license scheme to the Horizon user-based license scheme – Horizon Mirage no longer enforces license based on device count.
Coming soon! The VMware Windows 7 Migration Twitter Chat! Join VMware invites everyone to the #vEUCchat on March 26th at 6am and 9am PST.
Who’s chatting with you?
It’s recommended to use Twitterchat. The Hashtag for the event is #vECUchat
Here’s what VMware says:
Windows XP support ends in April 2014, at which time any remaining XP deployments can leave organizations at risk for compliance violations, security vulnerabilities and undesired support costs associated with user satisfaction and productivity. This Twitter Chat is designed to help address important questions and challenges IT is currently mitigating, while offering industry insight and solutions to move toward successful implementations.
A new article on HorizonFlux should get everyones attention who’s involved in Windows Migration projects. Tim Arenz again has published a great read on VMware ThinApp. Here’s a quick quote of his article but please visit his blog an learn how ThinApp can help you within a Windows 7 migration.
However other issues aren’t fixable at all. If an application relies on 16-bit components or is a 16-bit application itself and you want to migrate to a 64-bit version of Windows you are out of luck. The application simply will not work. You could however use VMware Workstation orView to deploy 32-bit virtual Windows machines for your legacy 16-bit applications. Another example for an application which will probably not work if it depends on APIs which are deprecated or undocumented and therefore not available or working different in Windows 7.
Other reasons why an application might fail to work on Windows 7 like deprecated .dll files, hard-coded locations and dependencies to specific versions of Internet Explorer are a perfect fit for ThinApp!
Welcome back to the VMware Mirage Series here at That’s my View. In previous parts of this series I’ve described what home lab I’m using for my Mirage infrastructure and how to install the Mirage Management Server, Mirage Server and the Mirage Management Console. This time you’ll get a walkthrough of the Console. I’ll try to explain all main options available.
The common wizards page is an easy way to perform the most common tasks used in Mirage. From here you can deploy, manager, support and protect all Mirage endpoints. Here’s a list of all wizards.
- Centralize Endpoint
- Disaster Recovery
- Assign Base Layer
- Capture Base Layer
- Windows 7 Migration
- Base Layer Provisioning
- Hardware Migration
- Update App Layers
- Capture App Layer
This option migrates the content of an endpoint to the Mirage Server. The endpoint needs the Mirage Client to be installed. After completing the centralization the endpoint will be protected and managed by the Mirage System.
Here you can restore a Client Virtual Desktop (CVD) to the same or to a new endpoint i.e. in case of a hard drive failure.
Assign Base Layer
Assigning a base layer to a CVD or collection of CVD’s is done here. After validation the layer will be deployed to the selected endpoints over the network.
Capture Base Layer
Capturing a base layer means creating a template for the default content of an endpoint. This layer includes commonly the operating system, service packs, patches and the core applications i.e. VPN client or anti virus solution.
Windows 7 Migration
This options helps migrating an Windows XP endpoint to Windows 7 preserving all end user data.
Base Layer Provisioning
When provisioning a base layer to an endpoint you’re going to clean up the device for corporate usage. After applying the base layer the device will automatically migrate it’s content to the Mirage Server.
During the hardware migration a CVD can be migrated to a new virtual or physical endpoint.
Update App Layers
Editing and assigning app layers to endpoints connected to the Mirage System.
Capture App Layer
Capturing an app layer allows you to capture a set or a single application into a layer for deploying it to a large number of endpoints.
The Dashboard provides a monitoring functionality for the system status and the operations. In a few statistics you can see the system activities and alerts. Information to be found in the dashboard is:
- System Status
- Server Information
- Update Progress
- Data Protection Information
- Compliance Meter gauge
- Capacity Status Information
- Efficiency Benchmarks
The information is provided in form of gauges, graphs and tables.
As the name already says the Task Monitoring gives you an overview of all tasks performed by the Mirage System. In a list you can see all tasks i.e. Cature an app layer or Assign a layer and their status, device and progress.
The Inventory node gives you access to all CVD’s and Collections. From here you can access devices in all states (Assigned, Pending and Rejected)
The Image Composer node is the main point to manage the base and app layers. Within this node you can also manage the Reference CVD’s and rules for all layers.
The driver library is a repository where all drivers for the Mirage endpoints are managed in. An Administrator can manage hardware specific drives here which are stored outside the layers. With an import wizard it’s possible to import new drivers. If configured the system will inject the necessary drivers to all relevant endpoints. The Driver Library copies the drivers from the Mirage system to the endpoints which will then be detected by the Windows Plug and Play mechanism.
The Mirage Reporting helps you to create different reports for storage, device, layer or hardware information. A very powerful tool.
Access the event and transaction logs from here. You can find loads of transactions information here i.e.
- Centralize endpoint
- Upload incremental changes
- Update base layer
- Update App Layer
- Base Layer Caching
- Base Layer Verification
- Restore Prefetch
- Restore streaning
The node gives you also the option to search and filter.
User and Roles
Within the user and role management you can define which user can access which functionality within the Mirage System. You can granularly define the roles as Mirage supports dynamic role-based access control (RBAC). A role can be grated to one or more groups from the Active Directory.
The System Configuration gives you control of the Mirage Servers, Volumes and Branch Reflectors.
I hope this has given you a first impression of the scope of the VMware Mirage solution. This is surely a very powerful tool!
The French blog (english language) www.vladan.fr has published a cool three article series about VMware Mirage. Learn how to install and setup Mirage and in the last article see how to migrate a Windows XP desktop to Windows 7.
I’ve learned that a Windows Xp to Windows 7 Migration is tough for loads of customers as the tools they mostly use aren’t easy to work with. Check out this video about an In-Place migration of Windows XP to Windows 7 with VMware Mirage.