This article outlines how to install the Arellia Management Server (AMS) when your target machine is not connected to the Internet.
The following steps require the use of PowerShell scripts, which are disabled in Windows Operating Systems by default. To enable PowerShell scripts, open an elevated PowerShell window and issue the command: Set-ExecutionPolicy RemoteSigned on both the Internet connected machine and your target AMS instance. (For more information on the Set-ExecutionPolicy cmdlet, go to the Technet KB article Using the Set-ExecutionPolicy Cmdlet.)
On a machine connected to the Internet
To download and install the AMS on a machine connected to the Internet, do the following steps:
- On a machine that is connected to the Internet, download the Create-AMSOfflinePackage.ps1 PowerShell script.
Run the script by right-clicking the context menu or using a PowerShell command window.
- Select the Release AMS Version and the New installation option. Optionally specify a different location for the package location.
- Click OK to start the offline package creation.
The script will create a directory in the location specified called AMS Offline Package which contains the necessary installation files.
On the Target AMS
To install on the target AMS machine, do the following steps:
- Copy the AMS Offline Package folder to your offline AMS instance.
Run the Install-AMSOfflinePackage.ps1 script located in the AMS Offline Package to install the AMS prerequisite components.
Note
During the installation you may be prompted to restart several times. This is expected behavior and the installation will automatically resume when you next log in.
- Once the machine has finished installing prerequisites run the Install-AMSOfflinePackage.ps1 script again to install the AMS.
- After the script has completed installing the bootstrap portion of the AMS, it will open a browser to http://localhost/Ams/Setup, at which point you can continue to install Arellia Solutions as normal.
After the AMS installation has completed you are free to delete the AMS Offline Package directory from your offline AMS instance.