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

  1. Select Install to install the server components after the configuration has completed.
  2. Select all components to install on the server.

    • Database
      • The database component is installed remotely based on the hostname and credentials previously configured in Step 5 of the Configure the ARM Installer task.
    • Core Services
    • Portal Services
    • Application Services
    • Connection Proctor
  3. Select Next.
  4. 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 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.
  5. Select Next.
  6. Configure the Authentication Credentials settings.

    Setting Description
    Enrollment Certificate Details
    Enrollment Certificate Password Enter the password for the enrollment certificate added during the Configuration portion.
  7. Select Next.
  8. Configure the Portal Credentials settings.

    Setting Description
    SSL Certificate

    Select the ... button to browse for the SSL Certificate installed before starting the Configuration portion.

    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, "rmstage01.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, "rmstage01.awmdm.com' and "rmstage02.awmdm.com'.
  9. Select Next.
  10. Configure the Connection Proctor Credentials settings.

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

    Select the ... button to browse for the SSL Certificate installed before starting the Configuration portion.

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

  11. If you are configuring a single server solution where the database is installed separately, you must deselect the "Controlplane.aetherpal.internal" check box in the more options ( ...) in the Connection Proctor screen. Skip this step if you are configuring a multi-server solution.
  12. Select Next.
  13. Select OK to confirm that you have opened the firewall ports.
  14. Select Next. The Execute Resource pack check box option appears. Make sure that this checkbox has been enabled.
  15. Select Finish. The resource pack is then imported automatically.

Next, proceed to Configure the Workspace ONE ™ UEM console.