VMware Horizon Mirage 4.4 Release Notes

VMware Horizon Mirage 4.4 | 4 March 2014

Last Document Update: 4 March 2014

These release notes cover the following topics:

About Horizon Mirage

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

What's New in Horizon Mirage 4.4?

This version provides the following new features and improvements:

  • The Horizon Mirage Web Management console and the File Portal now support only SSL connections as an additional security layer to prevent from transmitting sensitive user data over the network. Please follow the instructions in the Horizon Mirage Administrator's Guide to configure the web server with SSL.
  • Horizon Mirage supports Windows 8.0 and Windows 8.1 disaster recovery. The IT manager can restore lost, stolen, or broken beyond repair desktops and laptops with the Windows 8.0 or 8.1 operating systems. Additionally, disaster recovery can revert to previous snapshots, and can manage self-service file-level restores and file portal support.
  • The Mirage Edge server provides a secured gateway that is deployed outside the Mirage data center environment, enabling end users to connect to the Mirage servers through corporate networks without the use of VPN. The Horizon Mirage Edge server meets the enterprise security and firewall requirements and provides a better user experience for Mirage clients that access the Horizon Mirage servers through the Internet. The Edge server seamlessly integrates with the Horizon Mirage system with minor modifications to the Mirage system and protocol.
  • During Windows 7 migration, the IT manager can now select the image management only option. This option enables that migrating Windows XP to Windows 7, endpoints are not backed up to the Mirage server, saving centralization time and storage costs.

Known Limitations with Horizon Mirage 4.4

The following limitations are known in this Horizon Mirage 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 or base layer provisioning. 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 or app 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 Horizon Mirage Administrators 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, type zeros in the LastFullUploadTicks value in the registry:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wanova\Mirage Desktop Service\LastFullUploadTicks = 00 00 00 00 00 00 00 00
    and click Sync Now.
  • 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 or an app layer to the endpoint, Windows fixed-drive letters on the endpoint must be the same as on the reference machine from which the base or app layer was captured (for example, it cannot be C: on a CVD and D: on a base layer.)
    • By default, only the system volume is uploaded to the CVD. You can add volume drive letters to the upload policy to upload additional volumes.
  • Base layering and app layering do not currently support SQL Express/SQL Server.

Issues Addressed in the VMware Horizon Mirage 4.4 Release

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

  • When an error page is displayed, the error message is not translated to different languages.
  • Windows 8 users with a Chinese locale are identified by default as zh-Hans-CV users when using an Internet Explorer or Chrome browser. This means that the file portal language for viewing a Windows XP or Windows 7 CVD is in English and not Chinese. Currently, only zh-CN locale is supported.
  • When updating app layers for CVDs that also include unchanged layers (present on the CVDs both before and after assignment), those CVDs are mistakenly included in both the Assigned and Pending Assignment column counts in the App Layer view.
    As the devices finish uploading after the assignment, those CVDs with unchanged layers are no longer included in the Pending Assignment count.
  • Horizon Mirage might reject the creation of new base or app layer with a Name already exists error when there is a deleted base or app layer with the same name.
  • On deployments where the AD server does not support built-in recursive queries, Horizon Mirage will fail to detect group membership correctly for domain groups. This will cause installation failure if the supplied default group is a domain group, and will cause a post-installation login failure for users relying on such groups for permissions.
  • A Windows XP to Windows 7 in-place migration operation might result in a 0x0000007b stop message if the Windows 7 base layer or the driver library used does not contain the correct drivers for the target's disk controller.
  • When using a Chinese localized version of Windows and running the MMC, the dashboard view might have some overlapping text.
  • The MMC does not respect Windows Location settings for number formatting. The Digit grouping symbol is a comma (',') and the decimal symbol is a period ('.'), regardless of Windows Location configuration.
  • When assigning a base layer with antivirus or anti-spyware products, the Horizon Mirage Management console can mistakenly warn the user about anti-spyware Products mismatch. Proceed with the assignment. The warning has no effect on the operation.

Known Issues in Horizon Mirage 4.4

