Reply To: Installing the Microsoft Dynamics AX Feature Pack components and models


Andrew Jenson

Hi John,

On a high level, the upgrade process looks like this:

1. Freeze AX2012 code and make sure the environment compiles and works as expected.
2. Setup a new server since R2 components can not co-exist with RTM components.
3. Duplicate the AX2012 database into a new database intended for “R2 Test”.
4. Run setup and let it create the initial basis for a new R2 environment. Point to the test-database and install AOS, client and debugger for R2.
5. With Test up, duplicate it to a new environment intended for “R2 development”. The AOS can be installed on same server as test. This will be where code review will be done in order to fix code and prepare it for R2. Complete the code upgrade.
6. Let testers test R2 when it is ready for testing.
7. Upgrade AX2012 Live with already prepared R2 compatible axmodels, making sure both code compiles properly and there is no data loss in production.

A couple of tips:
1. Make sure there are enough available disk space on the disks containing your user hive (typically c-disk) and on the database server when running the AX2012 R2 setup.
2. If you chose to upgrade the Help Server content, you need to uninstall previous translated content – not the Help Server itself, but just the translated content. Use “Programs and Features” (Windows 2008) to locate the packages and just uninstall them one by one.
3. Set aside a lot of time, since the whole process involves multiple time consuming steps (like full compilation).

Skip to toolbar