NOTE: The Action1 agents now communicate with Action1 servers primarily over port 443, which is open by default in most enterprise environments. The agent first attempts to connect via port 443, and if that connection fails, it automatically falls back to port 22543.

NOTE: If the inbound communication between agents on the local network is not allowed, the agents will not be exchanging downloaded app pieces locally and will always download in full from the cloud.

NOTE: The Action1 agents communicate with Action1 Remote Desktop relay servers primarily over port 443, which is open by default in most enterprise environments. The agent first attempts to connect via port 443, and if that connection fails, it automatically falls back to port 22543.

NOTE: If you are using a proxy or security appliance that performs TLS/SSL inspection, exclude the outbound traffic from the Action1 agent to the Action1 Desktop Relay server from TLS/SSL inspection. Otherwise, the connection may experience latency. See TLS Inspection for details.

NOTE: * (asterisk sign) in DNS names means including all child subdomains, with multi-level nesting. For example,  *.example.com would include example.com, child.example.com, grand.child.example.com, and all other possible subdomains.

NOTE: To prevent software package downloads from failing when using a proxy appliance (such as Zscaler and Cisco Umbrella), you may need to exclude the outbound traffic from TLS/SSL inspection. See TLS Inspection for details.

NOTE: Action1 Deployer communicates with Action1 servers primarily over port 443, which is open by default in most enterprise environments. It first attempts to connect via port 443, and if that connection fails, it automatically falls back to port 22543.

NOTE: Action1 agents receive macOS system updates by means of the native Software Update utility that uses the connections listed above.

NOTE: To prevent software package downloads from failing when using a proxy appliance (such as Zscaler and Cisco Umbrella), you may need to exclude the outbound traffic from TLS/SSL inspection. See TLS Inspection for details.

NOTE: Linux app packages are installed from the online repository using an Action1 script that utilizes the native package manager. For details, see Deploy Software.