Meet the minimum requirements to ensure a successful installation.

Hardware Requirements

Requirement CPU Cores RAM (GB) Disk Space Notes

VM or Physical Server (64-bit)

2 CPU Core (2.0+GHz)

4 GB+ 20+ GB Sizing is an estimate and may vary based on your concurrent usage. Consider adding more resources or servers when CPU, RAM, or I/O utilization approaches 70-80%.
Sizing Recommendations
Number of Devices 1-1,000 1,000-5,000 5,000-25,000 25,000+

CPU Cores

 

 

2

 

 

4-8 or 2 load-balanced servers w/ 2 CPU cores

 

2 load-balanced servers w/8 CPU cores or 4 load-balanced w/ 4 CPU cores 4-8+ load-balanced servers with 4-8 CPU cores

RAM (GB)

4 8-16 total 16-32 total 32+ total

General Requirements

Requirements Notes

Internally registered DNS record

Register the Endpoint server.

Required for Standalone RFS and RFS with Content Gateway.

Externally registered DNS record

Required for Standalone RFS only.

SSL Certificate from trusted third party with subject name of server hostname

Requires a PKCS12 (.pfx) format and the trust of all device types in use. Keep in mind:

  • Android does not natively trust all Comodo certificates.
  • PKCS12 (.pfx) format includes the server certificate, private key, root chain, and password protection.
Dedicated storage location that supports NFS or CIFS

Serves as the location where RFS stores files.

Enable Multi-casting Recommended, not required. Multi-casting is a network protocol that allows RFS servers to detect and communicate with one another.

Software Requirements

Windows Requirements
Requirement Notes

Windows Server 2008 R2, 2012 or 2012 R2; 64-bit

Basic infrastructure type recommended.

Remote access to Windows servers

AirWatch recommends setting up Remote Desktop Connection Manager. Download the installer from: 

https://www.microsoft.com/en-us/download/details.aspx?id=44989

Admin Privileges

Ensure your admin permissions allow you to run the installer, create services, manage services, install features, create folders, and run processes.

Notepad++ (Recommended)

AirWatch recommends setting up Notepad++.

IIS 443 bound with SSL certificate

Validate that you can connect to the server over HTTPS (https://<yourAirWatchDomain>.com). At this point, you should see the IIS splash page.

Role from Server Manager installed

IIS 7.0 (Server 2008 R2)

IIS 8.0 (Server 2012 or Server 2012 R2)

IIS 8.5 (Server 2012 R2 only)

.NET Framework 4.6.2

The installer will install this version of .NET provided the server has Internet access. Otherwise, download and manually install it.

Requirement Notes

SSH access to Linux Servers and an admin account with full write permissions.

Root permissions, or sudo access with the same privileges as root required. Once installation completes, you can put restrictions into place for these account types.

yum Enabled

Enable to allow the installer to request and install any missing prerequisites.

CentOS 7.x

SUSE 12.x

RHEL 7.x

UI-less recommended.

Basic infrastructure type recommended.

Remove Java from server prior to install. Java packaged with installer.

Network Requirements

For configuring the ports listed below, all traffic is uni-directional (outbound) from the source component to the destination component.

Standalone RFS Network Requirements

Source Component Destination Component Protocol Port Configurable Notes

AirWatch Console & DS Server

RFS Server

HTTPS

443

Yes

Post-installation, activate RFS in the AirWatch Console to verify connectivity.

Devices (from Internet and Wi-Fi)

RFS Server

HTTPS 443 Yes

Post-installation, use health API's to verify endpoint availability.

RFS Server Other RFS Servers in cluster TCP

5701, 5702

Yes

Installing files and tokens on the same server opens two Hazelcast ports. Hazelcast opens the port 5701 by default, and follows this +1 naming convention for all subsequent ports. Post-installation, use diagnostic endpoints to verify availability.

RFS Server

NFS storage component

-OR-

CIFS storage component

TCP/UDP 2049, 111 No

Required if using a NFS share. Prior to installation, verify ports.

TCP 137-139, 445 No

Required if using a CIFS share. Prior to installation, verify ports.

 

RFS Behind Content Gateway Network Requirements

Source Component Destination Component Protocol Port Configurable Notes
Content Gateway Endpoint RFS Server HTTPS/HTTP

443,

80

Yes  
RFS Server Other RFS Servers in cluster TCP

5701, 5702

Yes

Installing files and tokens on the same server opens two Hazelcast ports. Hazelcast opens the port 5701 by default, and follows this +1 naming convention for all subsequent ports. Post-installation, use diagnostic endpoints to verify availability.

RFS Server

NFS storage component

-OR-

CIFS storage component

TCP/UDP 2049, 111 No

Required if using a NFS share. Prior to installation, verify ports.

TCP 137-139, 445 No

Required if using a CIFS share. Prior to installation, verify ports.