VMware Horizon Mirage 3.8

VMware® Horizon MirageTM 3.8 Release Notes

VMware Horizon Mirage 3.8 | 10 December 2012 | Build 898678

Last Document Update: 6 December 2012

These release notes cover the following topics:

About Horizon Mirage

VMware Horizon Mirage offers a unique solution for managing physical laptops and desktops 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?

Mirage App Layers

This version offers a new solution for packaging and distributing applications to user end points. Adding to the existing image management capabilities app layering enables IT administrators to define discrete layers that contain only applications, and to deliver the app layers to Mirage-managed devices independently of the Mirage base image.

Application layers delivered via Mirage:

  • Appear as having been fully installed on the user endpoint.
  • Do not rely on application virtualization technologies.
  • Execute locally on the end point.
  • Do not require network access for normal operation.

VMware Mirage 3.8 Documentation

VMware Mirage Administration Guide

VMware Mirage App Layers Capture Guidelines

Resolved Issues in the VMware Mirage 3.8 Release

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

  • USMT times out because of Trend Micro triggered streaming of files.
    Configure USMT as a trusted process in Trend Micro.
  • Distributing applications via the base layer that will Upgrade/Downgrade existing versions installed in the Machine Area can cause duplicate entries in the Add/Remove Programs menu (e.g. Firefox).
  • During a rebase with offline folders, the offline folders cache is sometimes corrupted and the user cannot use the offline folders on the target machine.
    If this should occur, contact the VMware support team to resolve the issue.
  • Users connected to a server but residing on an un-mounted volume are still shown as connected with no indication that they have a problem.
    If users cannot perform upload, check that the volume status is ok.
  • The Dashboard is cropped when using large fonts (120 DPI). Currently only 100 DPI is supported.
  • If the IT manager deletes a CVD while the client is initializing upload, the device will appear in the pending list only after the initialize action is finished.
  • After a user profile migration, the streamed file may appear as being offline. The file is downloaded successfully and can be used, but may have an offline bit.
    Remove the offline bit from the file attribute.
  • While running a USMT migration, the Mirage system tray icon displays Idle state.
  • Driver profile validations in a restore are based on the target device and not on the CVD. This may display a wrong validation message.
    Ignore the warning validation in this case.

Known Limitations with Mirage 3.8

The following limitations are know in this Mirage release.

  • Mirage supports up to 1,000,000 files per CVD.
  • Local users on a reference machine are not deployed through in a Base Layer, except when used in Windows 7 migration. In image assignment and layer updates only the default local user profile is deployed. Applications requiring the creation and usage of local user profiles are not suitable for inclusion in a Base Layer.
  • During streaming restore, applications will fail to access offline files before the Mirage service has started, which may impact their normal operation. You can extend the minimal restore set to accommodate these particular applications. For further details refer to the Mirage Administrators Guide<./li>
  • All changes to the CVD on the server (Base Layer assignment, policy change) will propagate to the client only on the next synchronization interval (by default, 1 hour, customizable by policy). Use the Sync Device action from the management console or the Sync Now action from the endpoint device to force synchronization.
  • If the machine account password has expired after a restore operation, you may not be able to connect to the domain. This is a common issue with Active Directory and backups. See http://support.microsoft.com/kb/175468 for resolution and more details.
  • Mirage requires the default Windows Shadow Copy provider 1.0. In order to view the VSS providers installed on the computer use the following command line: vssadmin list providers.
  • Mirage does not support the Windows Fast User Switching option and it must be disabled on the endpoint and reference machines before capturing a Base Layer.
  • Mirage will only upload and store the main NTFS stream of a file. All other streams are not uploaded to or restored from a CVD.
  • PST file changes are uploaded from the endpoint into the CVD once a day. To ensure that the PST file is successfully uploaded to the CVD before performing restore of a CVD to a new hardware, reboot the client and click on Sync Now. As a result, the PST file will be uploaded, and then you can proceed to the reassignment operation.
  • Kaspersky antivirus - please contact Support for deployment instructions.
  • Sophos SafeGuard - please contact Support for deployment instructions.
  • Clients with multiple volumes
    • Content of non-fixed drives (network maps, volatile devices such as Disk-on-key) will not be uploaded to the server.
    • When assigning a Base 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 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 may add volume drive letters to the upload policy to upload additional volumes.

