This article takes you through the process for installing Monitor on Windows devices with ARM processors.
Before you begin
Ensure you have the following installation requirements.
- At least Windows 11.
- Copy your Unique Organisation ID and UNCL Serial ID from Monitor > Organisation (select Edit) > License information.
- Download the Monitor installer sw-safeguarding-client-arm64-2.10.1.msi from Monitor > Organisation (select Edit) > Clients.
Install Monitor
You can install Monitor using one of two methods:
- Silent installation using a command line
- Push-installation using Active Directory Group Policy Object (GPO)
Option 1: Perform a silent install using the command line
-
Create a script with the following command line:
msiexec /i path-to-installer ORGID=orgid SERIALID=serialid PROXY=proxy:port ENABLEAZUREAD=#0 /qn
Where:
- path_to_installer is the full network path to the downloaded installation program.
- orgid is the unique ID provided for your organization.
- serialid is the unique serial number for your organization, this must start UNCL and have no spaces
- proxy (optional) is your organization proxy setting. Monitor uses device settings if you don’t provide this. If the proxy connection fails, Monitor attempts to connect directly.
- ENABLEAZUREAD (optional) and is only supported on version 2.5.0 onwards. Set the value to "#1" if users login with Azure Active Directory credentials. This will enable the correct username/domain to be detected. If you set the value to "#0" or omit the option, then conventional (on-prem) Active Directory will be used instead.
Example:
msiexec /i \\mynetworkdrive\downloads\sw-safeguarding-client-arm64-2.10.1.msi ORGID=123456789 SERIALID=UNCL1234 /qn
-
You can modify these values after installation by editing the registry
stored
in the following locations:
- Version 2.0.0:HKEY_LOCAL_MACHINE\SOFTWARE\Smoothwall
- Version 2.1.0 and laterHKEY_LOCAL_MACHINE\SOFTWARE\Smoothwall\Safeguarding Client
Option 2: Create an Active Directory GPO
- Use a GPO to create an unattended installation of Monitor on Windows devices with ARM processors in your network.
- Create a GPO policy that deploys the MSI client.
-
Configure the following registry settings. Note that the settings differ whether you are using MSI version 2.0.x or 2.1.x+
Note
For detailed instructions on setting up a GPO, consult your Active Directory documentation.
For MSI version 2.1.x
| Value Name | Value Type | Value Data |
|---|---|---|
| Hive Path | Key Path | HKEY_LOCAL_MACHINE\SOFTWARE\Smoothwall\Safeguarding Client |
| OrgID | Reg_SZ | Your organisation’s OrgID |
| SerialId | REG_SZ | Your organisation’s UNCL serial ID |
| ProxyServer | REG_SZ |
Your organization proxy setting. Enter the value in this format: ip.or.host:port This field is optional. If no proxy is provided, Monitor MS will use the device settings. If connections using the proxy settings fail, Monitor MS will attempt to connect directly. |
| EnableAzureAd | REG_DWORD |
Version 2.5.0 onwards only. This indicates if your organisation uses Azure Active Directory to authenticate users. Set it to 1 if you use Azure AD or 0 if not. It defaults to 0 if the value is omitted. Warning |
For customers with Organisation ID: Install Monitor Legacy Client version 1.x
Customers with only Organisation IDs need to install the legacy Version 1.x installer until they upgrade to the UNCL serial ID system. Contact our Support Team to get a copy of the Version 1.x installer.
There are two options for installing Version 1.x of Monitor.
Option 1: Create a silent install using a command line
Create a script to perform an unattended installation on all network devices:
msiexec /i "path-to-installer" ORGID="orgid" PROXY="proxy:port" /qn
Where:
- path_to_installer is the full network path to the location of the relevant downloaded installation program.
- orgid is the unique ID provided for your organization.
- proxy is your organization proxy setting. This is OPTIONAL. If you don't provide a proxy, Monitor uses the device settings. If a connection using the proxy settings fails, Monitor attempts to connect directly.
Example:
msiexec /i \\mynetworkdrive\downloads\sw-safeguarding-client-arm64-2.10.1.msi ORGID=123456789 /qn
Option 2: Create an Active Directory group policy object (GPO)
Using an Active Directory Group Policy Object (GPO), you can create an unattended installation to push the Monitor MS Client out to all network devices. For a detailed description of how to set up such a GPO, refer to your Active Directory documentation.
- Create a GPO policy that deploys the sw-safeguarding-client-arm64-2.10.1.msi installer for Windows 64-bit.
- Configure the registry settings:
Value Name |
Value Type |
Value Data |
|---|---|---|
| Hive Name | Key Path | HKEY_LOCAL_MACHINE\SOFTWARE\Smoothwall\Safeguarding Client |
| OrgID | REG_SZ | Your organisation's unique ID |
| ProxyServer | REG_SZ |
(Optional) Your organisation proxy setting. If no proxy is provided, Monitor will use the device settings. If the connection using the proxy settings fails Monitor MS will attempt to connect directly. Format is ip.or.host:port |