Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Marvis Windows Client

Complete the preinstallation tasks, and then choose the method that you want to use to install the Marvis client on your Windows device.

The Marvis client for Windows provides detailed visibility into how your Windows device interacts with the wireless network. The Marvis client helps optimize network performance, streamline troubleshooting, and enhance overall user experience by offering insights into device connectivity and performance.

Marvis Windows Client Installation Overview

You can download the Marvis client for Windows (marvisclient-installer.msi file) from the Juniper Mist portal.

To download the .msi file from the Juniper Mist portal:

  1. Select Organization > Admin > Mobile SDK from the left menu.

  2. Click Marvis Client at the top of the Mobile SDK page.

  3. Under Windows, select the app version, and then click Download Installer.

  4. Extract the marvisclient-installer.msi file from marvisclient-installer.zip.

Save the .msi file in a folder on your device.

Installation Options for the Marvis Windows Client

You can use any of the following installation options:

Prerequisites

Before you begin, you'll need to have:

  • .Net Framework Runtime (4.6.2 or above) installed on your device.

    Note:

    You can opt to install these applications later after installing the Marvis Windows client. However, installing the application later requires you to restart the device.

  • The secret token or QR code to onboard the Marvis client.

    1. Select Organization > Admin > Mobile SDK from the left menu.

    2. Click Token at the top of the Mobile SDK page.

    3. Create a new token, or use an existing token:

      • For a new token—Click Create Invitation. Enter a name for this invitation, and then click Create. When the token appears on the page, click View to see the QR code.

      • For an existing token—Refer to the token names to find the one that you want to use. Click the View link on the right side of the page to see the QR code.

    Note: To obtain the secret token using API, see https://api.mist.com/api/v1/docs/Org#sdk-invite.

  • Windows 10 or a later release running on the devices

Operational Modes

The Marvis client operates in the following modes:

  • Production mode—Standard operational mode for live environments that you can set using command-line parameters during installation.

  • Proof of Concept (POC) mode—Operational mode for testing and evaluation purposes and is also the default mode.

  • GUI or Non-GUI mode—Mode that enables or restricts visual access to the Marvis client. In non-GUI mode, you cannot access the UI or the icon in the taskbar.

  • Debug mode—Mode to access the logs. You cannot edit the configuration in this mode.

Note:

  • If you want to view the configuration settings when you're in Production mode, you'll need to switch to the debug mode. However, the settings are not editable.

  • In POC mode, you can view and edit the configuration settings without any dependency on the debug mode.

Connection States

The Marvis client status is indicated by the following visual indicators and connection states:

  •  Disconnected—Client is not connected to the Juniper Mist cloud.

  •  Connected—Client is connected to the Juniper Mist cloud.

  •  Connecting—Client is requesting to connect to the Juniper Mist cloud.

  •  Sleeping —Client is connected to the Juniper Mist cloud through a non-Juniper access point (AP).

Install the Marvis Windows Client (GUI Method)

To install the Marvis Windows client:
  1. Double-click the marvisclient-installer.msi file that you downloaded from the Juniper Mist portal.
  2. Click Yes to proceed with the installation.
  3. Verify that the installation is successful. After the installation is complete, you'll see the Marvis icon in the system tray.
  4. Click the Marvis icon in the system tray to open the Marvis client app. To see the menu, right-click the icon.
  5. Click the hamburger icon in the app and select Configuration.
  6. Enter the SDK token in the Mobile SDK Secret field and click Apply. By default, the Battery Saving mode is set to Standard and you can change the mode if required.

    The Battery Saving mode determines the frequency at which the payloads are sent.

    • High: In this mode, the client sends data payloads every 2 minutes. With reduced frequency of data transmission, this mode helps conserve battery power. This mode is suitable for scenarios that require less frequent updates.

    • Standard: In this mode, the client sends data payloads every 30 seconds. This mode provides a balance between data and battery consumption, offering more frequent updates without significantly impacting battery life.

    • Low: This mode provides the highest frequency of data transmission by sending data payloads every 10 seconds. This mode provides the most detailed insights into network performance but consumes more battery power when compared to the other modes.

Install the Marvis Windows Client (CLI Method)

