Silent Enterprise Control Room installation, also known as unattended installation, uses a customized script for a full setup or the command line for a hot fix patch. Silent install runs the entire installation process in the background without requiring user interaction or displaying messages.

1. Review the parameters and identify the settings you require.

   Enterprise Control Room installation parameters
   Variable Name	Description
   AA_CRCLUSTERCONFIG	if AA_SETCLUSTERMODE=1 then cluster IP comma separated
   AA_CRDBPORT	Enterprise Control Room database port. Default value is 1433
   AA_CRDBSSLMODE	Secure SQL Connection
   AA_CRFORCEHTTPSCONFIG=" "	-
   AA_CRFORCETOHTTPS="1"	Force traefik from HTTP to HTTPS
   AA_CRHTTPPORT	CR HTTP port. Default is 5432
   AA_CRHTTPSPORT	CR HTTPS port
   AA_CRLISTENPORT	Web server port. Default value is 80
   AA_CRSERVICECONFIRMPASSWD	if AA_CRSETLOCALSERVICECRED= 0 then confirm password
   AA_CRSERVICEPASSWD	if AA_CRSETLOCALSERVICECRED= 0 then password
   AA_CRSERVICEUSERNAME	if AA_CRSETLOCALSERVICECRED= 0 then domain\user name
   AA_CRSETLOCALSERVICECRED	1 if service logon as System 0 if service logon as specific user
   AA_CRWCCERTPASSWD	Certificate password
   AA_CRWCCERTPATH	Certificate path
   AA_SDSFEATURE	true=Cloud deployment type false=OnPremises deployment type
   AA_SETCLUSTERMODE	For cluster set 1 else 0
   AA_SETUPTYPE	Setup type Custom or Express
   INSTALLDIR	Installation Directory
   IS_SQLSERVER_AUTHENTICATION	0 for Windows authentication
   IS_SQLSERVER_DATABASE	SQL Database name
   IS_SQLSERVER_SERVER	SQL server name (host name)
   Elasticsearch Related Parameters
   AA_ELASTICSEARCHSYSIP	valid IP

2. Option: Edit the sample script to use an Microsoft SQL Server database.
   Use the script to install the Enterprise Control Room with the configuration options available in the installer.
   1. Correct values for variables such as: $service_username, $service_pwd, $db_server, $cr_port.
   2. Run the script with a Credentials in Service logon, and a non-secure connection using Microsoft SQL Server authentication with a new database.
   Sample script:

   $cr_port=80
   
   $service_username= "domain\username" #e.g."aaspl-brd\ellie.brown"
   $service_pwd="password"
   
   #$certpath = "C:\SilentInstall\test256.pfx"
   #$certpass = "changeit"
   
   $db_server="localhost"
   $cr_db_name="CRDB-NEW-SI-3"
   $db_user="sa"
   $db_pwd="Admin@123"
   
   
   
   $installation_path="C:\Program Files\Automation Anywhere"
   
   #Install latest setup
   $static_installation_path="\Enterprise\"""""
   $silent_details=" /s ","v""" -join "/"
   $installpath_details= 
   	"/qn INSTALLDIR=\"""
   
   $deployment_details=
           " /AA_SDSFEATURE=true"
   
   $custom_details=
   	" /vAA_SETUPTYPE=Custom 
   	/vAA_CUSTOMMODETYPE=1"
   
   $port_cluster_details=
   	" /vAA_SETCLUSTERMODE=0 
   	/vAA_CRLISTENPORT=$cr_port"
   
   #$service_details=
   	" /vAA_CRSETLOCALSERVICECRED=0 
   	/vAA_CRSERVICEUSERNAME=$service_username 
   	/vAA_CRSERVICEPASSWD=$service_pwd 
   	/vAA_CRSERVICECONFIRMPASSWD=$service_pwd"
   
   $service_details=
   	" /vAA_CRSETLOCALSERVICECRED=1"
   
   #$db_details=
   	" /vAA_BIMETADATADBTYPE=AA_BIMETADATADBTYPE 
   	/vIS_SQLSERVER_SERVER=$db_server 
   	/vIS_SQLSERVER_DATABASE=$cr_db_name 
   	/vIS_SQLSERVER_DATABASE1=$bi_db_name"
   
   $db_details=
   	" 
   	/vIS_SQLSERVER_SERVER=$db_server 
   	/vIS_SQLSERVER_USERNAME=$db_user 
   	/vIS_SQLSERVER_PASSWORD=$db_pwd 
   	/vIS_SQLSERVER_DATABASE=$cr_db_name 
   	/vIS_SQLSERVER_AUTHENTICATION=1 
   	
   
   $other=
   	"
          /vAA_CRWCHTTPPORT=80 
   	/vAA_CRWCHTTPSPORT=443 
   	/vAA_CRSELFSIGNCERT=1 
   	/vAA_OPTIONALCACERT=0 
   	/vAA_CRWCCERTPATH=$certpath 
   	/vAA_CRWCCERTPASSWD=$certpass 	
   	/vLAUNCHPROGRAM=1 
   	/v""
   	/LIweamoruc! log.txt"""
   
   $final_commandline = -join($silent_details,
   	$installpath_details,$installation_path,
   	$static_installation_path,$custom_details,
   	$port_cluster_details,$service_details,
   	$db_details,$pg_details,$other)
   
   Write-Host $final_commandline
   $a=Get-ChildItem $PSScriptRoot\* -Include *.exe
   #$a = "C:\Silent\AutomationAnywhereEnterprise_A2019_<build>.exe"
   
   Write-Host $a
   Write-Host "Starting the installation wait for sometime..."
   
   $processdetail=(Start-Process -FilePath 
   	$a -ArgumentList $final_commandline 
   	 -Wait -PassThru).ExitCode
   
   Write-Host $a.Name execution is done. 
   If installation is not proper check msi logs in the temp folder.
   pause

3. Save the script you edit to the server for installation.
4. On the installation server, logged on as an Administrator, open Powershell in admin mode and execute:
   Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force
5. Start Powershell in admin mode and execute:
   .\install.ps1

   Note: The silent install logs are stored in the folder from which the install script is executed. For example, if you run the script from C:\Silent Install, the logs are stored in C:\Silent Install folder.