Known Issues with VMware Mirage 3.8

The following known issues affect the Mirage 3.8 release:

Mirage Client

  • The VSS snapshot during final phases of the layer update operation may fail with a Shim execution failed to complete warning and the Mirage client automatically retries it later.
    Mirage recovers automatically.
  • Clicking Cancel when the Finalize Layer Capture wizard is refreshing device information may show an incorrect list of installed applications.
    Sync the device and retry.
  • In rare cases, after restoring a CVD with layers, the Mirage client may malfunction when new layers are assigned.
    Recentralize the malfunctioning device to a new CVD and then assign the layers you want. This operation will not remove previous layers.
  • Mirage may fail to restore a CVD if the following registry key is missing: Software\Microsoft\Windows\CurrentVersion\WindowsBackup.
    Create this registry key in the CVD and upload it before restoring again.
  • In rare cases, Mirage may continuously fail to complete a rebase operation with a FileNotFound error.
    Contact the VMware support team.
  • The Mirage client may malfunction if the Microsoft Software Shadow Copy Provider service isn't properly installed on the machine (for example, if the SYSTEM\CurrentControlSet\services\swprv key doesn't have a Start value.)
    Follow the Microsoft guidelines to fix the service in the machine (for example, by adding the Start value in the registry with value 3).
  • The Mirage desktop service process may appear to consume a significant amount of memory in Task Manager.
    The process automatically releases acquired memory when needed.
  • On layer update operations, the Mirage Management Console Transactions view may show transactions for base and app layers that were not changed in the layer update operation.
    This can be safely ignored.
  • A logged-on domain user is unable to access his CVD through the File Portal. Opening CVD properties > File Portal shows the user under Local User but File Portal User is empty.
    1. Log out the user and log in again on a remote machine when Mirage is connected. OR
    2. Manually add the user name to the File Portal User column.
  • In rare cases, the Mirage client may fail to resume an upload operation and will show a malfunction balloon.
    Mirage automatically recovers and resumes the upload.
  • During the layer update operation, the Mirage client may enter a malfunction state, automatically recover, and retry the operation.
    Mirage recovers automatically.
  • Plug-and-play driver installation during streaming may fail for drivers that require access to offline files during installation.
    Trigger plug-and-play driver installation by clicking Update Driver in the Device Manager after streaming is completed.
  • In rare cases, at the first Windows startup after applying a base layer, the Mirage user experience may slightly degrade for the first few minutes after startup.
  • Rebooting the machine while the Mirage client is being upgraded/installed may leave the Mirage client in an inconsistent state.
    Uninstall the Mirage client with the CleanState script (available from the VMware support team) and then reinstall the Mirage client.
  • Mirage does not support provisioning/migration/restoring to different hardware for Windows machines which use the UEFI/GPT configuration.
    Use the legacy MBR configuration.
  • Windows system restore points do not work on machines installed with Mirage.
  • Base layers that are used for XP to Windows 7 migration, must be re-captured with the Mirage 3.0 Client after upgrading from Mirage 2.0 to Mirage 3.0.
  • The Client does not start the upload process if base layer verification has already started - even if the Force Upload interval has passed.
    The Client will upload after the base layer is delivered successfully, or if the base layer assignment is canceled.
  • The Check Reference Machine menu option is missing from the Admin Tools menu on a Pending reference device in suspended mode. This happens only if the device becomes disconnected after being suspended.
    Unsuspend the device.
  • After a Selective Restore, a new user profile might be created for a preserved user profile. This only happens when restoring between a CVD that does not include the specified user to a device that does have the user profile. This is mainly relevant when restoring to an older snapshot that does not include the user profile. In this case, when the user logs in, he will have a new user profile but without its content.
    Manually copy data out of the old user profile, or only perform Selective Restore between CVDs and devices that have the same user list.
  • Canceling a Take VSS snapshot operation on the desktop might result in an Access Violation exception.
    Desktop will malfunction and automatically restart and retry the operation.
  • In rare cases, a post base layer script failure will not be reported at the server. This can happen if the post base layer script runs before the client is connected to the server.
  • A Driver package sent with a base layer that includes unprotected files will not work properly on the end points.
    Use the Mirage driver library feature and don't place these drivers in the base layer.
  • Reverting back to an XP CVD snapshot after migrating the client to Windows 7 will leave some Windows 7 directories on the machine.
  • Unprotected folders are uploaded by Mirage (only folders, not the files). This is due to Recursive rules in the policy that apply on the same folder in unprotected include and unprotected exclude, causing the inner folders to be protected.
  • File Level Restore (FLR) on offline files during streaming is not supported.
  • Restarting a client machine during Mirage client upgrade may cause the Mirage client to be removed from the machine.
    Manually install the Mirage client. If the Mirage client fails to install, contact the VMware support team.
  • After reverting back from a Win 7 snapshot to a XP snapshot with a different bitness type, Mirage can't be uninstalled.
    Contact the VMware support team.
  • The status window flickers between startup steps and streaming. After the pivot process, when the client starts the ignition steps and streaming, the status window reports both states interleaved.
  • In the User State Migration flow, local accounts on the source machine are not migrated to the new machine.
  • User profile migration is not supported if some or all user profile folders are redirected to a non-system drive.
    Call the VMware support team before performing user profile migration in such circumstances.
  • Open with does not work during streaming.
    Open the file by double-clicking it, or open the application first.
  • Reverting back from Win7 to an XP OS may leave some win7 directories on the machine, such as Program files (x86).
  • Client upgrade may fail after uninstallation of McAfee enterprise A/V version 8.8. When the McAfee software is uninstalled from the end user machine, it leaves its vb_script scan module registered in the registry (in a corrupted state). This means that the vb_script can't be executed by the Mirage MSI installer and prevents the Mirage client from being installed.
    See: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/error-2738-could-not-access-vb_script-run-time-for/1a4499ae-8bc1-4534-9c6f-4d399ac70d9a.

Mirage Client - Application Compatibility

  • By default, Mirage does not protect *.nsf files, which may lead to Lotus Notes errors when trying to open .nsf files (for example, name.nsf) after restore operations.
    Change the upload policy to include *.nsf files in the protected area.
  • In rare cases, applying a layer with a new version of Firefox on a machine with an older version of Firefox may lead to Babylon errors (mozglue.dll not found).
    Use one of the following workarounds
    • Uninstall Firefox, delete all the files in the c:\program files (x86)\mozilla firefox directory and reinstall Firefox.
    • Delete all the files in the c:\program files (x86)\mozilla firefox directory and then Enforce the Firefox layer.
  • After removing the CA Internet Security Suite (2010 version and later) using the Mirage app layer or base layer mechanism, the network may not be available.
    Run netsh winsock reset using the command line (as administrator) to restore the network to normal operation.
  • Auto-updating the Vipre anti-virus (from Vipre) after it was delivered from a layer, then removing this layer, may leave leftovers of Vipre in the machine, resulting in an error dialog box.
    Use one of the following workarounds.
    • Completely remove Vipre as instructed by the vendor (using a removal script).
    • Remove the Software\Microsoft\Windows\CurrentVersion\Run value corresponding to Vipre.
  • Distributing the McAfee Agent with an app layer or base layer when a different version of McAfee Agent is already installed in the CVD may lead to duplicate McAfee Agent entries in add/remove programs.
    Revert the CVD to a snapshot from before the layer was applied and update the McAfee Agent manually.
  • Delivering Altova XMLSpy with an app layer may remove the association of .xlsx and .pptx files to Excel/PowerPoint.
    Manually change the associations by using Open With....
  • Delivering Apple applications (for example, QuickTime) with a layer to a CVD which has an Apple application (for example, iTunes) of a later version may cause the application in the CVD not to launch or function as required.
    Capture a new app layer with the latest version of the Apple application you are trying to deliver and use it instead of the older layer.
  • Delivery of Corel Draw with a layer may lead to a one-time configuration screen when the application is launched on the end point.
    The application works correctly after the configuration is completed.
  • Applying a layer with CA Internet Security may leave the machine without the CA Internet Security firewall properly installed.
    Re-install CA Internet Security manually.
  • After delivering Symantec Endpoint Protection v12 with a layer, the Symantec teefer network component may not be properly installed.
    For Symantec Endpoint Protection - Consumer version: Turn Off the Symantec Tamper Protection option with Change Settings > Client Management, and clear the Tamper Protection checkbox.
    For Symantec Endpoint Protection - Managed/enterprise version: Add an exception for Wanova.Desktop.Service.exe as described in http://www.symantec.com/business/support/index?page=content&id=HOWTO55213#v39871590 .
  • The base layer update process does not support Kaspersky total space security versions.
  • Mirage cannot distribute Microsoft SQL Server using the base layer update process. Microsoft SQL Server uses locally installed Users and Groups that are not distributed by Mirage.
    Install Microsoft SQL Server on the endpoints as part of the Machine Area.
  • Distributing Microsoft Live Messenger from the base layer when a different version of Microsoft Live Messenger is installed in the Machine Area can cause Messenger not to work. The error msnmsgr.exe entry point not found (uxcore.dll) appears.
    Perform M-Cleanup, or manually remove the conflicting version of Live Messenger before distributing the base layer. The file that needs to be removed in this case is: c:\Program Files\Windows Live\Messenger\uxcore.dll.
  • The Mirage Client fails to update certain Windows files when McAfee VirusScan Enterprise is installed with the Prevent Windows Process Spoofing option set.
    Either mark Mirage as a Low Risk Process (see https://kc.mcafee.com/corporate/index?page=content&id=KB58692 , or disable the Prevent Windows Process Spoofing option.
  • Mirage cannot distribute the Alcohol 120% software via a base layer update as it does not break current installations on endpoints.
  • After removing the Sun Java Runtime Environment via a base layer update on a 64-bit machine, a problem arises when reinstalling the same version.
    Install a newer version of the Java Runtime Environment or manually delete the key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft.
  • The AutoPlay menu may show multiple options after a base layer update.
  • When a new version of an already installed application is installed from a base layer, the application conflict report may indicate that the application is being installed and not updated.
  • Upgrading Office 2007 to Office 2010 on a user machine that has Visio installed prevents the user from uninstalling Visio 2007 in future.
    Run repair on the Visio 2007 and then uninstall it.
  • When a base layer is assigned during Centralize end point, application conflict warnings do not appear.
  • Visio 2007 is not activated after a base layer update with Office 2007.
    Clean the Visio product leftover from the base layer, see http://support.microsoft.com/kb/895456.
  • Mirage does not support downgrading Office 2010 to 2007 through the base layer mechanism.
  • The Program List in MMC may not show applications which are listed under the following registry key in the CVD: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products.
  • Unactivated Office applications may also appear in the list of Office applications during the capture base layer wizard process.
  • Following a rebase of a CVD with pending WUs, WU failure may occur.
    Ignore the WU failure and re-check for WUs after reboot.
  • If Enforce Core Image with user application removal is performed on a CVD that has Google Chrome installed by the user and configured as default browser, the machine will be left without a default browser.
    Select another browser as the default browser.
  • User profile migration will not migrate Office application data if the CVD is Win7 64 bit and the Office version is 32bit.
  • Mirage fails to update files on a Symantec protected endpoint.
    Add Mirage processes to Symantec's Exceptions Policies.
  • Outlook may fail to open hyperlinks after a base layer update which changes the browser.
    Re-set the default browser settings.
  • Checkpoint full disk encryption software may cause BSOD to occur on the target machine after a rebase.
    Create the following value under this registry key on the target machine: HKEY_LOCAL_MACHINE\ControlSet001\Control\CriticalDeviceDatabase\gendisk] Service"="disk.
  • When delivering McAfee in a base layer, the McAfee Agent GUID comes from the base layer and is duplicated to all the endpoints. This causes all machines to appear the same in McAfee Management.
    See https://kc.mcafee.com/corporate/index?page=content&id=KB56086.
  • After Win7 migration, the target device has the same client Machine ID as the reference machine.
    Windows can generate a new CMID using: cscript c:\Windows\system32\slmgr.vbs /dli.
  • When a base layer that was captured on an ESX machine with ESX VMware tools is assigned to a Fusion machine, a BSOD error may occur. This happens because a version of VMware tools ESX is installed on the Fusion machine.
    Do not install VMware tools on the ESX reference machine if you want to use this reference machine to manage Fusion machines as well. Use the post base layer script to install VMware tools, or install VMware tools on the Fusion machine before applying the base layer.
  • Assigning a base layer with McAfee on a Fusion VM causes no network connectivity.
    The VMware support team will supply a script that must be installed in the reference machine before capturing the base layer.

