9.2. System configuration

The System configuration page provides information relating to the PxM Platform and allows you to configure a number of different settings.

The following tabs are available:

WebUI System Config tabs

9.2.1. Licencing tab

The Licencing tab shows the current status of the uploaded PxM licence.

WebUI System Config Licencing tab

The following information is presented in the page:

Heading Description
Product usage

PxM Platform version: PxM Platform software version that is currently running.

Users: Displays the total number of created PxM user accounts against the total number of allowed user accounts. The PxM support account and the first SuperAdmin accounts will not be included in this count.

Devices: Displays the total number of provisioned devices managed by PxM against the total number of allowed devices. The Osirium Server device will not be included in this count.

MAP servers: Displays the total number of provisioned MAP servers used with PxM against the total number of allowed MAP servers.

Enabled features Any additional features purchased will be listed here.
Active licence(s)

Licencee: Name of the organisation or individual which the licence has been assigned to.

Expiry: The date/time the license is due to expire.

Note

When a licence is within 30 days of expiry a countdown warning message will appear in the PxM banner on the Web Management Interface.

When a licence has expired, PxM will only be fully functional until midday on the following day.

After this period the only access will be to the Web Management Interface and the product licence upload page.

9.2.1.1. Uploading a license

To load a licence:

  1. Click the Load new licence button. A Question window opens.

  2. Click Yes to proceed.

  3. Within the Upload licence window, click Choose File.

    WebUI Upload Licencing window

  4. Within the File upload page navigate to and select a valid PxM licence file.

  5. Within the Upload licence window, click Upload. The new licence file will be loaded. The licence information is updated to reflect any changes.

9.2.2. System settings tab

The following can be configured on the System settings tab:


WebUI System Config System Settings tab

9.2.2.1. Support account

The PxM Support (osirium_support) account is a PxM Virtual Appliance Ubuntu server administrative account. This account can be used for troubleshooting issues.

By default it is disabled and no password set.

To enable:

  1. Click on the Edit pencil icon icon.

    WebUI System Settings Support Acc

  2. Check the enabled box and type in a password.

    WebUI System Settings Support Acc enable window

  3. Click Save.

    WebUI System Settings Support Acc Set

9.2.2.2. PxM Platform Password Policy

For locally authenticated PxM users, a password policy can be configured to implement strong authentication.

To configure:

  1. To the right of PxM Platform password policy, click the Edit pencil icon icon.

    WebUI System Settings Password policy

  2. Set the appropriate policy using the fields described below.

    WebUI System Settings Password policy window

    Field name Description
    Maximum Length

    The password must be less than or equal to the maximum length set.

    If set to 0, the password will not expire.

    Invalid Characters
    Enter any characters you don’t want used in a password.
    Any password containing these characters will be
    disallowed.
    Minimum Length The password must be equal to or greater than the minimum length set.
    Require Letters and Numbers If true (tickbox checked), the password must contain both letters and numbers.
    Password Retries

    The user will be locked if an incorrect password is entered this many times.

    If set to 0, the user will be allow inifinite retries to enter their password.

    Unlock time (In Seconds) Time the user will have to wait before the account is automatically unlocked.
    Maximum Password Age (In Days) From the moment a password is changed, it starts aging. When the maximum age is exceeded, the user will be forced to change their password at next logon.
    Password Must Differ From The Last N

    When the user sets a new password, it must be different from the last N passwords they have used.

    If left as the default 0, the password does not have to differ from any passwords used before.

  3. Click Save.

9.2.2.3. Debug task logging

Enabling debug logging allows more data to be shown in the logs.

Useful when you need to troubleshoot failed tasks.

To enable:

  1. Click on the Edit pencil icon icon.

    WebUI System Settings Debug Task Logging

  2. Check the Enabled box.

    WebUI Generic value window

  3. Click Save.

9.2.2.4. Use external filestore

The PxM Virtual Appliance can be configured to use an external filestore which will be used to store files that are created i.e. backups, techouts, session recordings and session archives.

To add an external filestore:

Firstly, you will need to add a virtual hard drive to your virtual appliance.

Then:

  1. Click on the Edit pencil icon icon.

    WebUI System Settings Use External Filestore

  2. Check the Enabled box.

    WebUI System Settings External filestore window

  3. Click Save. Uses the tasks in the PxM template to partition, format and map to the external drive.

    The disk usage bar will now be shown for the internal and external disks. See Manage files.

Note

The external filestore may take a little time to appear on Web Management Interface, depending on the size of the disk that is being configured.

9.2.2.5. PxM Platform scheduled session archive

Recorded sessions can be queued for archiving on a nightly schedule. All recorded sessions older than the defined maximum session age will be archived.

Archiving sessions on a regular basis helps manage disk space on your PxM Platform.

If a Remote backup server has been configured then the archived session recordings will be pushed to the backup server.

To configure:

  1. Click on the Edit pencil icon icon.

    WebUI System Settings Scheduled Session Archive

  2. Check the Enabled box.

    WebUI System Settings Scheduled Edit Window

  3. In the Maximum session age (days) field, type in the number of days before a session is archived.

  4. Click Save.

    WebUI System Settings Scheduled Session Archive Configured

    • The Archive Session task is run everyday at midnight and will now archive any PxM Client sessions that are older than the age (days) set.
    • When sessions are archived, the screenshots are deleted from the PxM filestore and database. Sessions are marked as archived on the Device access.
    • Archived session files can be viewed and downloaded from the Manage files page.
    • The archived files will be stored in the internal filestore. If an external file store has been configured then the archived files will be saved there by default.
    • If a remote back server has been configured then the archived sessions will also be copied to the Remote backup server server.

9.2.2.6. PxM Platform scheduled file removal

Generated files (shown on the Manage files page) can be queued for deletion on a nightly schedule. All files older than the defined maximum age will be deleted.

Removing files on a regular basis helps manage disk space on your PxM Virtual Appliance.

To configure:

  1. Click on the Edit pencil icon icon.

    WebUI System Settings Scheduled File Removal

  2. Check the Enabled box.

    WebUI System Settings Scheduled Edit Window

  3. In the Maximum file age (days) field, type in the number of days before a file is deleted.

  4. Click Save.

    WebUI System Settings Scheduled File Removal Configured

    • The File removal task is run everyday at midnight and will now remove any files that are older than the age (days) set.

9.2.2.7. User Group Synchronisation interval (minutes)

This setting defines how often any Active Directory user groups will be synced with Active Directory.

To configure:

  1. Click on the Edit pencil icon icon.

    WebUI System Settings User Group Sync Interval

  2. The default value is set to 15 minutes. The value must be greater than or equal to 5.

    WebUI Generic value window

  3. Click Save.

9.2.3. Client settings tab

The following can be configured on the Client settings tab:


WebUI System Config Client Settings tab

9.2.3.1. PxM Client Colour

The colour option allows you to specify a colour for the PxM Client. This is useful when you want to distinguish the PxM Client connections made to different PxM appliances.

To change the colour of the PxM Client:

  1. Click on the Edit pencil icon icon.

    WebUI Client Settings Desktop Client Colour

  2. Enter a HEX colour code.

    WebUI Client Settings Desktop Client colour window

    or click the Colour picker icon icon to use the Select a Color window:

    WebUI Client Settings Colour picker window

  3. Click Save.

Now when a user logs onto the PxM Client, the PxM Client window will contain a coloured border. The user will only see the changes the next time they logon.

9.2.3.2. Device Group Separation Identifier

Device group separation allows you to restrict access to device tools from multiple customers, to ensure that workstations don’t become a bridge point for data.

Before creating a group separation identifier, you need to create a meta-column entry of type “Device”. See Configure meta-info. The meta-column values define the groups that are available. When a user connects to device tools through the PxM Client, the group separation identifier controls which sets of device tools they can use at the same time.

To configure the group separation identifier:

  1. Click on the Edit pencil icon icon.

    WebUI Client Settings DGS Identifier

  2. Choose the appropriate option from the drop-down box.

    WebUI Client Settings DGS Identifier window

  3. Click Save. Now the values in the device type meta-column will determine which device tools can be accessed after the first device tool connection has been made.

    For example:

    Device Meta-column value
    Device A Group 1
    Device B Group 1
    Device C Group 2
    Device D Group 2

    From the PxM Client, if a user opens a tool from Device A which belongs to Group 1, the tool opens successfully. Then, whilst Device A is open, if the user opens a tool from Device B, then this will be allowed.

    In the default ‘block’ mode, if the user has a device tool from Group 1 open and then tries to open a tool on Device C which belongs to Group 2, then the user will be unable to access the tool and the Platform will show an error message:

    Osirium proxy separation error

    Only when all Group 1 connections have been closed can the user open device connections from Group 2.

    Note

    This only applies to device tools, not to device tasks. Tasks can still be run at any time for any device.

