Each organization’s HyperIntelligence deployment will differ depending on various circumstances; nevertheless, the common goal across all deployment types is the ability for the application to communicate with the desired host.
To determine how you will deploy the application, there are a few things to consider:
In addition to these questions, it’s important to note that communication can be accomplished remotely through SSH, a Remote Login session, or an installed agent. If the desired host is “managed” or part of the organization’s domain, additional options are available through native means such as Group Policy for Windows machines.
Strategy utilizes Systems Configuration Console Manager (SCCM) clients for domain-joined Windows machines and Parallels Mac Management (PMM) agent for MacOS machines in order to deploy HyperIntelligence to different machines.
These options are utilized in order to track the progress of the installation, push a configuration, and determine during the installation process if the application is already installed by a user.
Note: PMM integrates into the SCCM management console providing a single pane of glass for configuration management across all our company’s assets. We deployed using the “task sequence” option in order to deploy a script to track the installation progress.
HyperIntelligence utilizes two different scripts to meet its requirements. For Windows machines, the script was created using Powershell, for MacOS machines, a bash script was created.
Both scripts work as follows:

To ensure all company assets received the deployment, the installation process is tracked and Strategy will follow up on machines that have returned any errors.
Google Chrome will keep the latest version of the extension installed. No further action is required.
Google has documented how Chrome can install extensions via their “Alternative Extension” options outlined here: https://developer.chrome.com/extensions/external_extensions
This method covers Group Policy and Registry entries for Windows and creating a special .JSON file for MacOS machines.
KB442620