• Microsoft Dynamics Ax 2012 Logical Architecture
• Microsoft Dynamics Ax 2012 Visual Studio

This topic provides information about how to work in and maintain a Microsoft Dynamics AX 2012 R3 deployment on Microsoft Azure.

I have downloaded the AX 2012 virtual machine and am trying to figure out what my best option is. I have a server that does not have the architecture to handle a Windows Server 2008 R2/Hyper V x64 installation and am considering purchasing a new server for training/demo purposes. Is the only known method to run the AX 2012 virtual machine in this environment and if so, has anyone had experience as to the minimum recommended requirements for this to actually run (i.e. RAM, processor, etc).

Microsoft Dynamics Ax 2012 Logical Architecture

• Look at most relevant Dynamics ax 2012 vhd install websites out of 4.05 Thousand at KeyOptimize.com. Dynamics ax 2012 vhd install found at mbs.microsoft.com.
• Mar 27, 2013 Munib Ahmed posted an excellent step by step guide how to run an existing virtual machine on Hyper-V into Virtualbox.

Any ideas or experiences that you can share are greatly appreciated. Regards, Diane. Hello, Indeed Martin is once again correct.

I need not say more, and you can quite happily build a desktop for a reasonable price (un-inclusive of operating system or peripherals) that would suffice for single-user testing. However as a personal recommendation:. a reasonable spec processor e.g.

Ivan Cole, 4 March 2015 , The February 2015 release of Life Cycle Services (LCS) marks one of the remaining key customer implementation milestones. Until the latest release of LCS machine names were system generated.

C-media. Although each was identified by a machine type prefix there was no way to force a naming convention. For example at UXC Eclipse we have naming conventions we like to implement by environment type. Here is the comparison example of the machine names that were previously generated as compared to what is now possible.

Previous Auto Generated Machine Name New Custom Machine Name Description SQL-78919d6e63a AXDT-SQL-1 Database server AOS-4d6fb320af7 AXDT-AOS-1 AOS Server AOS-75ef871a238 AXDT-AOS-2 AOS Server CLI-f85a935f924 AXD-DEV-1 Client Although there were some networking techniques to work around this issue, it is obvious that this improvement offers the level of flexibility that customers and partners expect when they access Microsoft Dynamics AX virtual machines on Azure. In my previous blog we focused on the progression of significant enhancements and milestones that make using Life Cycle Services the only logical platform for Microsoft Dynamics AX customers. This latest release represents one of the remaining important enhancements in functionality as Microsoft extends Lifecycle Services for real world customer scenarios for Microsoft Dynamics AX customers. This article will walk through the steps to configure and generate a Dev/Text environment from Lifecycle Services using custom machine names. This latest release empowers Microsoft Dynamics AX clients to replicate their exact environment configurations using their standard internal virtual machine naming conventions.This entry assumes that you have a Windows Live login and have been given access to the.

Since previous articles have already walked through the process of creating a new LCS project we will start at the point at which you would build your Cloud Hosted Environments from your LCS project and your Azure subscription is already linked to your LCS environment. Here are the steps to configure and generate a Dev/Text environment from Lifecycle Services using custom machine names. 1 – Select the Cloud Hosted environments tile and select the Add plus sign to create a new environment. Currently there are Demo and DevTest Environment topologies available. Production on Premium Storage are in beta now and will be releasing shortly. 2- Next select the topology type from the available choices. There are a number of new options on the topology list within LCS that offer the flexibility to support many scenarios that are typically required when configuring a Dynamics AX environment.

Since each option gives you the ability to integrate into an existing domain infrastructure and environment you can always add-on additional environments to the existing domain and network created in earlier builds. For this example we are going to create a DevTest Environment integrated to an existing domain controller already running in Azure. There are a number of new options on the topology list within LCS that offer the flexibility to support many scenarios that are typically required when configuring a Dynamics AX environment.

Since each option gives you the ability to integrate into an existing domain infrastructure and environment you can always add-on additional environments to the existing domain and network created in earlier builds. For this example we are going to create a DevTest Environment integrated to an existing domain controller already running in Azure.

3 – Select the Advanced Settings button to customise the environment settings. In this scenario we will create a DevTest environment joined to an existing domain, the one we used when we stepped through how to integrate with existing domains in the previous article. For this example we will not need a Domain Server since it already exists and is running on Azure in our region.

Microsoft Dynamics Ax 2012 Visual Studio

We are going to generate 2 AOS servers so we can isolate one for Development and the second for Test. 4 – Lets select our existing domain in the domain customisation settings. 5 – Next we need to specify the existing domain passwords for the pre-defined AX installation service accounts.

Please note that creating these service accounts and the related security permissions were outlined already in our previous blog article in the hyperlink at the beginning of this document. 6 – Now we can customise each VM series using existing company naming conventions. If more than one VM of a type is indicated on the Environment Topology settings, the start Index is appended to the VM name and incremented for each subsequent VM created. 7 – We need to select an existing network that is the same as our existing Domain Controller in the region as our connected subscription.

8 – Once all of our customised settings are completed we can deploy to Azure. Once we deploy, LCS will show the status of Deploying from the LCS Project Dashboard. Selecting the environment in the LCS dashboard will show you details of the build process.

As the process advances you will see different machines appear as LCS works through the installation steps from the. After all of the virtual machines are deployed additional installation steps are automated by LCS.

First SQL settings are applied, AX Databases are created, and AOS instances are installed. You will see these stages on the environment details page. When all of the images are fully installed the overall status will be changed to Deployed. We are now ready to login to the Development client as the DomainNameDynamicsInstallUser to begin the initialisation checklist. Microsoft Dynamics AX is ready to go!! If we login to Active Directory Users and Computers we can see that the machines were created in the Computers node in Active Directory using our friendly naming conventions. In this article LCS automatically generated a complete 4 machine Dev Test environment using all of our customised settings and machine naming conventions.

These newest advancements allow for real world customer installation environments and represents one of the final milestones making LCS ready for live production usage scenarios. Never Miss An Update! Follow our Blog Here.