Thursday, October 17, 2013

Install the Horizon Mirage Client Silently

The administrator can deploy the Horizon Mirage client installer silently, without disturbing user
operations, by using command-line arguments.

Prerequisites
1 Verify that you have administrative permissions.
2 Verify that your platform meets the software and hardware requirements.
3 Because you cannot place Horizon Mirage servers in the customer's DMZ premises, use a VPN to
connect clients that will be used outside the network.
4 If the client will use SSL to connect to the server SSL must already be configured on the server.


Procedure
1 Select Start > Run, type cmd, and click OK.

2 Type the required expression for your environment and press Enter.
Option Description
32-bit clients <Mirage MSI path>\MirageClient.x86.buildnumber.msi
SERVERIP=MirageServer /quiet
For the SERVERIP parameter, you can use a DNS FQDN or hostname
instead of the server IP address.
64-bit clients <Mirage MSI path>\MirageClient.x64.buildnumber.msi
SERVERIP=MirageServer /quiet

3 (Optional) If SSL needs to be enabled, type the following expression and press Enter:
<Mirage MSI path>\MirageClient.x86.buildnumber.msi SERVERIP=MirageServer:port
USESSLTRANSPORT=true /quiet

4 (Optional) Restart your computer.
For first-time installation, restarting the computer assures better backup protection and enables
streaming which promotes faster restoration.

For an upgrade, restarting promotes better performance.

When the installation is finished, the Horizon Mirage client appears in the Management console in the
Pending Devices list.


Install the Server SSL Certificate

To set up SSL on the Horizon Mirage server, you must obtain SSL certificate values and configure them on
the server. SSL Certificates is a Windows feature.
Procedure

1 Access the certificate store of the local machine account to check the server SSL certificate details.
a Select Start > Run.
b Type certmgr.msc.
c Select Certificates > Personal > Certificates to navigate to your certificate.

2 If you do not have a certificate, create one with tools such as the Microsoft makecert, and import the
result into the Certificate Manager.

3 Note the Certificate Subject and Issuer values.
The certificate values appear in the details of the certificate you imported.

Connect the Console to the Horizon Mirage System

After you install the Horizon Mirage Management console, you can connect the console to the
Horizon Mirage system.


Procedure

1 In the Horizon Mirage Management console tree, right-click VMware Horizon Mirage in the root
directory and select Add System.
2 Type the IP address or host name of the Horizon Mirage Management server in the Management
Server Address text box.
3 Click OK.
The Management console is connected to the system. A Horizon Mirage server node now appears in the
console window.
After the console is connected, it shows Server Down status because a Horizon Mirage server is not yet
installed. The server status changes to Up when a server is installed.

Install the Horizon Mirage Management Console

The Horizon Mirage Management console is the graphical user interface used to perform scalable
maintenance, management, and monitoring of deployed endpoints. You install the Management console
after you install the Horizon Mirage Management server. The Management console is built as a Microsoft
Management Console version 3.0 snap-in.
The installation uses an .msi file located in the Horizon Mirage distribution.


Prerequisites

The End-User License Agreement appears during the installation. You must agree to its terms before you
can complete the installation.


Procedure

Double-click the .msi file for your environment.

64-bit Mirage.management.console.x64.buildnumber.msi
or
32-bit Mirage.management.console.x86.buildnumber.msi
A shortcut

A shortcut to the Management console is added to your desktop when the installation is finished.

Install the Horizon Mirage Management Server

The Horizon Mirage Management server is the main component that controls and manages the
Horizon Mirage server cluster.
The installation uses an msi file located in the Horizon Mirage installation package.


Prerequisites

Verify that the relevant software requirements are met.


Procedure

1 Double-click the Mirage.management.server.x64.buildnumber.msi file.
2 Type the SQL Server name.
3 Type the SQL Instance name.
Use the default SQL instance name if your MSSQL edition was installed with Default options, or the
custom instance name if a custom name was defined.
4 Set the remaining installation parameters.
The installation might take a few minutes.
5 Click Finish to complete the installation.

The Horizon Mirage Management server is installed.



Install the Horizon Mirage System


You must install the Horizon Mirage components in the specified order.


Prerequisites

Verify that all hardware and software prerequisites are fulfilled, that you have a valid license for the
system, and that the latest version of the Horizon Mirage software is downloaded from the support site.

Verify that the SQL server is installed and reachable. The SQL browser service must be started to allow
remote connections. Verify that firewall settings allow remote connections on the SQL server host. Go to
http://technet.microsoft.com/en-us/library/cc646023.aspx.

Verify that antivirus software running on the server machine excludes Horizon Mirage server folders
and processes from scanning.

Server folders, including the Mirage storage volumes and the local cache directory, for example,
C:\ProgramData\Wanova Mirage\LocalCache.

Server processes, for example, Wanova.Server.Service.exe.

Prepare the required database information, or install a new database instance to use with
Horizon Mirage.

NOTE You must have dbcreator privileges to create the Horizon Mirage database in the SQL express
database. If you do not have these privileges, ask the database administrator to create the database and
then assign you as the database creator.

Procedure

1 Install the Horizon Mirage Management Server
The Horizon Mirage Management server is the main component that controls and manages the
Horizon Mirage server cluster.

2 Install the Horizon Mirage Management Console
The Horizon Mirage Management console is the graphical user interface used to perform scalable
maintenance, management, and monitoring of deployed endpoints. You install the Management
console after you install the Horizon Mirage Management server. The Management console is built as
a Microsoft Management Console version 3.0 snap-in.

3 Connect the Console to the Horizon Mirage System
After you install the Horizon Mirage Management console, you can connect the console to the
Horizon Mirage system.

4 Install a Horizon Mirage Server 
The Horizon Mirage server manages the storage and delivery of base and app layers and CVDs to
clients, and consolidates monitoring and management communications. After you install and license
the Horizon Mirage Management server, you can install Horizon Mirage servers.

5 Install IIS and the Horizon Mirage File Portal
You must install Windows Internet Information Services (IIS) 7.0 and the Horizon Mirage file portal
on your Horizon Mirage server so that end-users can view files in their CVD snapshots from a Web
browser.

6 Managing Horizon Mirage Software Licenses 
The Horizon Mirage Management server requires a license. The license file enforces the number of
CVDs that you can run on your system and the duration of the license agreement.

7 Configure the Environment for Endpoints 
You must perform a minimum configuration before you can attach endpoints to your system.

Planning the Horizon Mirage Deployment

Planning the Horizon Mirage Deployment

The Horizon Mirage components support a range of operating systems. Software, hardware, and database requirements apply to each component. The Horizon Mirage system and clients use default communication ports and protocols.
Before you start to deploy Horizon Mirage, verify that operating system and other requirements are satisfied.


Operating System Requirements
Horizon Mirage client
Windows XP Professional with SP2 or SP3, 32-bit.
Windows Vista Business or Enterprise, 32-bit and 64-bit.
Windows 7 Professional or Enterprise, 32-bit and 64-bit.
Windows XP Fast User Switching mode must be turned off if the computer is not aAD domain member. Go to http://support.microsoft.com/kb/279765.

Horizon Mirage server
Windows Server 2008 R2 Standard or Enterprise Edition, 64-bit.
Windows Server 2012 Standard Edition, 64-bit.
Domain membership required.

Horizon Mirage Management server
Windows Server 2008 R2 Standard or Enterprise Edition, 64-bit.
Windows Server 2012 Standard Edition, 64-bit.
Domain membership required.

Horizon Mirage Management console
Same as Horizon Mirage client.

Horizon Mirage reference machine
Windows XP Professional with SP2 or SP3, 32-bit.
Windows 7 Professional or Enterprise, 32-bit and 64-bit.



Hardware Requirements

Horizon Mirage client
Client systems:
Enterprise-class laptops and desktops
Virtual machines compatible with Windows XP SP2 or later, Windows
Vista or Windows 7
Minimum RAM: 512MB for Windows XP, 1GB for Windows Vista and
Windows 7
Client installation and normal operation: At least 5GB of free space



Horizon Mirage server node (up to 1500 clients)
Minimum RAM: 16GB.
Minimum CPU: 2 x Quad-Core Processor, 2.26GHz Intel core speed or equivalent.
Minimum System Drive capacity: 146GB, including a 100 GB allocation for the Horizon Mirage network cache.
NOTE
Horizon Mirage SIS storage is not included. See Horizon Mirage Storage.
2 x Gigabit Ethernet Port.
NOTE It is a good practice to separate client network and storage network access to dedicated ports.



Horizon Mirage storage n Standalone Horizon Mirage server:

Direct Attached Storage (DAS).
Storage Area Network (SAN) connected through iSCSI or Fiber Channel
(FC). Network Attached Storage (NAS) connected through iSCSI, Fiber Channel (FC), or CIFS network share.
Horizon Mirage server cluster: Network Attached Storage (NAS) connected using a CIFS network share.
Alternate Data Streams: NAS through CIFS share must support Alternate Data Streams.
Storage Capacity: Consumed capacity varies, depending on file duplication level across CVDs, base layers, and the number of snapshots stored, but VMware estimates that on average each user requires 15 GB of data center storage.
Enabling Compression: For DAS, SAN (FC, iSCSI) and Windows-based NAS (CIFS shares), you can sometimes realize up to 40% in storage savings by enabling the built-in Windows NTFS compression on your Mirage Storage folder. For NAS systems that are not NTFS, you need to leverage their own compression options.


NOTE Apply this change only when Horizon Mirage services are stopped. It is also advisable to do this before the directory is heavily populated.


Horizon Mirage Management console
Minimum RAM: 512MB.
Network connectivity to the Horizon Mirage Management Server.

Minimum screen resolution: 1280 x 1024

Horizon Mirage Components

Horizon Mirage clients
Endpoint devices installed with the Horizon Mirage client can run a centralized virtual desktop (CVD) or
convert an existing desktop to a CVD.
The Horizon Mirage client software runs in the base operating system and makes sure the images at the
endpoint and the CVD are synchronized. The client does not create or emulate a virtual machine. No virtual
machines or hypervisors are required. The Horizon Mirage client software can run on any Type 1 or Type 2
hypervisor.

Horizon Mirage Management server
The Horizon Mirage Management server, located in the data center, is the main component that controls
and manages the Horizon Mirage server cluster.

Horizon Mirage Management console
The Horizon Mirage Management console is the graphical user interface used to perform scalable
maintenance, management, and monitoring of deployed endpoints.
Through the Management console, the administrator configures and manages clients, base and app layers,
and reference machines. The administrator uses the Management console to perform operations such as
update and restore, and monitors the system operation through the dashboard and event logs.

Horizon Mirage Web Manager
The Horizon Mirage Web Manager enables help-desk personnel to respond to service queries, and the
Dashboard feature assists the Protection manager role to ensure that user devices are protected. The Web
Manager mirrors Horizon Mirage Management console functionality. For more information, see the Horizon
Mirage Web Manager User Guide.

Horizon Mirage Server
The Horizon Mirage servers, located in the data center, manage the storage and delivery of base layers, app
layers, and CVDs to clients, and consolidate monitoring and management communications. You can deploy
multiple servers as a server cluster to manage endpoint devices for large enterprise organizations. It is good
practice to keep the server on a dedicated machine or a virtual machine. However, a server can be co-hosted
with the Management server.


NOTE The server machine must be dedicated for the Horizon Mirage server software to use. It must not be

used for any other purposes.


Centralized Virtual Desktop (CVD)
CVDs represent the complete contents of each PC. This data is migrated to the Horizon Mirage server and
becomes the authoritative copy of the contents of each PC. You use the CVD to centrally manage, update,
patch, back up, troubleshoot, restore, and audit the desktop in the data center, regardless of whether the
endpoint is connected to the network. A CVD comprises the following components:
n Base layer defined by the administrator, which includes the operating system (OS) image plus core
applications such as antivirus, firewall, and Microsoft Office. A base layer is used as a template for
desktop content, cleared of specific identity information and made suitable for central deployment to a
large group of endpoints.

App layers defined by the administrator, which include sets of one or more departmental or line-ofbusiness
applications, and any updates or patches for already installed applications, suitable for
deployment to large numbers of endpoints.
Driver profile defined by the administrator, which specifies a group of drivers for use with specific
hardware platforms. These drivers are applied to devices when the hardware platforms match the
criteria that the administrator defines in the driver profile.
User-installed applications and machine state, including unique identifier, hostname, any configuration
changes to the machine registry, DLLs, and configuration files.
Changes to data, applications, or the machine state made by end-user are propagated to the data center.
Conversely, all changes that the administrator makes to the base layer or app layers in the data center
are propagated to the endpoints. Administrators can identify data that does not need to be protected,
such as MP3s, or other files that are considered local only to the endpoint.

