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 :
Finance | Project Operations, Human Resources, ...
Suggested Answer

MS Dynamics GP 2018 on Azure - RDS Terminal Server Architecture on Azure for GP client access

(0) ShareShare
ReportReport
Posted on by 5

Dear All,

I am planning to lift & shift a customers Dynamics GP 2018 standalone physical server from on-premises to Azure. I have planned to architect the network connectivity using Site to site VPN connectivity. Approximately 3 users connect using the GP 2018 thick client to the GP server on-premises and the same no of users will connect once migrated to Azure.

I have read that the GP 2018 client is heavy client/server application which is not supported by Microsoft for on-premises connectivity to GP server on Azure. In that case is a RDS infrastructure on Azure the only option available for client connectivity to GP server for these 3 users? What are the desired RDS components required on Azure and VM sizes? How will this work?

Also the current GP server is running 6 physical cores/24GB RAM with avg CPU utilization of 2% and 80% memory. What should be the right VM size recommended and disks?

Pl advice.

Regards,

Savio F

Categories:
I have the same question (0)
  • Suggested answer
    Derek Albaugh Profile Picture
    on at

    I'm sure the only thing we've 'officially' tested, with Dynamics GP on Azure, would be the same type of VMs as we'd see on a non-Azure environment, such as one VM for the domain controller, one for the SQL Server and another for the applications server, or something along those lines.

    I know that there's many different configurations that customers are using, so hopefully others in the Community will share their expertise in what you're asking from their experiences.

    Thanks

  • Suggested answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Hi Savio,

    Basically you're not doing anything different when moving your on-prem infrastructure to Azure... The typical setup would include a SQL server, 1 RDS server and possibly some Web Proxy server, but in your case you seem to want to setup a permanent VPN link between the on-prem network and Azure.. which also means that you might already have a domain controller in your network, and all you need to do is setup AAD Sync to synchronize the user accounts for login between your AD and Azure.

    IMHO your SQL server setup was overkill for 3 users.. but I don't know your infra or other processes, but at 2% of CPU use, it's clearly underused. RAM usage is not an indicator, as SQL be default will typically grab 80% of the whole server RAM, unless told otherwise.

    For 3 users accessing GP, 8-12GB of RAM should be plenty enough with 4 vCPU's or less. The RDS server would also be typically 8-12GB to accomodate 3 remote users and that should be plenty enough for now. You can always switch to a bigger VM size in Azure if it turns out to be overloaded... which I doubt.

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 > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 592 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 478 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 305 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans