RAID Subsystem – Very important topics when you implement Dynamics AX

With an Enterprise Resource Planning (ERP) system such as Microsoft Dynamics AX 2012, the database server generally stores a very large amount of important data for the business. If this data is unavailable for any length of time, the business could experience significant financial losses. Using a Redundant Array of Independent Disks (RAID) can help reduce the possibility of this loss from occurring. Another important aspect for a database server is fine tuning for optimal performance. A RAID disk subsystem can also be used to help achieve this goal.

RAID refers to a group of two or more disks managed as a single unit to store the data together with additional, or redundant, information to provide recovery if
there is a disk failure. Usually a failed disk in a RAID system can be replaced while the server is still running. This is one benefit of RAID.

NOTE: More Information on RAID can be found on the Microsoft MSDN web site.

Read/Write Performance:

Hardware RAID controllers divide read/writes of all data from Windows and applications such as Microsoft SQL Server into slices (usually 16 KB - 128 KB) that are spread across all disks participating in the
RAID array. Splitting data across physical drives distributes the read/write Input/Output (I/O) workload evenly across all physical hard disk drives participating in the RAID array. This increases disk I/O performance because the
disks participating in the RAID array are all kept equally busy, instead of some disks becoming a bottleneck because of irregular distribution of I/O requests.

Fault Tolerance: RAID provides protection from hard disk failure and accompanying data loss with two methods: mirroring and parity. There are many types of RAID configurations; each is called a RAID level, but only some RAID
levels are typically used with Microsoft Dynamics AX 2012.

RAID 0
RAID 0, which is not recommended for use with Microsoft Dynamics AX 2012, is typically defined as a group of striped disk drives, without parity or data redundancy. RAID 0 arrays deliver the best data storage efficiency and
performance of any array type.

RAID 1
RAID 1 is also known as disk mirroring. This is a pair of disk drives that store duplicate data, but appear to the computer as a single drive. All writes move to both drives of a mirrored pair so that the information on the drives is kept
identical. However, each drive can perform concurrent, independent read operations. Mirroring therefore doubles the read performance of a single nonmirrored drive, while the write performance is unchanged. RAID 1 delivers the
best performance of any redundant array type.

RAID 5
RAID 5 is also known as a Rotating Parity Array. RAID 5 works by striping data and parity across all the drives. Typically RAID 5 arrays offer similar read performance as pure striping, although writes are slower because the parity
information is updated every time. If one hard disk fails, it must be replaced with a new one of equal or larger size and it rebuilds from the parity on the remaining drives.

RAID 0+1
RAID 0+1, is a dual-level RAID and achieves a balance between the increased data availability of RAID 1, mirroring, and the increased read performance of RAID 0, striping. Do not to confuse RAID 0+1 with RAID 10, they work
differently and RAID 0+1 is what is recommended.

For maximum performance configure the database server shown in the following example:
• Two disk RAID 1 for the operating system and database software
• A small, four disk RAID 0+1, or two disk RAID 1 for database logs
• A larger RAID 0+1 for the main database files
o To reduce cost, swap out the RAID 0+1 for a RAID 5. However, this will result in slower performance.

Firewall settings for Microsoft Dynamics AX components [AX 2012]

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

If you use Windows Firewall to help protect your computers, Microsoft Dynamics AX components require the settings in the following table. For more information about Windows Firewall, see the Windows documentation.

Component	Computer	Firewall setting	Notes
Setup	Any	Allow outbound HTTP connections.	To access the documentation that is available from the Setup wizard, you must be able to connect to the Internet from the computer where you are running Setup.
Databases	Database server	Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433.	For more information, see the SQL Server documentation.
Application Object Server (AOS)	AOS server	· Exclude the TCP/IP port that is used by the AOS instance. By default, AOS uses port 2712. Setup automatically creates the inbound rule "Dynamics AX 6.0 –MicrosoftDynamicsAX (RPC)" for the TCP/IP port. · Exclude the services WSDL port that is used by the AOS instance. By default, AOS uses port 8101. Setup automatically creates the inbound rule "Dynamics AX 6.0 –MicrosoftDynamicsAX (WSDL)" for the WSDL port. · Exclude the services endpoint port that is used by the AOS instance. By default, AOS uses port 8201. Setup automatically creates the inbound rule "Dynamics AX 6.0 –MicrosoftDynamicsAX (NetTCP)" for the services endpoint port.	Windows Firewall must be enabled on the computer. Each AOS instance must use a different port number. Note By default, every time that you install an additional AOS instance on a computer, the TCP/IP port number and the services endpoint port numbers are incremented by 1. For example, by default, the second AOS instance on a computer is assigned to TCP/IP port 2713.
Client	Client workstation	Exclude Ax32.exe.	The client uses a TCP port to connect to the AOS instance.
Microsoft SQL Server Reporting Services extensions	Report server	Exclude the port that is used by Reporting Services virtual directories, if Reporting Services uses a port other than port 80.	If you are installing Reporting Services extensions in a perimeter network, you may need to add a firewall policy that enables you to connect to the Microsoft Dynamics AX database. For example, if you are using Forefront Threat Management Gateway (TMG), you must add a Non-Web Server Protocol Rule. For more information, seeConfiguring SQL Server publishing in the Forefront TMG documentation.
Microsoft SQL Server Analysis Services integration	Analysis server	· Exclude the port that is used by Analysis Services. By default, Analysis Services uses port 2383. · If you are using SQL Server Browser, you must also exclude port 2382.	For more information about how to configure access to Analysis Services through Windows Firewall, see the SQL Server documentation on MSDN.
Debugger	Developer workstation	Exclude AxDebug.exe and its target programs, such as Ax32.exe and AxServ32.exe.	The debugger uses a dynamically allocated TCP port.
Enterprise Portal for Microsoft Dynamics AX	Web server	· Enable the Web Server (HTTP). · Exclude the port that is used by the Enterprise Portal website, if the site uses a port other than port 80.	If you do not enable the Web Server in Windows Firewall, you can view the site only from the local server.
Help Server	Web server	Exclude the port that is used by the Help Server web site, if the site uses a port other than port 80.
Enterprise Search	Web server	Exclude the port that is used by the Search web site, if the site uses a port other than port 80.
Web services	Web server	Exclude the port that is used by the services web site, if the site uses a port other than port 80.	External programs use this port to consume the Microsoft Dynamics AX web services that are based on Internet Information Services (IIS).
Management utilities	Remotely managed computer	Enable Remote Administration.	You must enable Remote Administration on computers that are administered remotely by using Windows PowerShell. For example, enable Remote Administration on a computer if you deploy reports to that computer from another computer where Windows PowerShell is installed.
Synch Service	Head-office communications server	· Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. · Exclude the port that is used by Synch Service. By default, Synch Service uses port 16750. · Exclude the port that is used by Real-time Service. By default, Real-time Service uses port 1239.	For instructions, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Synch Service	Store communications server	· Enable Internet Protocol security (IPsec). · Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. · Exclude the port that is used by Synch Service. By default, Synch Service uses port 16750.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Real-time Service		Exclude the port that is used by Real-time Service, if the site uses a port other than port 80.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Retail POS	Store communications server	Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. Exclude the port that is used by Synch Service. By default, Synch Service uses port 16750.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Retail POS	Store database server	Exclude the port that is used by Microsoft SQL Server. By default, SQL Server uses port 1433. On a register that has its own local database, you only need to open the firewall to SQL Server if Synch Service is on a computer other than the register.	For more information, see the PCI Implementation Guide for Microsoft Dynamics AX 2012 Feature Pack.
Microsoft Dynamics ERP RapidStart Connector	Microsoft Dynamics ERP RapidStart Services host machine	· Exclude the executable file for the Microsoft Dynamics ERP RapidStart Connector service. By default, the file is installed in this location: %SystemDrive%\Program Files\Microsoft Dynamics AX\60\RapidStartConnectorService\Microsoft.Dynamics.AX.AppConfig.ConnectorLoaderService.exe · Exclude the endpoint port that is used by the Microsoft Dynamics ERP RapidStart Connector service. By default, the service communicates with the Windows Azure Service Bus on ports 9350-9354, 80, and 443. · Exclude the Windows Azure Cloud Services Protocols.

How to: Export and Import a Model [AX 2012]

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

A model is a set of elements in a given layer. Each layer consists of one or more models. Models can be exported to files that have the .axmodel extension. These files are called model files. Model files are deployment artifacts that can be imported into a model store.

A model is permanently associated with the layer that is created in. If you need to move one of your models from one layer to another, you must create a project from the model in the AOT, export the project as an xpo file, create a target model in the desired layer, delete the original model to avoid having to resolve layer conflicts, and import the xpo file to the target model. If you are moving elements between models in the same layer, you can use the Move to model command in the AOT.

You can use either Windows PowerShell cmdlets or the AXUtil command-line utility to export models to model files and import model files into a model store.

Important

In Microsoft Dynamics AX 2012, element IDs and element handles are assigned during installation. Therefore, you must avoid randomizing element IDs and element handles when you install models. In general, never delete a model and then reinstall it. Always install a model over an existing model. For more information, see Maintaining Installation-Specific Element IDs and Element Handles.

Preparing the system

Drain client connections and validate permissions

1. Drain the client connections to the Application Object Server (AOS) instance that you are working with. For more information, see Drain users from an AOS.

2. Validate that you have appropriate permissions to work with the model store:

   • Administrative permissions on the local computer

   • System Administrator rights in Microsoft Dynamics AX

   • In Microsoft SQL Server:

     • Membership in the Securityadmin server role on the SQL Server instance

     • Membership in the db_owner role in the Microsoft Dynamics AX database

 

Exporting model files

You can export a model file if you want to distribute it internally or to customers. If you plan to distribute a model file to customers, we recommend that you strong-name sign the model. To strong-name sign a model, you must use the Strong Name Tool, SN.exe, to generate a key pair file.

Export an .axmodel file (Windows PowerShell)

1. On the Start menu, point to All Programs, point to Administrative Tools, and then click Microsoft Dynamics AX Management Shell.

2. At the Windows PowerShell command prompt, PS C:\>, type the following command, and then press ENTER.

    

   Export-AXModel –Model <name> -File <Filename.axmodel> 
   
   

   
   

   
   

   This example exports the specified model to a file that has the specified file name.

   
   

   You can use the –Server, –Config, or –Database parameters to specify the environment to export from.
   

   You can also use the -Key parameter to specify the strong-name key pair file to use to sign a model.
   

   For more information, see Export-AXModel.

   
   
3. 
   

   You can also use the Sign Tool to sign the file with a digital certificate, or the AXUtil genlicense command to Authenticode sign a file. For more information, see:
   

   
   
   • 
     

     Sign Tool

     
     
   • 
     

     ISV licensing agreement

 

Export an .axmodel file (AXUtil)

1. 
   

   On the Start menu, click Command prompt.

   
   
2. 
   

   Navigate to the directory for the management utilities. Typically, the location of this directory is %ProgramFiles%\Microsoft Dynamics AX\60\ManagementUtilities.

   
   
3. 
   

   At the command prompt, type the following command, and then press ENTER.

   axutil export /model:<modelname> /file:<filename> /verbose
   

   
   

   This example exports the specified model to a file that has the specified file name.
   

   You can use the [/key:SNK-file] parameter to specify the strong-name key pair file to use to sign a model.

   
   
4. 
   

   You can also use the Sign Tool to sign the file with a digital certificate, or the AXUtil genlicense command to Authenticode sign a file.

 

Importing an .axmodel file

When you import a model, elements in the model that you are importing may conflict with another model in the same layer. In this situation, you can create a conflict model in the patch layer that is associated with the layer that you are working in. You can then resolve the conflicts in the conflict model.

By default, when you import a model from Windows PowerShell or AXUtil, the installation mode is set to display the Model code upgrade checklist when the Microsoft Dynamics AX client starts. If you import a model by using Setup.exe, by default, the installation mode does not display the Model code upgrade checklist. For more information about importing a model by using Setup.exe, see:

• 
  

  Install the Microsoft Dynamics AX databases

  
  
• 
  

  Include cumulative updates and hotfixes in a new installation (slipstreaming)

By default, optimization steps, such as reindexing the model store, are performed when a model is installed for the first time. Optimization steps are also performed if the number of elements in a model increases by more than 50 percent when the model is reimported. For more information, see How to: Optimize a Model Store for Runtime.

Import an .axmodel file (Windows PowerShell)

1. 
   

   On the Start menu, point to All Programs, point to Administrative Tools, and then click Microsoft Dynamics AX Management Shell.

   
   
2. 
   

   At the Windows PowerShell command prompt, PS C:\>, type the following command, and then press ENTER.
   

    

   Install-AXModel -File <Filename.axmodel> -Details
   

   
   

   This command installs the specified file in the same layer that it was exported from.
   

   You can use the –Server, –Config, or –Database parameters to specify the environment to import to.
   

   By default, you will be prompted to install the model based on whether it has been signed. The following table describes the prompts shown.
   

   
   

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   

   Scenario	Prompt
   The model file is not signed.	The model is not signed. Are you sure you want to install this model (Y/N)?
   The publisher is recognized from the digital certificate.	The model is signed by ‘{0}’”. Would you like to continue (Y/N)?
   The publisher was not available from the digital certificate.	The certificate for the model was not recognized. Are you sure you want to install this model (Y/N)?
   The provider for the certificate is unknown.	The certificate for the model was not recognized. Are you sure you want to install this model (Y/N)?

   
   

    

   If the installation fails because of a conflict, we recommend that you rerun the cmdlet, and use the -Conflict Push option to push the element that has the conflict to the related update layer. You can then resolve the conflict. For more information, see How to: Resolve Conflicts After Importing a Model.
   

   For more information, see Install-AXModel.

Import an .axmodel file (AXUtil)

1. 
   

   On the Start menu, click Command prompt.

   
   
2. 
   

   Navigate to the directory for the management utilities. Typically, the location of this directory is %ProgramFiles%\Microsoft Dynamics AX\60\ManagementUtilities.

   
   
3. 
   

   At the command prompt, type the following command, and then press ENTER.

   axutil import /file:<filename> /verbose
   

   
   

   This command installs the specified file in the same layer that it was exported from.
   

   If the installation fails because of a conflict, we recommend that you rerun the command, and use the /conflict:push option to push the element that has the conflict to the related update layer. You can then resolve the conflict.

Drain users from an AOS – AX 2012

Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic describes how to close client sessions that are connected to an instance of Application Object Server (AOS) for Microsoft Dynamics AX. When you close client sessions without force, you are said to drain users. Administrators drain users from an AOS instance before they perform maintenance on the server or take it offline.

 

Important

The following procedure requires that you click the Reject new clients button in Microsoft Dynamics AX. After you click this button, you must not close your client. If you close your client before you click the Accept new clients button, you cannot open a new client session unless you restart the AOS instance by using the Windows Services Management console, or unless you reset Status of the SysServerSessions table in Microsoft SQL Server  to a value of 1.

 

1. Click System administration > Common > Users > Online users.

2. On the Server instances tab, select the AOS instance that you want to perform maintenance on.

3. Click Reject new clients.

4. When you are prompted, click OK to stop the AOS instance from accepting new client connections.

   After 5 minutes, all users receive a message informing them that they must save their work, because the administrator is shutting down the AOS instance. No new client connections are accepted during this time. The server forces client sessions to close after they have been idle for 2 minutes. Client sessions for administrators are never closed. When the number of clients that are connected to the AOS instance is displayed as 0 (zero), you can perform maintenance on the server.

