Unable to run Sage 100 as a RemoteApp on Windows Server 2016
Description

Workaround:

Run Sage 100 as a RemoteApp on Windows 2012 Server

Cause
  • The working directory of RemoteApps on Server 2016 is set to %windir%\System32 regardless of the application's directory
Resolution
[BCB:1:Backup warning:ECB]
[BCB:4:Operating system warning:ECB]
[BCB:5:Third-party support:ECB]

This issue was resolved with Windows Update: KB4041688 (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

or

Install latest Windows Updates

DocLink: How to Publish Sage 100 as a RemoteApp on Windows Server 2012 or higher
DocLink: What virtual platforms or virtualized operating systems and environments are supported for Sage 100?
Defect ID
106941
Steps to duplicate
Related Articles