Mirage Client - Device Drivers

  • Ghost devices might appear in the Device Manager after migration/base layer update.
    This does not affect the user in any way. The device can be removed manually using Device Manager or a post migration script.
  • Enforce base layer/base layer update might cause device reinstallation. This happens when the base layer includes device drivers older than the ones installed on the target machine.
    Make sure the base layer includes the latest versions of all drivers.
  • Enforce base layer/base layer update might cause graphic device reinstallation. This happens when the base layer includes a graphics driver that does not match the target device.
    Remove all graphics drivers from the reference machine. (See the appropriate guidelines document.)
  • After a base layer update, a problem occurs when installing drivers from the Driver Store. This can happen if the Reference Machine has a driver installed with the same name but a different binary than the one included in the Driver Store (e.g SoundMAX Audio Driver).
    Uninstall all unnecessary drivers from the Reference Machine.
  • After a rebase to VM, some Virtual Devices are not installed (Pointing Device, Audio and USB hub).
    A post base layer script is available to fix this issue. Contact the VMware support team.
  • During a restore, in some rare cases, the user will be unable to logon. This happens if installation of the keyboard driver plug-and-play requires a system reboot.
    Perform a hard reboot of the machine.

Mirage Server & Mirage Management Server.

  • The Start App Layer capture task and the reference machine may be unable to proceed to the Recording Layer state. The reference machine completes pre-scan but the upload fails in a loop with an IncorrectManifestData error.
    Cancel the current Capture App Layer task and start it again.
  • In rare cases, when a volume is disconnected, the Revert to Snapshot operation may stall in the middle, without the ability to proceed or to be cancelled.
    Currently not available.
  • A Capture App Layer task is unable to proceed after the task is paused and then resumed.
    Cancel the task and restart the capture.
  • The driver import process may fail due to Mirage being unable to parse the INF file. As a result, the driver will not be a part of the driver library and cannot be delivered by Mirage.
    Use alternative ways to deliver the driver to the end point. For example, include it as part of the base layer, distribute it using other distribution software, or install it manually.
  • Due to an NTFS compression limitation, do not use NTFS compression with Mirage server storage volumes in large deployments. See http://support.microsoft.com/kb/967351.
  • The Server can exceed Maximum Connection if multiple clients try to connect at the same time. This issue is mitigated by the fact that the window of opportunity is small and hence the occurrence of excessive connections will be quite limited.
    Manually disconnect devices from the server.
  • A non-empty volume cannot be added as a Mirage storage volume (even if it only includes the automatically created 'System Volume Information' folder).
    Create a directory on the volume and add the new directory as Mirage storage.
  • During a CVD restore, if the volume on which the CVD is located in the server fails for any reason, the CVD will move to Suspend mode. After resolving the volume problem, the IT manager should resume the CVD and re-confirm the restore operation.
  • If the IT manager performs a force remove to a volume where the USMT library is located, the system will continue to allow the IT manager to choose U migration although no USMT is present. The operation will fail, the end result being that the CVD will be connected to the new device without the user data moving to the right place.
  • Mirage server installation fails if Microsoft.NET Framework 4.0 is installed.
    Uninstall .NET 4.0 and install Microsoft.NET Framework 3.5.
  • The migration task Download phase may seem stuck at 100% for a long time. This is normal behavior due to Mirage performing actions on files on the target machine, and should be ignored.
  • The client is returned to pending restore after a disconnect during force upload.
    Perform the force upload operation again.
  • USMT 4.0 migration from x86 to x64 results in corrupted COM+ components.
    See http://support.microsoft.com/kb/2481190.