5. After you have finished performing maintenance on the server, click Accept new clients or restart the AOS instance.

Data Import / Export DIXF Framework is not visible as Module

Hi All,

As previous post  i published before with title "Microsoft Dynamics AX 2012 Data Import/Export Framework standalone version for AX 2012 R2 without installing full CU7".

I installed DIXF/DMF for AX 2012 R2 on my machine and it is installed and working properly since it is displayed as module on my system, But when i tried to install it on our test server it is installed without any error is occurred but DIXF /  DMF is not displayed as module on main menu. 

Solution:

Check AOT if DIXF is available or not, 

    - If yes so you can add it to Main Menu as Menu reference 

    - If Not, so please check your installation log may something wrong and re-install it.

Data Import / Export DIXF Framework not is visible as Module

Hi All,

As previous post  i published before with title "Microsoft Dynamics AX 2012 Data Import/Export Framework standalone version for AX 2012 R2 without installing full CU7".

I installed DIXF/DMF for AX 2012 R2 on my machine and it is installed and working properly since it is displayed as module on my system, But when i tried to install it on our test server it is installed without any error is occurred but DIXF /  DMF is not displayed as module on main menu. 

Solution:

Check AOT if DIXF is available or not, 

    - If yes so you can add it to Main Menu as Menu reference 

    - If Not, so please check your installation log may something wrong and re-install it.

How to: Call an AIF Web Service from C# to Create a Sales Order - Sample Code

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using ConsumeSalesOrderService.SalesOrder;

// Add a using statement for the service reference.

using System.Collections;

namespace ConsumeSalesOrderService

{

    class Program

    {

        static void Main(string[] args)

        {

            // Instantiate an instance of the service client class.

            SalesOrderService proxy = new SalesOrderService();

            // Create an instance of the document class.

            AxdSalesOrder salesOrder = new AxdSalesOrder();

            // Create instances of the entities that are used in the service and

            // set the needed fields on those entities.

            AxdEntity_SalesTable salesTable = new AxdEntity_SalesTable();

            salesTable.CurrencyCode = "USD";

            salesTable.CustAccount = "1101";

            salesTable.DeliveryDate = Convert.ToDateTime("2/14/2010");

            salesTable.Payment = "N060";

            salesTable.PurchOrderFormNum = "PO";

            AxdEntity_SalesLine salesLine = new AxdEntity_SalesLine();

            salesLine.ItemId = "1001";

            salesLine.SalesQty = 88;

            salesLine.SalesUnit = "ea";

            AxdEntity_InventDim inventDim = new AxdEntity_InventDim();

            inventDim.configId = "HD";

            inventDim.InventColorId = "01";

            inventDim.InventSizeId = "42";

            // Add the sub-entity instances to their parent entities as an array

            // of the sub-entity type.

            salesLine.InventDim = new AxdEntity_InventDim[1] { inventDim };

            salesTable.SalesLine = new AxdEntity_SalesLine[1] { salesLine };

            salesOrder.SalesTable = new AxdEntity_SalesTable[1] { salesTable };

            try

            {

                // Call the create method on the service passing in the document.

                EntityKey[] returnedSalesOrderEntityKey = proxy.create(salesOrder);

                // The create method returns an EntityKey which contains the ID of the sales order.

                EntityKey returnedSalesOrder = (EntityKey)returnedSalesOrderEntityKey.GetValue(0);

                Console.WriteLine("The sales order created has a Sales ID of " + returnedSalesOrder.KeyData[0].Value);

                Console.ReadLine();

            }

            catch (Exception e)

            {

                Console.WriteLine(e.ToString());

                Console.ReadLine();

            }

        }

    }

}

Microsoft Dynamics AX 2012 Data Import/Export Framework standalone version for AX 2012 R2 without installing full CU7