9.2.3.3. Device Group Separation Behaviour

Device group separation behaviour can be changed from the default ‘block’ setting (meaning devices from multiple groups can’t be accessed at the same time) to a ‘warn’ setting. Selecting ‘warn’ means that a warning message appears when a user tries to connect to two devices from different groups, but the user can still continue to access both devices.

To configure the separation:

  1. Click on the Edit pencil icon icon.

    WebUI Client Settings DGS behaviour

  2. Select the warn value from the drop-down box.

    WebUI Client Settings DGS behaviour window

  3. Click Save. Now when a users opens up two connections to a devices in different device separation groups, they won’t be blocked but will be presented with a warning:

    DGS behaviour warning message

9.2.4. Network settings tab

The Network settings tab allows you to configure the following settings on the PxM Platform:

WebUI System Config Network Settings tab

9.2.4.1. PxM Platform DNS servers

To set DNS servers:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings Osirium DNS servers

  2. Set the primary, secondary and tertiary servers as required.

    WebUI Network Settings Osirium DNS servers window

  3. Click Save.

9.2.4.2. DNS search suffix

Adding DNS search suffix entries will help resolve IP addresses when adding new devices.

To add a DNS search suffix:

  1. Click on the Plus icon next to DNS Suffixes to add an entry.

    WebUI Network Settings DNS search suffix

  2. Click the Edit pencil icon icon for the newly added entry.

    WebUI Network Settings DNS search suffix New Entry

  3. Fill in the suffix:

    WebUI Generic value window

  4. Click Save.

9.2.4.3. PxM Platform NTP server

To set an NTP server:

  1. Click on the Plus icon next to Osirium NTP server. Osirium NTP server 1 will be added.

    WebUI Network Settings Osirium NTP server New Entry

  2. Click the Edit pencil icon icon for Osirium NTP server 1.

  3. Enter the IP Address or pool of the NTP servers.

    WebUI Network Settings Osirium NTP server window

  4. Click Save.

You can add multiple NTP servers by clicking the Plus icon icon several times.

9.2.4.4. PxM Platform syslog server

The PxM Platform will send copies of its syslog messages to as many external syslog servers as you wish.

To add an external Syslog server:

  1. Click on the Plus icon next to Osirium Syslog server. Osirium Syslog server 1 will be added.

    WebUI Network Settings Osirium Syslog Server New Entry

  2. Click the Edit pencil icon icon for Osirium Syslog server 1.

  3. Enter the IP Address of the Syslog server PxM will be communicating with.

    WebUI Generic IP value window

  4. Click Save.

9.2.4.5. Use CEF formatted syslog messages

Enabling this setting allows PxM to use the CEF formatting standard when displaying syslog messages.

To enable:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings CEF setting

  2. Check the Enabled box.

    WebUI Generic value window

  3. Click Save.

9.2.4.6. Logstash server

Enter your logstash server details to allow PxM to push events to your logstash server.

To add a logstash server:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings Logstash server

  2. Fill in the details.

    Webui Network Settings Logstash config window

    Field name Description
    Host: Enter the host name or IP address of the logstash server.
    Port Enter the port number assigned to the logstash server.
    Unchecked box icon Enabled Enabling will allow PxM to connect to the logstash server.
  3. Click Save.

9.2.4.7. PxM Platform SMTP Configuration

Configure the SMTP to allow emails to be sent from PxM Virtual Appliance. SMTP is required if you want to setup Email subscriptions, see Email subscriptions.

Note

The SMTP server should support TLS (Transport Layer Security) otherwise there is a risk that a password will be sent in plain text.

