You can set default values of parameters that govern the behavior of branch reflectors.

About this task

The current Maximum Connections and Cache Size values apply to newly defined branch reflectors. You can correct them individually for selected branch reflectors. See Configure Specific Branch Reflector Values.

Other parameters in this window apply system-wide to all branch reflectors, existing or new.

Prerequisites

Verify that the branch reflector endpoint has enough disk space to support the Default Cache Size value, in addition to its other use as a general purpose desktop.

Procedure

  1. In the Mirage Management console tree, right-click System Configuration and click Settings.
  2. Click the Branch Reflector tab and configure the required default values.

    Option

    Action

    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.

    Use 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.

    Wake-on-LAN

    The Wake-On-LAN protocol allows the administrator to start machines from a dormant state (State from which you can resume. Depends on the NIC, and whether it keeps a low power state).

  3. Click OK.