Have you made any further headway with this idea.

I'm starting to check out cloud services as well; with the same thought in mind.

We are currently using Sage 100 v4.4 with DM2 add ins in the Azure Cloud and use RDS to connect. We have also been testing Sage 100 v2016 in the same environment. The Number one thing I can telly you is to BE SURE TO USE PREMIUM STORAGE. The IOPS and Latency is a real problem in a Standard storage account BLOB whereas a Premium Storage account has an SLA which guarantees spectacular latency and IOPS. Microsoft has gone as far as to say that no data heavy production servers should ever be in a Standard Storage BLOB.

There are also some definite hoops to jump through, but they are mostly the same as the ones that you would deal with on a RDS VM hosted anywhere else:

-The ForegroundLockTimeout set to 0 in the registry fix
-Open up the correct port in the Windows firewall on the servers
-When you publish the RemoteApp, use the workstation pvxwin32.exe location on the RDS server and check the "Always use the following Command-line parameters" Radio Button. Use this string (with Quotes) and enter your server and port where specified: ../launcher/sota.ini *Client -ARG "<Server Name>" "<Port>" "MAS 200"
-If you plan to use Redirected Printers (not recommended) be sure that nobody has the "Sage PDF Converter" printer installed on their PC. This will stop it from working on any version.
*Paperless office will not function on Windows Server 2012 R2 RemoteApp Servers.


If you need any additional advice or have any questions, let me know. I will try to help as best as I can.

We have same issue with printer redirection, when we print 10 check its fine but if we try to print 20 30 checks Sage gets crashed.

We are using Azure Premium Storage with 32GB disk space so IOPs is 120 and throughput is 25 MB/s.

Do you think if we change storage to 64GB (IOPs 240 and throughput 50 MB/s) could solve the issue??

Thank you in advance.