Everbridge 360 for Windows is distributed as an MSI package, which can be downloaded by clicking here.
You can deliver the MSI package to client devices using device and application management tools like Microsoft Intune and Microsoft Endpoint Configuration Manager.
MSI packages can also be deployed using the command line. The Everbridge 360 installer handles the standard command line options described here.
Installing
To install silently in the background, use the /quiet command line option. After installation the Everbridge 360 app will launch, and be configured to start each time a user logs in.
msiexec /package "C:\Path\To\Your\Everbridge360.msi" /quiet
When deploying via Intune or other enterprise software deployment tools, include any MSI properties (for example, ORG_CODE) in the install command line. Detection rules (such as checking for the C:\Program Files\Everbridge 360 folder) and uninstall commands (for example, using MsiExec.exe with the product GUID and /qn) remain separate and are not affected by adding ORG_CODE or other MSI properties to the install parameters.
Optional Parameters
The MSI installer takes a number of optional parameters to configure the application. They can be used like this:
msiexec /package "...\Everbridge360.msi" ORG_CODE=MyOrgCode FORCE_START_IN_TRAY=true /quiet
The available parameters are:
ORG_CODE=MyOrgCode
HIDE_EXIT_MENU_ITEM=true
FORCE_START_IN_TRAY=true
USE_IN_APP_BROWSER_FOR_SSO=true
HIDE_IN_APP_BROWSER_FOR_SSO=true
KEEP_NOTIFYING_UNTIL_ACTIONED=true
DURESS_CODE=1234
CRITICAL_SOUND=default
PRIORITY_SOUND=default
EXCLUDE_WATCHDOG=true (Requires 24.3.1 or higher)
For more information on these parameters click here.
In enterprise silent deployments, some administrators use FORCE_START_IN_TRAY=true to have Everbridge 360 start directly in the system tray after installation. Be aware this also causes the application to continue launching to the tray even when users start it from the Start menu. If you want to suppress any post-install screens without forcing tray-only behavior, you can omit FORCE_START_IN_TRAY and instead use your deployment tooling to close or hide any post-install UI as a post-install step.
Watchdog
From version 24.3.1, Everbridge 360 comes with a watchdog application to launch Everbridge 360 if it is not already running. The Everbridge360Watchdog process will be launched when Everbridge 360 first starts.
The watchdog is included by default but can be excluded by using the EXCLUDE_WATCHDOG argument with the installer.
If you use transforms (MST) or packaging scripts to customize deployment, you may want to ensure that both Everbridge360.exe and Everbridge360Watchdog.exe are stopped before upgrading or uninstalling. For example, some enterprise packaging teams add a pre-uninstall step similar to:
taskkill.exe /IM Everbridge360.exe /IM Everbridge360Watchdog.exe /T /F
The MSI includes an UpgradeCode, which is designed to remove the previous version and install the new version during an upgrade, without requiring a reboot between uninstall and reinstall in most environments. If your packaging process does not fully remove an older version, coordinate with your internal packaging team to add a pre-uninstall or process-stop step as needed and validate in a pilot group before broad rollout.
Uninstalling
Uninstall Wizard Method
- Open Add or remove programs in the Control Panel.
-
Find Everbridge 360. Choose uninstall.
- Windows will complete the uninstall process.
If the uninstaller can not close all requested applications due to lack of administrator rights, you may be prompted to manually close the running applications.
Command line method
If the original MSI file that was used to install Everbridge 360 is available, you can run following command, specifying the /uninstall switch and the full path to the MSI file.
msiexec /package "C:\Path\To\Your\Everbridge360.msi" /quiet