VMware Mirage 5.5 Release Notes

Mirage 5.5 | 01 OCT 2015 | Build 105294

Updated on: 01 OCT 2015

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

About VMware Mirage

VMware Mirage offers a unique solution for managing physical or virtual desktops and laptops, and for BYO users, combining 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.

Localization

VMware Mirage 5.5 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese

What's New with Mirage 5.5

Mirage 5.5 facilitates image management for enterprise organizations. It provides a variety of features that control layer updates, endpoint provisioning, and enable administrators to customize the Mirage system by using the Mirage API and Mirage PowerCLI.

New Features

  • Branch PC technicians and administrators can provision new laptops and desktops directly from the device using the self-service provisioning interface.
  • Administrators can specify base layer and app layer download only operations and manually initiate layer updates for a future time, for example, off-peak hours.
  • Administrators can specify bandwidth limitation rules according to time and day.
  • Administrators can update base layers and app layers by using the Mirage API and Mirage PowerCLI.
  • Bare-metal provisioning supports POSReady 2009.

General Enhancements

  • You can delete Mirage layers by using the Mirage Web console even if the layers are assigned to active or archived CVDs.
  • Mirage preserves Static IP and DNS network configurations as part of OS migration, provisioning, or restore operations.
  • Microsoft Office layer conflict validations display the names of the conflicting components.
  • Mirage can manage endpoints protected by McAfee Data Loss Prevention Endpoint (DLP), for various operations, such as OS migration, provisioning, and restore and layer update.
  • Mirage uses MongoDB database for storing system data and small files. For recommended installation configurations see the VMware Mirage Installation Guide.
  • MongoDB database files are managed separately from Mirage volumes.
  • Administrators are notified when there is low disk space on the drive that MongoDB database is running on.

Mirage Web Console Enhancements

  • Administrators can configure the following general settings using the Mirage Web console:
    • View and edit Mirage licenses
    • Import USMT
    • File portal settings
    • CVD auto-create
    • Gateway authentication
  • Drill down to view layer assignments for CVDs that are part of a collection or task.
  • Manage Mirage servers and Mirage Gateway servers.

Known Limitations

The following limitations are known in this Mirage release.

  • Mirage supports up to 1,000,000 files per CVD on 32-bit systems. There are no file limits on 64-bit systems.
  • 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 application 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.
  • 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.
  • You cannot use the Windows Fast User Switching option. You must disable this option 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, perform a Sync Now procedure from the Mirage client UI.
  • You cannot apply a base layer to an endpoint that removes or installs Kaspersky antivirus software. See http://kb.vmware.com/kb/2048424 for additional details and a solution.
  • When restoring a CVD that does not have Sophos SafeGuard Encryption installed to a machine that does have SafeGuard installed, the restoring procedure might fail. See http://kb.vmware.com/kb/2081607 for additional details and a solution.
  • 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 you assign a base layer or an application 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.)
    • When you migrate from an older Mirage version to a newer Mirage version, the existing CVD policy is not modified, and in most cases only the system volume is uploaded.
  • You cannot deliver a SQL server in an app layer. You can perform layer provisioning and OS migration procedures with a SQL server in a base layer.
  • You cannot update a SQL server application using a Mirage base layer update or app layer update.
  • When reverting to Windows XP after an OS migration from Windows XP to Windows 7, 802.1X settings might not be preserved.
  • Mirage only supports delivery of a full Microsoft Office suite to endpoints that do not already have a Microsoft Office suite installed.
  • You cannot deliver two, full Microsoft Office suites in different layers.
  • Scenarios in which an endpoint has more than one version of a full Microsoft Office suite are not supported by Mirage.
  • Windows system restore points do not work on machines that have Mirage installed.
  • When you migrate from Windows XP to Windows 7 on machines that have McAfee Endpoint Encryption installed, you must first perform one of the following procedures.
    • Decrypt the machine before the migration.
    • Centralize the machine, perform a bare metal provisioning procedure that includes user-profile migration, and perform a user-profile migration procedure from the CVD to the machine.
  • You cannot deploy different versions of Microsoft Office applications in different layers as part of the same deployment procedure.
  • You cannot perform migration operations and layer update operations on machines running Check Point Endpoint Full Disk Encryption.
  • Mirage does not support EFS-encrypted files on Windows Embedded Point-of-Service (WEPOS).
  • Mirage decrypts EFS-encrypted files that were captured in the base layer as part of bare metal provisioning.
  • You cannot customize access roles in the Mirage Web Management console.
  • When you use a base layer that has a non-system drive, the layer provisioning operation is blocked.
  • When you perform an enforce layers operation, the drivers on the layer are not updated.
  • English is the only supported language for importing and exporting bandwidth limitation rules to or from a .csv file.
  • If you remove security products as part of a layer removal or layer reassignment procedure, the layer might not work correctly.
  • If Windows already has a driver, Mirage does not initiate plug-and-play driver redetection.
  • IPv6 configuration is not supported by Mirage clients. Verify that you have IPv4 configured on the Mirage clients.

