# [ ax2012 ] calling Ax32.exe instead of AxHLink.exe

Since AxHLink.exe will limit to only the default configuration, we will call the Ax32.exe that is more open to various configuration instead.

To do that,

AxHLink.exe Dynamics://0?DrillDown_5637192587

we use startupCmd parameter of Ax32.exe

&quot;C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin\Ax32&quot; &quot;C:\path\to\configuration.axc&quot; -startUpCmd=DrillDown_5637192587

Note that we can find multiple feature of startUpCmd under Switch section of the following class ( as explained in MS ref )

\Classes\SysStartupCmd\Construct

Note2 : allow all arguments to pass from the client is risky, so it is better to call to .bat or .lnk instead of calling directly to ax32.exe

# [ ax2012 ] dynamics protocol

[HKCR\dynamics]

URL Protocol=””

[HKCR\dynamics\Shell\Open\Command]

ref : http://stackoverflow.com/questions/3468000/problem-setting-up-custom-url-protocol-on-windows-ce

NOTE: to open RemoteApp ( .rdp ), use mstsc command, for example

(Default) = mstsc.exe &quot;D:\AXHLink.rdp&quot;

or if we would like to pass parameter, just use the simple batch file and point the link to batch file

(Default) = D:\AXHLink %1

batch file that append remoteapplicationcmdline:s:

@echo off
call D:\\AxHLink.rdp
If there is only one Ax instance, we have to set in the RemoteApp Manager of Client.
If there is more than Ax instance, save the Ax configuration to (.axc), then point the Path of RemoteApp Manager to .axc file.