VMware Horizon Mirage 4.0
VMware

VMware® Horizon MirageTM 4.0 Release Notes

VMware Horizon Mirage 4.0 | 04 March 2013 | Build 59447

Last Document Update: 14 March 2013

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 Horizon Mirage is installed on a Windows PC, it centralizes a complete virtual copy of that endpoint 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. Horizon Mirage enables central image management of desktops while still allowing local execution at the user endpoint.

What's New in Version 4.0?

This version provides the following new features:

  • Endpoint centralization - Performance improvement when a large number of endpoint centralizations are performed, by reducing the number of IO operations required from the storage.
  • License implementation - Integration with VMware licensing. New licenses are provided as a serial-key instead of the former Wanova license-file.
  • Server 2012 support - Horizon Mirage servers can now run on Windows server 2012.
  • App layering OEM support - Mirage app layering now also supports capture of OEM software, including drivers.
  • App layering conflict report - Reporting and usability improvements. Reports now take app layers into account.
  • App layering capture process improvements.
  • App layering update - The administrator can easily send a new app layer update to all CVDs that were previously assigned the former app layer version.
  • Windows 7 migration usability improvements - Operation progress can be monitored in the Windows login screen.
  • Active-Directory filtering - You can create a filter for multiple Active-Directory elements (for example, filter CVDs whose users belong to AD Group X or AD Group Y).
  • Hardware Migration - App layers can be changed during hardware migration, for example OEM layer.

VMware Horizon Mirage 4.0 Documentation

VMware Horizon Mirage Administrator's Guide

VMware Horizon Mirage App Layer Capture Guidelines

Resolved Issues in Horizon Mirage 4.0

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

  • USMT times out because of Trend Micro triggered streaming of files.
  • 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 (for example, 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.
  • 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.
  • 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 might appear as being offline. The file is downloaded successfully and can be used, but might have an offline bit.
  • While running a USMT migration, the Horizon 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 might display a wrong validation message.
  • In rare cases, the Horizon Mirage client might fail to resume an upload operation and will show a malfunction balloon.
  • During the layer update operation, the Horizon Mirage client might enter a malfunction state, automatically recover, and retry the operation.
  • 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.
  • A Driver package sent with a base layer that includes unprotected files will not work properly on the endpoints.
  • User profile migration is not supported if some or all user profile folders are redirected to a non-system drive.
  • Horizon 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 Horizon Mirage.
  • 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.
  • The Horizon Mirage Client fails to update certain Windows files when McAfee VirusScan Enterprise is installed with the Prevent Windows Process Spoofing option set.
  • Horizon Mirage fails to update files on a Symantec protected endpoint.
  • Outlook might fail to open hyperlinks after a base layer update which changes the browser.
  • Checkpoint full disk encryption software might cause BSOD to occur on the target machine after a rebase.
  • 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.
  • 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.
  • The Start App Layer capture task and the reference machine might 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.
  • A Capture App Layer task is unable to proceed after the task is paused and then resumed.
  • The user might not be able to compare Programs between a new base layer and the current base layer during base layer assignment.
  • Assigning a base layer from an un-mounted volume does not work but no error message or log is generated.
  • 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.

Known Limitations with Horizon Mirage 4.0

The following limitations are known in the Horizon Mirage 4.0 release.

  • Horizon 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 Horizon Mirage service has started, which might impact their normal operation.
    You can extend the minimal restore set to accommodate these particular applications. For further details refer to the VMware Horizon Mirage Administrator's Guide.
  • 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 might 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.
  • Horizon 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.
  • Horizon 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.
  • Horizon 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) is not 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 might add volume drive letters to the upload policy to upload additional volumes.

Known Issues with Horizon Mirage 4.0

The following known issues affect the Horizon Mirage 4.0 release:

