Contents x
    Deploying a Pre-installed Client
    • 24 Sep 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Deploying a Pre-installed Client

    • Updated on 24 Sep 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    If you are supporting employees, you might decide to deploy the Windows MSI or MacOS PKG files to your employees’ machines. 

    Doing so will enable them to open the ScreenMeet desktop application to enter the remote support code rather than navigate to a URL to download the on-demand client.

    If you are updating the ScreenMeet client from an older version below 2.61.6, you will need to uninstall the previous version before you install the new client.

    Client Download Links

    Windows Client

    The Windows MSI can be downloaded here.

    NOTE:

    When Installing on Windows, you will be given the option to install the Beam service. This service is required by the Beam application for unattended remote control. If you do not want to install the Beam service, you can select to have the feature unavailable, as shown below.

    Command-line Reference

    When deploying the ScreenMeet.msi you can pass certain configuration options in a command line for faster deployment.

    Here's a list of the configuration options you can specify and an example command:

    Common settings

    Argument

    Value

    Description

    APPLICATIONFOLDER

    [Path to ProgramFilesX86]\ScreenMeet

    Path to the folder where the ScreenMeet application will be installed.

    The default value is [Path to ProgramFilesX86]\ScreenMeet.

    PROGRAMMENUSHORTCUT

    1|<empty string>

    Add a shortcut to the Program Menu.

    PROGRAMMENUSHORTCUT="1" will add a shortcut.

    PROGRAMMENUSHORTCUT="" disables the shortcut.

    Default value is 1.

    DESKTOPSHORTCUT

    1|<empty string>

    Add a shortcut to the Desktop.

    DESKTOPSHORTCUT="1" adds a desktop shortcut.

    DESKTOPSHORTCUT="" disables the desktop shortcut.

    The default value is 1.

    AUTOCHECKUPDATES

    true|false

    Automatically check for updates.

    Default is true.

    AUTOUPGRADE

    true|false

    Automatically download and install client updates.

    Default is true.

    Note:  Can be set to true only if AUTOCHECKUPDATES is also true.

    ADDLOCAL

    [SupportFeature[,BeamFeature]]

    Provide a comma-separated list of features to be installed.

    Default is SupportFeature,BeamFeature.

    SupportFeature allows the application to be used for attended remote support sessions. The end user can open the application and enter the PIN created by the Agent.

    Example:

    ADDLOCAL=”SupportFeature,BeamFeature”

    ORGRESTRICT

    0|1

    Restricts usage for specific organizations listed in ORGRESTRICTLIST.

    Default is 0.

    ORGRESTRICTLIST

    List of comma-separated organization IDs (e.g., “82,154“) which are allowed to use the client.

    Note:  The ScreenMeet Organization IDs can be obtained from https://console.screenmeet.com  under Organization.

    Example Command

    msiexec /i ScreenMeet.msi /quiet APPLICATIONFOLDER="C:\Program Files (x86)\ScreenMeetApp" ADDLOCAL="SupportFeature" DESKTOPSHORTCUT="1" 

# This example will perform a silent install of the ScreenMeet application to the folder C:\Program Files (x86)\ScreenMeetApp, 
# enable the Remote Support application, and create a desktop shortcut.

    MacOS Client

    The MacOS Client PKG can be downloaded here.  Unlike the Windows Installer, the MacOS client is configured post-installation by executing the Application package with specific parameters.

    Note

    Unlike the Windows Installer where configuration is performed during installation, the MacOS client is configured post-installation by executing the Application package with specific parameters.

    Command-line Reference

    After installation of the PKG, the client can be configured from the command-line:

    open -n -a "/Applications/ScreenMeetSupport.app" --args <argument>=<value>

    Supported Session Parameters

    Argument

    Value

    Description

    code

    <session pin>

    If specified will attempt to connect to this session upon application start.

    Example:

    open -n -a "/Applications/ScreenMeetSupport.app" --args code="977113"

    confirmconsent

    <true|false>

    Skips the consent screen from screen sharing.

    true waits for user consent.

    false skips the user consent.

    Example:

    open -n -a "/Applications/ScreenMeetSupport.app" --args code="196900" confirmconsent="false"

    fileLogsLevel

    <1-4>

    Controls the level of logging output (if file logging is enabled)
    1 - Critical
    2 - Warning
    3 - Info
    4 - Debug

    proxy_url

    <url>

    If using a proxy, the proxy URL.

    proxy_username

    <username>

    The proxy username.

    proxy_password

    <password>

    The proxy password.

    Supported Configuration Parameters

    Argument

    Value

    Description

    getAllowedOrgIDs

    Returns the stored value for the allowed organization IDs.  Supported in 2.95 and later.

    Note: To use this parameter with the open command, you must specify the -o <filename> option to output the value:

    open -n -o stdout.txt -a "/Applications/ScreenMeetSupport.app" --args getAllowedOrgIDs

    setAllowedOrgIDs

    <comma-separated list of organization IDs>

    A comma-separated list of allowed organization IDs for this client.  Setting this with an empty value will DISABLE the restriction feature.  Supported in 2.95 and later.

    Example:

    open -n -a "/Applications/ScreenMeetSupport.app" --args setAllowedOrgIDs="123,124"

    Was this article helpful?
    What's Next