This post is machine-translated. The original post in german language can be found here.
These post applies to following version:
Dynamics AX 2012
Dynamics AX 2012
|
|
|
|
|
|
This post is machine-translated. The original post in german language can be found here.
These post applies to following version:
Dynamics AX 2012
|
Recently, I wanted to update my locally installed AX 2012 R3 CU8 to a newer version. This requires the following:
Below are some screenshots and comments I made during the update.
Log in to LCS and download the installer
Start the installer
At this point, we decide whether we want to install a previously stored package, or download the available updates from the Internet. I decided on the latter at this point.
By my previous selection, I ended up again in the Lifecycle Services where I could decide on a drop-down list, which program status I would like. Specifically, I decided on "Most recent", in example the last program (from January 30, 2018).
Here we make the selection whether we only want to update the client-side programs and/or the application.
At this point you can see what is included in the package, including details about the individual hotfixes.
In the next step you can already see recognized conflicts.
Now, it's about whether we want to update AX now, or just create a package that will be uploaded at a later time. I have opted for the latter here as well.
Installation of a previously assembled package
Now the installation is ready, it is necessary to reinitalize the modelstore and to delete all *ald and *.ali files from the application directory (ex. C:\Program Files\Microsoft DynamicsAX\60\Server\<instancename>\bin\Application\Appl\Standard).
Remember to restart your server now.
Starting Dynamics AX
As expected, AX starts with the software update checklist, which you now have to go through step by step.
From here actually begins the work of AX developers. The resulting effort depends heavily on the degree of modifications made in your application.