Unattended Installation & Uninstallation
    • PDF

    Unattended Installation & Uninstallation

    • PDF

    Article summary

    Glasswall Meteor can also be installed and uninstalled silently using Windows Command Line Interface (CLI).

    Installation

    Unattended installation is a procedure for installing software without user intervention.

    Example:
    "Glasswall Meteor Setup.exe" /S /D="D:\My Files" --force-run

    /S :silent
    /D :install directory
    /allusers - Install for all users (requires command to be executed as Admin)
    /currentuser - Install for current user only (default)
    --force-run :to run directly after installation
    

    Uninstallation

    For Windows, an uninstaller is provided in the preferred installation directory. From the example above, this would be found in D:\My Files.

    Please refer to Appendix A for default install paths.

    Example:
    "D:\My Files\Uninstall Glasswall Meteor.exe” /S

    /S :silent
    

    Predefined Configuration

    System administrators may prefer to install the software with a configuration that limits users from making changes within the UI. A source JSON file can be referenced, and this will be copied to the ‘config’ folder under the ../AppData/Roaming/Glasswall Meteor path during the installation command.

    Example:
    "Glasswall Meteor Setup 3.0.0.exe" /ConfigPath="C:\config.json"

    A sample config file, that is inactive by default will be copied into the same directory by default and does not require a ‘ConfigPath’ location to be provided. This can serve as a template for an active config.

    Sample default ‘config.json’ file created in the config directory:

    {
      "configActive": false,
      "readOnlyUI": true,
      "policyEditable": false,
      "defaultManualCleanFolder": "C:\\Users\\userabc\\Desktop\\clean",
      "auditFolder": "C:\\Users\\userabc\\Documents\\audit",
      "Syncs": {
        "syncId1": {
          "name": "examplesync1",
          "sourceFolder": "C:\\Users\\userabc\\Documents\\examplesource1",
          "destFolder": "C:\\Users\\userabc\\Documents\\exampledest1"
        },
        "syncId2": {
          "name": "examplesync2",
          "sourceFolder": "C:\\Users\\userabc\\Documents\\examplesource2",
          "destFolder": "C:\\Users\\userabc\\Documents\\exampledest2"
        },
        "syncId3": {
          "name": "examplesync3",
          "sourceFolder": "C:\\Users\\userabc\\Documents\\examplesource3",
          "destFolder": "C:\\Users\\userabc\\Documents\\exampledest3"
        },
        "syncId4": {
          "name": "examplesync4",
          "sourceFolder": "C:\\Users\\userabc\\Documents\\examplesource4",
          "destFolder": "C:\\Users\\userabc\\Documents\\exampledest4"
        },
        "syncId5": {
          "name": "examplesync5",
          "sourceFolder": "C:\\Users\\userabc\\Documents\\examplesource5",
          "destFolder": "C:\\Users\\userabc\\Documents\\exampledest5"
        }
      }
    }
    

    Explanation of example:

    • The configuration is currently inactive, and therefore will be ignored on startup.
    • The user interface is read-only, meaning that file paths cannot be modified.
    • The content management policy is not editable.
    • The default manual clean folder is located at "C:\Users\userabc\Desktop\clean".
    • The audit folder is located at "C:\Users\userabc\Documents\audit".
    • There are five syncs defined, each with a unique sync ID.
      • Each sync has a name, a source folder, and a destination folder.
      • The source and destination folders are specified using file paths on the user's computer.

    Was this article helpful?