Skip to main content

How to run AX2012 HyperV on Virtualbox (Step by step guide)

    Download virtual box and the extension pack.

Once you have installed, create a new virtual machine.

Select Windows 2008 64bit

Allocate a good portion of memory (4GB recommended)

Un-tick the boot Hard Disk. Add disks manual after the wizard is finished.

6. Click on your new virtual image settings

Navigate to Storage
Add hard disks by clicking the disk icon – then “Choose existing disk”
Repeat this step for all 3 vhd files.
·         AX5-W8R2-01.vhd
·         AX5-W8R2-01_DB.vhd
·         AX5-W8R2-01_PF.vhd

After you have finished. Settings should look like this:

9. Start your image

Configure sharepoint 
After you have managed to get it to start, there are a couple other things to be aware of:
1. Start the AOS by going to the windows services and start manually
2. All seems to work except for Enterprise Portal
To fix this modify your hosts file “C:\Windows\System32\drivers\etc\Hosts”
Open this file with notepad and add in the line
It should look like this:

3.  When you run a report - it will be slow on first run. Don't kill it; leave it for a few minutes. Mine took ~4minutes to run first time. After that, it is very responsive. Standard SSRS caching.

Update 07-10-2011:
RTM version of the image uses



Popular posts from this blog

Dual Write - How Pricing and Inventory On-Hand works in CE?

In the recent updates of Dual Write, Microsoft released a pricing and inventory on hand integration in CE. Real time pricing calculation and inventory on hand as per FinOps business logic. In this post, I wanted to cover how it seems to magically work. As you know by now, Dual Write uses a push architecture. Where either FinOps pushes to CE or CE pushes to FinOps. Both call a web service on the other side to sync data. Any errors that occur are presented to the user in real time. However, the pricing and inventory on-hand feature is different. These two features pull limited calculated data as needed. Watch the " Prospect to cash in dual write " tech talk from Microsoft and you will see why.  You wouldn't want to integrate (replicate) inventory levels or pricing logic in CE. The reason this is done this way is because integrating this kind of data would cause performance problems or a lot of chattiness. So, what Microsoft has done is a pull the data as needed (pull archit

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds