VCAP6-DTM Deployment Objective 1.2 – Configure and Manage VMware Mirage Components

Configure/Manage Mirage permissions

To manage View Mirage server permissions, open VMware Mirage Console from desktop and connect to your Mirage server by specifying FQND or IP address.

In new console window select Users and Roles.

Users and Roles in Mirage Console

User and Roles

To create new Role right click Users and Roles and select Add Role. Type Name and Description and click OK to create.

Add Role

Add a Role window

To modify new role select Users and Roles to show all existing and new role, choose which permission you want to assign to new role.


Permissions window

To add group to new role select that role and click green plus button in top left corner or right click the role and choose Add Group.

Manage bandwidth limitation to prevent Mirage from consuming all bandwidth for a single site/subnet

Mirage allow to control bandwidth setting to set upper limit for Mirage traffics.
To do that in VMware Mirage Server Console right click on System Configuration and choose Settings. From new window select Bandwidth Limiting and click Sample rules in bottom right corner.


Bandwidth Limiting configuration

New Window will open with sample rule, follow the rule to create new one save as txt or csv, Click Import rules to import and start using new rule

SubnetMaskV4,Site,Download Limit,Upload Limit, Start Time, End Time, Days of Week


Sample Rule


Imported Rule

Import Microsoft User State Migration Tools (USMT) files for required base layer operations

Mirage supports USMT 4 and USMT 5 for Windows XP and Windows 7, and USMT 6.3 for Windows 8.1.
To upload USMT files first download from PC with installed Windows Automated Installation Kit AIK.

Copy this file in to directory on Mirage server. From Mirage Console right click System Configuration and click Settings. Click Import USMT Folder..


USMT Settings

Configure/Manage Branch Reflectors

First Branch Reflectors need to be selected from Mirage Clients endpoints, Open Mirage Server Console and expand Inventory and select Assigned Devices, choose one device right click and select Branch Reflector > Enable Branch Reflector. After device is selected it will appear in Branch Reflectors under System Configuration.

To modify default settings for Branch Reflector right click System Configuration > Setting open tab Branch Reflector. Modify below setting according to deployment plan.

Default Maximum Connections – Maximum number of endpoint devices that can simultaneously connect to the branch reflector.
Default Cache Size (GB) – Cache size allocated to the branch reflector
Required Proximity (msec) – Maximum time for a branch reflector to answer a ping before an endpoint start downloading through the branch reflector.
Use Active Directory Sites – Mirage uses subnet and physical proximity information to choose branch reflectors.
Always Prefer Branch Reflector – To keep network traffic as low, select this option to force clients use branch reflector when one becomes available. If the option is not selected, client connects to the Mirage server directly.


Branch Reflector settings

To disable Branch Reflector under System Configuration select Branch Reflectors choose Endpoint right click and choose Disable Reflector click YES to conform.

Configure Centralized Virtual Desktop (CVD) settings according to a deployment plan

CVDs represent the complete contents of each PC. This data is migrated to the Mirage server and becomes copy of the contents of each PC. CVD contain serval layers:

Base layer – The base layer includes the operating system (OS) image and core applications such as antivirus, firewall, and Microsoft Office.
App layers – App layers include sets of one or more departmental or line-of-business applications, and any updates or patches for already installed applications.
Driver profile – The driver profile specifies a group of drivers for use with specific hardware platforms.
User-installed applications and machine state – End users User-installed applications and machine state can include a unique identifier, host name, any configuration changes to the machine registry, DLLs, and configuration files.


One response to “VCAP6-DTM Deployment Objective 1.2 – Configure and Manage VMware Mirage Components

  1. Pingback: VCAP6-Desktop and Mobility Deployment Study Guide – Virtual Elementary·

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.