« Back to myAirWatch

Advanced Remote Management Requirements

You must meet the listed requirements before using Advanced Remote Management (ARM).

General Requirements

For SaaS customers, the general requirements are the only requirements that must be met.

The ARM requires the following on the admin side.

Requirements Minimum
Supported Browsers Latest version of Google Chrome, Safari, Internet Explorer, or Edge.
AirWatch version

AirWatch v9.0.2+ with the AirWatch Rugged EMM Bundle.

Ensure that your version of AirWatch includes these features by contacting your account representative.

Active Directory Requirements

ARM requires specific Active Directory users and groups.

Requirement Description
AD Group

Create an Active Directory group.

Portal Admin User

Create a user with the following settings.

  • First name: Portal.
  • Last name: Admin.
  • Full name: PortalAdmin.
  • User login name: PortalAdmin.
  • Create a password that the user cannot change and which does not expire.
  • Add this user to the previously created AD Group.
T10 Interface User

The T10 Interface User is created by the installer.

Hardware Requirements

Hardware Minimum
Remote Management Server
CPUs 2.4 GHz Processors, 4 Logical Processors,
2 CPU 2 Core 2x2 or 4 Physical depending on machine type VM vs Physical.
Memory 16 GB
Hard Drive IOPS 15,000 SAS minimum
Hard Drive Space 100 GB for OS drive
Remote Management Database
Hard Drive Space

200 GB for databases
200 GB for backups and logs

Remote Device Maximum
Given a single server deployment with the above minimum specifications, the maximum number of concurrent remote device sessions is 250.

Software Requirements

Ensure that you meet the following on-premises installation requirements.

To ensure proper configuration of the roles and features, use the ARM installation PowerShell scripts. For more information, see Advanced Remote Management Server Installation PowerShell Scripts.

Requirements  
Remote Management Server
Operating System Microsoft Windows 2012 R2.
Software

Microsoft .NET Framework 4.6.2

Microsoft Report Viewer 2010 Redistributable Package.

Multi-Node Configuration: the Microsoft Report Viewer 2010 Redistributable Package must be included where Portal Services are installed.

Server Roles
  • Application Server.

  • Web Server IIS.

To ensure proper configuration of the roles and features, use the ARM installation PowerShell scripts. For more information, see Advanced Remote Management Server Installation PowerShell Scripts.

Features
  • .NET Framework 3.5 Features.
    • .NET Framework 3.5 (includes .NET 2.0 and 3.0).

    • HTTP Activation.

    • Non-HTTP Activation.

    • IIS Management Console.

  • .NET Framework 4.5 Features.
    • .NET Framework 4.5.
    • ASP .NET 4.5.
    • WCF Services.
      • HTTP Activation.

      • Message Queuing (MSMQ) Activation.

      • Named Pipe Activation.

      • TCP Activation.

      • TCP Port Sharing.

  • Message Queuing Services.
  • Windows Process Activation Service.
    • Process Model.
    • .NET Environment 3.5.
    • Configuration APIs.
Remote Management Database
Operating System
  • Microsoft Windows 2012 R2.
  • MS SQL Server 2012 Standard, or
    MS SQL Server 2014 Standard, or
    MS SQL Server 2014 Enterprise.
  • MS SQL Management Studio 2012.
  • Microsoft .Net Framework 4.6.2.
  • Microsoft SQL Server Management Objects (SMO) DLL.
Server Roles
  • Sysadmin
  • Bulkadmin.
  • Dbcreator.
User Mapping
  • Dbowner.
  • Dbbackupoperator.
  • SQLAgent dependent.
  • serverGroup dependent.

Network Requirements

Source Component

Destination Component

Protocol

Port

AirWatch Console ARM Server TCP 443
End-User Devices ARM Server TCP 443, 8446
Console User ARM Server TCP 443
Remote Management Server ARM Database TCP 1433
Remote Management Server Active Directory TCP 53, 389, 636
Remote Management Server

ARM Server

Note: these ports are internal and within the RMS for service-to-service communication.

Multi-Node Configuration: Install Application/Core Components on a different server than the Portal Server/Connection Proctor Server.

TCP 80, 636, 8865, 8866, 8867, 8870, 12780

 

Domain Name Service

The ARM server requires a forward lookup zone and three DNS records within the forward lookup zone. These records enable devices to communicate properly with the components within the ARM server. The forward lookup zone, the host record, and service records all must point to the ARM server.

Consider using the PowerShell Script for creating controlplane Forward Lookup Zone. For more information, see Advanced Remote Management Server Installation PowerShell Scripts.

Requirement Description
Forward Lookup Zone

Create a forward lookup zone that points to your ARM server.

The forward lookup zone must be named.

controlplane.aetherpal.internal
Host Record

The host record must be named the following.

admin.  
  • If the ARM Server is behind a load balancer, then the host record must point to the internal virtual IP (VIP) for the load balanced pool.
  • If the ARM server is not behind a load balancer, then create a host record in your DNS that points to your ARM Server IP address.
Service Coordinator Service Records
  • Record type: SRV.

  • Domain: controlplane.aetherpal.internal

  • Service: _svc.

  • Protocol: _tcp.

  • Priority: 0
  • Weight: 0
  • Port number: 8870
  • Host Offering this service: admin.controlplane.aetherpal.internal
Data Tier Proxy Service Record
  • Record type: SRV.

  • Domain: controlplane.aetherpal.internal

  • Service: _dtp.

  • Protocol: _tcp.

  • Priority: 0.

  • Weight: 0.

  • Port number: 8865.

  • Host Offering this service: admin.controlplane.aetherpal.internal