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