Understand the behavior of the network, the types of communication, the communication channels between components, and license management. Review the considerations to avoid possible issues.

Important:

Do not send confidential packages with peer distribution. See the encryption section in this topic for information.

  • Common Network - The peer-to-peer server, the VMware Enterprise Systems Connector, and the peer-to-peer clients must all communicate on the same network. If these system components are on subnets of your network and the subnets can communicate, then the feature can transfer applications. Clients that are not on the network cannot receive applications with peer-to-peer distribution.

  • Encryption - Communication between the peer-to-peer server and AirWatch is encrypted. The communication is not encrypted between peer-to-peer clients in the network. This communication uses UDP but the package itself is not encrypted between clients. Although the system checks for tampered packages, a best practice is to not send confidential packages with peer-to-peer distribution.
  • UDP - The peer-to-peer server and client use UDP to communicate with AirWatch.

  • Central Office - The peer-to-peer server must reside in one of the subnets in the top-tiered Central Office.
  • License Overages - The peer-to-peer system does not stop you from assigning more licenses than you have bought. If you assign extra licenses, the system charges you for them.

    To help gauge license usage, the ratio of client installation to used license is one to one.

  • Open Ports - The peer-to-peer client needs specific ports open to transfer metadata. Find out if your network management team has closed the required ports or has blocked broadcasting on these ports. If these ports are closed or do not allow broadcasting, contact your VMware AirWatch representative about alternative ports. See Ports Used for Peer Distribution for information.
  • Console, Client, and Server Versions - You must deploy and use the supported version of the peer-to-peer client and the peer-to-peer server. Update the peer-to-peer server when the AirWatch Console includes an update to the peer-to-peer client. If the versions are not supported, the feature does not work.
  • SQL Server Express - Download and install SQL Server Express on the same server that has the VMware Enterprise Systems Connector. Install this component before configuring peer-to-peer setup because it might take some time to complete its installation.
  • Application Metadata - The peer-to-peer system stores and transmits the blob ID (or content ID), the application size, and the application hash. It does not store or transfer any other data.
  • Initial Downloads - The first download in a peer distribution process takes the longest time. After the initial downloads and as more devices in the subnet receive the application, download times get faster.
  • Activation Processes - After you save your configurations, the system activates the peer-to-peer server and clients with a license key. You can input your topology or use the one the network generates at activation. Also at the time of activation, the system publishes all the existing Win32 application content to the peer-to-peer server. From this point on, devices that belong to the peer distribution network begin to receive the application download.