Microsoft Dynamics AX (Archived)

Dynamic AX on RDS Session Host is very slow

(0) Share

Report

Posted on by ThomasMonesi

110

Hi,

I have a RDS Farm 2012 with 2 Session Host on primary site and 1 session host on a remote site.

When I open AX client on remote session host, the connection is very slow, all other program run normaly. My partner AX says that the RDS Farm MUST stay ONLY on primary site on AX environment, but it's a problem for me because in the remote site I have a remote printer server and dfs server, for this I can't move my session host to primary site.

My question Is: is "the RDS farm must stay only on primary site" a requirement for AX Environment or simply my partner AX hasn't a solution for my problem ?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

dekaasboer 1,530 on at

Like (0)

Report

There can be a lot of data transfer depending on your operation. 6 mbit is not a lot.

You could reduce some traffic by turning of preview panes and factboxes. And maybe you could gain something by creating a custom client config for slow connections.

Was this reply helpful? Yes No
ThomasMonesi 110 on at

Like (0)

Report

OK, 6 mbits is not a lot, in fact i ask a 20 mbps for the future, but i need to know if terminal farm must stay only on primary site for AX environment requirement or not, because my partner AX says this.

Thank's a lot for your reply

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,953 Most Valuable Professional on at

Like (0)

Report

The problem may not be in throughput at all but in latency. AX client is quite chatty and especially some forms can generate a huge amount of RPC calls. If latency isn't perfect, the delay multiplied by number of calls easily render the system unusable.

There is no technical requirement to have AOS and clients on the same site, but there is a requirement for a really good connection. It usually means keeping them close to each other.

Was this reply helpful? Yes No
Rudi Hansen 4,075 on at

Like (0)

Report

I would say your partner is right it is best to keep the RDS farm on the same location as the AX environment.

So the question is why don't you map the printer and dfs server to the RDS farm?

I know its possible to map the printer, but i am not sure about the dfs server, what do you need to use the dfs server for?

Is it just a file folder you need access to, then that should also be possible.

Was this reply helpful? Yes No
Guy Terry 28,924 Moderator on at

Like (0)

Report

The system requirements document says "In a WAN environment that has more than 100 milliseconds peak latency, you must use Remote Desktop Services to deploy Microsoft Dynamics AX Windows clients."

I think that means if your WAN has more than 100 milliseconds peak latency you should run the client on the LAN, and use Remote Desktop (where the RDS should be on the LAN).

Putting the RDS on the WAN is no different to running the AX client directly on a device attached to the WAN.

Was this reply helpful? Yes No