« Back to myAirWatch

Install the Advanced Remote Management Server Components

After running the Configure portion of the Advanced Remote Management (ARM) installer, run the Install portion to install the components.

Prerequisites

Copy the install.config file created during the Configuration portion of the ARM onto the server hosting the ARM components. For more information, see Configure the Advanced Remote Management Installer.

Procedure

  1. On the server, extract the contents of the installer ZIP file into C:\temp.

    Important: Extract all contents from the ZIP file into c:\temp. Do not move the files around inside the temp folder as the installer needs all the files in their extracted locations. Do not rename or move the temp folder.

  2. Start the installer.
  3. Select Next.
  4. Select Install.
  5. Select the components you want to install on the server. If you are installing the Database component on a separate server, select only Database when selecting components.

    Install the following components on the same server.

    • Core Services
    • Portal Services
    • Application Services
    • Connection Proctor
  6. Select Next.
  7. If you are installing the database component, configure the Database Credentials settings.

    Setting Description
    SQL Database
    Server Name Enter the Database server hostname.
    Authentication Select the database account authentication. The authentication can be either Windows Authentication or SQL Authentication.
    User name Enter the user name of the database account. This user name is used by the installer to automatically create all the databases required to install Remote Management.
    Password Enter the password of the database account.
    Application Access
    Database Owner Password Set the password for the ARM database owner SQL account. This account does not have system-wide permissions. The account only has permissions within the ARM databases.
    Database User Password Set the password for the ARM database user SQL account. This account does not have system-wide permissions. The account only has permissions within the ARM databases.
  8. Select Next.
  9. If you are installing the remaining components, configure the Authentication Credentials.

    Setting Description
    Enrollment Certificate Details
    Enrollment Certificate Password Enter the password for the enrollment certificate added during the Configuration portion.
    Active Directory Authentication
    User name Enter the Active Directory user name.
    Password Enter the Active Directory password.
  10. Select Next.
  11. If you are installing the remaining components, configure the Portal Credentials.

    Setting Description
    SSL Certificate

    Select the ... Button to browse for the Site certificate installed before starting the Configuration portion. For more information, see Advanced Remote Management Requirements.

    SAN (subject alternative name) certificates are supported. The implementation of SAN certificates depends upon your server arrangement.

    • Single Node – The SAN certificate must define the FQDN for each public facing server/SSL termination point that hosts the solution.
    • Multi-Node – The SAN certificate must have an FQDN defined for each connection proctor server and advanced remote management server.
      • For example, presume you have 2 connection proctor servers and 2 advanced remote management servers. The 2 ARM servers host portal services, which need TLS/SSL traffic terminated at the load balancer. The FQDN for the SAN certificate must reflect the fully qualified domain name, for instance, "customerRM.awmdm.com'.
      • Meanwhile, for each of the 2 CP servers, TLS/SSL traffic terminates at the connection proctor, and therefore, you must have 2 FQDNs defined in the SAN certificate, for instance, "customerRMCP1.awmdm.com' and "customerRMCP2.awmdm.com'.
  12. Select Next.
  13. If you are installing the remaining components, configure the Connection Proctor Credentials.

    Setting Description
    CP Binding (Local) This setting is auto-populated.
    Port This setting is a verification which you can use to check for port 8446.
    CP FQDN Enter the server fully qualified domain name. For example, "<hostname>"
    Port Enter the actual port number used for the Connection Proctor component. Consider using 8446.
    CP certificate

    Select the ... Button to browse for the Site certificate installed before starting the Configuration portion. For more information, see Advanced Remote Management Requirements.

    This certificate is the same one used on the Authentication Credentials screen in the previous step.

  14. Select Next.
  15. Select OK to confirm that you have opened the firewall ports.
  16. After installation completes, select Close.