The AirWatch Cloud Connector runs in the internal network. The connector serves as a proxy that securely transmits requests from Workspace ONE Express to the organization's critical enterprise infrastructure components.

It runs from within your internal network and allows you to benefit from Workspace ONE Mobile Device Management (MDM). AirWatch Cloud Connector works with your existing Active Directory (AD), Lightweight Directory Access Protocol (LDAP), email, and other internal systems.

While completion of the Express Setup configures the AirWatch Cloud Connector, refer to this section for information which has been designed for Workspace ONE Express. If you need further details about any specific AirWatch Cloud Connector element, consult the AirWatch Cloud Connector Documentation (available on docs.vmware.com) or contact Workspace ONE Support.

Prerequisites

Ensure that your system meets the necessary Hardware Requirements to deploy AirWatch Cloud Connector as part of a SaaS deployment.

  • Virtual Machine or Physical Server, one CPU Core, 2.0+ GHz, Intel processor required.
  • 2-GB RAM or more.
  • 6-GB disk space for the VMware Enterprise Systems Connector application, Windows OS, .NET runtime, and Workspace ONE Express logging operations.

Ensure the server running Workspace ONE Express meets the necessary Software Requirements.

  • Windows Server 2008 R2 SP1, Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019 Desktop Experience.
  • .NET Framework version 4.6.2.
    • The AirWatch Cloud Connector (ACC) auto-update feature does not function correctly until your ACC server is updated to .NET Framework 4.6.2.
    • The ACC auto-update feature does not update the .NET Framework automatically.
    • Install .NET 4.6.2 manually on the ACC server before performing an upgrade.

Ensure that the Network Requirements for the AirWatch Cloud Connector Server are met.

  • Workspace ONE Express Console (for example, https://cn274.awmdm.com)
    • Protocol: HTTP or HTTPS
    • Port: 80 or 443
    • Verify by entering https://cnXXX.awmdm.com and ensure that there is no certificate trust error.
    • Replace 'XXX' with the same number as used in your environment URL, for example, '100' for cn100.
    • If an auto-update is enabled, AirWatch Cloud Connector must query the Workspace ONE Express console for updates using port 443.
  • AirWatch API (for example, https://cn274.awmdm.com)
    • Protocol: HTTPS
    • Port: 443
    • Verify by entering https://asXXX.awmdm.com/api/help and ensure that you are prompted for credentials.
    • Replace 'XXX' with the same number as used in your environment URL, for example, '100' for cn100.
    • AirWatch Cloud Connector to API access is required for the proper functioning of the AirWatch Diagnostics service.
  • CRL (for example http://csc3-2010-crl.verisign.com/CSC3-2010.crl)
    • Protocol: HTTP
    • Port: 80
    • For various services to function properly.
  • Optional Network Requirements
    • Internal SMTP using port 25.
    • Internal LDAP under protocol LDAP or LDAPS using port 389, 636, 3268, or 3269.

Procedure

  1. Enable AirWatch Cloud Connector from the Workspace ONE Express Console.
    1. Generate certificates and select the enterprise services and Workspace ONE Express services to be integrated.
  2. Install the AirWatch Cloud Connector.
    1. Run the AirWatch Cloud Connector installer on your configured server that meets all the prerequisites.
  3. Verify a Successful AirWatch Cloud Connector Installation from within the console.