HERMES Installation Guide

Applicable Versions: Alemba Service Manager HERMES, v10.6 and above

Alemba no longer provides a Patch MSI or Setup EXE file for install or upgrade.

We have found that this process is out of sync with current trends and maintaining these install tools is preventing improvements in the design, development, test, release, and maintenance processes.

We believe that ASM will be easier to install, own and operate without the old install process. ASM Gaia (v10.4) marks the last release which supports the old installation process.

ASM Eos (v10.5) and ASM Hermes (v10.6) is geared towards automated installation on cloud environments.

For On Premise Installations Alemba now provides an AlembaSetup.exe package that contains the installation files, please contact the Service Desk for more information.

If you currently have a version of ASM earlier than v10.5.1, ASM is going to be removed and reinstalled during the upgrade process.

Any screen designs used in this document are used to represent the solution and may differ from what is delivered.

Summary of the Automated Installation Process

Below are the steps the automated installer performs. If monitoring the installation, you will be able to follow along with this list. Space is available for you to take notes during the process.

Item #	Detail
1	Check for powershell 5 or later
2	Check current user is a member of the built in Administrator role
3	Find package.zip
4	Install Azure Platform Utilities if on Azure and that ASM KeyVault environment variable is set.
5	Validate install parameters. Parameters are gathered in the following order: from script arguments from Azure Key Vault secrets (if ASM KeyVault is set for the environment) environment variables (prefixed with ASM_) user input (if interactive)
6	Validate database connection string
7	Uninstall ASM Gaia or earlier
8	Disable Windows Defender Realtime monitoring
9	Extract files to ALEMBA_PATH\Staging
10	Stop ASM Services
11	Check if upgrade is supported Only if it’s a minor upgrade e.g. 10.6.5 to 10.6.6 If not, the existing version will be removed before the install continues
12	Install Prerequisites Windows Features .NET Core
13	Uninstall existing versions of ASM if necessary
14	Copy files for each system
15	Remove existing files (if necessary)
16	Copy new files
17	Update Registry
18	Configure IIS
19	Configure IIS and Registry for each system
20	Install ASM Services
21	Configure connection string and update database for each system
22	Start Services
23	Verify Installation using health status page
24	Restore Windows Defender Realtime monitoring
25	Reboot to complete install of prerequisites if required

Prerequisites Summary Checklist

• SQL 2019 - From EOS (10.5.X) , SQL 2019 or later is necessary if you wish to create a new database

• PowerShell >5.0

• User is Administrator

• Key Vault

• ADO net connection String

• Host Name

• System Name

• SSL Certificate (Required for ASM Application)

• Certificate Thumbprint

• Certificate Store Location

• Download Prerequisites

• License Key Text

• Ensure Outlook is not installed on the Application Server

• Minimum 8GB RAM, Recommended 16 GB RAM in Production Environments

SQL Server 2019

From EOS (10.5.X) , SQL 2019 or later is necessary if you wish to create a new database. You can check it by opening the Properties:

Go to Options and click on the Compatibility Level:

There should be a SQL Server 2019 option.

You need the Full Text feature on the SQL Server.

You must change the Database recovery mode from full to simple. Failing to do so will fill the transaction log and cause the database to sill up and run out of disk space.