We have recently released the new version for Microsoft Dynamics AX 2012 Data Import/Export Framework as part of Microsoft Dynamics AX 2012 R2 CU7. We received lot of requests to get the new version for AX 2012 R2 (Base R2 and/or CU1, CU6, hotfixes) without taking full CU7. To make this happen, we have released an application hotfix for DIXF which can be installed on AX 2012 R2 (Base R2 and/or CU1, CU6, hotfixes).  The hotfix does not contain the binary files for the Data Import/Export Framework. You must install the binary files for the Data Import/Export Framework by using the CU7 update installer.

Application Components

The application hotfix contains the application files for the version of the Data Import/Export Framework that was released with cumulative update 7.

Important: This hotfix does not contain the binary files for the Data Import/Export Framework. You must install the binary files for the Data Import/Export Framework by using the CU7 update installer.

Download:

Application files for the Data Import/Export Framework, cumulative update 7 version

Instructions:

To install the Data Import/Export Framework:

1. Install this hotfix using the installer that it ships with.
2. Complete the software update checklist.

Binary Components

You must install the binary files for the Data Import/Export Framework by using the CU7 update installer.

Download:

Microsoft Dynamics AX 2012 R2 Cumulative Update 7 (KB2885603 )

Instructions:

Install Data import export framework Client, AOS and Service components.

http://technet.microsoft.com/EN-US/library/hh538446.aspx%23InstallCU7

CU 7: Install the Data Import/Export Framework (binary)

---