To configure SMTP:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings Osirium SMTP configuration

  2. Fill in the details.

    WebUI Network Settings Osirium SMTP configuration window

    Field name Description
    SMTP Server IP address of the SMTP server.
    Port Enter the port number assigned to the SMTP server.
    Username Enter the username that will be used to authenticate onto the SMTP server.
    Password Enter the password that will be used to authenticate onto the SMTP server.
    From Email Address Used to set the Reply-To and Sender headers user@domain of the outbound email.
    From name Used to set a text description in the Reply-To and Sender headers of the outbound email.
    SMTP Server Debug This allows email server transaction messages to be directed to the server.log file
    Force STARTTLS If checked, will force PxM to use STARTTLS. If the remote server does not support STARTTLS then an error will be logged in server.log
  3. Click Save. All SuperAdmins will receive an email to confirm that email has been successfully configured.

9.2.4.8. PxM Platform SNMP Configuration

Configure SNMP to allow PxM to be monitored on your network.

To configure SNMP:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings Osirium SNMP Configuration

  2. Fill in the details.

    WebUI Network Settings Osirium SNMP Configuration window

    Field name Description
    Read only community string Enter a valid read-only community string to allow SNMP requests to be sent.
    System location Enter the location of the the PxM Platform.
    System contact Enter a valid contact name for the PxM Platform.
  3. Click Save.

9.2.4.9. PxM Platform RADIUS Configuration

For PxM users to be authenticated through RADIUS, configure the RADIUS settings.

To configure Radius:

  1. Click on the Plus icon next to Osirium RADIUS configuration. Osirium RADIUS configuration 1 will be added.

    WebUI Network Settings Osirium RADIUS server New Entry

  2. Click the Edit pencil icon icon for Osirium RADIUS configuration 1.

  3. Fill in the following details:

    WebUI Network Settings Osirium Radius window

    Field name Description
    Address Enter the IP Address of the RADIUS server.
    Port Enter the port number assigned to the RADIUS server service.
    Secret Enter the RADIUS Secret that will be used to authenticate onto the RADIUS server.
  4. Click Save.

9.2.4.10. Poll RADIUS Servers

When enabled, PxM will test the connectivity to all the Radius servers it is configured to use.

To enable:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings Poll RADIUS servers

  2. Check the Enabled box.

    WebUI Generic value window

  3. Click Save.

    PxM will poll each Radius Server every 5 minutes. If the destination is unreachable a red message banner will appear on the Web Management Interface.

9.2.4.11. Remote backup server

If the remote backup server is configured, PxM will automatically push PxM backups to the specified server at the end of the backup task. If session recording is enabled, session recording archives will also be pushed automatically at the end of the archive task.

Supported protocols are SCP, SFTP and SMB.

To setup remote backup:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings Osirium Remote Backup

  2. Within the Edit entry window, fill in the following details:

    WebUI Network Settings Osirium Remote Backup window|

    Field name Description
    Server type

    Select the method to be used to copy the backup file.

    Note

    If None is selected from the drop-down list then the settings will be saved but the backup file will not be copied to the remote server.

    Server IP address Enter the IP address of the remote backup server.
    Port (SMB=445, SCP=22, SFTP=22) Enter the port number for the Server type selected.
    Path or share name Enter the path where the file will be saved to on the remote backup server.
    Username Enter a valid username with access to the remote backup server. The user must have the correct permission to write to the path specified.
    Password Enter a valid password.
  3. Click Save.

9.2.4.12. RDP Credential Check

PxM can attempt NTLM authentication before initiating RDP SSO connections. This provides nicer user feedback if the connection credentials are invalid.

Credential check is disabled by default. When enabled, PxM will do the credential check when any user opens an RDP SSO connection.

The credential check requires connectivity over ports 445 and 139.

To enable:

  1. Click on the Edit pencil icon icon.

    WebUI Network Settings RDP Credential Check

  2. Check the enabled box.

    WebUI Generic value window

  3. Click Save.

9.2.4.13. Routing table

Allows you to add static routes into Osirium’s local routing table.

To add entries:

  1. Click the Edit pencil icon icon.

    WebUI Network Settings Routing Table

  2. Within the Edit value window, click New and select Plus iconAdd entry.

    WebUI Network Settings Routing Table New Entry

  3. Enter the values you want to add to the routing table.

    WebUI Network Settings Routing Table Field Entry

  4. Click Save icon to save the new entry.

  5. Click Save changes.

    PxM must be rebooted before the routing table is applied to the PxM Platform. This can be done through the |os| device detail page > Tasks tab or the PxM Virtual Appliance Console window.

