This Quick Start guide will help you to start using the blësk Asset Life Manager (ALM) after installing the blësk Network Monitoring system.
You can download the latest ALM Agent installer, available for 64-bit systems. It includes both a graphical interface and command-line tools for flexible usage. By default, the installer launches in graphical mode unless the msiexec /i and /quiet options are used for a silent installation. All available installer parameters are detailed below on this page.
By default, the installer will launch the graphical user interface unless it is executed from the command line using the /i and /quiet options.
C:\> msiexec /i GLPI-Agent-1.15-x64.msi /quiet NO_SSL_CHECK=1 RUNNOW=1 SERVER=<URL>/i Specify this is a normal installation. This is indeed a msiexec.exe option. When used with msiexec.exe, it must be used just before the MSI package path.
/quit Silent installation. This is indeed a msiexec.exe option. (By default: No). We require a silent installation.
NO_SSL_CHECK=1 Do not check server certificate. (By default: 0). Since we do not use a valid SSL certificate, we are skipping this step.
RUNNOW=1 Launches the agent immediately after its installation. (By default: 0). We want the agent to perform a local inventory scan immediately after installation.
SERVER=<URL> Sends results of tasks execution to given servers. Use the following URL: https://<IP>/glpi/plugins/glpiinventory/, where <IP> is the IP address of your blësk server.
When using command line parameters, you should keep in mind:
Parameters beginning with a slash are indeed msiexec.exe options,
Options names are case-sensitive,
Options values are not case-sensitive, unless specified,
The equal sign must not be preceded or followed with a space character: LOCAL = C:\temp is incorrect,
If a value contains a space, it must be surrounded with single ' or double quotes ",
If you want to set a empty value, put an empty string (LOCAL= or LOCAL="").
In environments where the ALM Agent must be deployed across a large and diverse set of Windows systems, a VBScript can be an effective solution to automate the process. The script can handle the following tasks:
Perform a silent installation, using predefined variables from a configuration script.
Detect and uninstall existing agents such as old version, if required.
Apply application settings via command-line parameters.
Log installation progress and errors for later review and troubleshooting.
To facilitate this deployment, a script named glpi-agent-deployment.vbs is provided and can be used to automate the rollout across the network.
This VBScript includes several configurable variables that can be adapted to your environment. Simply uncomment the lines you need, and comment out those you don’t.
SetupVersion
Define the version of the ALM Agent to be installed.
SetupLocation
Set the source path for downloading the MSI installer. This can be:
an HTTP/HTTPS URL (e.g., from the official GitHub release page)
a CIFS network share
a local directory
SetupArchitecture
Define the system architecture for the installer:
x86 for 32-bit
x64 for 64-bit
or leave it dynamic to auto-detect based on the system
Installation Options (Command Line Parameters)
It’s recommended to include /quiet to perform a silent installation without user interaction.
If you prefer to monitor each step, remove /quiet to allow installer windows to appear.
Reconfigure
Set to Yes to reapply configuration settings even if the same version is already installed.
Useful for changing settings like the ALM server URL without changing the agent version.
Repair
Re-registers the MSI service DLL and reinstalls the agent with the defined parameters.
Only works if the agent is currently installed.
Verbose
Enables detailed logging for troubleshooting. Set to True or False.
RunUninstall
Uncomment the lines related to FusionInventory Agent or OCS Inventory Agent if you want the script to automatically uninstall these older agents before installing ALM Agent.
Adding this VBScript to a Group Policy Object (GPO) as a startup script is generally the most effective approach, especially in environments where some users do not have installation privileges.
To ensure successful execution:
The MSI installer must be accessible to all target computers.
If you are using a network share (CIFS) or a public URL (e.g., GitHub Releases), verify that the systems can reach and download the file from the specified location.
Ensure appropriate network permissions and firewall rules are in place to allow access to the installer source.
Below are links to external references related to this software feature. These resources provide access to more detailed and advanced information on the topic.