VMware Mirage 5.6 Release Notes

Mirage 5.6 | 08 DEC 2015

Updated on: 08 DEC 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.6 is available in the following languages:

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

What's New with Mirage 5.6

VMware Mirage 5.6 introduces support for in-place OS migration from Windows 7 to Windows 10. Support for Microsoft SQL Server 2014 Express, Standard, and Enterprise editions is also now offered. In addition, Mirage 5.6 offers improved stability compared to the previous releases.

New Features

  • In place OS migration from Windows 7 to Windows 10. Mirage accelerates OS migration of Windows 7 endpoints to Windows 10 with minimal impact on end-users. This includes:
    • Migrate endpoints running a custom Windows 7 image while maintaining the end user's data and settings.
    • Deliver application layers as part of the OS migration operation.
    • Quickly revert the system back to Windows 7 if something goes wrong.
    • Reduce bandwidth consumption when distributing Windows 10 image using Mirage Branch Reflector and WAN optimization technology.
    • Easily migrate Bit-locker encrypted Windows 7 endpoints without the need to decrypt endpoints.
  • You can now run Mirage database on Microsoft SQL Server 2014 Express, Standard, and Enterprise editions also.
  • Administrator can now change the Management Server's MongoDB data path using the Mirage Web Console.

General Enhancements

  • Administrator can change the hostname of a device or specify a naming pattern when provisioning multiple endpoints using Mirage PowerCLI.
  • Mirage can detect latency and stability issues of MongoDB, generate a critical event and suspend the faulty MongoDB to prevent data corruption.
  • Mirage sends an event whenever endpoints encounter branch reflectors issues during layer download operations.
  • Self-Service endpoint provisioning validations now appear in foreign languages (DE, JP, CN, FR)
  • Mirage Gateway components have been updated:
    • Base OS is now SUSE Linux Enterprise Server 12
    • Open SSL is now 1.0.1p
    • Nginx is now v1.8.0
    • Java runtime environment version is now 1.8.0_66

Mirage Web Console Enhancements

  • It is now possible to delete obsolete pending devices from the Mirage Web Console.
  • New notification appears in the Mirage Web Console whenever the system is running with a single active Management Server.

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.
  • Using ReFS file system on Mirage volumes is currently not supported since ReFS does not support names streams.
  • Including applications with drivers as app layers in Windows 10 OS migration operation is currently not supported. It is recommended to add such applications in the Windows 10 base layer used for OS migration.
  • Provisioning a Windows 10 endpoint is currently not supported.
  • Centralizing or restoring a Windows 10 endpoint is currently not supported.
  • Updating the base or app layers of a Windows 10 endpoint is currently not supported.

Resolved Issues

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

  • Significant Fixes
  • Minor Fixes
  • Significant Fixes

    • Mirage v5.5 servers and Management Servers traffic to the SQL database is extremely high causing slow user experience response.
    • When running 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
    • On some occasions, after OS Migration or Endpoint Provisioning Windows Recovery environment is disabled.
    • Last Logged-on user on reference machine is shown to end-user after OS migration.
    • Mirage client auto upgrade from legacy versions sometimes fails.
    • Mirage client does not download Citrix and several anti-virus applications that were captured as app layers.

    Minor Fixes

    • Screen saver appears every 5 second of inactivity while finalizing OS migration before login.
    • Windows Diagnostics and Tracking service causes signature mismatch errors on Mirage client.
    • Failed to export or import layers using server tool.
    • Frequent offline scans are triggered for endpoints with "Layer Management" only policy.
    • Several Mirage operations on CVDS (archive, delete, endpoint provisioning ) fail due to a rare overflow the in CVD's database records.
    • MongoDB critical low disk space status doesn't appear after upgrade from v5.4.
    • On very rare occasions, a device may become suspended and cannot be managed.
    • Server installation terminates sometimes when failing to create performance counters.

    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 https://support.microsoft.com/en-us/mats/program_install_and_uninstall

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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

    • New Custom Windows explorer libraries need to be manually created after OS migration.
    • New End user's wallpaper is not migrated when reference machine and target machine contains the same user with different wallpapers.
    • New Certain types of external hard drives are identified as fixed drives and might cause Mirage to ignore the drive mismatch validation.

    • Workaround: Disconnect external hard drives from the reference machine before capturing a base layer.

    • New Due to a limitation in Microsoft SSRS, exporting reports to .csv format when using SQL Server 2014 Express edition is not supported.

    • To export reports to CSV using Microsoft SQL server 2014, use a different edition of Microsoft SQL Server 2014 Standard or above.

    • New You cannot include applications with drivers in bare metal provisioning procedures when using a 64-bit WinPE image.
      When providing a 64-bit .iso when creating the Mirage WinPE image, you cannot deliver an app layer that has applications with drivers as part of bare metal endpoint provisioning.

      Workaround: Provide the x86 WinPE .iso file when building the Mirage WinPE image. Note: to boot using the x86 Mirage WinPE image, the device's boot mode should be set to UEFI Hybrid or Legacy boot modes.

    • New Japanese, Korean, or Chinese input methods are not supported by default in the Mirage WinPE or Self Service Provisioning portal.

      Workaround: Edit the BuildMirageWinPE.cmd script and add the required Input Method Editor (IME) settings as described in KB: 2138902.

    • New Mirage fails to download\stream files when two files in the same directory have the same shortname.
      In rare cases, Mirage may not be able to complete a restore operation (either in the ‘Restore – prefetch’ phase or in the ‘restore – streaming’ phase). This can happen if several files in the same directory have conflicting names (For example, name of one file is ‘DESCRI~1.HTM’ and the name of the other file is ‘description.htm’).
    • Workaround: Add one of the conflicting files to the UnprotectedArea or DoNotRestoreArea of the master policy. Contact VMware technical support for further help.