The administrator can deploy the 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 Mirage servers in your DMZ premises, you must use a VPN to connect clients that are used outside the network.

  4. You must configure SSL on both the Mirage client and the Mirage server for the clients to connect using SSL.

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

    SERVERIP is the FQDN, hostname, or IP of the Mirage server or shared IP of the load balancer.

    64-bit clients

    		 
    <Mirage MSI path>\MirageClient.x64.buildnumber.msi
					 SERVERIP=MirageServer /quiet

    SERVERIP is the FQDN, hostname, or IP of the Mirage server or shared IP of the load balancer.

  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 and re-installation, restarting the computer assures better backup protection and enables streaming which promotes faster restoration.

Results

After the Mirage client is installed, the endpoint appears in the Mirage Management console as Pending Assignment.

What to do next

Verify that SSL is enabled on the Mirage server.

Activate the device in the Mirage Management console to assign the device to a CVD on the server. This process synchronizes the device and centralizes management of the device data.