Hello community. I am wondering about the best way to install and configure AX 2012 R3 clients for over 200 network PCs. Here is what I've tried and the issues I've run into:
I have create a computer startup script via group policy to remotely install the AX client. That script is as follows.
"%~dp0setup.exe" RunMode=Custom AcceptLicenseTerms=1 HideUi=1 ByPassWarnings=1 InstallClientUi=1 ClientConfigFile="\\server\share\PROD_AX2012R3_x64.axc" ClientLanguage=en-us ConfigurePreRequisites=1 LogDir="C:\logs"
The issue I have with this is that it fails as apparently the \\server\share is not supported in the installation script. That's according to the errors in the DynamicsSetupLog.txt file. This is a computer startup script as my users do not have admin rights, so running the install at logon is not an option. Since it is a computer startup script, the use of a mapped drive for the configuration file is also not supported. In other words, I have tried this:
net use A: \\server\share\PROD_AX2012R3_x64.axc and then set ClientConfigFile="A:\PROD_AX2012R3_x64.axc", but this won't work because the install is attempted without a user logging into the system. So the errors in the DynamcsSetupLog is that the system can't find the shared configuration file. If I were to logon to the computer as an admin and run the script with the mapped drive, it runs without issue.
What will work is removing the ClientConfigFile= part and using ClientAOSServer=<AOSServerName>. The problem with this approach is that I haven't figured out how to add multiple (clustered) AOS servers using that variable. Otherwise, the install works fine that way, just no load balancing.
So my questions are as follows:
1. Is there a way to allow for a remote install that can point to a shared configuration file at computer startup time?
2. Is there some way I can change the original configuration en masse so that when a user clicks the Dynamics AX Client link they point to the shared configuration file - or whatever way would allow for them to point to all clustered AOS servers for load balancing.
I am also interested in number 2 as I have a number of users pointed to our TEST environment need to find some way of pointing them to our PROD servers when we go live. I do not want to visit each PC, and I don't believe I'd be able to change the configuration as the users do not have admin rights (original configuration would be grayed out). I know there is a registry setting to change the AOS server, but again, I don't know how to modify that registry entry to add multiple AOS servers to the configuration.
And, yes, I can give users a link to the shared configuration file, but I want them to go to the correct load-balanced environment when they click the Dynamics AX program icon.
Regards,
-Steve
