Cumulative Update 9 Installation Guide: Microsoft Dynamics AX 2012 R2
Cumulative Update 9 Installation Guide: Microsoft Dynamics AX 2012 R2
Cumulative Update 9 Installation Guide: Microsoft Dynamics AX 2012 R2
Microsoft Corporation
Published: September 2015
Table of Contents
Before you install cumulative Update 9 ..................................................................................................... 4
Review the release documentation ........................................................................................................ 4
Download the files or get CU9 directly from Lifecycle Services ............................................................. 5
Get CU9 directly thru Lifecycle Services for an existing installation.......................................................... 6
Apply CU 9 as an update to an existing Microsoft Dynamics AX 2012 R2 installation ............................. 6
Step 1: Prepare for the update ............................................................................................................... 6
Step 2: Install and analyze updates ....................................................................................................... 7
Step 3: Restart AOS and Internet Information Services (IIS) ............................................................... 10
Step 4: Reinitialize the model store ...................................................................................................... 10
Step 5: Complete the software update checklist .................................................................................. 11
Step 6: Update other Microsoft Dynamics AX components ................................................................. 14
Step 7: Validate the update and roll it out to the production environment ........................................... 14
Include CU 9 in a new installation of Microsoft Dynamics AX 2012 R2 .................................................. 15
Installation
method
All
Update
Slipstream
installation
Country-specific updates
Application hotfixes
Binary hotfixes
Hybrid hotfixes
The known issues in CU 9 can be found by using Issue search in Lifecycle Services. You must log in to LCS
by using your CustomerSource or PartnerSource account. Then, in the Issue search box, enter "CU9 known
Description
Installation Guide
If you are including CU 9 in a new slipstream installation, we recommend that you review the Microsoft
Dynamics AX 2012 Installation Guide (http://go.microsoft.com/fwlink/?LinkID=163796). This
documentation contains detailed installation instructions for all components of Microsoft Dynamics AX.
3.
4.
5.
6.
Select the diagnostic enabled environment for AX 2012 R2 within the LCS project.
You should see a new tile for Cumulative Update 9.
Select the tile to view the fixes that are available in CU 9. The fixes, already reported as, installed by
diagnostics, will not be included in the list.
The hotfixes listed here will show the details as well as impact of the hotfix on your environment.
Select and download all of the fixes, and select and download only those that you need based on
your system configuration. For ISVs, it is recommended to select all hotfixes.
A review page will open where you can view a summary of impact for all of the selected hotfixes on
your environment.
Select download, and when prompted, click Save package and download the zip file (Package.zip).
This will take some time to download due to the package size.
Extract the zip file on a local folder on a machine where the updates needs to be applied.
Run the AxUpdate.exe and install the different components. Follow the next section to understand in
detail how updates must be applied.
Back up the database that is being updated. By backing up the database, you can roll back to a
known, reliable version if you have to. In this manner, you can reduce downtime if an unexpected
error occurs. For more information, see Back up and recover databases
(http://technet.microsoft.com/en-us/library/dd362128.aspx).
Schedule a time when the fewest system users, or no users, are affected. As a best practice, announce
the time of the update in advance, to make sure that users are aware of the pending update and the
expected downtime. By notifying all users of the time of the update, you can minimize data loss, data
corruption, and loss of productivity.
Make sure that the system runs in single-user mode while the update is installed, and that only the
administrator is designated to perform the update. Because changes to the code can affect
Application Object Server (AOS), the changes can affect users who are currently on the system.
Caution:
Changes to the application require a compilation or synchronization of the application. These
operations increase downtime.
If your environment includes tax integration for China, you must export external invoices before you
install updates.
a.
Click Accounts receivable > Periodic > Tax integration > Export to file.
b. On the Batch tab, enter a description for the batch, and then click OK. By default, all invoices are
selected.
Install binary updates only (for AOS, the client, components, Setup, or Retail)
Use the following procedure to install any binary update.
Important:
All binary updates on a computer must be updated at the same time. If more than one AOS
instance is installed, all the instances must be updated.
1.
Browse to the location where you extracted the files for the update, and then double-click
AxUpdate.exe
2.
On the Welcome to Microsoft Dynamics AX Update Installer Wizard page, click Next.
3.
On the Software license terms page, review the license terms, and then click Accept and continue.
4.
On the Select packages to update page, select the packages to update, and then click Next.
Only updates that are available for installation can be selected.
5.
Clear Database, select all other packages that can be installed on the local computer, and then click
Next.
6
7.
On the Ready to install page, review the summary, select the Automatically restart the AOS
instances after installation check box, and then click Install.
8.
After the installation is completed, verify that the updates were installed successfully and then exit the
wizard.
9.
Browse to the location where you extracted the files for the update, and then double-click
AxUpdate.exe.
2.
On the Welcome to Microsoft Dynamics AX Update Installer Wizard page, click Next.
3.
On the Software license terms page, review the license terms, and then click Accept and continue.
4.
On the Select packages to update page, select the packages to update, and then click Next.
Only updates that are available for installation can be selected.
5.
Select all applicable packages that can be installed, and then click Next. You must select Database as
one of the packages.
6.
On the Choose a model store page, select a local instance to update, or click Add existing model
store to enter the name of a remote database instance.
7.
On the Select type of installation page, Select Express installation. -> Click Next
8.
9.
On the Ready to install page, review the summary, and then click Install.
Install the binary components, including the client. For more information, see Install binary updates
only (for AOS, the client, components, Setup, or Retail).
After binary components have been installed, you must reinitialize the model store. For more
information, see Step 4: Reinitialize the model store.
Important:
You must install binary components and reinitialize the model store before you can use the
Advanced installation option to select application updates.
2.
Browse to the location where you extracted the files for the update, and then double-click
AxUpdate.exe.
3.
On the Welcome to Microsoft Dynamics AX Update Installer Wizard page, click Next.
4.
On the Software license terms page, review the license terms, and then click Accept and continue.
5.
On the Select packages to update page, select all applicable packages that can be installed on the
local computer, and then click Next. You must select Database as one of the packages.
6.
On the Choose a model store page, select a local instance to update, or click Add existing model
store to enter the name of a remote database instance.
7.
Optional: If you have access to a project in Lifecycle Services that contains business processes that you
want to use to help select appropriate updates, click Log in to Microsoft Dynamics Lifecycle
Services, and then click Next. When a browser window opens, follow these steps:
a.
b. If the Lifecycle Services License terms page opens, click Accept and continue.
c.
9.
Select a Lifecycle Services project and then click OK. Once the business process information has
been retrieved, the browser window closes.
On the Select application updates page, click Applicable updates. You can optionally use the
Group by list to filter the application updates by module, country/region, configuration key, or
business process.
For any hotfix, the details pane displays the title of the hotfix, the model and layers that the hotfix
applies to, and any updates that are included. Review the hotfix details, and then click the Conflicts
tab to view the conflict summary. Use Get conflict details to view additional detailed information or
open the Impact Analysis Wizard for a single hotfix. For information about the Impact Analysis Wizard,
see Run the Impact Analysis Wizard to analyze updates (optional) later in this document.
10. Select all appropriate hotfixes for your environment and then click Next.
The Review updates to be installed page opens. This page lists the models that will be installed and
the details (model name, description, layer, and updates that are included).
You may also want to click Export update list, so that you can later use the file to speed up applying
application updates to another computer.
11. On the Review updates to be installed page, click Next.
12. On the Ready to install page, review the summary, and then click Install.
10. Continue with the next steps in the update process.
The Welcome to Microsoft Dynamics AX Update SetupImpact Analysis Mode page lists all
hotfixes that you previously selected. Click Next.
2.
On the Select client configuration page, select a client configuration or a configuration file to use
for comparison with the updates that you plan to install, and then click Next.
3.
On the Select model store page, select a model store to analyze. The model store that you select
must be the same model store that is used by the client configuration that you selected. Click Next.
4.
On the Select baseline model store page, select a baseline model store to use for the impact
analysis. The baseline model store that you select must be the same model store that is used by the
client configuration that you selected.
Note:
The Review the impact analysis configuration page displays the selected configuration. For the
Select layers to analyze field, select whether to analyze all layers or only layers that include changes,
and then click Start Analysis.
The Analyzing impact page is displayed until the analysis is completed.
6.
The Results page lists the objects that are affected and the number of cross-references. Click Open
the impact analysis results log file to view the results.
7.
Click Advanced to open the AX 2012 R2 client to view the details of the impact analysis.
8.
9.
2.
If Enterprise Portal for Microsoft Dynamics AX is deployed in your environment, open a Command
Prompt window on the Enterprise Portal server, type iisreset, and then press ENTER.
Warning:
If you do not restart IIS, you receive the following message, and Enterprise Portal is not
deployed to other servers if you try to redeploy: Could not load type
Microsoft.Dynamics.Framework.Portal.EPSoapSecurity
On the Start menu, point to All Programs, point to Administrative Tools, and then click Microsoft
Dynamics AX Management Shell.
2.
At the Windows PowerShell command prompt, PS C:\>, type the following command, and then
press ENTER.
Initialize-AXModelStore
10
After installing an update, open the client in the lowest layer with customizations that you want to
merge hotfix changes into.
2.
3.
4.
5.
Specify the title for the project to be created when you are prompted, and then run the tool.
After the comparison has completed, a form displays the results of the merge. For changes that were
merged successfully, the changes should be reviewed to make sure that they are correct. For changes
that remain in conflict, the user must manually investigate and merge conflicts.
6.
7.
After resolving all conflicts, compile the application again and perform whatever functional testing is
required to make sure that all conflicts have been merged.
Repeat for each layer that contains customizations.
2.
3.
Complete the items on the checklist, in the order in which they are listed.
11
Checklist section
Upgrade preparation
Code upgrade
Compile application
This option compiles X++ code for the application. Compilation can require an
hour or longer.
12
Checklist section
Data upgrade
13
Update to CU 9.
After the update has been tested, you must install the update in the production environment. You must
install all binary and pre-processing hotfixes, but you can roll the code changes forward to the production
environment by importing and exporting the model store. Use the methodology that is described in
Deploying Customizations Across Microsoft Dynamics AX 2012 Environments (White paper)
(http://technet.microsoft.com/en-us/library/hh292604.aspx) and How to: Export and Import a Model Store
(http://technet.microsoft.com/en-us/library/hh433530.aspx). By exporting and importing the model store,
you can avoid having to compile code in the production environment.
14
Create a shared network location from which to install Microsoft Dynamics AX. For more information
about how to install Microsoft Dynamics AX from a shared network folder, see Create a shared
directory for installation (http://technet.microsoft.com/en-us/library/dd362101.aspx).
2.
Copy the contents of the Microsoft Dynamics AX DVD to the shared network location.
3.
In the Updates folder of the Microsoft Dynamics AX DVD, create a folder for CU 9.
The installation files for CU 9 are contained in a self-extracting package. Double-click the package to
extract the files to the new CU 9 folder that you created.
4.
After you have copied the CU 9 installation files to the Updates folder, run Setup as you would for any
new installation. Setup automatically detects and installs the updates that are included in the Updates
folder.
For detailed information about how to install Microsoft Dynamics AX, see the Microsoft Dynamics AX
2012 Installation Guide (http://go.microsoft.com/fwlink/?LinkID=163796).
15