Prerequisites for ezdeploy Usage

Owned by Leigh Jones
Last updated: Mar 08, 2024
1 min read

  1. Antivirus Exclusions for target computers

    C:\EZdeploy\*.*
    folder and all contents

  2. If you have Active Malware Protection (like Cisco Meraki) covering target computers you will need to whitelist the following FQDNs:

    api.ezdeploy.io
    api2.ezdeploy.io

    Note: For use with OneTouch ppkg and WebStart msi files downloaded prior to ezdeploy rebrand - you will still need to have the following FQDNs as well:

    api.msptoolshed.com
    api2.msptoolshed.com

  3. If you are using ezdeploy integrations with services like ConnectWise Automate, ConnectWise Manage or Microsoft Teams and you have IP restrictions in place to access those services - you will need to allow traffic for the following Azure IP address over port HTTPS/443:

    172.169.203.251

    These IP’s cover our API and Portal, which is responsible for communicating with an integration for activities that happen in the UI or background operations in the cloud.

  4. If you are using Cisco Umbrella DNS, we suggest you add to the whitelist the above Integration IPs above, and require you add the following FQDN:

 

packages.chocolatey.org

When a machine deployment is running, the Agent Installation for RMM and other RMM API calls may occur from the machine itself and not from the ezdeploy API. In order for the product to work properly, deployments must be executed from a network location that can access your integrated products.

 

The content of this site is proprietary and confidential information of Stack Advisors, LLC. It is not intended to be distributed to any third party without the written consent of Stack Advisors, LLC.