Horizon Mirage Client

  • The VSS snapshot during final phases of the layer update operation might fail with a Shim execution failed to complete warning and the Horizon Mirage client automatically retries it later.
    Horizon Mirage recovers automatically.
  • Clicking Cancel when the Finalize Layer Capture wizard is refreshing device information might show an incorrect list of installed applications.
    Sync the device and retry.
  • In rare cases, after restoring a CVD with layers, the Horizon Mirage client might 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.
  • Horizon Mirage might 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, Horizon Mirage might continuously fail to complete a rebase operation with a FileNotFound error.
    Contact the VMware support team.
  • The Horizon Mirage client might malfunction if the Microsoft Software Shadow Copy Provider service is not properly installed on the machine (for example, if the SYSTEM\CurrentControlSet\services\swprv key does not 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 Horizon Mirage desktop service process might 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 might 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 Horizon Mirage is connected. OR
    2. Manually add the user name to the File Portal User column.
  • Plug-and-play driver installation during streaming might 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 Horizon Mirage user experience might slightly degrade for the first few minutes after startup.
  • Rebooting the machine while the Horizon Mirage client is being upgraded/installed might leave the Horizon Mirage client in an inconsistent state.
    Uninstall the Horizon Mirage client with the CleanState script (available from the VMware support team) and then reinstall the Horizon Mirage client.
  • Horizon 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 Horizon Mirage.
  • 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.
  • Unprotected folders are uploaded by Horizon 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.
  • After reverting back from a Windows 7 snapshot to a XP snapshot with a different bitness type, Horizon Mirage cannot 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.
  • Using Open with to open a file might not work during streaming.
    Open the file by double-clicking it, or open the application first.
  • Reverting back to an XP CVD snapshot after migrating the client to Windows 7 will leave some Windows 7 directories on the machine.
  • Client upgrade might 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 cannot be executed by the Horizon Mirage MSI installer and prevents the Horizon 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.

Horizon Mirage Client - Application Compatibility

  • Horizon Mirage generally does not backup removable disks. However, Horizon Mirage might backup eSATA disks if Windows recognizes them as IDE devices.
  • The "Wanova Volume Information" directory might grow to occupy several GBs of disk space.
    Contact VMware Horizon Mirage technical support to obtain a cleanup script.
  • The list of programs for a device or CVD in the Horizon Mirage Management Console might be inconsistent with the list of programs in the Windows Programs and Features - Add/Remove Programs view.
  • During migration to Windows 7, the Horizon Mirage Management Console might show that the active user on a device is "Mirage Migration".
    The MMC shows the real user name when the migration process is completed and a real user is logged on.
  • The Horizon Mirage client might temporarily show a "Malfunction" balloon when Windows denies access to Horizon Mirage's internal files/directories.
    Horizon Mirage recovers automatically.
  • The "Windows Internet Explorer 9" program name does not appear in the Horizon Mirage Management Console under the "Program Files" tab in the CVD or device properties.
  • After Windows XP to Windows 7 migration, the "Always Available Offline" option might be missing when right-clicking a network folder.
    Use the directions in KB http://support.microsoft.com/kb/942974 to fix the issue.
  • In rare cases in which the data of an internal Horizon Mirage client file had been corrupted, the Horizon Mirage client will enter Pending Assignment or Pending Restore state.
    If the device previously had a CVD and it is now Pending restore, use the Force Upload feature to re-sync the device with the CVD by performing an upload of its content into the CVD.
    If the device is Pending Assignment, assign a new CVD to it.
  • The Horizon Mirage client might temporarily enter malfunction after assignment of an OEM app layer.
    Horizon Mirage recovers automatically.
  • On every Horizon Mirage boot operation (e.g. layer assignment, restore), Horizon Mirage resets the McAfee Agent GUID so that the McAfee Agent can synchronize with the McAfee management server.
  • After layer assignment, Horizon Mirage might require several hours to complete a post-layer assignment step ("compiling WMI classes").
    When the step is completed, Horizon Mirage continues to work normally.
  • Provisioning a Windows 7 image into a device via Horizon Mirage might fail with the following event in the Horizon Mirage event log: "Error: No entry for disk controller".
    The base layer which was used for provisioning needs to be re-captured with the required disk controller drivers and their corresponding registry entries installed in the reference machine before capture. Contact VMware Horizon Mirage technical support for further information.
  • After using a Windows 7 base layer with VMware Tools to migrate an XP machine, printers might not be installed properly.
    Do not install VMware Tools on the Windows 7 reference machine if possible.
  • By default, Horizon Mirage does not protect *.nsf files, which might 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 might 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 Horizon Mirage app layer or base layer mechanism, the network might 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, might 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 might 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 might 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 might 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 might lead to a one-time configuration screen when the application is launched on the endpoint.
    The application works correctly after the configuration is completed.
  • Applying a layer with CA Internet Security might 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 might 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.
  • Horizon Mirage cannot distribute the Alcohol 120% software via a base layer update.
  • 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 might 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 might 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 endpoint centralizaion, 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.
  • Horizon Mirage does not support downgrading Office 2010 to 2007 through the base layer mechanism.
  • The Program List in MMC might not show applications which are listed under the following registry key in the CVD: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products.
  • Unactivated Office applications might 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 might 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.
  • After Windows 7 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 might 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.

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

Horizon Mirage Server & Horizon Mirage Management Server

  • When provisioning a new XP device, the Horizon Mirage Management Console can mistakenly warn the user about a missing Driver Library profile.
    Proceed with the provisioning. The warning has no effect on the operation.
  • In some cases of restoring to a clean machine (that is a domain member), the endpoint loses its domain membership after the Restore is completed.
    Use one of the following solutions:
    1. Manually rejoin the endpoint to the domain.
    2. Use a different or temporary machine name for the clean machine before the restore.
  • In extreme cases of storage outage, the Create Reference CVD from Base Layer task might fail and the user will not be able to proceed with applying the Reference CVD content on the reference machine (operation fails in a loop).
    Recreate the Reference CVD from the same Base Layer.
  • In some cases of extremely slow network conditions, the Horizon Mirage Client provisioning process stops at 90% progress and never completes.
    Reboot the endpoint.
  • In rare cases, an endpoint can start a Base Layer Provisioning operation and is unable to complete it. The operation starts, fails after some time, and then starts again. Horizon Mirage Client logs show sharing violation errors.
    Restart the endpoint.
  • The Horizon Mirage Client fails to synchronize when the protected area contains a file bigger than 100GB.
    Exclude the file from the Upload Policy.
  • In some scenarios (such as Revert to Snapshot), the Horizon Mirage Management Console can display an unfinished Incremental Upload transaction under the Transaction Log, meaning the transaction End Time is missing.
  • Some multi-server, DAS-based deployments might show CVD restore failures with a FileNotFound error. Horizon Mirage logs will contain an access failure for special file names such as @GMT-2012-1-02.123...
    Perform the following steps:
    1. Run the following CLI on the server: Wanova.Server.Cli -c "setConfigParamvolumePathOptimizationEnabled false"
    2. Remount CVD's volume.
    3. Run CVD integrity (Fix for Restore) for the affected CVD.
    4. Exclude the problematic file from Upload Policy and assign a policy to the CVD.
    5. Resume the device and proceed with the Restore.
  • In rare cases, when a volume is disconnected, the Revert to Snapshot operation might stall in the middle, without the ability to proceed or to be cancelled.
    Currently not available.
  • The driver import process might fail due to Horizon 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 Horizon Mirage.
    Use alternative ways to deliver the driver to the endpoint. 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 Horizon Mirage server storage volumes in large deployments. See http://support.microsoft.com/kb/967351.
  • A non-empty volume cannot be added as a Horizon 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 Horizon 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.
  • Horizon 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 might seem stuck at 100% for a long time. This is normal behavior due to Horizon 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.

Horizon Mirage Management Console

  • The Horizon Mirage Management Console does not update the status and progress of tasks in the Task Monitoring view. Clicking Refresh triggers loading but the loading never completes.
    Reopen the Horizon Mirage Management Console.
  • The Assigned Devices view might 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 Horizon Mirage upgrade might fail with an unclear message when the user installing it does not have the permissions to access the Horizon 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 might reach 100% but is not finished.
    Wait for the task to reach done state.
  • Horizon 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 might 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 might not receive the Web Portal registration window if he logs in to the machine before the Horizon Mirage service was able to connect to the server.
    Re-login to the machine.
  • In rare cases, Webinstall might fail with the error message: MSI failure. Error: INSTALL_FAILURE.
    Run the installer again.