--- title: "Evaluate new DATs and engines before distribution" slug: "evaluate-new-dats-and-engines-before-distribution" tags: ["Product Usage", "ePolicy Orchestrator – On-prem", "ePO 5.10.x", "ePO 5.10.0"] updated: 2026-09-07T17:46:49Z published: 2026-09-07T17:46:49Z canonical: "docs.trellix.com/evaluate-new-dats-and-engines-before-distribution" --- > ## 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. # Evaluate new DATs and engines before distribution You might want to test DAT and engine files on a few systems before deploying them to your entire organization. You can test update packages using the **Evaluation** branch of your Main Repository. The ePO - On-prem software provides three repository branches for this purpose. For details about product features, usage, and best practices, click ? or Help. 1. Create a scheduled Repository Pull task that copies update packages in the **Evaluation** branch of your Main Repository. Schedule it to run after Trellix releases updated DAT files. 2. Create or select an evaluation group in the **System Tree**, then create a Trellix Agent policy for the systems to use only the **Evaluation** branch. The policies take effect the next time the Trellix Agent calls into the server. The next time the agent updates, it retrieves them from the **Evaluation** branch. 1. Select the **Evaluation** branch on the **Updates** tab in the **Repository Branch Update Selection** section. 3. Create a scheduled update client task for the evaluation systems that updates DAT and engine files from the **Evaluation** branch of your repository. Schedule it to run one or two hours after your Repository Pull task is scheduled to begin. The evaluation update task created at the evaluation group level causes it to run only for that group. 4. Monitor the systems in your evaluation group until satisfied. 5. Move the packages from the **Evaluation** branch to the **Current** branch of your Main Repository. Select **Menu** → **Software** → **Main Repository** to open the **Main Repository** page. Adding them to the **Current** branch makes them available to your production environment. The next time any client task retrieves packages from the **Current** branch, the new DAT and engine files are distributed to systems that use the task.