Installing the Microsoft Dynamics AX Feature Pack components and models

This topic contains 2 replies, has 3 voices, and was last updated by  Locus IT 6 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #20612

    John
    Participant

    Can anyone please let me know how can I Install the Microsoft Dynamics AX Feature Pack components and models for performing in-place upgrade to AX 2012 R2?

    #20964

    Locus IT
    Participant

    Hello John,

    An upgrade from Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 Feature Pack to Microsoft Dynamics AX 2012 R2 is classified as an in-place upgrade. The great thing about this type of upgrade is that it does not requires source-to-target workflow, which is when we needed to upgrade an AX 4.0 instance to AX 2009 before bringing it to AX 2012, instead the upgrade is done directly into the source AX 2012 system, so look for upgrade XPO in your AX 2012 R2 setup files.

    1. Create a Test System

    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 Microsoft Dynamics AX version, and then copying over the production database

    2. Run the Microsoft Dynamics AX 2012 R2 Setup on the Test System

    By running Microsoft Dynamics AX 2012 R2 Setup on the test system, you accomplish the three numbered tasks shown in the following picture. Back up the Test System Model Store
    Create a file backup of the model store. This backup is used during code upgrade of the models in the customer layer. i.e. AxUtil.exe exportstore /file:[full path of file and file name]

    3. Back up the Test System Model Store

    Create a file backup of the model store. This backup is used during code upgrade of the models in the customer layer. i.e AxUtil.exe exportstore /file:[full path of file and file name]

    4. Create Development System

    Duplicate the Microsoft Dynamics AX 2012 R2 test system to create the development system, which is used to upgrade customer models

    5. Upgrade Customer Models

    Customer models belong to one of the customer layers. In ascending order, these layers include the ISV, VAR, CUS, and USR layers. Code upgrade is performed by layer, meaning that each customer layer is upgraded separately, starting at the lowest layer and working up through the higher layers.

    6. Upgrade Code on the Development System and Export the Upgraded Models

    All tasks on the checklist have to be completed for each layer that contains models that require upgrade.

    7. Import the Model Store Backup to the Development System

    On the development system, import the backup of the model store that you made in the procedure “Back up the test system model store.” i.e. AxUtil.exe importstore /file:[full path of file and file name] /idconflict:overwrite

    8. Import Upgraded Models into their Layers on the Development System

    Import the upgraded model or models into the appropriate customer layers. Start with models from the lowest layer, then work up through the higher layers.

    9. Repeat Code Upgrade for Each Layer

    For each remaining layer that contains customized models, repeat the upgrade procedure, moving from the lowest remaining layer to the highest layer.

    10. Export the Upgraded Model Store

    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. i.e. AxUtil.exe exportstore /file:[full path of file and file name]

    11. Import the Upgraded Model Store into the Test System

    On the test system, import the model store file that you made in the procedure “Export the upgraded model store.” i.e. AxUtil.exe importstore /file:[full path of file and filename] /idconflict:overwrite

    12. Perform Data Upgrade on the Test System

    13. Upgrade Production System

    On the production system, enter single-user model. All client users other than the administrator will be disconnected form the Microsoft Dynamics AX system at this point. This action starts the downtime window during which new business transactions cannot be processed.

    14. Upgrade the Core Production System

    Upgrade on the production system requires that you run Microsoft Dynamics AX 2012 R2 Setup on each computer in your deployment.

    15. Upgrade AOS and Other Components

    Run Setup on the production system to upgrade the core server and client components.

    16. Perform Data Upgrade on the Production System

    Complete the tasks on the checklist as described earlier in this how-to in the section “Perform data upgrade on the test system.”

    17. Upgrade Additional Server Components

    When data upgrade is completed, you can complete the upgrade of server components.

    18. Upgrade Additional Clients

    Run Setup on your additional Microsoft Dynamics AX client systems to upgrade the client software.

    #20619

    Andrew Jenson
    Participant

    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).

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Skip to toolbar