Apply updates to on-premises deployments

This article explains how to apply supported updates to Dynamics 365 Finance + Operations (on-premises). All updates to on-premises environments are done through Microsoft Dynamics Lifecycle Services.

Search for and download updates

For more information about how to find the updates that you can apply to your on-premises environment, see Issue search in Lifecycle Services (LCS). For information about how to download updates from the tiles in the Updates section of the Environment details page in Lifecycle Services, see Download updates from Lifecycle Services (LCS).

Update an on-premises deployment

You can apply updates to an on-premises environment either during deployment or after the deployment is completed.

While an on-premises environment is being deployed, you can select to deploy a custom package in the Advanced settings. For more information about how to apply customizations or application X++ updates, see Develop and deploy custom models to on-premises environments.

To apply updates to an on-premises environment after it's deployed, follow these steps.

1. In Lifecycle Services, open the Environment details page for the environment.
2. Under Maintain, select Apply updates.

Apply platform update package updates through Lifecycle Services

You can use the following steps to apply platform update packages.

Prerequisites

• Before you begin, complete a full backup of the Management Reporter (MR), Microsoft Dynamics AX, and Microsoft SQL Server Reporting Services (SSRS) databases. Although the code is restored through Lifecycle Services, the database must be manually restored to help ensure that no data loss occurs.

• Update the local agent to the latest version. For more information, see Update the local agent.

• Depending on the type of update, complete the following steps to generate a deployable package:

  • Platform update packages – Download or save the update directly to the Asset library in Lifecycle Services by following the steps in Download updates from Lifecycle Services (LCS).
  • Customizations – Follow the steps in Develop and deploy custom models to on-premises environments.

Update a sandbox environment

1. In Lifecycle Services, open the on-premises implementation project, and then, on the project menu, select Asset library. In the Asset library, ensure that the platform update package or custom deployable package appears on the Software deployable packages tab.

2. In the on-premises implementation project, open the Environment details page of the environment to update.

3. Under Maintain, select Apply updates. A dialog box shows the updates that were uploaded to the Asset library. Note that only packages that are marked as Valid in the Asset library appear.

4. Select the update, and then select Prepare to prepare your on-premises environment for servicing.

   Note

   While the environment is being prepared for servicing, its state is Deployed. However, the Deployment status field shows the progress of the preparation. During preparation, actions such formatting the package and downloading the package are performed.

   Because the environment isn't directly touched during preparation, there is no downtime at this point. Users can continue to use the system during preparation.

5. After preparation is completed, Abort and Update Environment buttons appear. To start to apply the update, select Update environment. If preparation fails, see the Resolve a failed update application section later in this article.

6. In the confirmation message that appears, select Yes. The servicing operation now begins on the environment. This point is the start of the downtime on your environment.

   The environment state is changed from Deployed to Deploying.

   After the update is completed, the environment state is changed back to Deployed. If application of the update fails, the environment state is changed to Failed. For information about what to do if package application fails, see the Resolve a failed update application section later in this article.

   Note

   During the update, the database is synchronized to update any changes to table definitions. This action can take some time for larger databases. Additionally, all reports are deployed again to the SSRS nodes.

7. Open the History and Environment details pages to view the operations that were performed on the environment. You can view a record of major actions that were performed on the environment, such as deployments, servicing, and rollbacks.

Update a production environment

Before you update a production environment, you must successfully complete the package application update on a sandbox environment.

1. In the project for the sandbox environment that you applied the package to, open the Asset library, and then, on the Software deployable packages tab, select the package, and mark it as a Release candidate.
2. On the Environment details page, under Maintain, select Apply updates. The dialog box that appears shows only packages that are marked Release candidate.
3. Select the Release candidate package to apply to the production environment.

The rest of the update flow is the same as the flow for a sandbox environment.

Resolve a failed update application

When preparation fails, the environment state is Deployed. When the application of an update fails, the environment state is Failed. The first step is to determine why there is a failure. The location of the logs varies, depending on the stage where the failure occurred:

• Preparation stage – If the operation fails during the Preparation stage, the logs are uploaded to Lifecycle Services. In the log files, select Download logs to download the log files. If the package has any merge issues, the error is included in the log file.
• Deploying stage – If the operation fails during the Deploying stage, the logs are located in the on-premises environment. Sign in to the environment, and then access the logs and event viewer.

For more information about how to use the troubleshooting logs, see Troubleshoot on-premises deployments.

After you review the logs and determine the cause of the failure, complete one of the following operations to restore the environment to a healthy state. No actions can be performed on an environment that is in a Failed state. The environment must first be restored to a healthy state.

• Retry failed operation – If update application fails, select Retry to recover from the failed operation.

• Abort failed operation – Because there is no change made to the on-premises environment, if the preparation fails, you have the option to cancel the operation. Select Abort to cancel the preparation.

• Roll back the update – To roll back the update that failed, select Rollback. Before you start the rollback, you must restore the database to the last known good state. When you select Rollback, the environment is restored to the last known good state. The environment state is then changed to Preparation, then to Deploying, and then to either Deployed or Failed.

  Note

  The Rollback button doesn't roll back the database. You're responsible for restoring the database to the last known backup that was made before update application. This step is critical to help guarantee that there is no data loss.

• Refresh the state – If update application fails during the Preparation stage, the failure is on the Lifecycle Services side, and update application hasn't yet started. Therefore, the on-premises environment is in a good state. To restore the Lifecycle Services environment state to Deployed, on the project dashboard page, select Refresh.

• Delete and redeploy an environment – If the retry and rollback options don't work, you must delete and redeploy the environment. To delete the environment, on the project dashboard page, select Delete. You then see the option to configure the environment.

  Important

  This option should not be used on a production environment. However, it can be used on a sandbox deployment to restore the environment to a healthy state.

  Because this option requires that you do a fresh deployment of the environment, you lose any updates that were previously applied. Any customizations and binary updates must be reapplied to the environment.