Mirage

Licensing:

Mirage is sold in increments of 10 and 100 named users and is available as a standalone solution or as part of the Horizon Advanced or Enterprise Editions. Contact your local reseller for specific pricing.

See more at: http://www.vmware.com/products/horizon-mirage/pricing.html

 

Training:

About:

Dynamic Layering for Endpoint and Application Management

Manage PCs, or Horizon persistent virtual desktops, as a set of logical layers owned by either IT or the end-user. Update IT-managed layers while maintaining end-user files and personalization. Easily deploy applications or VMware ThinApp packages to any collection of end users with Mirage application layering technology.

Automated Backup and Full System Recovery

Store full desktop snapshots in the data center with continual synchronization of IT or end-user initiated changes. Recover partial or full desktops when needed with centrally stored desktop images and periodic endpoint snapshots. Allow self-service file recovery for end users and follow-me access to files across devices for enhanced productivity.

Simplified Windows 7 and Windows 8.1 Migrations

Accelerate the most common approaches to Windows 7 and Windows 8.1 migrations: upgrading an existing Windows XP device to Windows 7, upgrading Windows 7 to Windows 8.1, or migrating an end user’s profile and files to a new Windows 7 or 8.1 machine.

Designed for Distributed Environments

Mirage Branch Reflectors allow IT to download any updates once from the Mirage server and allows peer-to-peer updates from the Branch Reflectors to other Mirage clients in the branch office. Manage devices at scale with minimal infrastructure and controlled bandwidth.

Easy Extension of PC Lifecycle Management (PCLM) Tools

Complement existing PCLM tools with dynamic layering, backup and recovery, and rollback options to minimize helpdesk support. Extend existing PCLM tools by supporting mass OS deployments with just a few clicks. Use API extensibility and reporting framework to help manage devices more efficiently.

See more at: http://www.vmware.com/products/horizon-mirage/

Below are some design recommendations and requirements to follow for a Mirage deployment:

Mirage Architecture – Manage Centrally, Execute Locally

mirage

 

 Typical Mirage Deployment

miragedeploy

 

 

Mirage Architecture – Optimized Branch Management

miragebranch

 

Components:

Mirage installation (1 server required, 2 for resiliency, or bandwidth depends on number of simultaneous endpoints)

  • Mirage management server (interfaces with database)
    • Mirage server (controls all operations and objects)
    • Mirage management console (UI for Mirage administrator)
    • Can run the SQL database, if needed

File Portal

  • Optional feature
  • Must be on a server that is on the domain
  • Can co-reside on the Mirage server itself

Mirage client

  • 4MB .msi deployed to endpoints

Branch reflector

  • Peer-to-peer download for Mirage updates to remote offices
  • No additional install or setup required; simply designate an existing endpoint as a branch reflector

 

Software Requirements:

Mirage server

  • Windows Server 2008 R2 (Standard or Enterprise) 64-bit
  • .NET 3.5 SP1
  • Database (SQL Server 2008 R2, SQL Server 2008 R2 Express)

Using File Portal

  • IIS 7.0 (or later)
  • ASP.NET components required
  • IIS 6 management compatibility components required

Mirage client

  • Windows XP 32-bit, Windows 7 x86 or x64
  • .NET 3.5 SP1

 

Hardware Requirements: 

mirageharardwaare

Storage

  • Use SAN, NAS or local storage  (Spec out 1 IOPS Per CVD)
  • Needed storage per CVD varies greatly (948 GB)
    • Initial estimation during presales is 20 GB after de-duplication
  • Must support Windows ACLs and alternate data streams
  • Enable compression on Mirage storage volumes for disk space savings up to 25%
  • Does not require a high speed storage array

Mirage Client

  • Windows XP 32-bit, Windows 7 32-bit or 64-bit
  • Recommend at least 5GB free disk space on endpoint

 

Network Recommendations:

Average of 15Kbps per endpoint, roughly 50MB per endpoint per day

  • Varies by scenario, as Mirage performs file level deduplication across many managed endpoints

QoS can be implemented on any of the routers to throttle bandwidth and deliver quality

  • Third-party software can also be used

Client-side throttling:

  • Automatic bandwidth throttling depending on user activity level improves client experience
  • End users can “snooze” any Mirage network operations

Security:

  • SSL can be enabled for all communication between the client and the server
  • Global change – all clients or no clients must use SSL
  • NTFS is used on the server side, so all regular Windows Security (ACLs) apply
  • Can use NAS storage (such as NetApp or EMC) and associated data security tools in conjunction with Mirage to protect user data
  • MD5 checksum is used on all data files (backup and restore) for data integrity
  • Support for Windows encrypting file system
  • Compatible with BitLocker, Sophos Safeguard, and other encryption technologies

Installation Order:

mirage_install_order