This article explains changes to the ePO update strategy. ePO 5.10 Update 15 is the last update in the initial series of cumulative updates (CUs) for ePO 5.10. The next release after that may have two different packages.

NOTE: CU in this article indicates any update that's applied using the ePO 5.10 update tool.

• ePO 5.10 Service Pack 1 (ePO 5.10 SP1): This package can be used to install ePO for the first time and includes the updates in CU 1–15. It's also used to upgrade some versions of ePO 5.9.1 and earlier to ePO 5.10 SP1. For details, see the "Supported Upgrade Paths" section below.
   
• ePO 5.10 Service Pack 1 Update (ePO 5.10 SP1 CU): This package can be used to upgrade an existing ePO 5.10 server to service pack 1. You don't need to install this if you've already installed ePO 5.10 Service Pack 1.

EPO 5.10 SP1 Update is the last update to support both upgrading from and rolling back to ePO 5.10 CU 1–15. The update numbering then resets so that the next release after ePO 5.10 SP1 might be ePO 5.10 SP1 Update 1 (ePO 5.10 SP1 CU1), and so on. If you're on ePO 5.10 Update 15 or earlier, you must first apply ePO 5.10 SP1 CU before upgrading to ePO 5.10 SP1 CU1 or later.

Supported Upgrade Paths
See the table below for supported upgrade paths. The following list provides further details for the table that follows:

• Blocked: This is an unsupported upgrade path and may be explicitly blocked by the installer or is otherwise unsupported.
• Current ePO Version: This column header identifies the row that represents the version of ePO that you're upgrading FROM.
• EPO 5.10: This indicates the base installation of ePO 5.10 with no update or service pack applied.
• N/A: This means that the path isn't applicable because this won't be an upgrade.
• Repair: You can run a repair using the ePO 5.10 SP1 CU package but you cannot run it as a standard update. 
• Supported allows Rollback: Upgrade is supported. Automatically rolls back after a failed upgrade but also allows rollback after a successful upgrade. Also allows Repair. In the context of the table below, the rollback is supported from the version in the Target ePO Version column to the version in the Current ePO Version row.
• Supported: Upgrade is supported. Rollback is supported but only in a failed upgrade scenario. If the upgrade fails, the installer should roll back automatically to the version that you're upgrading from.
• Target ePO Version: This column represents the version of ePO that you're upgrading TO.

Current ePO Version

Target ePO Version

5.10 SP1 CU X

5.10 SP1

5.10 SP1 CU

5.10 CU 1-15

5.10

5.9.1 (EOL)

5.9.0 (EOL)

5.3.3 (EOL)

5.3.2 (EOL)

5.3.1 (EOL)

5.3.0 (EOL)

5.10 SP1 CU X

Supported with Rollback where Current ePO CU is less than Target ePO CU

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

5.10 SP1

Supported allows Rollback

N/A

Repair

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

5.10 SP1 CU

Supported allows Rollback

N/A

Repair

N/A

N/A

N/A

N/A

N/A

N/A

N/A

N/A

5.10 CU 1–15

Blocked

Blocked

Supported with Rollback

Supported with Rollback where Current ePO CU is less than Target ePO CU

N/A

N/A

N/A

N/A

N/A

N/A

N/A

5.10

Blocked

Blocked

Supported with Rollback

Supported with Rollback

N/A

N/A

N/A

N/A

N/A

N/A

N/A

5.9.1 (EOL)

Blocked

Supported

Blocked

Blocked

Supported

N/A

N/A

N/A

N/A

N/A

N/A

5.9.0 (EOL)

Blocked

Supported

Blocked

Blocked

Supported

Supported

N/A

N/A

N/A

N/A

N/A

5.3.3 (EOL)

Blocked

Supported

Blocked

Blocked

Supported

Supported

Supported

N/A

N/A

N/A

N/A

5.3.2 (EOL)

Blocked

Supported

Blocked

Blocked

Supported

Supported

Supported

Supported

N/A

N/A

