--- title: "Deploy update packages automatically with global updating" slug: "deploy-update-packages-automatically-with-global-updating" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:26Z published: 2026-09-07T17:46:26Z canonical: "docs.trellix.com/deploy-update-packages-automatically-with-global-updating" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploy update packages automatically with global updating You can enable global updating on the server to automatically deploy user-specified update packages to managed systems. For details about product features, usage, and best practices, click ? or Help. 1. Click **Menu** → **Configuration** → **Server Settings**, select **Global Updating**, then click **Edit** at the bottom of the page. 2. On the **Edit Global Updating** page next to **Status**, select **Enabled**. 3. Edit the **Randomization interval**, if wanted. Each client update occurs at a randomly selected time within the randomization interval, which helps distribute network load. The default is **20 minutes**. For example, if you update 1000 clients using the default randomization interval of 20 minutes, roughly 50 clients update each minute during the interval. This randomization lowers the load on your network and on your server. Without the randomization, all 1000 clients would try to update simultaneously. 4. Next to **Package types**, select which packages initiate an update. Global updating initiates an update only if new packages for the components specified here are checked in to the **Main Repository** or moved to another branch. Select these components carefully. - **Signatures and engines** — Select **Host Intrusion Prevention Content**, if needed. > [!NOTE] > Note > > Selecting a package type determines what initiates a global update (not what is updated during the global update process). Agents receive a list of updated packages during the global update process. The agents use this list to install only updates that are needed. For example, agents only update packages that have changed since the last update and not all packages if they have not changed. 5. When finished, click **Save**. Once enabled, global updating initiates an update the next time you check in any of the selected packages or move them to another branch. > [!NOTE] > Note > > Make sure to run a **Pull Now** task and schedule a recurring **Repository Pull** server task, when you are ready for the automatic updating to begin.