I'm assuming you are referring to Sage 100 ADVANCED, not STANDARD? The command line in the other thread is specifically for Sage 100 ADVANCED. If you are truly using Sage 100 Advanced, look at the menu shortcut for any other computer that already has the client installed (note that you must install it to get all the required programs in place for Sage 100 Advanced - the shortcut command line only runs the program, it doesn't install it).

And now after doing a little research, I understand what RemoteApp is. Never knew that RDS had this feature. Always thought you had to use Citrix to get that effect. Time for some experimenting.

My client has Sage 100 Standard 2014 currently installed. I have installed the workstation client on the RDS server and it works from from an RDP session (just like the user in the post I mentioned in my original post). I'm getting the same issue where the ProvideX Application Development Environment CLI launches instead of the actual application. I will look at the shortcut on another workstation and see if I can pull the command line.

The reason we are using RemoteApp is so that the remote users can use their local desktops and just launch the application like they would if it was locally installed, but instead it runs the application in an RDP session.

Ok, Thomas, you helped steer me in the right direction. On the RDS server itself I went into the properties of the shortcut file and I found the start-up argument, which was very similar to the one from the other poster, and it worked.

Can you share more details on how you got this to work? I have the same issue running Sage 100 Standard 2016. I've tried using the command line argument from the sage shortcut on my desktop: -hd ..\launcher\sota.ini ..\soa\startup.m4p

However, when I use that argument, I get: "Unable to initialize lead program. Error #12: File does not exist (or already exists)"

Which arguments did you use to get RemoteApp working?

blazeboy, are you using server 2012 r2? I think I recall getting that error and I had to turn on compatibility view for the application to launch properly. You need to make sure that after you install the application on your RDS server to get it to work locally first.

onIT, thanks for the quick response! I'm actually using Windows Server 2016. I tried setting Compatability Mode on pvxwin32.exe. I clicked "Change Settings for all users" and then selected various combinations of Compatibility Mode for Windows 95/98/XP/7/8, as well as Run as Administrator -- I still get the same Error #12: File does not exist (or already exists). Which Compatability Mode are you using?

Are you using the same command line argument that I am? -hd ..\launcher\sota.ini ..\soa\startup.m4p

This issue was resolved with Windows Update: KB4041688

NOTE: Installing latest Windows Update should also resolve issue. Fixed in Windows Server 2016 OS Build 14393.1794 or higher. (How to find OF Build:  Go to Start, Run; Type: Winver; Select OK)

October 17, 2017—KB4041688 (OS Build 14393.1794)

• Addressed issue where the working directory of RemoteApps on Server 2016 is set to %windir%\System32 regardless of the application's directory.

To get the standalone package for this update, go to the Microsoft Update Catalog website

Confirmed by:

Nathan Shaw
Sage Support Analyst