N/A

5.3.1 (EOL)

Blocked

Supported

Blocked

Blocked

Supported

Supported

Supported

Supported

Supported

N/A

N/A

5.3.0 (EOL)

Blocked

Blocked

Blocked

Blocked

Blocked

Blocked

Blocked

Blocked

Supported

Supported

N/A

Finding your ePO 5.10 Build Number
Follow these steps if you have access to your ePO console and the ePO server is at the build number that you're recovering:

1. Log on to your ePO console.
2. Go to Menu, Configuration, Server Settings.
3. Select Server Information.
4. Review the build number in the Version column.

If the ePO server that you're recovering is non-functional or the version that you're recovering doesn't match the currently installed version, you can use these instructions to determine the build number:

1. Restore the ePO DB if it isn't already hosted on an SQL server. See KB52126 - How to back up and restore the ePolicy Orchestrator database using SQL Server Management Studio for details. 
2. Run the following query against your ePO database. See KB67591 - How to run a SQL script provided by Technical Support against the ePolicy Orchestrator database for details. 
   
   select [Version] from OrionExtensions where [Name] = 'EPOCore'
    
3. Note the value returned. This will be the build number for the ePO server associated with that database.

Upgrading from ePO 5.10.0.4067 to ePO 5.10.0.4098
The original build of ePO 5.10 Service Pack 1 was ePO 5.10.0.4067, but it was refreshed as ePO 5.10.0.4098 to address the issue documented in KB96464 - Eventparser.exe and Apache.exe crashes frequently, faulting module name: ccme_base.dll is reported after you upgrade to ePO 5.10 SP1. If you're currently using ePO 5.10.0.4067, we recommend that you upgrade your build to ePO 5.10.0.4098. Instructions for identifying the build number of ePO that you're restoring are in the "Finding your ePO 5.10 Build Number" section of this article. If you're currently using ePO 5.10.0.4067 (original release of ePO 5.10 SP1), you can follow these instructions to upgrade to ePO 5.10.0.4098 (refreshed release of ePO 5.10 SP1):

Note: You'll need to repeat these instructions on all remote agent handlers if you have any. 

1. Download the refreshed release of ePO 5.10 SP1 Update package. The filename name is ePO_5.10.0_1359_ServicePack1Update.zip. See KB56057 - How to download product updates and documentation for download instructions. 
2. Extract the package
3. Stop all ePO services
4. Run ePOUpdater.exe
5. Enter your SQL credentials, accept the license agreement and click Continue
6. Click Previously Installed Updates
7. Click Repair
8. Click Finish once the install completes

You can follow the steps in the Finding your ePO 5.10 Build Number section of this article to validate that the build number is now ePO 5.10.0.4098. 

Disaster Recovery

NOTE: The information in this section only applies to ePO 5.10.

When you perform a disaster recovery for ePO, be it a snapshot recovery or a manual disaster recovery (KB66616 - ePolicy Orchestrator server backup and disaster recovery procedure), it's important to select the correct ePO installation package that corresponds to the build number of ePO that you're recovering. Instructions for identifying the build number of ePO that you're restoring are in the Finding your ePO 5.10 Build Number section of this KB article. 

Select the correct package from the following table based on the build number of ePO that you're recovering.

EPO Build being Recovered	Description	Installation Package Filename	How to download the file
5.10.0.2428	Original Base build of ePO 5.10 with No SP installed. This includes any ePO server with CU 1–15 installed.	EPO510_2428_68_LR6.Zip	Contact Technical Support.
5.10.0.4067	EPO 5.10 with SP1 installed.	EPO5100_ServicePack1.Zip	Contact Technical Support.
5.10.0.4098	EPO 5.10 with SP1 Refresh or later installed.	EPO5100_ServicePack1_4098_LR1.Zip	KB56057 - How to download product updates and documentation.

• If you are a registered user, type your User ID and Password, and then click Log In.
• If you are not a registered user, click Register and complete the fields to have your password and instructions emailed to you.