Answered

GP 2018 as a RemoteApp

(0) Share

Report

Posted on by Yamanote235

Hi all,

Looking for some help here as our users would like to get away from having to log into an RDP session to run GP. It seemed like it would be possible to install the client on the users' workstations and run it but when I tried this on my own machine, the loading times make this method unusable. It can take anywhere from 10-15 minutes to load into the home screen and that experience is carried through when selecting other menus. I have read that user customizations or menu access may cause slow load times but I have my own test account with little to no permissions and absolutely no personalized menus so I don't think this is what's happening here.

We run GP 2018 in AWS on Server 2016. I can't seem to find a thorough guide on setting up GP as a RemoteApp so I'm hoping someone can help.

Thanks!

Categories:

Administration and Setup

Install and Upgrade

All responses (9)

Answers (2)

Verified answer

Beat Bucher GP Gee... 28,021 Moderator on at

Like (1)

Report

RE: GP 2018 as a RemoteApp

If you read my blog post, the way I'm suggesting Dynamics GP should be published is through a batch launch file.. which holds all the parameters to run GP properly.

An example is provided in the blog post on how to create it.
Yamanote235 10 on at

Like (0)

Report

RE: GP 2018 as a RemoteApp

@Béat Bucher - Thanks so much for providing this resource! I have a meeting today to discuss some additional challenges for the users when utilizing GP in the TS environment (they mentioned some Excel and PDF formatting issues) but will be looking into this once I have the time today.

In your reply you mention not publishing the Dynamics.exe client by using the wizard. If not by the wizard, how else does the Dynamics.exe client get published to the RDWeb Access portal for the end user to access?

I also have a question. The configuration for our RemoteApps only shows GP once but when I log into the RDWeb page, I see two GP applications. One doesn't work. Its not obvious to me why I only see one published app but then see two in the RDWeb portal.
Verified answer

Beat Bucher GP Gee... 28,021 Moderator on at

Like (1)

Report

RE: GP 2018 as a RemoteApp

Hi Yamanote235,

As a general advice, I wouldn't try to publish the Dynamics.exe client by using the Wizard, and once it's published, the only way to correct it properly is to use PowerShell's RDS addin to edit the parameters you can't edit from the GUI side..

Please read this blog post about how to setup Dynamics GP in a Citrix or TS environment. You want to use an individual DEX.ini file for each user to avoid conflicts..

https://dyngpgeek.wordpress.com/2014/07/25/using-dynamics-gp-in-a-citrix-ts-environment/

Feel free to reach out if you need any help
Community Member Microsoft Employee on at

Like (0)

Report

RE: GP 2018 as a RemoteApp

That error you had seems to be rds error, not gp. You have any windows admin you can speak to
Community Member Microsoft Employee on at

Like (0)

Report

RE: GP 2018 as a RemoteApp

Heres my regular dynamics, no dynamics.set specified in parameters, I only user dynamics.set file in parameter for specific user ie userxxx.set because they have additional addin or use a different reports dictionary. Does it work if you take out dynamics.set
Community Member Microsoft Employee on at

Like (1)

Report

RE: GP 2018 as a RemoteApp

In you server manager for RDS, follow the wizard to publish the app, it should see it as as the list populates

Once its publish, in the parameter, you can set different set files also

Issue is everyone that logs in see last user id, I had so much complain about that, adding dex.ini to users home folder and having shortcut look at home drive; profile \dex.ini to fix that issue.

Also I recommend adding dex.ini to launch short cut. My rds uses this to have individual dex.ini

"C:\Program Files (x86)\Microsoft Dynamics\GP2018\Dynamics.exe" "C:\Program Files (x86)\Microsoft Dynamics\GP2018\Dynamics.set" %userprofile%\dex.ini

community.dynamics.com/.../417694
Yamanote235 10 on at

Like (0)

Report

RE: GP 2018 as a RemoteApp

Justin Sutton -- I'm just getting a chance to look into this and it looks like our old MSP was almost there in terms of configuration. The RemoteApp is configured as dynamics.exe without the dynamics.set. However, this is where I run into an issue. Anytime I try to modify the parameters of the collection/remoteapp, I get the following error:

"Unable to retrieve the session collection properties. Some or all identity references could not be translated."

I'm still looking into this myself but am hoping you're familiar with the error and can point me in the right direction if I don't find the solution myself in the meantime!
Yamanote235 10 on at

Like (0)

Report

RE: GP 2018 as a RemoteApp

Hi Justin, I'll review how to get RemoteApp setup and will give this a shot this week. I appreciate your reply and will get back to you with how things go!
Suggested answer

Justin Sutton on at

Like (1)

Report

RE: GP 2018 as a RemoteApp

Hello Yamanote,

Overall we wouldn't recommend installing the GP Client on the User's workstations. This is because GP requires a constant connection to SQL, and the chances that a user will be able to connect from home, all the way to the SQL Server without dropping a packet is slim. This also increases the travel time of all of the packets, and GP sends a lot of them, you are seeing the performance limitation already. This is partially covered here:

community.dynamics.com/.../working-from-home-with-microsoft-dynamics-gp-general-recommendations-and-troubleshooting

As for Remote App, we don't have any walk-throughs, but if you have published anything else, GP should be roughly the same. Just make sure that when you publish the Shortcut that you are adding in the Dynamics.set on top of the Dynamics.exe. For example, here is what my Shortcut looks like:

"C:\Program Files (x86)\Microsoft Dynamics\GP\Dynamics.exe" Dynamics.set

Let the community know if you need more help.