You can use the CLI method to install the Marvis client app if you want to make some advanced customization during installation.

  1. Open a command prompt window as an administrator or as a user with administrator privileges.
  2. Navigate to the folder where you saved the marvisclient-installer.msi file.
  3. Use one of the following options to install the client using your secret SDK token:
    Note:

    You must install the Marvis client in quiet mode using administrator privileges. For Windows 11, ensure to enter the quiet mode parameter /qn at the end of the msiexec installation command. For Windows 10, there is no restriction on the placement of the /qn parameter.

    • Default configuration:

    • Custom configuration:

      You can customize the installation by configuring additional parameters listed in Table 1. Here's an example:

      Table 1: Custom Configuration Parameters for Marvis Client Installation

      Parameter

      Description

      MOBILE_SDK_SECRET

      The SDK invite code or secret for your organization

      MIST_BATTERY_SAVING

      Determines the frequency at which the client sends the payloads. You can use one of the following battery saving modes:

      • High: In this mode, the client sends data payloads every 2 minutes. With reduced frequency of data transmission, this mode helps conserve battery power. This mode is suitable for scenarios that require less frequent updates.

      • Standard: In this mode, the client sends data payloads every 30 seconds. This mode provides a balance between data and battery consumption, offering more frequent updates without significantly impacting battery life.

      • Low:

        In this this mode, the client sends data payloads every 10 seconds. With the highest frequency of data transmission, this mode provides the most detailed insights into network performance. However, this mode requires more battery power compared to the other modes.

      PRODUCTION

      Determines the visibility of features in the Marvis client UI based on the operational mode:

      • True: Indicates the Production mode, which is the standard operational mode for live environments.

      • False: Indicates the Proof of Concept (POC) mode that is used for testing and evaluation purposes.

      The default value is False.

      MIST_LOG_LEVEL

      Defines the log level for the Marvis client.

      MIST_UI_ENABLED

      Hides (value=True) or shows (value=False) the Marvis client UI during installation. The default value is true.

      Proxy Server Settings

      MIST_PROXY_URL

      Complete URL of the proxy server including the port.

      MIST_PROXY_BYPASS_LIST

      List of hosts on which you don’t want to apply the proxy settings.

      MIST_PROXY_USERNAME

      Username (required if the proxy server requires authentication).

      MIST_PROXY_PWD

      Password (required if the proxy server requires authentication).
  4. Verify that the installation was successful. See Verify the Marvis Client Installation for Windows.

Install the Marvis Windows Client (Configuration File Method)

You can install the Marvis client using a transform file, which enables customized or bulk installations.
  1. Set up a transform file. The transform file (*.mst) provides the .msi file with the configuration parameters to customize the default installation. You can use the configuration parameters listed in Table 1.

    For information about setting up a transform file, see How to Edit an MSI File using [ORCA Editor (plus alternative tool)].

  2. Open a command prompt window and enter the following command:

Deploy the Marvis Client on Windows Devices Using an MDM

You can deploy the Marvis client on Windows devices by using the SOTI or Intune mobile device management (MDM) solution. Before you begin, verify that all devices have the appropriate MDM profiles and permissions assigned.

Deploy the Marvis Windows Client Using the Intune MDM

To deploy the Marvis client using the Intune MDM:

  1. Enroll the target device in Intune.

  2. Add the .msi installer as a Windows LOB (Line of Business) app in the Intune portal.

  3. Configure the necessary policies and include the following post-installation script:

    Refer to Table 1 for details about the parameters.

    Depending on your policy type (mandatory or suggested), the Marvis client app is either directly installed or appears in the company portal as an optional app that you can install.

  4. Verify the installation status on the MDM portal to confirm that the deployment is successful.

Upgrade the Marvis Windows Client in Intune

To upgrade to a newer version of the Marvis client, replace the existing .msi file with the latest version in the Intune portal. The post-installation script does not require any changes. It might take some time for the updates to reflect on the Intune portal.

Update the Marvis Windows Client Configuration in Intune

To update the Marvis client configuration parameters, you can change the registry values on the target devices and restart the system. This method enables you to update configurations without reinstallation. Make configuration script updates and registry adjustments cautiously to customize app functionality and user experience.

  1. Update the Marvis client configuration values under the following registry path:

    Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Juniper\Marvis\Config

    Values: MOBILE_SDK_SECRET, MIST_BATTERY_SAVING, PRODUCTION

    Refer Table 1 for details about the parameters.

    Note:

    You cannot update the MIST_UI_ENABLED parameter through the registry after the Marvis client is installed.

  2. Create a registry update script. Use PowerShell to update the registry values as shown:

    Some configuration changes might require restarting the device. If needed, include the restart command at the end of the script:

  3. Deploy the registry update script.

    Navigate to Device Configuration > Scripts to assign the script to the device group.

Uninstall the Marvis Windows Client Using the Intune MDM