9.2.4.14. Integrating with SailPoint IdentityIQ

The PxM Platform can be integrated with SailPoint IdentityIQ to provide a governance based identity access management solution.

Integrating the PxM Platform with SailPoint IdentityIQ, enables the PxM users and PxM user groups to be synchronised into the SailPoint IdentityIQ server. SailPoint IdentityIQ can then manage and instruct PxM on provisioning requests for user creation, modifications, deletes, enable, disable and password changes.

Before the PxM Virtual Appliance can be configured to integrate with your SailPoint IdentityIQ the following prerequisites must be configured on your SailPoint IdenitityIQ server:

  • The Simple Table Integration (STI) module must be installed and configured.
  • The PxM Platform STI schema which has been created, and is available through SailPoint must be applied. The schema provides the default integration configuration requirements as well as creating the database tables that will contain the the PxM user and PxM user group fields.

Note

For more information, refer to the SailPoint IdentityIQ documentation.

Then, when the PxM Virtual Appliance has been configured to connect with your SailPoint IdentityIQ implementation the following will be enabled:

  • SailPoint will be able to create users and user groups on the PxM Platform which will be disabled as default.
  • When new PxM users are created on the PxM Platform they will be automatically synchronised onto the SailPoint IdentityIQ server.
  • Multiple PxM Platform can be added to the SailPoint IdentityIQ server as long as they have a unique hostname.
  • Policies defined within SailPoint IdentityIQ will be applied directly into the PxM Platform.

To synchronise your PxM Virtual Appliance with SailPoint IdentityIQ:

  1. On the left-hand menu, udner SYSTEM, click System configuration. The System configuration page appears.

  2. Click the Network settings tab.

  3. On the table, click the Edit value Edit pencil icon icon to the right of Sailpoint IdentityIQ integration configuration.

    WebUI Network Settings SailPoint

    The Edit entry window appears.

    WebUI Network Settings SailPoint Edit Entry window

  4. Within the Edit entry window, provide the following details to allow SailPoint IdentityIQ to synchronise with PxM:

    Field name Description
    Host The unique hostname of the SailPoint IdentityIQ server.
    Port The port number assigned to the SailPoint IdentityIQ STI database.
    Database Name Name of the STI database created in SailPoint IdentityIQ.
    Username The SailPoint username used to access the STI database.
    Password The password of the SailPoint username used to access the STI database.
    Unchecked box icon Enabled By default, SailPoint IdentityIQ integration in PxM is disabled. Select the checkbox to enable SailPoint IdentityIQ integration.
  5. Click Save. The SailPoint IdentityIQ integration details are added to the table.

    WebUI Network Settings SailPoint details

    Note

    When SailPoint IdentityIQ integration is complete, PxM automatically begins communicating with SailPoint. Desired integration behaviours, such as policies, must be configured within SailPoint IdentityIQ.

9.2.4.15. ServiceNow Ticket integration configuration

ServiceNow ticket integration in PxM allows tickets entered in the PxM Change Management Tool to be validated against an existing ServiceNow configuration management database (CMDB), providing the following benefits.

  • Accountability: ability to see when, why and how tickets are allocated.
  • Security: attackers require a valid change ticket on top of privileged credentials.

Prerequisites

  • PxM must be configured as an OAuth provider on the ServiceNow CMDB. When configured, a Client ID and Client Secret are created. Make a note of these credentials as they will be required to identify PxM to ServiceNow.

  • Obtain a ServiceNow refresh token by running the relevant command on your workstation, as detailed in the ServiceNow documentation. The client ID and client secret created above, as well as the ServiceNow CMDB URL, are required, as per the example below.

    Example command:

    $ curl -d "grant_type=password&client_id=be3aeb583ace210011c15b24a43e25d8
    			&client_secret=client_password
    			&username=admin&password=admin"
    			https://instancename.service-now.com/oauth_token.do
    			

    Make a note of the obtained refresh token.

    Note

    The refresh token has a lifespan designated in ServiceNow. When the refresh token expires, PxM automatically generates a new token.

