Upgrading Trellix ePolicy Orchestrator (ePO) from version 5.9 to 5.10 is a critical step for organizations looking to stay secure, supported, and aligned with modern endpoint management requirements. While the upgrade process itself is well-documented, many administrators encounter upgrade failures due to SQL Server database configuration issues, particularly a misconfigured Auto Close setting.
This guide explains the most common and proven issue that causes ePO 5.9 to 5.10 upgrade failures, how to fix it safely, and the best practices you should follow to ensure a smooth, rollback-free upgrade.
Why Upgrade to Trellix ePO 5.10?
Upgrading from ePO 5.9 to 5.10 is strongly recommended because:
- ePO 5.10 introduces improved performance and scalability
- It offers better compatibility with newer Trellix endpoint products
- Older versions like 5.9 approach or reach end-of-support
- Security patches and hotfixes are no longer released for outdated builds
However, before starting the upgrade, database readiness is non-negotiable.
The Most Common Upgrade Problem From ePO 5.9 to 5.10
SQL Server “Auto Close” Option Enabled
The single most common and confirmed cause of failed upgrades from ePO 5.9 to 5.10 is when the SQL Server database has the Auto Close option set to True.
How to Fix the Auto Close Issue Before Upgrading ePO
You must disable Auto Close on both the main ePO database and the Events database.
- Connect to SQL Server
- Log in to the SQL Server instance hosting the ePO databases using Microsoft SQL Server Management Studio (SSMS).
- Open Database Properties
- In Object Explorer, expand Databases
- Right-click the main ePO database (for example: ePO_ServerName)
- Select Properties
- Disable Auto Close
- Navigate to the Options page
- Locate Auto Close
- Set it to False
- Click OK
- Repeat for the Events Database
- Right-click the Events database (for example: ePO_ServerName_Events)
- Open Properties → Options
- Set Auto Close = False
- Save changes
Important: Skipping the Events database is a common mistake and can still cause upgrade failures.
What Happens After Auto Close Is Disabled?
Once Auto Close is set to False:
- SQL Server maintains persistent connections
- The ePO installer can complete schema changes safely
- Upgrade logs complete without database disconnect errors
- The upgrade proceeds smoothly from 5.9 to 5.10
In real-world environments, this single change resolves the majority of failed upgrade attempts.
Final Thoughts
Upgrading Trellix ePO from 5.9 to 5.10 is straightforward only when SQL Server is configured correctly. The Auto Close setting is a silent but critical dependency that often goes unnoticed until the upgrade fails.
By proactively disabling Auto Close on both the ePO and Events databases, you eliminate the most common upgrade blocker and dramatically improve your chances of a clean, successful upgrade.
If you manage enterprise security infrastructure, this one configuration check can save hours of troubleshooting and downtime.
