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 1 Discover 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 running a RDS Windows 2016 and I wanted to know if someone else
had tried it out and experienced slow responds from the AOS/Database?
We are aware that Windows 2016 is not a supported OS for this version,
Current setup is a Windows 2008 Terminalserver where it all works fine,
im aware that the Axapta version should be updated,but this is the situation
at the moment, any tips or information is appreciated.
A lot of people, reported similar experience.
Use perfmpn and or maybe the trial of datadog https://www.datadoghq.com/
check the power setting is High in the bios.
""We get a lot of “slow performance in RDP session” cases
Se his informative post by RDS product group. The article goes into great detail on how to use the new performance counters to troubleshoot slow performance, including how to add and configure counters, how to analyze and understand captured data, and provides example of what an overloaded system looks like . The new counters are available through Windows Insider Program.
•Use performance counters to diagnose app performance problems on Remote Desktop Session Hosts - docs.microsoft.com/.../rds-rdsh-performance-counters
•Windows Insider Program - https://insider.windows.com/
Hello John Wallys,
If you are still on AX4.0 is an upgrade to a more recent version (D365FO) an option?
AX4.0 is already out of support and rather than spending time on fixing an old system wouldn't an upgrade be the better option?
AX 4.0 is very old version. Are you not considering upgrading it? That should be there in your roadmap. I would suggest upgrading AX 4.0 to latest version and get all the benefits.
Thanks for the information @Magic1949 i will look into this.
Ludwig Reinhard This is not the information we looking for, we are aware of the option to upgrade, which as of this moment is not viable.
Khushhal Garg This is not the information we looking for, we are aware of the option to upgrade, which as of this moment is not viable.
I can understand where you are coming from but just be aware that running the software on a non support OS might have unforeseen issues. If your local partner cannot fix any issue on this config and have to escalate it, Microsoft will not bother trying to fix it and just inform you that the OS is not supported. I'm gonna assume you are also using the DB in compatibility mode since its actually maybe a much older sql version. Though it may work fine, you're in uncharted territory.
I am sure most of us would like to know your journey and how it works out. Good luck to you.
I want to share my experience with AX4.0 on Windows 2016 environment.
Last year(2019) we moved a large customer to new servers ( on Azure platform) . AX4 AOS servers remained on Windows2008R2 servers, but the clients were running on Windows2016 servers, with XENAPP-Citrix on top of the RDP servers. It required some tuning from Xenapp , but finally we got it all working, except 1 issue that remained with printing in AX4.
Problem : Local printers from the client, that were created in the Citrix-client sessions and the "default printer" could not always be detected in the AX4 client as it was in previous windows server versions. Windows 2016 is acting differently,using some different registry entries.
As AX4 was already end of life and we were using AX4 in an 'unsupported setup' , Microsoft has not taken this problem as an issue, and did not provide a solution or workaround.
After 6 months it was decided to switch back to Windows 2012 servers for the XENAPP/Citrix to resolve the printing issue.
Business Applications communities