Wednesday, October 27, 2010

Using Surface Area Configuration Tool for SQL Server 2005

Although I was aware of the surface area configuration tool for SQL Server but honestly I never used it. In a scenario where I had two VMs running on Windows 7 host OS, one with AX2009 AOS, client etc installed while the other VM only had SQL Server 2005 on it. The goal was to let AOS communicate with SQL in this virtual environment. Using the configuration tool on SQL VM, I was able to do this by allowing remote connections to this SQL from the AOS VM. Take a look at this KB article from MS:

http://support.microsoft.com/kb/914277

For SQL 2008, the tool has been taken away and I believe the SQL Server Configuration Manager now takes care of remote connectivity.

Tuesday, October 19, 2010

New Compatibility Study for MS Dynamics AX4.0 and AX2009

I found this Compatibility Testing results from the AX Sustained Engineering blog. Thought its worth to share it with others.

Friday, October 15, 2010

AX4.0 to AX2009 Upgrade (Functional)

Scenario (Functional Upgrade)

• Your task is to upgrade the current AX version to AX2009 in Production environment.

• The existing system contains lots of customizations on different layers, so a functional upgrade is required.

Below are the steps that you will perform:

1. Take the backup of AX4.0 database.

2. Take the backup the application files (*.aod, *.ahd, *.ald, *.add, *.khd) from Drive:\Dynamics AX 4.0\Application\Appl folder for layers BUS, VAR, CUS, USR and respective patch layers. Please make sure to copy the files only for the respective configuration. If using standard configuration, the path should be Drive:\Dynamics AX 4.0\Application\Appl\Standard. We are doing this because of customizations exist in these layers and we need to take them over to AX2009.

3. Also backup the application files (*.aod, *.ahd, *.ald, *.add, *.khd) from Drive:\Dynamics AX 4.0\Application\Appl folder for layers SYS, GLS. Please make sure to copy the files only for the respective configuration. If using standard configuration, the path should be Drive:\Dynamics AX 4.0\Application\Appl\Standard. The whole idea is to compare the previous application code with the new one while upgrading.
4. Next step is to run AX2009 setup from available media.

5. During installation when asked, select the existing AX4.0 database.

6. After the installation is completed, install AX2009 SP1 if required.

7. Do not start AX2009 AOS instance already created.

8. Now put the application files you took backup in step#2 to Drive:\Microsoft Dynamics AX\50\Application\Appl\. If found, delete the axapd.aoi file from the “Appl” folder. The update index file will get created once we will start the AOS in later step.

9. Create a folder named “Old” in AX2009 application folder (for example Drive:\Microsoft Dynamics AX\50\Application\Appl\\Old) and copy the files from step#3 into the “Old” folder.

10. Start the AOS for AX2009.

11. Start AX2009 client. The Upgrade checklist will get displayed. Complete the steps to continue upgrading. If you stuck in any issue, refer to AXUpgradeGuide.pdf file from partner source.

My next post will point out some of the lessons learned while upgrading.

Wednesday, October 13, 2010

AX4.0 to AX2009 Upgrade (Technical)

While upgrading from source (AX4.0) to target (AX2009) AX version, there are two possible types of upgrade:

Technical Upgrade
This type of upgrade is performed when there are no new customizations or product features are required.This is the most straight forward upgrade and usually take like a week or so to get completed.

Functional Upgrade
Mostly, the upgrades fall into this category as customers want business specific customizations or new product features. Depending upon the complexity of required customizations, the upgrade time will vary. Required new features are handled outside of the Upgrade project as a separate project.

Scenario (Technical Upgrade)

• Your task is to upgrade the current AX4.0 version to AX2009 in Production environment.
• The existing system does not have any customizations, so a technical upgrade is required.

Below are the steps that you will perform (these steps were practically implemented so slight variations may exist depending upon your scenario):

• Take the backup of AX4.0 database.
• Backup the application files (*.aod, *.ahd, *.ald, *.add, *.khd) from Drive:\Dynamics AX 4.0\Application\Appl folder. Please make sure to copy the files only for the respective configuration. If using standard configuration, the path should be Drive:\Dynamics AX 4.0\Application\Appl\Standard.
• Next step is to run AX2009 setup from available media.
• During installation when asked, select the existing AX4.0 database.
• After the installation is completed, install AX2009 SP1 if required.
• Start AX2009 AOS instance already created.
• Start AX2009 client. The Upgrade checklist will get displayed. Complete the steps to continue upgrading. If you find any DB synchronization errors for Dimension* tables, this is a known issue. Refer to AXUpgradeGuide.pdf on partner source to fix this issue.

In the next post, I will mention the workflow for functional upgrade using a practical scenario.

Sunday, October 3, 2010

Microsoft Dynamics Sure Step Methodology (Useful resources)

A couple of useful resources if you are preparing for Sure Step methodology:

The exam syllabus is here http://www.microsoft.com/learning/en/us/exam.aspx?ID=MB5-858#tab2

Get to know the Sure Step role-based learning roadmaps: https://mbs.microsoft.com/partnersource/partneressentials/serviceplans/surestep/

Work through the Introduction to Sure Step eLearning ( http://go.microsoft.com/fwlink/?LinkID=182558&clcid=0x409 ) and Using Sure Step on-demand courses ( http://go.microsoft.com/fwlink/?LinkID=182559&clcid=0x409 ). You need to be an MS Dynamics Partner with active plan to see these.

If you can download the 80199 or 80235 training courses from PartnerSource and work through those, it would be really helpful.
Go through everything on https://mbs.microsoft.com/partnersource/surestep

There is an online test/assessment http://go.microsoft.com/fwlink/?LinkID=181000&clcid=0x409