Microsoft

MicrosoftDynamics
DynamicsAX
AX2012
2012R2:
R2: How
Howto
toupgrade
upgradefrom
froman
anearlier
earlierrelease
releaseof
ofAX
AX2012
2012
3 Save reports
& Web Parts

2 ...to create
test system

AX 2012 / FP

AX 2012 / FP

4 Install Microsoft Dynamics AX 2012 R2

AX 2012 / FP

2
AOS, EP, SSRS, Help

Clients

Client

AOS, EP, SSRS, Help

AX database

AOS, EP, SSRS, Help

AX database

AX database

Split
AX 2012 R2

CUS (customer)
VAR (customer)
ISV (customer)
SLN (Microsoft)

CUS (customer)
VAR (customer)
ISV (customer)
SLN (Microsoft)

FPK (Microsoft)

Code
layers

CUS (customer)
VAR (customer)
ISV (customer)
SLN (Microsoft)

FPK (Microsoft)

GLS (Microsoft)

Code
layers

SYS (Microsoft)

AX 2012 R2
client
components

Business data

AX database

GLS (Microsoft)

Code
layers

SYS (Microsoft)

USR (customer)

Model
store

USR (customer)

CUS (customer)
VAR (customer)

AX 2012 R2
models from
Microsoft

FPK (Microsoft)

Upgraded AX
2012 R2 models &
legacy customer
models. You will
reimport these
each time you
finish upgrade on
a code layer.

1a

Setup

ISV (customer)
SLN (legacy)

1b

GLS (Microsoft)

FPK (legacy)

SYS (Microsoft)

GLS (legacy)

AOS

Client

Business data

Business data

Model
store

USR (customer)

VAR (customer)

ISV (customer)

SLN (2012 R2)

FPK (2012 R2)

GLS (2012 R2)

SYS (2012 R2)

If you are using customized

reports or customized EP Web
Parts, import them into the
AOT before running Setup.exe.
These components will need to
be redeployed on the upgraded
system.

Production
environment

GLS (2012 R2)

11 Redeploy reports
& Web Parts

12 Enter single-user mode

AX 2012 / FP

USR

USR

AX 2012 R2

Create a file backup of the

model store. This backup is
used during code upgrade of
the models in the customer
layers.

AX 2012 R2

Duplicate your existing test

system to create the
development system. You can
accomplish this by copying a
virtual machine image or by
building a new system with AX
R2 Setup and then importing
the test system model store.
This can be a simplified system
consisting of only the AOS,
databases, and a client.

SLN (2012 R2)

Client

Client

AOS, EP, SSRS, Help

Client

AOS, EP, SSRS, Help

Upgraded
AX 2012 R2
model store file

Clients

Business data

AX database

USR

Business data

ISV
SLN

Business data

Model
store

USR (2012 R2)

VAR

CUS (2012 R2)

VAR (2012 R2)

VAR (2012 R2)

ISV (2012 R2)

ISV (2012 R2)

SLN (2012 R2)

SLN (2012 R2)

FPK (2012 R2)

GLS

FPK (2012 R2)

GLS (2012 R2)

SYS

GLS (2012 R2)

SYS (2012 R2)

On the production system, enter

single-user mode. All client users other
than the administrator will be
disconnected from the AX system at
this point. This action starts the
downtime window during which new
business transactions cannot be
processed.

SYS (2012 R2)

After data upgrade is complete, redeploy any customized

reports and EP Web Parts that were imported into the
AOT in step 3. When deployment is complete, validate
that these components are working correctly. The test
system is now ready to serve as a platform for user
acceptance testing (UAT) before the production system is
upgraded.

Test environment

Before beginning data upgrade, set

the SQL Server logging model to
Simple, and confirm that the AOS is
set up as a batch server and that it
can process the DataUpgrade batch
group. Then start the client and
open the Data upgrade checklist
for in-place upgrade. Complete the
tasks in the checklist.

14 Upgrade AOS & other

core components

13 Run setup to upgrade the database

Business data

Run data
upgrade
checklist

Model
store

USR (2012 R2)

CUS (2012 R2)

FPK

Important:
Don t attempt to
complete the
checklist without
following the
detailed instructions
for each checklist
task in the Microsoft
Dynamics AX 2012
Upgrade Guide.

