web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AX client on remote desktop server is slow to open

(0) ShareShare
ReportReport
Posted on by 245

This is Dynamics AX 2012 R2 CU7, latest Kernel.  OS is Win2012 R2.

We have the AX client installed on two AOS servers and one remote desktop server.

On the AOS, the AX client opens within 5 sec.

On the remote desktop server (not remote app), the AX client opens in 46 sec.  It takes 40 seconds before the splash screen shows.

What can I look at to understand why it is taking 40 sec to open? This is impacting all of our users. I read that roaming profiles/user profile disks for the remote app session can help performance but we have a single Remote Desktop server with a single collect and host server, and all of our users' profiles are already created on the disk.

Anything obvious I am missing?  Is it recommended to use profile disks anyways in this case?

*This post is locked for comments

I have the same question (0)
  • BorisD Profile Picture
    2,826 Moderator on at

    Hello pnwguy,

    What are the hardware specs on this remote server and how many users do you have logging on at the same time? Is it a virtual server? Hyper-V or VMWare?

  • pnwguy Profile Picture
    245 on at

    Hi Boris, it is VMWare.  On average we have 50 users using AX in remoteapp, but VM has 48 GB RAM, 8 procs, shared SSD for disks.  The above mentioned elapsed time was measured after midnight when I was the only user logged in, so I don't believe resource contention is the issue.

  • Suggested answer
    BorisD Profile Picture
    2,826 Moderator on at

    Your hardware setup looks good! There is some performance tuning that you should do if you haven't already.

    For the NICs, make sure to Disable “Allow the computer to turn off this device to save power” this is done in the Network card properties, click Configure, click Power Management.

    To see the current TCP settings Open CMD in elevated mode and run: Netsh int tcp show global

    If Chimney Offload State is enabled you can disable it by going to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TCPIP\Parameters\DisableTaskOffload

    Setting this value to one disables all of the task offloads from the TCP/IP transport. Setting this value to zero enables all of the task offloads.

    If DisableTaskOffload key is not there, just Add a new DWORD of DisableTaskOffload to the registry key and set value to 1

    Additionally, set the following TCP settings by Running the following commands in a CMD prompt in elevated privileges:

    netsh interface tcp set global chimney=disabled

    netsh interface tcp set global rss=disabled

    netsh int tcp set global netdma=Disabled

    The following changes are per the VMWare best practice for Latency-Sensitive Workloads in vSphere VMs

    Verified they were using the VMXNET3 cards and disabled interrupt coalescing

    VM Settings > Options tab > Advanced General > Configuration Parameters and add an entry for

    ethernetX.coalescingScheme with the value of disabled

    If you are running VMWare6 without update 2 or older please see some recommendations for performance tuning at link below.

    blogs.msdn.microsoft.com/.../performance-issue-in-vmware-6

    Also see this white paper for best practices for performance tuning of latency-sensitive workloads in vSphere VMs.

    www.vmware.com/.../vmw-tuning-latency-sensitive-workloads-white-paper.pdf

  • pnwguy Profile Picture
    245 on at

    thanks I will have our NOC team take a look at this and make any necessary changes.  Assuming none of this is implemented, would that cause the 40 sec load time that I am seeing?

  • BorisD Profile Picture
    2,826 Moderator on at

    Yes, it can. Since the performance is good on the AOS when running the client, you can start with just changing settings for the RDS. that's the netsh commands I sent you. This alone can improve performance. Also check power settings on the RDS server.

    1. Click on Start and then Control Panel.

    2. From the list of displayed item under Control Panel click on Power Options, which takes you to Select a power plan page. If you do not see Power Options, type the word 'power' in the Search Control Panel box and then select Choose a power plan.

    3. By default, the option to change power plans is disabled. To enable this, click the Change settings that are currently unavailable link.

    4. Choose the High Performance option

    5. Close the Power Option window.

    If changing the power settings helps see the link below to apply necessary fixes. The power settings fix was a workaround to some updates needed for Windows Server 2008 R2

    support.microsoft.com/.../slow-performance-on-windows-server-when-using-the-balanced-power-plan

    How is performance through RDS in your test environment?

    Where you always having this slowness, or did it start recently? 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans