Skip to main content

Objective 1.2 - Configure and Manage VMware Mirage Components

This Post will cover Objective 1.2 of the VCAP-DTM Deployment Exam

Tools and References for Objective 1.2:

VMware Mirage Management Console

Skills and Abilities:

Configure/Manage Mirage 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.
  • To create new Role right click Users and Roles and select Add Role. Type Name and Description and click OK to create. 
  • To change a new role select Users and Roles to show all existing and new role, choose the permission you want to assign to the new role.
  • To add AD group to new role select that role and click green plus at the top left corner.

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

  • On the VMware Mirage Server Console right click on System Configuration and choose Settings.
  • Select Bandwidth Limiting and click Sample rules.
  • A sample rule will be displayed follow the rule to create new one save this as txt or csv file,
  • Then click Import rules to import and start using new rule SubnetMaskV4,Site,Download Limit,Upload Limit, Start Time, End Time, Days of Week

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

  • The version that this test covers Mirage supports the following USMT versions:
    • Version 4 and 5: for windows xp and windows 7
    • Version 6.3: for Windows 8.1
  • Find the USMT folder in the directories installed with the Windows Automated Installation Kit (AIK) software.
    • You can download this software free of charge from Microsoft.
  • Copy the USMT folder and all subdirectories to your Mirage server.
  • Right-click the System Configuration node and click Settings.
  • Click the USMT tab.
  • Click Import USMT Folder.
  • Navigate to the location of the USMT folders and click OK.
  • After the Mirage Management console imports the USMT file for the specific operating system, a check mark is displayed next to each USMT version.

Configure/Manage Branch Reflectors

  • You can select any Mirage client endpoint to function as a branch reflector, in addition to serving a user. Alternatively, you can designate a branch reflector to a dedicated host to support larger populations. A branch reflector can run on any operating system compatible with Mirage clients.
Enable Branch Reflectors:
  • In the Mirage Management console tree, expand the Inventory node and select Assigned Devices.
  • Right-click an endpoint device and select Branch Reflector > Enable Branch Reflector.
    • When a device is enabled as a branch reflector, it is listed in the Branch Reflectors window, as well as remaining on the Device Inventory window.
  • (Optional) Select System Configuration > Branch Reflectors to view which devices are enabled as branch reflectors
Configure Defaults for Branch Reflectors:
  • In the Mirage Management console tree, right-click System Configuration and click Settings.
  • Click the Branch Reflector tab and configure the required default values.
    • Default Maximum Connections
      • Type the maximum number of endpoint devices that can simultaneously connect to the branch reflector.
    • Default Cache Size (GB)
      • Type the cache size that the branch reflector allocated.
    • Required Proximity (msec)
      • Type the maximum time, for example 50 ms, for a branch reflector to answer a ping before an endpoint considers downloading through the branch reflector. The endpoint downloads from the server if no branch reflectors satisfy the specified proximity.
    • User Active Directory Sites
      • Mirage uses subnet and physical proximity information to choose branch reflectors. Select this check box to use Active Directory site information to determine to which branch reflector to connect.
    • Always Prefer Branch Reflector
      • To keep network traffic as low as possible, select this option to force clients to continually repeat the matching process until a suitable branch reflector becomes available. In this case, a client connects to the Mirage server only if no branch reflectors are defined. If the option is not selected, and no match is found or suitable branch reflectors are currently unavailable, the client connects to the Mirage server directly as a last resort.
  • Click Ok
Configure Specific Branch Reflector Values:

Note:
  • Newly created branch reflectors are assigned default parameter values. You can adjust some of these values for individual branch reflectors.
Procedure:
  • In the Mirage Management console tree, expand the System Configuration node and click the Branch Reflectors tab.
  • Right-click the branch reflector device and select Branch Reflector > Configure.
  • Click OK.
  • The branch reflector configuration settings take effect immediately. You do not need to restart the branch reflector client.
Disable Branch Reflectors:
Notes:
  • When a branch reflector is disabled, the device is deleted from the Branch Reflectors list. But it continues to be available because an endpoint device remains as a regular Mirage endpoint in the device inventory.
  • When a branch reflector is disabled, its base layer cache is deleted.
Procedure:
  • In the Mirage Management console tree, expand the System Configuration node and click the Branch Reflectors node.
  • Right-click the branch reflector device and select Branch Reflector > Disable Branch Reflector.
Reject or Accept Peer Clients:
Notes:
  • When you use the Reject Peers feature, the branch reflector is not deleted from the Branch Reflectors list. The branch reflector cache is preserved.
  • You can use the Accept Peers feature to resume providing service to the peer clients of a paused branch reflector.
Procedure:

  • In the Mirage Management console tree, right-click System Configuration, select Settings, and click the Branch Reflectors tab.
  • Right-click the branch reflector device and reject or accept the peer clients.
Suspend or Resume Server Network Operations:

Notes:
  • Suspending network operations for a branch reflector still allows peer clients to download layer files from the branch reflector cache, but the branch reflector cannot download new files from the server.
  • When you resume network operations, the branch reflector or the individual endpoint device can communicate with the Mirage server cluster.
Procedure:
  • In the Mirage Management console tree, right-click System Configuration, select Settings, and click the Branch Reflectors tab.
  • Right-click the branch reflector device and select Suspend Network Operations or Resume Network Operations.
  • (Optional) Select Connection State from the column headings drop-down menu to view which branch reflectors are connected or suspended in the Branch Reflectors window.

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

CVD contain several layers listed below:
  • Base layer – The base layer has the (OS) and core applications for example: antivirus and firewall.
  • App layers – App layers include 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 – User-installed applications and machine state can include a unique identifier, host name, any configuration changes to the machine registry, DLLs, and configuration files.

Configure connectivity between Mirage components

Below is a list of network source and destination requirements for Mirage components
  • Items not listed below are:
    • Mirage management servers share access with SQL DB and Storage volumes
Source Default Port Protocol Destination Notes
Mirage Client (Software) 8000 SSL/TLS Mirage Geteway Destination Program /opt/miragegateway/bin/miragegateway
Mirage Client (Software) 8000 TCP/IP or SSL/TLS Mirage Server
Branch Reflector Mirage Server
Mirage Server Branch Reflector
Branch Reflector 8001 TCP/IP Mirage Client (Software)
Mirage Gateway 8000 SSL/TLS Mirage Server Destination program: C:\program files\wanova\mirage server\wanova.mirage.server.exe
Mirage Web Manager 8080 TCP/IP Mirage Gateway
Mirage Web Manager 8443 TCP/IP Mirage Management Server
Mirage Gateway 389 or 636 LDAP or LDAPS Active Directory LDAP Uses Port 389 and LDAPS uses port 636
Browser 6443 TCP/IP Mirage File Portal Server
Browser Port Used by VPN Protocol Used by VPN File Portal Server
Labels:

Comments

Post a Comment