The steps that I stated earlier in a prior blog post was to create the initial R3 Test environment and to create the "Gold" modelstore. After that is completed you can clone it and create a Development environment.
Once that is completed, the project team can begin to regression test R3 with company data. Customizations can be validated and modified if necessary. Code updates can be applied and modelstore updated.
For the production upgrade, you will follow similar steps as previously noted but instead of installing vanilla AX, applying models, etc, your DBA will "upgrade" the modelstore using the modelstore from your Dev/Test environment.
Once that is completed, the project team can begin to regression test R3 with company data. Customizations can be validated and modified if necessary. Code updates can be applied and modelstore updated.
For the production upgrade, you will follow similar steps as previously noted but instead of installing vanilla AX, applying models, etc, your DBA will "upgrade" the modelstore using the modelstore from your Dev/Test environment.
From Technet article on Performing in-place upgrade to AX 2012 R2/R3 |
It’s awesome that you want to share those tips with us. Enterprise Resource planning! It is a very useful post Keep it up and thanks to the writer.
ReplyDelete