VMware Mirage 5.0 Release Notes

VMware Mirage 5.0 | 24 June 2014

Last Document Update: 23 June 2014

These release notes cover the following topics:

About VMware Mirage

VMware Mirage offers a unique solution for managing physical or virtual desktops and laptops that combines centralized management for IT and local execution for end users. When Mirage is installed on a Windows PC, it centralizes a complete virtual copy of that end point to the data center and keeps it synchronized. The synchronization includes changes from a user's Windows PC being uploaded to the data center, and changes from IT being downloaded and applied directly to the user's Windows PC. Mirage enables central image management of desktops while still allowing local execution at the user end point.

What's New in Mirage 5.0?

Mirage 5.0 introduces more than 20 new features, enabling you to extend the management of remote and mobile users. Mirage Image Management now extends to Windows 8.1 desktops. Included are the following new features and improvements:

  • Mirage provides full support for Windows 8.1. Every OS operation for Windows 8.1 also applies to Windows 8.1 U1. IT Managers can now protect and manage Windows 8.1 machines, and also migrate Windows 7 machines to Windows 8.1. The Windows 8.1 features include:
      Windows 8.1 Image Management
      • Support for base layers and app layers.
      • Ability to upgrade to Windows 8.1 U1.
      • Ability to provision Windows 8.1 machines.
      Operating System Migration
      • Ability to migrate user profiles from Windows 7 to Windows 8.1.
      • In-place migration from Windows 7 to Windows 8.1.
      • Ability to migrate to Windows 8.1 using the mass-migration tool.
      • Support for cross 64-bit and 32-bit operating systems for in-place migration. For example, the reference CVD might be 32-bit and the target device 64-bit.
      • The migration preparation tool is no longer required when you capture a base layer for an OS migration.
      Windows 8.1 Provisioning
      • Base layer provisioning of a Windows 8.1 image on a Windows 8.1 machine.
      • Base layer provisioning of a Windows 8.1 image on a Windows 8 machine.
      • Base layer provisioning of a Windows 8.1 image on a Windows 7 machine.
  • The Mirage Gateway server is deployed as a Linux virtual appliance. You can now safely deploy the Mirage Gateway in your DMZ environment. Additional information about Gateway servers, such as status, CPU, RAM, and so on, is displayed in the Mirage Management console. The Gateway server supports up to 5,000 concurrent users.
  • IT managers can centrally monitor and troubleshoot CVDs with the new CVD alarm feature. The CVD Inventory view in the Mirage Management console and in the Mirage Web console has an alarms column, which alerts IT managers when there is an open alarm on a CVD. The Mirage Management console now has a Problematic CVDs node, which includes all CVDs that have an open alarm. Mirage includes alarms such as:
    • Client does not have enough disk space
    • VSS failures
    • Download loop
    • Upload fails on volume, not enough disk space
  • The Mirage Web Manager console includes usability and stability improvements to the CVD Inventory page, the Collections page, and the Policies page. Users with a Protection Manager or Help Desk role can use dockable wizards and a dynamic scrolling function.
  • Mirage uses a device driver validation feature to alert the IT manager in the case in which the layers do not include the relevant drivers, based on the endpoint hardware devices, before sending layers to endpoints.
  • IT managers can perform future server upgrades in a single MSI installation, without having to uninstall and reinstall the system.

Before You Begin

Important: This Mirage release has been updated to address the following OpenSSL issues:

  • The OpenSSL library is updated to version openssl-1.0.1h where necessary to address CVE-2014-0224.
  • The OpenSSL library is updated to version openssl-0.9.8za where necessary to address CVE-2014-0224.
  • This Mirage release does not include versions of the OpenSSL library that are vulnerable to the Heartbleed issue.

Known Limitations with Mirage 5.0

The following limitations are known in this Mirage release.

  • Mirage supports up to 1,000,000 files per CVD.
  • Local user profiles on a reference machine are deployed only in a base layer when used in Windows 7 migration or base layer provisioning. In image assignment and layer updates, only the default local user profile is deployed. Applications that require the creation and use of local user profiles are not suitable for inclusion in a base layer or an app layer.
  • During the streaming restore process, applications cannot access offline files before the Mirage service has started, which might impact their normal operation. You can extend the minimal restore setup to accommodate these specific applications. For further information, see the VMware Mirage Administrator's Guide.
  • All changes to the CVD on the server (base layer assignment, policy change) only propagate to the client on the next synchronization interval (by default, 1 hour, customizable by policy). Use the Sync Device action from the Mirage Management console or the Sync Now action from the endpoint device to force synchronization.
  • If the account password for a machine has expired after a restore operation, you might not be able to connect to the domain. This is a known issue with Active Directory and backups. See http://support.microsoft.com/kb/175468 for additional details and a solution.
  • Mirage requires the default Windows Shadow Copy Provider 1.0. Use the line: vssadmin list providers command to view the VSS providers installed on the computer.
  • Mirage does not support the Windows Fast User Switching option. You must disable it on the endpoint and reference machines before capturing a base layer.
  • Mirage only uploads and stores the main NTFS stream of a file. All other streams are not uploaded to, or restored from, a CVD.
  • Changes to a .pst file are uploaded from the endpoint into the CVD once a day. To ensure that the .pst file is successfully uploaded to the CVD before you perform a restore operation of a CVD to a new hardware, type zeros in the LastFullUploadTicks value in the registry:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wanova\Mirage Desktop Service\LastFullUploadTicks = 00 00 00 00 00 00 00 00
    and click Sync Now.
  • If you use Kaspersky antivirus software, contact the VMware support team for assistance.
  • If you use Sophos SafeGuard software, contact the VMware support team for assistance.
  • If you work with multiple volumes, note the following:
    • Content of non-fixed drives (network maps, volatile devices such as Disk-on-key) is not uploaded to the server.
    • When assigning a base layer or an app layer to the endpoint, Windows fixed-drive letters on the endpoint must be the same as on the reference machine from which the base layer or app layer was captured. (For example, it cannot be C: on a CVD and D: on a base layer.)
    • By default, only the system volume is uploaded to the CVD. You can add volume drive letters to the upload policy to upload additional volumes.
  • Base layering and app layering do not currently support SQL Express or SQL Server.