To uninstall the Marvis client:

  1. Revoke the application assignment in Intune. Remove the policy that enforces Marvis client installation for the target devices.

  2. Create a script using the CLEAN=true parameter to remove the Marvis client completely:

  3. Deploy the uninstallation script. Use Device Configuration > Scripts and assign the PowerShell script to the device group.

    Note:

    After the uninstallation is complete, ensure to remove the devices from the Uninstall rule to avoid conflicts during future installations.

Deploy the Marvis Windows Client Using the SOTI MDM

To deploy the Marvis client using the SOTI MDM:

  1. Ensure that the target Windows device is enrolled in SOTI MobiControl and is connected to the management console.

  2. Upload the .msi installer for the Marvis client:

    1. Navigate to Add Applications in SOTI MobiControl and select Enterprise Apps > Windows.

    2. Select and upload the .msi installer for the Marvis client to the SOTI server.

  3. Assign the Marvis client app to the appropriate devices or device groups within SOTI. Based on the deployment settings, the application is automatically installed or is available on demand.

  4. Create a separate Script Job in SOTI with the required environment variables for configuration.

Upgrade the Marvis Windows Client in SOTI

To upgrade the Marvis client in SOTI:

  1. Replace the current .msi installer for the Marvis client with the updated installer in SOTI.

  2. Reassign the application.

    The policy will push the updated installer to devices according to the assignment.

Update the Marvis Windows Client Configuration in SOTI

You can apply configuration updates directly through registry edits:

  1. Update the Marvis client configuration values under the following registry path:

    Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Juniper\Marvis\Config

    Values: MOBILE_SDK_SECRET, MIST_BATTERY_SAVING, PRODUCTION, MIST_UI_ENABLED

  2. Create a registry update script. Use PowerShell to update the registry values as shown:

    Some configuration changes might require a system restart. If needed, include the restart command at the end of the script:

  3. Deploy the registry update script. Use the Jobs feature to deploy this PowerShell script to the target devices.

Uninstall the Marvis Windows Client Using the SOTI MDM

To uninstall the Marvis client:

  1. Revoke the application assignment in SOTI. Remove the policy that enforces Marvis client installation for the target devices.

  2. Create a script using the CLEAN=true parameter to remove the Marvis client completely:

  3. Deploy the uninstallation script. Use the Jobs feature to deploy this PowerShell script to the target devices.

    Note:

    After you've uninstalled the client, ensure to remove the devices from the Uninstall rule to avoid conflicts during future installations.

Verify the Marvis Client Installation for Windows

Use any of the following options to verify that the Marvis client was installed successfully:

  • Verify services:

    1. Open Task Manager and navigate to the Services tab. Alternatively, you can use the Windows Service Manager (compmgmt.msc).

    2. Verify that the MarvisClient service is running.

  • Verify files and system registry:

    1. Verify that the files are located in the C:/Program Files(x86)/Juniper Networks/Mist/Marvis folder.

    2. Navigate to the system registry and verify that the configuration variables are listed under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Juniper\Marvis\Config.

  • Verify that the Marvis client icon is displayed in the startup folder C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp.

View Logs in the Marvis Windows Client

The Marvis Windows client classifies the logs as:

  • Info—General information

  • Error—Critical issues

  • Debug—Detailed data that you can use to debug issues

To view the logs in the Marvis Windows client app, you'll need to enable debug mode on the app:
  1. Click the hamburger icon and then click the Marvis icon 7 times.
    You'll be prompted for a password.
  2. Enter the password as AIDriven.

    You'll see the Logs option listed in the menu.

  3. Select Logs. You can select the type of information you want to view by selecting an option from the Log Level drop-down list.

    You'll see recent logs based on the selected log level.

    You can click the Copy button to copy the log details and send the data to the support team for troubleshooting.

  4. Click View to view the logs captured by the Marvis client in your OS-specific log viewer.
    Note:

    If you contact the Juniper Mist support team to resolve any issue, you might be asked to provide details such as the organization ID, UUID, and organization name. You can find these details listed in the About page, which you can access from the hamburger menu.

    The information in the About page varies based on the operational mode of the Marvis client:

    • Production mode—Application version, UUID, and organization name

    • POC and Debug modes—Application version, UUID, Mobile SDK Secret, Org ID, and organization name

Uninstall the Marvis Windows Client

You uninstall the Marvis client only when you make major changes, such as name changes or file path location changes. Minor updates or change in organization do not require that you uninstall the Marvis client.

To uninstall the Marvis client:

  1. Navigate to Settings > Apps on your device.
  2. Search for MarvisClient from the list of applications.
  3. Click … and select Uninstall.

The Marvis client will be uninstalled from your device.

Note:

Uninstalling the client might not remove all log files and folders. You can choose to delete the files manually if required. To completely remove Marvis client along with all the logs and configuration files, use the following command: