Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have a terminal server for all users to remote in and run AX, how to setup default client configuration for all users?
I setup one, but that apparently only works for myself.
You need to export the client configuration as .axc file from the client configuration utility. Then place this file on a network share.
Then make shortcut for all your users, which launches ax32.exe and points also to the .axc file.
The Target of the shortcut should be something like this:"C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin\Ax32.exe" "\\myFileShare\myAXConfig.axc"
To make it seamless, as Nikolaos said, you will have to export the configuration file (.axc) and then configure every user shortcut to point to it.
If the users have more than one environment to access, you can just let them open the .axc files directly from the shared folder.
Thank you guys, we had same shortcut as you guys said, which is working fine.
There are other shortcut just pointing to 'AX32.exe', which should pick up default config, I want to make them work for everyone, but I guess that's profile related, no way to do it.
.axc file is the way to manage it centrally. You can also update this one file easily if server names change, or you want to direct the clients to another (disaster recovery) system.
Business Applications communities