Issues Addressed in this Release

The following issues have been resolved since the last Mirage release:

Mirage Client

  • After you restore a Windows 8.1 CVD, you might receive licensing errors for some Metro apps. You might have to perform the "Sync licenses" action for the Metro apps to work correctly.
  • In Restore and Rebase scenarios with streaming, the Windows Search Indexer streaming feature might conflict with the Mirage streaming feature.
  • Adding rules to the Unprotected Area in the upload policy might prevent you from properly restoring CVDs. If you restore the CVD later, Windows might fail to operate correctly.
  • Disabling the SuperFetch service on the reference machine might increase the boot time after the Mirage base layer is updated.
  • In rare cases, deploying a base layer might disable the CriticalDeviceDatabase key, causing the system to fail.
  • When you perform a Windows 7 migration with layers, the layers do not capture network components and other drivers.
  • When you perform a user profile migration from Windows 7 to Windows 7, the Windows printers might not migrate.
  • When you perform a user profile migration from Windows 7 to Windows 7, the time zone settings might not migrate.
  • When you perform an OS migration and provisioning actions, the Offline Files database might not work. There might be an increase in the boot time.
  • When you assign a base layer in a multi-volume environment, the base layer is cloned to all volumes, not only the selected volume.
  • When you perform an OS migration with app layers and you try to deliver additional layers, the migration operation might stall.

Mirage Client - Device Drivers

  • After a rebase from a physical machine to a VM, some virtual devices are not installed, such as the pointing device, the audio, and the USB hub.
  • During a restore, in rare cases, the user is unable to log on. This occurs when installation of the keyboard driver plug-and-play requires a system reboot.

Mirage Server & Management Server

  • When you perform an OS migration, Mirage might not detect corrupt base layers or app layers. Also, when Mirage does detect corrupt base layers or app layers, it might not block them during the OS migration.
  • When you try install a Management server that is already associated with a database, you do not receive a warning message that there is already a Management server associated with that database.
  • Mirage does not report Access Denied errors when the connection is lost between NAS and the Active Directory.

Mirage Management Console

  • When you perform the Move CVD Task action, the action status might display as being 100% complete, but the action does not finish.
  • When you select the System Only Restore option during a rebase operation, the target machine's local User Area is preserved and replaces the CVD User Area. This causes the CVD to lose data.
  • When you create the Operational Unit there are limitations to the characters you can use. For example, you cannot use a comma when defining the Operational Unit.

Known Issues in Mirage 5.0

The following known issues affect the Mirage 5.0 release:

  • After applying a Windows 8.1 base layer with a different Windows product ID than the one in the CVD, assigning this CVD to a different hardware device might cause user-installed Windows Store applications to not work. Clicking Repair when you try to launch these Windows Store applications might not repair them.

  • Workaround: Reinstall any user-installed Windows Store applications that are not working.
  • After deploying a base layer or app layer that includes Microsoft Office 2013 or Microsoft Office 2013 SP1, you might be required to manually reactivate Microsoft Office 2013 product keys.
    Workaround: Contact the VMware support team for assistance.
  • When performing an in-place Windows 8 migration, McAfee AntiVirus software might prevent Mirage from setting the correct access rights on directories. You might not be able to create or edit files.
    Workaround: Before you start the OS migration, disable McAfee access protection. For more information, see http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052489
  • When updating a base layer or app layer, the power settings might be re-configured to the power settings of the reference machine.
    Workaround: Add the following exclusion to the base image rules: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\User\PowerSchemes\ActivePowerScheme
  • After performing an OS migration from Windows 7 to Windows 8.1, if you try to revert to the previous Windows 7 image, the migration might fail due to lack of available disk space.
    Workaround: Ensure that the available disk space is greater than the Windows 7 image. You can run the disk-cleanup utility and delete Windows installations to increase space.
  • When performing an OS Migration from Windows 7 with Sophos SafeGuard 5.6 in the base layer to Windows 8.1 with Sophos SafeGuard 6.1 in the base layer, the migration might fail.
    Workaround: Before starting the OS migration, remove Sophos SafeGuard 5.6 from the Windows 7 base layer. After you migrate to Windows 8.1, install Sophos SafeGuard 6.1 on the Windows 8.1 machine.
  • Mirage does not currently detect the compatibility of a processer with the Hybrid Sleep capability of Windows 7 and Windows 8.1. After peforming an OS migration from Windows 7 to Windows 8.1, the Hybrid Sleep function might not work.
    Workaround: Before you capture base layers for OS migration, disable Hybrid Sleep on the reference machine.
  • When you try to install an OS using a Mirage boot USB that has been configured for Windows 8.1 U1, the installation might fail.
    Workaround: When you configure the Mirage boot USB for Windows 8.1, do not use Update 1.
  • In rare cases, McAfee's Access Protection mechanism might block Mirage operations, such as downloading base layers, OS migration, provisioning, and so on.
    Workaround: Exclude the Mirage service from security products.
  • When reverting to Windows XP after an OS migration from Windows XP to Windows 7, 802.1X settings might not be preserved.
    Workaround: Contact the VMware support team for assistance.