As of cumulative update 7, you can install the Data Import/Export Framework from the update installer. For an overview of the Data Import/Export Framework, see Data import/export framework user guide ( (DIXF, DMF).

Caution

If you have previously installed the Data Import/Export Framework from InformationSource, you must fully uninstall it before installing again with cumulative update 7 for Microsoft Dynamics AX 2012 R2. This includes removing all binary files by using Add/Remove Programs, and the uninstalling Data Import/Export Framework model. For more information see How to: Remove (Uninstall) a Model.

1. Browse to the location where you extracted the files for the update, and then double-click AxUpdate.exe.
2. On the Welcome to Microsoft Dynamics AX Update Setup page, click Next.
3. On the Software license terms page, review the license terms, and then click Accept and continue.
4. On the Select packages to update page, select the components of the Data Import/Export Framework that can be installed on the local computer, and then click Next.
5. The prerequisite validation check runs. Address any issues that the prerequisite check finds outside the installer, and then restart the validation check. When all prerequisites have been found, click Next.
6. If you are installing on the computer that runs Microsoft SQL Server Integration Services, specify a service account and the version of SQL Server that is running. We recommend that you use the AOS service account.

–or–

If you are installing on the AOS computer, specify the name of the server that is running SQL Server Integration Services.

1. On the Review updates to be installed page, click Next.
2. On the Ready to install page, review the summary, select the Automatically restart the AOS instances after installation check box, and then click Install.
3. After the installation is completed, verify that the updates were installed successfully, and then exit the wizard.

 

Imparted from here

Step by Step Guide How to Install Dynamics AX 2012 - Part 1

 

How to Install and Configure Dynamics AX 2012 Components
Over the past few weeks, I was involved in installing and configuring Dynamics AX 2012 Components on couple of machines running Server 2008 and Windows 7 Enterprise O/S.

Thought I will share my experience here in a series of posts covering  installation of all major components of AX 2012 - Database, AOS, Client, EP Components, Sharepoint 2010, Reporting Services and Business Intelligence.

Overall Installation Experience/Highlights: (Good)

a. I can say compared to my previous experiences with installation of Dynamics AX 4.0 and 2009, Dynamics AX2012 is less error-prone and satisfactory even though, the number of Pre-Requisites to be installed is quite a significant one in 2012

b. Validate Pre-Requisite Tool is quite handy which helps one to prepare for installation so that one is not taken by surprise when he/she performs the actual installation of components
c. Summary Report which comes up at the end is quite cool and user-friendly.

Considerations:
a. Requires more computing power in terms of RAM (As per System Requirements Guide it says 4 GB is the minimum). And from my personal experience, I have seen that AOS service (AX32serv.exe at it's peak, especially when you start the service and bring up the AX Client first time, it goes up close to 1 GB).

b. I also tried the fully loaded image from PartnerSource  on a machine which had overall 6GB RAM, allocated 4GB to the VM, but still it was crawling. It took me ages to bring up the AOS Service.

c. Since now the AOD is no longer file based and the models reside in SQL Server, you also need to plan ahead for the disk capacity for your SQL boxes. Standard AX database (Application) along with the model database (AOD) bulks up to 3 GB approx and if you want Contoso DB (Demo Data loaded) you should free up atleast 10 GB.
Ok, Now I will jump start the installation process starting with installation of Database, AOS and Client Components. I had captured the screenshots along the way as this will help me and my peers when we setup DEV, Test, Pre-Prod and Prod Environments.

Initial Setup Screen

Pre-Requisite Validation Utility
Note - Here, I'm just installing the components which are checked below: Database, AOS, Client Components, Debugger (My favorite ;-) and Management Utilities
Tip - I would suggest from my personal experience of installing AX, even though Single-Computer Installation sounds easy and quick but we don't get the proper control here, so I prefer Custom Installation and choose my components, easy to troubleshoot and learn as we go

This screen shows you the list of validation errors which means you need to install the base pre-requisites software before you proceed.
The first error shown below is about the SQL Server Full Text Search is not installed or the service is not running

Launch SQL Server Setup and Install Full-Text Search component

Next, comes the Report Viewer Control. You need to download it from herehttp://www.microsoft.com/download/en/details.aspx?id=6442

Some other pre-requisites which needs to be configured and installed are as follows:

• .Net Framework 4.0 http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718
• Hotfix for .Net Fx 4.0http://archive.msdn.microsoft.com/KB2390372/Release/ProjectReleases.aspx?ReleaseId=4917 (Select the correct hotfix based on your OS 32-bit or 64-bit)
• Open XML SDK for Microsoft Office http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5124
• (Tip - Install OpenXMLSDKv2.msi first and then OpenXMLSDKTool.msi, otherwise it spits out error) 
• SQL Server Analysis Management Objects http://go.microsoft.com/fwlink/?LinkId=130655

• VC++ 2008 SP1 Redistributable (x86) http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5582
• VC++ 2008 SP1 Redistributable (x64) http://www.microsoft.com/download/en/details.aspx?
• VSTO http://go.microsoft.com/fwlink/?LinkId=158918

Please Note, as per the Operating System whether it's Server 2008 or Win 7, it might ask you for some other pre-requisites as well, so I would suggest you run the pre-requisite validator and please don't go by the assumption that the above  links are the ONLY pre-requisites required.
.

Once the Pre-Requisites are installed successfully, you can kick start the Installation

Tip - You can change the location here

Select the Components you want to install, based on your implementation topology you might want to install different components on different boxes. As I'm setting up a Sandbox at the moment, I just installed everything in one box

Didn't thought of much experimenting with Themes so left it as it is.

You can change the database names at this step below if you want to.

Key in the ports for AOS and Services

Note - For demo or training purposes, it's ok to go with network service but when you are setting up for pre-prod or production environments, you should choose a proper service account for AOS Account

This is kinda cool as you have the option below to choose the installation type as Developer, Administrator or Business and accordingly it will bring up the workspace for you after the install. At this moment, I'm wearing the administrator hat :-)

All set and ready to go...

You can take a break now ;-) and come back as this step took me good 15-20 mins time!

I love this :-)

And this too.. The Summary Report comes up quite good (This is a new installation feature in 2012 which is a brief summary of the components installed )

Next, you can go ahead with the Compile Checklist.. One other small nice feature which I like is "Processing..." pop up below, it's quite interactive unlike previous versions, where you don't know what's happening and everything looks stuck

Next, I will be posting my experience on other big components of AX2012 starting with Configuring EP, Sharepoint 2010, SSRS and Business Intelligence. Keep looking at this space!! Till then Happy Dax'ing...

Imparted from here