Update Automation 360 on Microsoft Windows Server using scripts

Update Automation 360 using a customized script with parameters to maintain existing user configurations.

Prerequisites

To perform the task, you must have a Control Room administrator account with the required rights and permissions.

Verify Automation 360 On-Premises prerequisites.
Ensure that you have the following:
- Automation Anywhere Control Room installation file
- TLS certificate
- License file

Sample config.properties file: For your reference, you can find a sample config.properties file at the end of the page.

Note: For instructions on performing silent install and configuration of Automation 360 separately, see .Silent installation and configuration of Automation 360 using scripts (A-People login required.

Create and run a PowerShell script to update Automation 360.

Procedure

Create a PowerShell script with the required parameters:

The following is a sample PowerShell script for upgrading Automation 360:

# Script Begins
# It fetches Data from config.properties file present under the same directory level

$PropertyFilePath = 'C:\script\config.properties'
$rawProperties = cat $PropertyFilePath
$propertiesToConvert = ($rawProperties -replace '\\' ,'\\') -join
[Environment]:: NewLine;
$properties=ConvertFrom-StringData $propertiesToConvert
$env:SEE_MASK_NOZONECHECKS = 1

# Setting up the logger and InstallerRoot Directory

$baseLogFilePath=$properties.baseLoggingDirectory
$logFilePath=$baseLogFilePath+'Express_CR_Installation_Scenario1.txt'
$baseInstallerPath=$properties.baseInstallerDirectory
$installer_name_regex=$properties.installerNameRegex

# Logging Begins

Start-Transcript -Path $logFilePath -Append -IncludeInvocationHeader

$binary = Get-ChildItem $baseInstallerPath | Where-Object { $_.FullName -imatch $installer_name_regex }
$a = $binary.FullName
$final_commandline = " /update /s /v/qn /v""/L*v CR_Onprem_Installationlog_Scenario1.txt"""

# Recording the Start Time
Get-Date -Format g

# Invoking the Installer here
$processdetail = (Start-Process -FilePath $a -ArgumentList $final_commandline -Wait -Passthru).ExitCode

# Recording the End  Time
Get-Date -Format g


Stop-Transcript

Optional: Customize the script to include parameters according to your requirements.
Save the script to the installation server.
Log in to the installation server as administrator.
Start PowerShell in administrator mode.
Run the following:
Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force

.\install.ps1

Note: The silent installation logs are stored in the folder from which the installation script is run. For example, if you run the script from C:\Silent Install, the logs are stored in the C:\Silent Install folder.
Validate the following:
- All Automation Anywhere services are running in Windows Task Manager.
  Verifying Automation Anywhere services
- You are able to log in to the Control Room from a supported browser.
  Log in to Automation Anywhere Control Room
- You are able to install the required license in the Control Room.
  Installing additional licenses
- All automations (deployed and scheduled) are running in the Control Room.
  Activities

Example of config.properties file

# Properties utilized across all Scenarios

# Default/Express Mode Params

baseLoggingDirectory=C:\script\logs\
baseInstallerDirectory=C:\script\
installerNameRegex=AutomationAnywhereEnterprise_A2019