To integrate ServiceNow with PxM:

  1. On the left-hand menu, udner SYSTEM, click System configuration. The System configuration page appears.

  2. Click the Network settings tab.

  3. On the table, click the Edit value Edit pencil icon icon to the right of ServiceNow Ticket integration configuration.

    WebUI Network Settings ServiceNow

    The Edit entry window appears.

    WebUI Network Settings ServiceNow Edit Entry window

  4. Within the Edit entry window, provide the following details to allow ServiceNow to integrate with PxM:

    Field name Description
    Host URL of the ServiceNow CMDB.
    Client ID Client ID generated when PxM was configured as an OAuth provider.
    Client Secret

    Client secret generated when PxM was configured as an OAuth provider.

    Note

    For more information, see the ServiceNow Ticket integration configuration prerequisites.

    ServiceNow Instance Refresh Token

    Refresh token obtained when PxM was configured as an OAuth provider.

    Note

    For more information, see the ServiceNow Ticket integration configuration prerequisites.

    Emergency Ticket (blank to disable)

    In the event that a incident or change ticket number does not exist on the ServiceNow CMDB, or if you are unable to access the ServiceNow CMDB, you can provide an emergency ticket. PxM does not check the emergency ticket against ServiceNow.

    Note

    This feature should only be used in an emergency and should otherwise be left blank.

    Unchecked box icon Enabled By default, ServiceNow integration in PxM is disabled. Select the checkbox to enable ServiceNow integration.

    WebUi Network Settings ServiceNow entered

  5. Click Save. The ServiceNow integration details are added to the table.

9.2.5. Mesh tab

The Mesh mechanism will allow an Active PxM Virtual Appliance primary to push a copy of its backup file to a Mesh secondary virtual appliance. The Mesh secondary virtual appliance does not contain any live configurations. A public key is used between the Active primary virtual appliance and the Mesh secondary virtual appliance to validate the mesh connection.

The stored backup file on the Mesh secondary virtual appliance can then used to restore an Active primary virtual appliance in a disaster recovery situation. See Osirium appliance restore instructions using a Mesh backup

Note

When you build a mesh or upgrade a mesh osirium, ensure you don’t delete or move the install files in /data/kits/latest in place, as these are required for the restore process to work.

WebUI System Config Mesh tab

To setup:

  1. Within the Active primary virtual appliance, click on the System Configuration > Mesh tab.

  2. Click the Plus icon icon next to Outbound Mesh connection. An Outbound Mesh connection 1 entry will be added.

    WebUI System Config Mesh Outbound Mesh Connection 1

  3. Click the Edit pencil icon icon for Outbound Mesh Connection 1.

  4. Fill in the following details:

    Field name Description
    IP Address IP address of the Mesh secondary virtual appliance where the backup will be stored.
    Push Backups Check to enable. This will allow the backup to be copied to the Mesh secondary virtual appliance.
  5. Click Save.

  6. Now click on the Public key and copy.

  7. Log onto the Mesh secondary virtual appliance and open up the Web Management Interface.

  8. Click System Configuration in the left-hand menu.

  9. Within the System configuration window, click on the Mesh tab.

  10. Within the Mesh tab, click on the Plus icon next to Inbound Mesh connection. An Inbound Mesh connection 1 entry will be added.

    WebUI System Config Mesh Inbound Mesh Connection 1

  11. Click the Edit pencil icon icon for Inbound Mesh Connection 1.

  12. Enter the API Key copied from the Active primary virtual appliance.

    WebUI System Config Mesh API key

  13. Click Save.

    Now, an outbound connection can be made from the Active primary virtual appliance to the Mesh secondary virtual appliance. The Mesh secondary virtual appliance will now accept file transfers from the Active primary virtual appliance.

  14. Now you need to create a profile to run the backup task against the Active primary virtual appliance - see Creating a new profile, at a scheduled time - see Creating a schedule or use an existing schedule.

    Once the scheduled backup has been created, it is automatically transfered to the Mesh secondary virtual appliance using SCP file transfer.

    Note

    Any PxM backup files created through manual execution will also be pushed to the Mesh secondary virtual appliance.

    Example:

    Active primary virtual appliance

    WebUI Mesh Profile example

    Backup file copied to the Mesh secondary virtual appliance

    WebUI Mesh remote Osirium Manage files page