Mirage Management Console

  • The Mirage Management Console doesn't update the status and progress of tasks in the Task Monitoring view. Clicking Refresh triggers loading but the loading never completes.
    Reopen the Mirage Management Console.
  • The user may not be able to compare Programs between a new base layer and the current base layer during base layer assignment.
    Go to Report > Layer Dry-Run (Program Executable) and create a new report that compares the new base layer with the current one.
  • The Assigned Devices view may present an error pop-up window when performing a quick search for device by its CVD ID.
    Hide the CVD column from the view and use the filter panel to search for the relevant devices.
  • A Mirage upgrade may fail with an unclear message when the user installing it doesn't have the permissions to access the Mirage system.
    Verify that the user performing the upgrade is a member of a group defined with the Administrator Role.
  • System only Restore is available during a rebase operation. When using System only Restore with a rebase, the target machine's local User Area is preserved and replaces the CVD User Area, causing loss of data from the CVD.
    Do not use Selective Restore with rebase.
  • When performing a migration operation on a device in Restore Streaming state, the migration starts immediately at the end of streaming without forcing an upload on the new machine.
    Wait for streaming to complete before initiating the migration.
  • When restoring a reference machine from a base layer, the operation seems to start but the CVD is suspended until the server copies the base layer files to the CVD.
    Wait for the server to finish copying the files.
  • The Program Inventory displays out-of-date information after a base layer update/rebase operation before the first upload.
    Wait for the first upload to complete (can be forced by Sync Device in management).
  • Changing the Upload Interval via Upload Policy only takes effect after the next Upload Interval.
    Wait for the next upload to see the new settings take effect.
  • When attempting to update a filter based on Active Directory Groups, only groups present at the time the filter was created are offered.
    Remove the filter and create a new filter. The list of Active Directory Groups will be refreshed.
  • Move CVD Task may reach 100% but is not finished.
    Wait for the task to reach done state.
  • Assigning a base layer from an un-mounted volume does not work but no error message or log is generated.
    If a base layer assignment does not seem to be progressing, check that the volume that the base layer resides on is running properly.
  • Mirage Management Console supports only the following resolutions: 1280x800, 1440x900, 1680x1050.
  • The Set driver library operation is not supported while another operation is running on the CVD. No blocking or warning occurs.
    Re-apply the driver library set operation.
  • When importing new drivers to the driver library while preserving the folder structure, the drivers do not immediately appear under the Driver Library node.
    Refresh by pressing F5.
  • A false server communication error may be displayed on the Management console. This can happen if the management console is open for a long time. The error can be safely ignored.

File Portal

  • A wrong error message is generated when management service is not available. The end user is notified of a bad username or password although the problem is actually that the management service is down.
  • In rare cases, the end user may not receive the Web Portal registration window if he logs in to the machine before the Mirage service was able to connect to the server.
    Re-login to the machine.
  • In rare cases, Webinstall may fail with the error message: MSI failure. Error: INSTALL_FAILURE.
    Run the installer again.