Resolved Issues

The following issues from previous releases have been resolved in this release.

  • Significant Fixes
  • Minor Fixes
  • Significant Fixes

    • When the first VSS scan fails, the branch reflector freezes on caching status.
    • When you upgrade the Horizon View agent with a Mirage base layer or app layers, the upgrade fails.
    • If the Mirage system is in the pending boot state and Windows updates installation begins, the layer verification phase does not start.
    • False validations for Microsoft Office architecture mixing blocks layer update or assignment procedures.
    • When a Mirage storage path contains non-ASCII characters, MongoDB restarts.
    • When User Account Control (UAC) is enabled, you cannot install a Mirage server or the Mirage Management console.
    • If you capture a base layer when the reference machine has pending Windows updates, Windows might fail.
    • When you perform a base layer procedure, the static IP address configured on the endpoint is not preserved.
    • When you try to delete a layer, you receive a warning that the layer is assigned to at least one CVD. The CVDs that have that layer assigned do not appear in the Layer Assignments view.
    • When you apply a download-only image assignment to a device while it is still downloading the assignment, the first download-only assignment appears as running although it is canceled.
    • When you perform a bare metal provisioning operation on a machine that is encrypted using BitLocker encryption, and use the default upload policy, the provisioning operation might fail.
    • When you move a CVD to another volume while the CVD is uploading, incremental upload temporary disk space is not removed from the volume.
    • The CVD Integrity Report fails when node content is "DATA".
    • The branch reflector experiences high memory consumption when downloading a base layer.
    • Frequent storage disconnects might cause MongoDB database to become corrupt.
    • Mirage service is locked by database deadlocks.

    Minor Fixes

    • When you move a CVD to a different volume during an upload operation, the disk space that is consumed by a CVD is not cleared.
    • When you reinstall a Mirage Management server on a machine with a different name, MongoDB does not start.
    • You cannot run an SIS integrity scan on a system that has a single volume that contains system data.
    • Network providers are not correctly merged in layers.
    • Network filters are not set on the target machine as part of a layer update.
    • In rare cases, the Windows boot menu appears after an OS migration procedure or provisioning procedure completes.
    • Several columns are missing in the Layers tab in the Mirage management console.
    • The default domain join user account is not populated in the Endpoint Provisioning wizard for the Mirage Web console.
    • In rare cases, after completing an OS migration procedure, the Microsoft Word error Cannot create work file appears.
    • When restoring POSReady 2009 devices, missing driver validations appear.
    • The path C:\windows\temp contains multiple obsolete temporary files.

    Known Issues

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

      Workaround: Reinstall any user-installed Windows Store applications that do not work.

    • After you perform an in-place Windows 8 migration, you might not be able to create or edit files.
      When you perform 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/kb/2052489

    • Power settings might be re-configured to the power settings of the reference machine.
      When you update a base layer or app layer, the power settings might be re-configured to the power settings of the reference machine.

      Workaround: Add the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\User\PowerSchemes\ActivePowerScheme exclusion to the base image rules.

    • OS migration might fail due to lack of available disk space.
      After you perform an OS migration, if you try to revert to the previous OS image, the migration might fail due to lack of available disk space. Mirage does not consume local disk space for local files that are identical to the files in the reverted CVD image and in the same path.

      Workaround: Verify that the available disk space is greater than the size of the previous OS image. You can run the disk-cleanup utility and delete Windows installations to increase space.

    • OS migration from Windows 7 to Windows 8.1 might fail due to different versions of Sophos SafeGuard
      When you perform 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.

    • After you perform an OS migration procedure, the Hybrid Sleep function might not work.
      Mirage does not detect the compatibility of a processer with the Hybrid Sleep capability of Windows 7 and Windows 8.1. After performing 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.

    • McAfee's Access Protection mechanism might block Mirage operations.
      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.

    • An OS migration procedure might fail when the endpoint has Symantec Endpoint Protection (SEP) version 12.1.671.4971 installed.
      When you have an endpoint that has Symantec Endpoint Protection (SEP) version 12.1.671.4971 installed that you are migrating from Windows XP to Windows 7, the migration might fail.

      Workaround: Before starting the migration procedure, either uninstall SEP or upgrade to a newer version of SEP.

    • Endusers receive an error message when their default Web browser was removed during a base layer or app layer update.
      If you perform a base layer or app layer update that removes a Web-browser application that an end user has specified as their default Web browser, the end user might receive an error message when opening Websites or HTML files.

      Workaround: Advise the end user to re-install the Web browser or select another default Web browser.

    • Having multiple versions of Microsoft Visio on a single machine, the Microsoft Office configuration window might display on an end user's machine when they open Microsoft Visio.
      When you perform a layer procedure that results in multiple versions of Microsoft Visio on a single machine, the Microsoft Office configuration window might display on an end user's machine when they open Microsoft Visio.

      Workaround: This is a known issue with Microsoft Office. See http://support.microsoft.com/kb/298947 and http://support.microsoft.com/kb/314392.

    • The Microsoft Office configuration might appear when you perform a layer procedure that includes Microsoft Office.
      When you perform a layer procedure that includes Microsoft Office, if you open a Microsoft Office application before the "completing system updates" phase is finished, the Microsoft Office configuration window might appear.

      Workaround: Wait for all layer assignment procedures to finish before you run any Microsoft Office applications.

    • Some sysprep operations might fail when delivering a base layer.
      In rare cases, when you deliver a base layer that includes a Windows Live account, some sysprep operations might fail.

      Workaround: Do not capture a base layer that includes a Windows Live account. If you deliver a base layer that includes a Windows Live account and the user experiences issues, recapture the base layer without a Windows Live account.

    • When two or more Microsoft Office applications are installed on a machine, and at least one is part of a layer, the interoperability of the remaining Microsoft Office applications might not work.
      When two or more Microsoft Office applications are installed on a machine, and at least one is part of a layer, the interoperability of the remaining Microsoft Office applications might not work.

      Workaround: There is no workaround for this issue.

    • When there are at least two Microsoft Office products with differing architectures on a single machine, you cannot manually install Microsoft Offices products on the machine.
      When you deploy a layer that includes Microsoft Office products to a machine that already has Microsoft products installed, and the architectures are different, you cannot manually install Microsoft Office products on the machine.

      Workaround: There is no workaround for this issue.

    • If you deliver and then remove a layer that includes Microsoft Office products, you might not be able to manually install Microsoft Office products.
      When you deploy a layer that includes a Microsoft Office product, and you update the Microsoft Office product, if you remove the layer that includes the Microsoft Office product, you might not be able to manually install Microsoft Office products.

      Workaround: See http://support.microsoft.com/kb/290301

    • Microsoft Office 2013 license activation does not migrate with a CVD.
      When you migrate a CVD that has Microsoft Office 2013 installed, the Microsoft Office license activation does not migrate and Microsoft Office is in an unlicensed state.

      Workaround: Manually activate the Microsoft Office license from any application.

    • A taskbar shortcut or desktop shortcut for an application is not deleted when you remove layer that contains that application.
      When you deliver a program in an app layer, a taskbar shortcut or desktop shortcut is automatically created. When you remove the program from the layer, Mirage does not delete the shortcut.

      Workaround: There is no workaround for this issue.

    • When you perform an OS migration procedure on a machine that contains ActivID software, the Mirage screen might disappear.
      When you perform an OS migration procedure on a machine that contains ActivID software, the Mirage screen might disappear.

      This is a display issue. The migration procedure completes successfully.

    • The boot menu language is set to English-U.S. after you perform a bare metal provisioning procedure.
      When Mirage repartitions a device as part of a bare metal provisioning procedure, the boot configuration data does not retain the specified locale, and the boot menu language is set to English-U.S.

      Workaround: There is no workaround for this issue.

    • When you perform a provisioning procedure using a WinPE image, the Multiple file errors during scan warning message appears.
      When you perform a provisioning procedure using a WinPE image, the Multiple file errors during scan warning message appears.

      You can ignore this warning.

    • When the Mirage client upgrade fails after a bare metal provisioning procedure, an event log is not sent to the server.
      When the Mirage client upgrade fails after a bare metal provisioning procedure, an event log is not sent to the server.

      Workaround: There is no workaround for this issue.

    • VSS might fail with a timeout error.
      VSS might fail with a timeout error.

      Workaround: Install the hotfix for Windows 7 SP1 and later, see https://support.microsoft.com/en-us/kb/2996928.

    • When you run the BuildMirageWinPE command with certain OS versions, the procedure fails.
      When you run the BuildMirageWinPE command on the following operating system versions, the procedure fails.

      • Traditional Chinese Windows 7 x64
      • Simplified Chinese Windows 8.1 x86
      • German Windows 8.1 x64
      • French Windows 8.1 x64

      Workaround: Do not use these operating systems to run the BuildMirageWinPE command.

    • POSReady 2009 clients enter a reboot loop after performing a restore operation.
      In rare cases, after you perform a restore operation on a POSReady 2009 machine, the POSReady 2009 client enters a reboot loop because of the recurring LSA Shell failure.

      Workaround: This is a known Microsoft OS issue.

    • When you perform an OS migration procedure on machines that are encrypted using Sophos Safeguard 5.60.1, the operation might fail.
      When you perform an OS migration procedure on machines that are encrypted using Sophos Safeguard 5.60.1, the operation might fail.

      Workaround: Contact the VMware support team for assistance.

    • The operating system of the provisioned device is set as the default operating system.
      When you perform a bare metal provisioning procedure on machines that have multiple boot operating systems, the operating system of the provisioned device is set as the default operating system.

      Workaround: Add the secondary operating system in the boot manager.

    • The Mirage Gateway server might have the status "Up" in the Mirage Management console, but endpoints cannot connect to the Mirage Gateway server.
      When you configure the Mirage Gateway server with a cluster of Mirage servers and DNS round-robin, the Mirage Gateway server might have the status "Up" in the Mirage Management console, but endpoints cannot connect to the Mirage Gateway server.

      Workaround: Contact the VMware support team for assistance.

    • The snapshot time that appears is the last upload time.
      The snapshot time that appears in the Archived files tab is the last upload time, not the time that the snapshot was taken.

      Workaround: There is no workaround for this issue.

    • Checkpoint encryption might cause migration procedures to fail.
      When you perform a migration procedure from Windows XP to Windows 7, and Checkpoint encryption is installed, the migration procedure fails.

      Workaround: There is no workaround for this issue.

    • Custom reports are not removed when you reinstall Mirage.
      When you reinstall Mirage with the create new storage areas option, custom reports are not removed from SSRS.

      Workaround: Delete the custom reports from the Reports tab after the installation finishes.

    • New Safend Data Protection cannot be removed through a layer procedure.
      You cannot remove a Safend Data Protection Agent through a base layer procedure.

      Workaround: Uninstall the Safend Data Protection Agent from the target machines before applying a layer that does not have a Safend Data Protection Agent.

    • New When the SQL server feature Always On is enabled, upgrading the Mirage Management server might fail.
      When you try to add or upgrade a Mirage Management server, and the SQL server feature Always On is enabled, the procedure might fail.

      Workaround: Disable the Always On feature for the SQL server when you add or upgrade a Mirage Management server. Enable the feature after you add or upgrade the Mirage Management server.

    • New You cannot include applications with drivers in bare metal provisioning procedures.
      You cannot deliver an app layer that has applications with drivers as part of bare metal endpoint provisioning.

      Workaround: There is no workaround for this issue.

    • New When using certain versions of Firefox, you cannot connect to the Mirage Web console.
      If you are using Firefox v39.0 or later you cannot connect to the Mirage Web console.

      Workaround: Disable TLS 1.0 and enable TLS 1.1 or TLS 1.2. See https://support.mozilla.org/en-US/kb/tls-error-reports.

    • New When you include a Horizon View client as part of an app layer, you cannot enable USB redirection.
      When you install a Horizon View client as part of an app layer to machines that did not already have a Horizon View client installed, you cannot enable USB redirection.

      Workaround: There is no workaround for this issue.

    • New The Mirage Gateway server cannot bind with LDAP.
      The Mirage Gateway server cannot bind with LDAP using a user name that contains non-ASCII characters.

      Workaround: Use an administrator user name that only contains ASCII characters.

    • New SQL Server Reporting Services 2008R2 is not compatible with .NET 4.5.
      If SQL Server Reporting Services 2008R2 is installed on the same machine as the Mirage server, the Web reporting feature might not work.

      Workaround: Set the reporting service to run on .NET 2.0.

      1. Navigate to <SQL Server install dir>\MSRS10_50.<report server instance name>\Reporting Services\ReportServer\bin.
      2. Open the ReportingServicesService.exe.config file.
      3. Add the below lines after the <configSections>...</configSections> section.

        <startup>
        <supportedRuntime version="v2.0.50727"/>
        </startup>

      4. Restart the reporting service.

    • New MongoDB database might cause Mirage Management servers to fail.
      If the free disk space for the MongoDB database falls below 5%, the Mirage Management servers in the system might fail.

      Workaround: See <insert link to KB article> for a solution.

    • New MongoDB database files might cause data integrity issues.
      When you set MongoDB database files on a remote storage location that has high latency or an unstable connection, you might encounter data integrity issues.

      Workaround: Set the MongoDB database on a low latency, reliable storage path. VMware recommends setting the MongoDB database on a local drive or SAN.