Model
store

USR (customer)

AOS

FPK (2012 R2)

GLS (2012 R2)

GLS (2012 R2)

SYS (2012 R2)

SYS (2012 R2)

A. Assign the working layer (VAR in

this illustration)
And delete the models in higher
layers.

B. Complete the tasks on the

Code upgrade checklist for inplace upgrade, then export
the upgraded models.

D. Import the newly upgraded

customer models into their layers.
Repeat steps A through D until all
models have been upgraded.

C. Import the model store

backup from the test system.

AOS

Business data

Model
store

CUS (2012 R2)

VAR (customer)

Before completing the

development steps, you
must export any changed
models on the production
system and merge their
changes into the upgraded
model store. This requires
that you run an additional
code upgrade cycle for
each affected layer.

VAR (2012 R2)

ISV (customer)

ISV (2012 R2)

SLN (2012 R2)

SLN (2012 R2)

FPK (2012 R2)

FPK (2012 R2)

GLS (2012 R2)

GLS (2012 R2)

SYS (2012 R2)

SYS (2012 R2)

Client

Model
store

USR
CUS

SLN (2012 R2)

15 Perform data upgrade on

the production system

16 Upgrade additional
server components

Export the fully upgraded model

store that you have created on the
development system to a file. This
file acts as the source of the
upgraded customer models that are
used to prepare for data upgrade
first on the test system and later on
the production system.

17 Redeploy reports
& Web Parts
AX 2012 / FP

AX 2012 R2

AX 2012 / FP

SYS (2012 R2)

Client

AX 2012 R2

Business
data

Archived
legacy
model
store

Setup

AX database

ISV
ISV(2012
(Legacy)
R2)
SLN (Legacy)

VAR (2012 R2)

ISV (2012 R2)

GLS (Legacy)
SYS (Legacy)

Setup

Import

CUS (2012 R2)

ISV (2012 R2)

SLN (2012 R2)

GLS (2012 R2)

SYS (2012 R2)

Model
store

VAR (2012 R2)

FPK (2012 R2)

Business
data

USR (2012 R2)

SLN (2012 R2)

FPK (Legacy)

Client

AX 2012 R2

CUS (2012 R2)

Business data

VAR
VAR(2012
(Legacy)
R2)

AX 2012 R2
AOS, Help
server, client,
and utilities

Model
store

USR (2012 R2)

USR
USR(2012
(Legacy)
R2)
CUS
CUS(2012
(Legacy)
R2)

AOS, Help

AX 2012 R2

Upgraded
AX 2012 R2
model store file

Run Setup on the computer that hosts the AOS. (1) Designate the existing AX
database as the business database, (2) create a new database to contain the
model store, and (3) import the upgraded model store file. The legacy model
store tables persist alongside the business data but are not used. These tables
should not be deleted, because they act as an archive of your pre-upgrade
code customizations.

FPK (2012 R2)

GLS (2012 R2)
SYS (2012 R2)

Run Setup again on the

computer that hosts the AOS.
Install new versions of the
AOS, client, debugger, and
management utilities.

Business
data
Model
store

USR (2012 R2)

CUS
VAR (2012 R2)
ISV (2012 R2)

Upgraded ISV
model files

Import

SLN (2012 R2)

FPK (2012 R2)
GLS (2012 R2)
SYS (2012 R2)

AX 2012 / FP

Client

Run data
upgrade
checklist

USR

Setup

Client

AOS, Help

Upgraded VAR
model files

Model
store

18 Upgrade additional clients

AOS

Upgraded
AX 2012 R2
models & legacy
customer
models

Development environment

AOS
AOS, Help, EP, etc.

Client

Business data

ISV (upgraded)

GLS (2012 R2)

You will also load

this same file when
you upgrade the
production system.

AOS

VAR (upgraded)

FPK (2012 R2)

On the test system, import the

model store file that you made in
the previous step. Afterward,
create a backup of both AX
database.. If you experience an
error during the data upgrade
procedure, you can revert to this
earlier state, resolve the
underlying issue, and try the data
upgrade again.

AX 2012 R2

Business data

Setup

2013 Microsoft Corporation

SLN (2012 R2)

Client

USR (2012 R2)

