Microsoft Dynamics AX 2012 Update Process

What is an Update? Installation Order

Updates include hotfixes, cumulative updates, and feature packs. This diagram describes the order in which updates are applied The differences in a production
in a test environment, and then applied in a production environment are:
Hotfix: Cumulative update: Feature pack: environment. 1. Import the model store from the test
A fix or set of fixes that 1. Apply updates to the database. environment to apply updates to the
An update that contains all A group of updates that
address a specific issue, 2. Apply updates to a single local AOS instance. database.
previous hotfixes to date. relate to a feature area or
problem, or customer 3. Apply updates to a single local client. (Compile, 7. Mass deploy client updates (optional).
group of functionality.
scenario. Synchronize, and get the environment running)
Contains design changes.
4. Deploy reports to the report server.
5. Deploy web parts to the Enterprise Portal server. Production environment
Types of Hotfixes 6. Deploy updates to any retail components. 1
To determine which type of update is in a package, download the package, and then extract contents and review
Database
them to determine which type of update it is.
Test environment
1 2
Model
Database
Store AOS

2
3
AOS Client

3 4
Client Report
server

4
Report 5 Enterprise
How can I tell if a binary update requires a schema update, and model store reinitialization? server Portal
The KB article will indicate that a hotfix requires a schema update, and that you should reinitialize the model store.
You should assume that all cumulative updates require a schema update, and reinitialize the model store.
5 Enterprise Retail
6 components
How can I tell if an application update contains a report or web part? Portal
There is currently no simple way to tell if a hotfix contains a report or web part. We recommend that you assume
that all cumulative updates, service packs, and feature packs contain reports and web parts, and re-deploy reports
and Enterprise Portal. Retail
6 components
7 Clients
If you encounter an error after installing a hotfix, try deploying reports and web parts.
(mass
deploy)

Detailed Update Process Update Tips and Tricks

This diagram describes the update process in detail, in both the test and production environments.
Always update in a test environment first and run the Impact
Back up your Wizard for application updates
business, model Download an
store, and retail update You can reduce the downtime of your production environment
databases by fixing all code conflicts in a test environment, and
Steps with an asterisk (*) may not be required for all updates, or in all environments. identifying them early.
Test environment
Database/AOS/Client/EP/Retail
Make sure that you have the correct product version
Install on retail Run Retail Most updates apply only to released versions of a product.
Retail
components Database Utility*
Note: Many demonstration virtual machines run pre-release
versions of Microsoft Dynamics AX, and cannot run updates.
Binary
If includes a
Determine Complete the Install binary updates first, and if needed, reinitialize the
Install on database schema
Run AxUpdate which components to Restart the AOS Software Update
install on
components change, reinitialize
Checklist model store before installing application updates
the model store*
If you do not reinitialize the model store, you will encounter
many more errors in the Data Upgrade Cockpit.

Do not skip the Software Update Checklist

Database Reporting services Enterprise Portal Database
After you install an update, on the Model store has been
Run the Impact Complete the Redeploy the Export the model modified form, select Start the software update checklist.
Determine the Run AXUpdate to Run store using AXUtil
Application Analysis Wizard Software Update default reports
hotfix type install models AXPortalUpdate to or Windows
(AXImpactAnalysis) Checklist using Windows
PowerShell*
deploy EP updates* PowerShell If you must generate CIL, restart all AOS instances

Install updates on all appropriate components (reports and

web parts)
Client It is difficult to tell whether an update contains modified or
Complete the new reports, or web parts—we recommend that redeploy
Preprocessing Import XPO files Restart the AOS software update reports and web parts with all CUs.
checklist

Check to see whether all of your current hotfixes are

Production environment
contained in the most recent cumulative update or feature
pack—if not, reinstall it
Database/AOS/Client/EP/Retail If you have a recent hotfix that is not included in the
Retail
Install on retail Run Retail cumulative update or feature pack that you are installing, it
components Database Utility* will be removed. Reinstall the hotfix after you have applied
update.

If includes a Consider slipstreaming updates if you are doing a fresh install

Determine Complete the
Install on database schema
Binary Run AxUpdate which components to Restart the AOS Software Update
components change, reinitialize
install on Checklist
the model store* If you are installing industry solutions, install them before
installing updates

Database AOS Reporting services Enterprise Portal

To minimize downtime, consider importing the model store
into a non-default schema in the production environment,
Import the model Redeploy the and then switching it to be the default schema
Determine the store using AXUtil Run
Application Restart the AOS default reports
hotfix type or Windows using Windows
AXPortalUpdate to For information about using non-default schemas, read How
PowerShell deploy EP updates*
PowerShell* to: Create, Drop, or Reinitialize a Model Store.

Client

Complete the
Preprocessing Import XPO files Restart the AOS software update
checklist

© Copyright Microsoft Corporation, 2013