--- title: "Pull content automatically: best practice" slug: "pull-content-automatically-best-practice" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:45:37Z published: 2026-09-07T17:45:37Z canonical: "docs.trellix.com/pull-content-automatically-best-practice" --- > ## 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. # Pull content automatically: best practice Pull the Trellix content from the public Trellix servers. This pull task keeps your protection signatures up to date. You must schedule your pull tasks to run at least once a day after 3 p.m. Eastern Time (19:00 UTC or GMT). In the following example, the pull is scheduled for twice daily, and if there is a network problem at 5 p.m., the task occurs again at 6 p.m.. Some users like to pull their updates more frequently, as often as every 15 minutes. Pulling DATs frequently is aggressive and unnecessary because DAT files are typically released only once a day. Pulling two or three times a day is adequate. > [!NOTE] > Note > > Testing your DAT files before deployment requires a predictable pull schedule. For details about product features, usage, and best practices, click ? or Help. 1. Select **Menu** → **Automation** → **Server Tasks**, then click **Actions** → **New task**. 2. In the **Server Task Builder** dialog box, type a task name and click **Next**. 3. Specify which signatures to include in the pull task. > [!TIP] > Tip > > **Best practice:** When you create a pull task for content, select only the packages that apply to your environment instead of selecting **All packages**. This keeps the size of your **Main Repository** manageable. It also reduces the bandwidth used during the pull from the Trellix website and during replication to your distributed repositories. 1. In the **Actions** dialog box, from the **Actions** list, select **Repository Pull**, then click **Selected packages**. 2. Select the signatures that apply to your environment. 4. Click **Next**. 5. Schedule your pull task to run at least once a day after 3 p.m. Eastern Time, then click **Next**. 6. Click the **Summary** tab, confirm that the server task settings are correct, then click **Save**. Now you have created a server task that automatically pulls the Trellix DAT files and content from the public Trellix servers.