CUS (customer)

AX 2012 / FP

Important: Upgrade on
the production system
requires that you run AX
2012 R2 Setup on each
computer in your
deployment. To insure a
successful upgrade, you
must install the AX
components in a specific
order and on a specific
topology. Components of
the deployment must be
upgraded in the order that
is shown in the following
procedures.

VAR layer (2012 R2)

FPK (2012 R2)

AX 2012 R2

AX 2012 R2

Run code
upgrade
checklist

ISV (2012 R2)

8 Export the upgraded

model store

Export

Models

AX 2012 R2
AOS, EP, SSRS, Help

CUS

Business data

VAR
VAR

Enter singleuser mode

AOS, Help, EP, etc.

Exported
VAR models

CUS

CUS

9 Import upgraded
model store

10 Test data upgrade

Client

SYS (2012 R2)

Important: To insure a successful upgrade, you must install the AX 2012 components in a specific order and on a specific
topology. For information, see How to: Perform in-place upgrade to Microsoft Dynamics AX 2012 R2 on TechNet.

Test environment

AOS

Model
store

Models

`
Models

Run Setup three times on the test system as follows: (1a) split the
database and (1b) install the new Microsoft models; (2) upgrade
the AOS and other server components; and (3) upgrade the client,
the debugger, and management utilities. This installation order
must be strictly observed. The database on the left is the original
single AX database; the ones on the right are the result of the
separation of the model store from the business data.

AX 2012 R2

SLN (2012 R2)

FPK (2012 R2)

GLS (2012 R2)

Client

Important:
Don t attempt to
complete the
checklist without
following the
detailed instructions
for each checklist
task in the Microsoft
Dynamics AX 2012
Upgrade Guide.

Business data

Deleted models

ISV (customer)

SLN (2012 R2)

FPK (2012 R2)

AOS

CUS (customer)

VAR (customer)

ISV (customer)

Model
store

USR (customer)

CUS (customer)

SYS (2012 R2)

When the test system is ready

for upgrade, it contains legacy
AX 2012 or AX 2012 Feature
Pack models and also any
customer models.

To preserve the element IDs in your customized code, upgrade the models
in each code layer separately, starting at the lowest layer and working up.
Repeat until all models in all layers are upgraded.

AX 2012 R2

AX 2012 R2

VAR (customer)

Layers
containing
upgraded
Microsoft
models

Client

AOS, EP, SSRS, Help

CUS (customer)

SYS (legacy)

Duplicate your existing production

system to create the test system. You can
accomplish this by copying a virtual
machine image, or, alternatively, you can
build a new system by using Setup from
your legacy AX version (taking care to
apply all the same hotfixes), and then
copying over the production database.

7 Upgrade customized code

USR (customer)

Business data

Business data

USR (customer)

Business data

USR (customer)

6 For code upgrade, create

the development system

Client

AX 2012 R2
server
components

Client

5 Back up the model store

AX 2012 R2

AOS
EP
SSRS
Help

Business data

1 Copy the existing

production system...

AX 2012 R2
Other server
components

Client
Help

AX 2012 R2
clients

Help

Servers

Databases

Enterprise Portal
Enterprise Portal

Final Testing
&
Go Live

CUS (2012 R2)

Databases

VAR (2012 R2)

ISV (2012 R2)
SLN (2012 R2)

Databases
Reporting Services and
Analysis Services

Reporting Services and

Analysis Services

FPK (2012 R2)

GLS (2012 R2)
SYS (2012 R2)

Before beginning data upgrade, set the SQL Server logging

model to Simple, and confirm that the AOS is set up as a
batch server and that it can process the DataUpgrade batch
group. Then start the client and open the Data upgrade
checklist for in-place upgrade. Complete the tasks on the
checklist.

When data upgrade is

finished, you can upgrade the
other server components. Run
Setup on the computers that
host EP, Reporting Services,
and Analysis Services.

After data upgrade is complete,

redeploy any customized
reports and EP Web Parts that
were imported into the AOT in
step 3. When deployment is
complete, validate that these
components are working
correctly.

Run Setup on your additional AX

client systems to upgrade the
client software. Select the Client
and Management utilities
components for installation. For
large deployments, you may want
to perform a silent installation.

Production environment