Microsoft Dynamics AX (Archived)

Microsoft Dynamics AX 4.0 on Windows 2016

(0) Share

Report

Posted on by John Wallys

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.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Verified answer

guk1964 10,888 on at

Like (1)

Report

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.

docs.microsoft.com/.../rds-rdsh-performance-counters

References:

•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/

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

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?

Best regards,

Ludwig

Was this reply helpful? Yes No
Khushhal Garg 1,514 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
John Wallys 7 on at

Like (0)

Report

Thanks for the information @Magic1949 i will look into this.

Was this reply helpful? Yes No
John Wallys 7 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
John Wallys 7 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
real_ashwin 1,225 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Plouis 22 on at

Like (1)

Report

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.

Was this reply helpful? Yes No