Horizon Mirage Reference Machine
A Horizon Mirage reference machine is used to create a standard desktop base layer for a set of CVDs. This
layer usually includes OS updates, service packs and patches, corporate applications for all target end-users
to use, and corporate configurations and policies. A reference machine is also employed to capture app
layers, which contain departmental or line-of-business applications and any updates or patches for already
installed applications.
You can maintain and update reference machines over time over the LAN or WAN, using a Horizon Mirage
reference CVD in the data center. You can use the reference CVD at any time as a source for base and app
layer capture.

Horizon Mirage Branch Reflector
A Horizon Mirage branch reflector is a peering service role that you can enable on any endpoint device. A
branch reflector can then serve adjacent clients in the process of downloading and updating base or app
layers on the site, instead of the clients downloading directly from the Horizon Mirage server cluster. Using
a branch reflector can significantly reduce bandwidth use during mass base or app layer updates or other
base or app layer download scenarios. The branch reflector also assists downloading hardware drivers.

Distributed Desktop Optimization
The Distributed Desktop Optimization™ mechanism optimizes transport of data between the
Horizon Mirage server and clients, making it feasible to support remote endpoints regardless of network
speed or bandwidth. Distributed Desktop Optimization incorporates technologies that include read-write
caching, file and block-level deduplication, network optimization, and desktop streaming over the WAN.

FAQ VMware Horizon Mirage

Q. What is VMware Horizon Mirage?
A. VMware Horizon Mirage is a layered image management solution that separates a desktop, laptop, or virtual endpoints into logical layers that are owned and managed by either IT or the end user. You can update IT-managed layers while maintaining end-user files and personalization. To maximize end-user productivity, snapshots and backups of layered desktop images enable quick recovery or rollback in case of failure.

Q. How does Horizon Mirage work?
A. Horizon Mirage categorizes a PC or virtual endpoint into logical layers owned by either IT or the end user, sends a complete copy of the system to the Mirage Server in the data center and keeps it synchronized. If an end user goes offline, Horizon Mirage performs a synchronization the next time that user comes back online. Synchronization pushes updates to the IT-managed layers and sends user-initiated changes back to the data center. Centralization and synchronization enable IT to manage the PCs and virtual endpoints more effectively. Images managed by Horizon Mirage can run natively on
Windows laptops and desktops or as virtual desktops running locally on Mac or Linux systems with VMware Fusion Professional, or in VMware Horizon View.

Q. How do the Horizon Mirage logical layers work?
A. When the Horizon Mirage client is installed on an endpoint, it scans the entire device and categorizes all of its contents into a number of logical layers. It creates two groups of layers: those that IT owns and manages and those that the user controls (such as the user’s profile and data and the applications the user installs). Horizon Mirage does not move anything around on the endpoint and does not isolate or virtualize the components. Instead, Horizon Mirage categorizes the data on an endpoint so that IT can perform more-granular management of the system components. After an update is made to a layer, that change is merged into the image running on that end-user system.

Q. How does Horizon Mirage categorize the data on the computer into separate logical layers?
A. The data is all stored in the data center, and Horizon Mirage uses algorithms to determine which objects on the endpoint belong to which logical layer. The information in the data center is stored in logical groupings of data from each endpoint that the Horizon Mirage server records.

Q. What was new in Horizon Mirage 4?
A. Horizon Mirage 4 included the capability for application layering. IT administrators can build layers that include individual applications or groups of applications to deploy and manage centrally for any combination of end users. Horizon Mirage 4 includes Fusion Professional, so IT administrators can deploy corporate images and applications to virtual machines running on Mac- or Linux-based desktops and laptops. Horizon Mirage 4 includes VMware ThinApp application virtualization technology to enable isolation and encapsulation of traditional Windows desktop applications for inclusion in image layers managed by Horizon Mirage.

Q. What is new in Horizon Mirage 4.3?
A. With this release, IT can leverage Horizon Mirage for image
management of Horizon View virtual desktops. IT can install and update base and application layers to full clone virtual machines in persistent desktop pools, in the same way they would with physical PCs. Using Horizon Mirage to manage images on full clones allows IT to update base and application layers on virtual machines without affecting user-installed applications and data. IT can effectively use Horizon Mirage to manage both physical and virtual endpoints at scale. Parent virtual machines for floating pools can also be managed by Horizon Mirage. Additional enhancements in 4.3 include a calculator that provides time estimates around centralization, new endpoint policy features, branch reflector enhancements, and a web console to ease administration. Additionally, in a Windows 7 migration, application layers can now be staged with the base layer.

Q. How well does the synchronization perform over the WAN?
A. Horizon Mirage was designed to excel over the WAN by leveraging deduplication both in storage and during network transfers. Horizon Mirage uses a global manifest in storage to ensure that data is stored only once. Horizon Mirage sends data across a network only when it is needed. Horizon Mirage (before network transfer) scans the source and the destination, computes the delta (i.e., determines which files are missing) and sends only what is required. Horizon Mirage also compresses network transmissions for additional network savings.


Q. Does Horizon Mirage replace my PC life-cycle management (PCLM) solution?
A. No, Horizon Mirage is not a replacement for PCLM solutions but complements and extends existing tools and processes.
The image-layering technology enables IT to easily migrate user data and profiles for in-place OS migration or hardware  refresh processes. Additionally, snapshots of PCs enable rollback or quick recovery in case of a failure.

Q. Can I adjust policies in Horizon Mirage?
A. The IT administrator can use settings in Horizon Mirage to customize how the Horizon Mirage system works—including how often snapshots are taken, what types of files are (and are not) centralized and how endpoints are centralized to the system—and to control role-based authentication for the Horizon Mirage management system.

Q. How does Horizon Mirage enable end-user personalization of PC systems?
A. Horizon Mirage maintains all end-user data even when an IT
administrator applies base layers. The only time end-user data is changed or modified is when it conflicts with data in the base layer. For example, if an end user has previously installed Office 2007, and an IT administrator deploys a base layer with Office 2010, that user’s instance of Office is upgraded to Office 2010. Otherwise, user personalization, files and applications are all completely persistent.

Q. How is data security managed?
A. The key points with regard to Horizon Mirage security are
• Third-party encryption can be used on the Horizon Mirage storage volumes in the data center.
• Third-party file-based encryption solutions are compatible with Horizon Mirage.
• Server-client communication can be encrypted using SSL.
• NTFS permissions are maintained on all files backed up by Horizon Mirage into the data center.
• Administration is role-based.
• Full audit logs are provided for tasks initiated in the Horizon Mirage console.

Q. How much of the desktop image is backed up?
A. Horizon Mirage provides a backup of the entire PC—not just the files. Restoration is simple, because Horizon Mirage restores an exact image of the user’s old PC—including personal applications, files and personalization—to the replacement desktop or laptop.

Q. How granular is the recovery process for a desktop image?
A. Because of the layering technology in Mirage, IT has three options for desktop recovery:
• Restore the entire device (OS, applications, user data and profile).
• Restore just the applications, user data and profile.
• Restore just the user data and profile.

Q. Can the end user initiate the repair?
A. No, restore and migration tasks must be initiated by the IT administrator. However, the end user can initiate files or directory restores. Windows 7 Migration

Q. How does Horizon Mirage streamline Windows 7 migration?
A. Horizon Mirage enables the two most common approaches to Windows 7 migrations: in-place and hardware refresh. Horizon Mirage can deliver a new IT-provisioned Windows 7 image to upgrade an existing Windows XP device or migrate an end user’s profile and files from that user’s previous Windows XP device to a new Windows 7 device.

Q. Can Horizon Mirage help reduce potential downtime when a migration fails?
A. Before attempting an in-place migration, Horizon Mirage  takes a full system snapshot of the Windows XP system. In case of a failure, IT can quickly restore the end user to the previous system.

Q. What is the typical end-user downtime during migration?
A. The user can continue working normally while the user’s device downloads the Windows 7 image from the Mirage server. End-user downtime—usually no more than 30 minutes—occurs during the reboot to apply the Windows 7 image (after it is done downloading).

Q. What are the Horizon Mirage client bandwidth requirements?
A. Horizon Mirage was developed to work effectively over the
WAN. On average, Horizon Mirage requires 15kb/sec per user, which equals roughly 50MB per user per day. Also, quality of service can be implemented in a number of ways in a number of locations to ensure that bandwidth is not taxed. The Horizon Mirage client also automatically monitors bandwidth and latency to throttle itself up or down, as appropriate, based on user needs.

Q. Do users need to be online to use a system managed by Horizon Mirage?
A. No. Horizon Mirage clients and images are installed directly
onto Windows PCs or in virtual machines with Fusion Professional. Horizon Mirage enables end users to leverage local computing resources of the device and maintain offline productivity.

Q. Are Horizon Mirage clients available for DOS, Linux, Mac and UNIX?
A. Horizon Mirage clients are supported in Windows XP 32-bit and Windows 7 32-bit and 64-bit systems. Horizon Mirage clients can be run inside of virtual machines, enabling PCa images to be delivered to Macs and Linux-based systems, and inside Horizon View virtual desktops.

Q. Does Horizon Mirage synchronize across different PCs?
A. Horizon Mirage does not support synchronization of the same end-user image across multiple devices.

Q. How is Horizon Mirage licensed?
A. Horizon Mirage is priced and licensed on a per-named-user model.

Q. How can I purchase Horizon Mirage?

A. Horizon Mirage is available for purchase—a la carte, with Horizon View to support image management for persistent virtual desktops or bundled in the VMware Horizon Suite—directly from VMware or any VMware authorized reseller partner.FAQ VMware Horizon Mirage

Q. What is VMware Horizon Mirage?
A. VMware Horizon Mirage is a layered image management solution that separates a desktop, laptop, or virtual endpoints into logical layers that are owned and managed by either IT or the end user. You can update IT-managed layers while maintaining end-user files and personalization. To maximize end-user productivity, snapshots and backups of layered desktop images enable quick recovery or rollback in case of failure.

Q. How does Horizon Mirage work?
A. Horizon Mirage categorizes a PC or virtual endpoint into logical layers owned by either IT or the end user, sends a complete copy of the system to the Mirage Server in the data center and keeps it synchronized. If an end user goes offline, Horizon Mirage performs a synchronization the next time that user comes back online. Synchronization pushes updates to the IT-managed layers and sends user-initiated changes back to the data center. Centralization and synchronization enable IT to manage the PCs and virtual endpoints more effectively. Images managed by Horizon Mirage can run natively on
Windows laptops and desktops or as virtual desktops running locally on Mac or Linux systems with VMware Fusion Professional, or in VMware Horizon View.

Q. How do the Horizon Mirage logical layers work?
A. When the Horizon Mirage client is installed on an endpoint, it scans the entire device and categorizes all of its contents into a number of logical layers. It creates two groups of layers: those that IT owns and manages and those that the user controls (such as the user’s profile and data and the applications the user installs). Horizon Mirage does not move anything around on the endpoint and does not isolate or virtualize the components. Instead, Horizon Mirage categorizes the data on an endpoint so that IT can perform more-granular management of the system components. After an update is made to a layer, that change is merged into the image running on that end-user system.

Q. How does Horizon Mirage categorize the data on the computer into separate logical layers?
A. The data is all stored in the data center, and Horizon Mirage uses algorithms to determine which objects on the endpoint belong to which logical layer. The information in the data center is stored in logical groupings of data from each endpoint that the Horizon Mirage server records.

Q. What was new in Horizon Mirage 4?
A. Horizon Mirage 4 included the capability for application layering. IT administrators can build layers that include individual applications or groups of applications to deploy and manage centrally for any combination of end users. Horizon Mirage 4 includes Fusion Professional, so IT administrators can deploy corporate images and applications to virtual machines running on Mac- or Linux-based desktops and laptops. Horizon Mirage 4 includes VMware ThinApp application virtualization technology to enable isolation and encapsulation of traditional Windows desktop applications for inclusion in image layers managed by Horizon Mirage.

Q. What is new in Horizon Mirage 4.3?
A. With this release, IT can leverage Horizon Mirage for image
management of Horizon View virtual desktops. IT can install and update base and application layers to full clone virtual machines in persistent desktop pools, in the same way they would with physical PCs. Using Horizon Mirage to manage images on full clones allows IT to update base and application layers on virtual machines without affecting user-installed applications and data. IT can effectively use Horizon Mirage to manage both physical and virtual endpoints at scale. Parent virtual machines for floating pools can also be managed by Horizon Mirage. Additional enhancements in 4.3 include a calculator that provides time estimates around centralization, new endpoint policy features, branch reflector enhancements, and a web console to ease administration. Additionally, in a Windows 7 migration, application layers can now be staged with the base layer.

Q. How well does the synchronization perform over the WAN?
A. Horizon Mirage was designed to excel over the WAN by leveraging deduplication both in storage and during network transfers. Horizon Mirage uses a global manifest in storage to ensure that data is stored only once. Horizon Mirage sends data across a network only when it is needed. Horizon Mirage (before network transfer) scans the source and the destination, computes the delta (i.e., determines which files are missing) and sends only what is required. Horizon Mirage also compresses network transmissions for additional network savings.


Q. Does Horizon Mirage replace my PC life-cycle management (PCLM) solution?
A. No, Horizon Mirage is not a replacement for PCLM solutions but complements and extends existing tools and processes.
The image-layering technology enables IT to easily migrate user data and profiles for in-place OS migration or hardware  refresh processes. Additionally, snapshots of PCs enable rollback or quick recovery in case of a failure.

Q. Can I adjust policies in Horizon Mirage?
A. The IT administrator can use settings in Horizon Mirage to customize how the Horizon Mirage system works—including how often snapshots are taken, what types of files are (and are not) centralized and how endpoints are centralized to the system—and to control role-based authentication for the Horizon Mirage management system.

Q. How does Horizon Mirage enable end-user personalization of PC systems?
A. Horizon Mirage maintains all end-user data even when an IT
administrator applies base layers. The only time end-user data is changed or modified is when it conflicts with data in the base layer. For example, if an end user has previously installed Office 2007, and an IT administrator deploys a base layer with Office 2010, that user’s instance of Office is upgraded to Office 2010. Otherwise, user personalization, files and applications are all completely persistent.

Q. How is data security managed?
A. The key points with regard to Horizon Mirage security are
• Third-party encryption can be used on the Horizon Mirage storage volumes in the data center.
• Third-party file-based encryption solutions are compatible with Horizon Mirage.
• Server-client communication can be encrypted using SSL.
• NTFS permissions are maintained on all files backed up by Horizon Mirage into the data center.
• Administration is role-based.
• Full audit logs are provided for tasks initiated in the Horizon Mirage console.


Q. How much of the desktop image is backed up?
A. Horizon Mirage provides a backup of the entire PC—not just the files. Restoration is simple, because Horizon Mirage restores an exact image of the user’s old PC—including personal applications, files and personalization—to the replacement desktop or laptop.

Q. How granular is the recovery process for a desktop image?
A. Because of the layering technology in Mirage, IT has three options for desktop recovery:
• Restore the entire device (OS, applications, user data and profile).
• Restore just the applications, user data and profile.
• Restore just the user data and profile.

Q. Can the end user initiate the repair?
A. No, restore and migration tasks must be initiated by the IT administrator. However, the end user can initiate files or directory restores. Windows 7 Migration

Q. How does Horizon Mirage streamline Windows 7 migration?
A. Horizon Mirage enables the two most common approaches to Windows 7 migrations: in-place and hardware refresh. Horizon Mirage can deliver a new IT-provisioned Windows 7 image to upgrade an existing Windows XP device or migrate an end user’s profile and files from that user’s previous Windows XP device to a new Windows 7 device.

Q. Can Horizon Mirage help reduce potential downtime when a migration fails?
A. Before attempting an in-place migration, Horizon Mirage  takes a full system snapshot of the Windows XP system. In case of a failure, IT can quickly restore the end user to the previous system.

Q. What is the typical end-user downtime during migration?
A. The user can continue working normally while the user’s device downloads the Windows 7 image from the Mirage server. End-user downtime—usually no more than 30 minutes—occurs during the reboot to apply the Windows 7 image (after it is done downloading).

Q. What are the Horizon Mirage client bandwidth requirements?
A. Horizon Mirage was developed to work effectively over the
WAN. On average, Horizon Mirage requires 15kb/sec per user, which equals roughly 50MB per user per day. Also, quality of service can be implemented in a number of ways in a number of locations to ensure that bandwidth is not taxed. The Horizon Mirage client also automatically monitors bandwidth and latency to throttle itself up or down, as appropriate, based on user needs.

Q. Do users need to be online to use a system managed by Horizon Mirage?
A. No. Horizon Mirage clients and images are installed directly
onto Windows PCs or in virtual machines with Fusion Professional. Horizon Mirage enables end users to leverage local computing resources of the device and maintain offline productivity.

Q. Are Horizon Mirage clients available for DOS, Linux, Mac and UNIX?
A. Horizon Mirage clients are supported in Windows XP 32-bit and Windows 7 32-bit and 64-bit systems. Horizon Mirage clients can be run inside of virtual machines, enabling PCa images to be delivered to Macs and Linux-based systems, and inside Horizon View virtual desktops.

Q. Does Horizon Mirage synchronize across different PCs?
A. Horizon Mirage does not support synchronization of the same end-user image across multiple devices.

Q. How is Horizon Mirage licensed?
A. Horizon Mirage is priced and licensed on a per-named-user model.

Q. How can I purchase Horizon Mirage?
A. Horizon Mirage is available for purchase—a la carte, with Horizon View to support image management for persistent virtual desktops or bundled in the VMware Horizon Suite—directly from VMware or any VMware authorized reseller partner.

Features and Benefits of VMware Horizon Mirage

Simplified Desktop Management

Layered Image Management
Manage your endpoint image as a set of logical layers owned by either your IT organization or the end user. Update IT-managed layers while maintaining end-user files and personalization.
Then, if an endpoint malfunctions, IT can restore the system layers on the endpoint to fix an issue, without compromising user applications and data. Or quickly migrate a user from an old PC to a new PC without losing any end-user data or personalization.
Horizon Mirage complements and extends existing management processes and solutions for the PC life cycle.

Desktop Backup and Recovery
Full PC snapshots and ongoing synchronization of changes in the data center ensure quick desktop recovery. By quickly restoring the system to a new device, you can minimize end-user downtime when a PC is lost, stolen or damaged.

Application Layering
Easily deploy individual applications or groups of applications— or VMware® ThinApp® packages—to any collection of end users by leveraging Horizon Mirage managed- application layering. Applications common to a certain team can be grouped into a single application layer and applied to all of the
endpoints for a group of employees. VMware ThinApp is included in Horizon Mirage.

Scalability with Small Infrastructure Footprint
Horizon Mirage is designed to support up to 1,500 end users per Horizon Mirage server, and it can easily scale up to 20,000 end users per server cluster.

Branch Office Optimization
Optimize branch office management by enabling any Horizon Mirage client endpoint to be a branch reflector. A Horizon Mirage branch reflector allows you to download any updates once from
the Horizon Mirage server, followed by peer-to-peer updates to other Horizon Mirage clients in the branch office. Advanced algorithms ensure that only required data is sent between the Horizon Mirage server and Horizon Mirage clients in a remote location or office.

Flexible PC Image Deployment
Provision centrally managed Horizon Mirage images to physical Windows desktops and laptops, or support “bring your own computer” initiatives by delivering IT-managed images to virtual machines with VMware Fusion Professional, which is included in Horizon Mirage.

View Desktop Image Management
Manage virtual desktops in your Horizon View environment using Horizon Mirage. Install and update Mirage layers to full clone virtual machines in persistent desktop pools, just as you would with physical PCs. This includes updating applications, OS patches, and base images. Managing virtual desktop images with Horizon
Mirage also allows updates to applications without affecting userinstalled applications and data. IT can effectively use Mirage to manage both physical and virtual endpoints at scale.


Empowering End-User Productivity
Across Boundaries

Personalized Performance
Enable end users to leverage the local computing resources of their desktops and laptops and maintain offline productivity. Images managed by Horizon Mirage install natively onto Windows desktops and laptops—or as virtual desktops in Fusion Professional running on Mac or Linux systems. Image layering gives end users
the flexibility to personalize their systems.

Optimized and Adaptive Experience
The Horizon Mirage client monitors the resources being used on an end user’s PC to ensure that the backup and synchronization processes never interfere with user productivity. Horizon Mirage
dynamically adjusts CPU, RAM and network usage as needed to guarantee a seamless end-user experience.

Self-Service File Access and Recovery
The Horizon Mirage file portal enables end users to access any file on their endpoint from any Web browser. Users can also restore any file or directory with a few clicks.

For more info http://www.vmware.com/products