Product Deployment
Last updated
Last updated
ePO simplifies the process of deploying security products to the managed systems in your network, by providing a user interface to configure and schedule deployments.
There are three processes you can follow to deploy products using ePO.
The Product Deployment page is a single location, where you can create, monitor, and manage your product deployment projects.
Click on the information (i) icons to view additional information about each main part of the page.
Continuous deployments use System Tree groups or tags for the systems, which allows you to move systems to those groups or assign system tags, applying the deployment to those systems.
There is no limit to number of systems selected for a continuous deployment but be mindful of any bandwidth, implications with scheduling, etc.
Fixed deployments use a fixed or defined set of systems. System selection is done using your System Tree or Managed Systems Query output tables.
Limited to 500 systems in a Product Deployment Project. If more than 500 systems are selected, you will be prompted to select few systems.
Audit logs from your deployment projects contain records of all product deployments made from the console, using the Product Deployment feature.
These audit log entries are displayed in a sortable table within the Deployment details area of the Product Deployment page, as well as on the Audit Log page, which contains log entries from all auditable user actions. You can use these logs to track, create, edit, duplicate, delete, and uninstall product deployments. Click a log entry to display entry details.
Another way to deploy software products is using the Client Task Catalog.
Assigned at any level in the System Tree
Inherited by groups and systems lower in the tree
Allows inheritance to be broken
Can be shared across multiple registered ePO servers
Must be assigned to managed systems
Can be scheduled to run or run immediately
Product Deployment client tasks deploy products to your managed systems from the Main Repository. Product Update client tasks control when and how managed systems receive updates when global updating is not used. If you are not using global updating, client update tasks is the only way you can control client updating with ePO software.
You can also create a deployment task from the Main Repository as shown below. Click the Create Deployment Task button to create a task.
Typically, ePO Cloud administrators create an installation URL that can be used to install Endpoint Security Client on managed systems. They can:
Use this URL to install the client software locally on their own system.
send this URL to users, with instructions for installing the client software on their local systems.
From the ePO console, select Menu > Dashboards, then select Getting Started with ePolicy Orchestrator from the drop-down list.
The products in the Main Repository, available to install on managed systems, are listed under My Products.
Click the Customize Installation button and complete the required information.
Client Task Management