The following known issues affect the Horizon Mirage 4.4 release:

Horizon Mirage Client

  • When performing an in-place migration with profiles folder that is not on the system drive and is configured to be in the exact same location both on the migrated machine and on the Base Layer, the folder name of the migrated profiles will have a ".000" suffix.
    Workaround: Contact Horizon Mirage support to receive a custom USMT script.
  • In some cases, reverting to Windows XP after performing a Windows 7 migration might not preserve the 802.1x authentication settings.
    Workaround: Contact VMware technical support to provide a post-revert script which will re-apply the 802.1x settings.
  • Because of limitations in Windows Store, changing the physical device of Windows 8 might require performing "Sync licenses" for the Metro apps to properly work. As a result, hardware migration scenarios might require to perform the following steps: Open Windows Store -> Settings (from Charm bar menu) -> App updates -> "Sync licenses". For more detailed steps, see http://www.microsoft.com/surface/en-us/support/apps-and-windows-store/troubleshoot-windows-store-apps-on-surface#sync
  • The Windows 8 Activity Moderator may impede Mirage activity when the device is in "connected standby" power state. This will slow down Mirage operations significantly. Additionally, when the device is connected through VPN, no network activity will be performed at all in this mode.
    Workaround:Prevent the device from going into "connected standby" mode by connecting the device to the power supply and leaving the screen on.
  • When migrating user data and settings in Windows 8.0 or 8.1, the Live ID account from the source machine is not migrated. This is a Microsoft limitation.
    Workaround:Manually add the live ID account.
  • A user performs a restore over a VPN. After the system restart, the endpoint is not connected to the VPN and cannot rejoin the session. The domain is required to log in and to connect to the VPN.
    Workaround:In the restore wizard, select "Keep CVD Name". Consequently, the domain will not be rejoined. Alternatively, if your VPN supports connecting to the VPN on login, you can enable this feature.
  • In Restore/Rebase scenarios with streaming, the Dropbox streaming feature may conflict with the Mirage streaming feature and will slow down both programs and regular Windows interaction.
    Workaround:Temporarily disable Dropbox during Mirage restores that include streaming.
  • To improve user experience during a streaming operation, Mirage temporarily disables thumbnails view of images in Windows Explorer. When streaming is completed, Mirage restores the thumbnails setting to its previous setting.
  • In rare cases, when the Mirage client needs to be upgraded while Mirage restore streaming is in progress, the upgrade process may fail.
    Workaround: Contact VMware technical support to add the Mirage client MSI file under %windows%\installer to the "static minimal set".
  • USMT enters an infinite loop if a user redirects a profile folder (documents, pictures, music, and so on) to :\, :\Windows, :\Windows\Temp.
    Workaround: Remove the redirection prior to the migration, or contact Horizon Mirage support.
  • After a base layer update, a user-customized Windows 7 login screen in the endpoint resets to the Windows default background. This occurs because the login screen settings in the base layer overrides the local settings at the endpoint.
    Workaround: Update the base layer override policy (layer rules) and add a rule that prevents the base layer from overriding the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background\OEMBackground registry value.
  • During Windows 7 migration or provisioning, some devices might remain installed with the default driver, instead of the driver that should have been installed by the driver library.
    Workaround: On the reference machine, check the [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching] "SearchOrderConfig"=dword registry value and verify that the value is set to 0, then re-capture a new base layer.
  • A base layer or app layer update might change the active power plan of the client machine.
    Workaround: Add an exclusion of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\User\PowerSchemes\ActivePowerScheme registry value to the base image rules.
  • On base layer or app layer updates, Horizon Mirage does not force automatic activation of Office 2010 keys if the CVD did not have any Office 2010 product before the operation. Activation can be invoked manually and might be invoked automatically by Office 2010.
    Workaround: Activate Office 2010 manually (via the Office 2010 menus).
  • When migrating to Windows 7, some start menu items might not be migrated to the new system.
    Workaround: It is not always desirable to transfer all start menu items on a migration since some applications in the original system might not be available in the new system.
  • Performing a Horizon Mirage restore or base layer update operation when the target device and the CVD or base layer contain the McAfee DLP Agent might lead to an endless loop of Horizon Mirage retries.
    Workaround: This can be corrected in the following ways:
    • Disable or uninstall the McAfee DLP Agent during the operation.
    • If possible, add the Wanova.Desktop.Service.exe to the McAfee safe list.
  • In very rare cases, after migrating an ESX VM from Windows XP to Windows 7 and then reverting the machine back to Windows XP, a black screen with a solid cursor might appear on boot.
    Workaround: This can be corrected in the following ways:
    • Convert the ESX VM to a VMware Workstation machine.
    • Contact support to receive instructions on how to install the Windows 7 boot loader instead of the Windows XP boot loader.
  • In very rare cases, file system corruption might cause Horizon Mirage to enter an endless loop of restore attempts.
    Workaround: Try to run chkdsk to fix the file system.
  • Adding rules to the Unprotected Area in the upload policy might prevent you from properly restoring CVDs. For example, if you unprotect "*.bin" from %anyvolume% (with recursive=true), these files will not be uploaded to the CVD (including files like that files in c:\windows, c:\program files). If you later restore the CVD, Windows might fail to operate correctly.
    Workaround: Fix the upload policy by unprotecting only files which are not required by the operating system.
  • 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.
    Workaround: Horizon Mirage recovers automatically.
  • In rare cases, after restoring a CVD with layers, the Horizon Mirage client might malfunction when new layers are assigned.
    Workaround: Recentralize the malfunctioning device to a new CVD and then assign the layers you want. This operation will not remove previous layers.
  • In rare cases, Horizon Mirage might continuously fail to complete a rebase operation with a FileNotFound error.
    Workaround: Contact the VMware support team.
  • The Horizon Mirage desktop service process might appear to consume a significant amount of memory in Task Manager.
    Workaround: The process automatically releases acquired memory when needed.
  • On layer update operations, the Horizon Mirage Management console Transactions view might show transactions for base and app layers that were not changed in the layer update operation.
    Workaround: 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.
    • Log out the user and log in again on a remote machine when Horizon Mirage is connected.
    • Manually add the user name to the File Portal User column.
  • In rare cases, at the first Windows startup after applying a base layer, the Horizon Mirage user experience might degrade slightly 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.
    Workaround: Uninstall the Horizon Mirage client with the CleanState script (available from the VMware support team) and then reinstall the Horizon Mirage client.
  • Windows system restore points do not work on machines installed with Horizon Mirage.
  • 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.
    Workaround: 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.
    Workaround: Desktop will malfunction and automatically restart and retry the operation.
  • 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 Windows XP snapshot with a different bitness type, Horizon Mirage can't be uninstalled.
    Workaround: 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.
  • Open with does not work during streaming.
    Workaround: Open the file by double-clicking it, or open the application first.
  • Reverting back from Windows 7 to an Windows XP OS might leave some Windows 7 directories on the machine, such as Program files (x86).
  • When performing a Windows XP to Windows 7 migration or a Windows 7 to Windows 7 user profile migration, and there is a profile with a folder name longer than 20 characters that isn't located in the default profiles folder, USMT might fail to complete.
    Workaround: Remove the long user profile name from the non-standard location before performing the operation. Contact VMware technical support for further assistance.
  • In rare cases, Horizon Mirage might not complete a restore operation Prefetch phase or Streaming phase. This can happen if some files in the same directory have conflicting names, for example, file1 is called DESCRI~1.HTM and file2 is called description.htm.
    Workaround: Add one of the conflicting file names to the Unprotected area or Do Not Restore area of the master policy. Contact VMware technical support for further help to confirm the reason for the restore failure.
  • Horizon Mirage currently cannot base layer provision a machine if the provisioned base layer contains more than one volume.
    Workaround: Contact VMware Technical Support for assistance.
  • A machine that is restored with streaming may fail to detect NVIDIA drivers on Plug and Play, leaving the machine installed with only the Windows video drivers.
    Workaround: Reinstall the NVIDIA drivers manually.
  • In rare cases, Horizon Mirage might fail a download operation because a non-system drive included in a multi-disk base image was not detected as a fixed drive.
    Workaround: Reboot the machine to resume the download operation.
  • In rare cases, when migrating a device from Windows XP to Windows 7, Windows Plug and Play may take too long to install some drivers, resulting in a timeout that stops their installation.
    Workaround: Contact VMware technical support.
  • After a rebase failure, or if Mirage fails to download a driver library from a branch reflector, the local user sees the Idle status instead of a special status.
    Workaround: A workaround is not currently available.
  • Applying a base layer that does not include Visual Studio Tools for Applications to a machine whose previous base layer did include it might cause the local user-installed Visual Studio not to function.
    Workaround: Capture the new base layer with Visual Studio Tools for Applications.

Horizon Mirage Client - Application Compatibility

  • If a target machine has Hitachi HIBUN installed, and Horizon Mirage tries to create a symbolic link, the operation might fail, causing restore/Windows 7 migration/base layer update operation to also fail.
    Workaround: Contact Horizon Mirage Support for assistance.
  • 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.
    Workaround: Change the upload policy to include *.nsf files in the protected area.
  • 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.
    Workaround: Run netsh winsock reset using the command line (as administrator) to restore the network to normal operation.
  • 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
  • Applying a layer with CA Internet Security might leave the machine without the CA Internet Security firewall properly installed.
    Workaround: 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.
    Workaround: 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.
  • Horizon 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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 Windows updates, a Windows update failure might occur.
    Workaround: Ignore the Windows update failure and re-check for Windows updates 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.
    Workaround: Select another browser as the default browser.
  • After Windows 7 migration, the target device has the same client Machine ID as the reference machine.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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

  • Unknown or invalid devices might appear in the Device Manager after migration/base layer update.
    Workaround: 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).
    Workaround: 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).
    Workaround: 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.
    Workaround: Perform a hard reboot of the machine.

Horizon Mirage Server & Management Server

  • On very rare occasions clients may fail to download and apply a Base Layer or App Layer.
    Workaround:Re-capture the Base Layer or App Layer and assign them to the clients.
  • Modifying app layers during a migration is always blocked.
    Workaround: Cancel specific app layers via the Assignments view.
  • When migrating a device from Windows XP to Windows 7, the devices that start migration but do not complete it still appear in the Migration wizard as XP machines that are ready for migration.
    Workaround: Avoid re-migrating devices for which migration has already been started manually.
  • During a centralize endpoint operation performed simultaneously on multiple devices (via multi-select or the Centralization wizard), if there is an error for one of the devices, none of the devices will start a centralization.
    Workaround: Solve the issue for the affected device and try again for all devices. If this is unsuccessful, try centralizing smaller batches.
  • In some cases of storage corruption, Move CVD or Remove CVD tasks become stuck in the middle of the process without failing or correctly reporting the reason.
    Workaround: Cancel the task.
  • A device that is configured to be a branch reflector will malfunction if it runs out of disk space. If the cache size is configured to be greater than the amount of available disk space, the branch reflector will use up all available disk space, eventually causing a malfunction.
    Workaround: Ensure that enough free disk space is available when configuring the branch reflector cache size.
    If the device malfunctions, it is recommended to free some disk space and restart the desktop service.
  • When running a CVD integrity report on a loaded storage, an error might appear, stating: "Unable to verify [filename] - The process cannot access the file because another process has locked a portion of the file(33)" In this situation, not all files have been properly scanned by the CVD integrity report.
    Workaround: Run the CVD integrity report again to ensure the relevant file has been checked.
  • 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.
    Workaround: A workaround is currently not available.
  • 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.
  • 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.
    Workaround: Manually disconnect devices from the server.
  • 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).
    Workaround: 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 being moved to the right place.
    Workaround: After applying a force remove to the volume, re-import the USMT.
  • Horizon Mirage server installation fails if Microsoft.NET Framework 4.0 is installed.
    Workaround: 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.
    Workaround: Perform the force upload operation again.
  • USMT 4.0 migration from x86 to x64 results in corrupted COM+ components.
    Workaround: See http://support.microsoft.com/kb/2481190.
  • During a first upload operation, if Force Upload is used and Enforce Layers is attempted, the error message indicates that the CVD is in a restore operation instead of a force upload operation.
    Workaround: The user can ignore this warning.
  • When you capture a base layer that includes a Microsoft Office application that requires a license, the capture wizard might not ask for the license key. As a result, the Office license can be invalid when the base layer is distributed to endpoints.
    Workaround: If the Wizard does not ask for the license key, restart the reference machine after the Microsoft Office installation, or perform a manual synchronization. In the Management console, expand the Image Composer node, select Reference CVDs, right-click the reference CVD and select Sync Device.
  • The Horizon Mirage Management command line interface (CLI) does not support unicode names and descriptions.
    Workaround: Use an ASCII-based name in the CLI, or perform the action through the Horizon Mirage Management console.
  • During a Windows XP to Windows 7 migration, after the target device finishes downloading the image but before it reconnects to the server as a Windows 7 machine, the device is effectively a Windows 7 machine but the device state on server is not updated yet.
    During that time interval, if you revert the device back to Windows XP and System Only Revert is indicated, the validation does not warn of a problem. The revert eventually fails on the desktop and generates an event.
    Workaround: When reverting a machine from Windows 7 to Windows XP, verify that the System Only option is unchecked.

Horizon Mirage Management Console

  • Some Japanese characters might appear as ? in the MMC.
    Workaround: A workaround is not currently available.
  • Using GB18030 characters for base layer and app layer names, or for policy names is not supported. Attempting to create such names results in the GB18030 characters being ignored.
    Workaround: Do not use GB18030 characters for layer or policy names.
  • When adding a new policy with the same name as an existing policy, the operation will silently fail.
    Workaround: A workaround is not currently available.
  • The Horizon Mirage CVD auto-create option allows the administrator to specify a customized message. A message of more than 200 characters is truncated by the Horizon Mirage user interface.
    Workaround: Use a message length that is less than 200 characters.
  • In certain cases of network disconnects between MMC client and Horizon Mirage servers, the validation step of Horizon Mirage wizards becomes stuck and does not return control to the user.
    Workaround: Restart the MMC.
  • When trying to delete a base layer that is in use, the error message does not include the layer name. It shows only its ID.
    Workaround: A workaround is not currently available.
  • In the Update App Layers wizard app layer selection step, when already selected items are clicked, the layer properties panel at the bottom might not update.
    Workaround: Select another app layer in the same panel, then reselect the app layer you want.
  • When using the MMC's common wizards' Disaster Recovery to replace a hard disk, it is not possible to restore only the system without restoring the user data.
    Workaround: There are two ways to restore only the system:
      Option 1:
      1. Go to the Pending Devices list in the inventory tree.
      2. Right-click the required device and select Confirm Restore.
        In this wizard the Restore System Only option is selectable.
      Option 2:
      1. Go to the All CVDs list in the inventory tree.
      2. Right click the required device and select Restore.
        In this wizard the Restore System Only option is selectable.
  • Occasionally, 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.
    Workaround: 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.
    Workaround: 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 doesn't have the permissions to access the Horizon Mirage system.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
    Workaround: 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.
  • When connecting the Horizon Mirage Management console to the Horizon Mirage system, if add a system IP address that is not valid to the Management console tree root, the Management console might stop operating. Restart the Management console and provide a valid IP address.
  • When system configuration is attempted using the Horizon Mirage Management console System Settings, but the system is not yet licensed or the license expired, the configuration operation fails due to license validation, without clear indication of the reason to the user.
    Workaround: Provide a valid license key.

Horizon Mirage 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, an end user might not receive the Web Portal registration window if log in to the machine is made before the Horizon Mirage service was able to connect to the server.
    Workaround: Re-login to the machine.
  • In rare cases, Webinstall might fail with the error message: MSI failure. Error: INSTALL_FAILURE.
    Workaround: Run the installer again.