Accessing Dynamics AX client using Terminal Services

Continuing my efforts to take advantage of virtualization for Dynamics AX deployment, I used Windows Server 2008 terminal services to access AX client application from another machine (with Windows Vista Ultimate). I used the normal procedure of installing terminal services from the following article:

http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/working-terminal-services-remote-applications-part1.html

Using the TS RemoteApp Manager on server machine, I allowed AX2009 client application to be accessed remotely by creating an .rdp file and through TS Web Access. On the client machine, I accessed the terminal server using the URL something like http://servermachine/ts (you might need to use fully qualified server machine name like servermachine.mydomain.com) and was able to see the AX client application listed in the browser window. Just click the application icon and AX client will get opened just like you are accessing it locally on the client machine.

You can also use the application specific .rdp file, change its icon (one that your normally use for AX client) and paste it on the client desktop or leave it on the shared network location as you like.

AX2009 Development Licences

I was asked to clarify how AX2009 development licence works and what are the different development licences one needs to have in order to take complete development environment. Actually, you need to have four development licences:

Base Application: This will allow to have access to UI elements like Menus, Forms.
MorphX Development Suite: With this licence you will be able to see the Data Dictionary and other UI objects (reports etc).
Web MorphX Development Suite: Controls access to web development objects in AOT.
X++ Source Code: This licence allows to have access to Class objects in AOT.