This new feature improves the local resources management of a MulitPress Client application executed with Windows Remote Desktop Services. 

Windows Remote Desktop Services allows users to open a Windows session or a RemoteApp, inside and outside the company network. By doing this, users can connect to their applications from everywhere through an internet connection. When the application is not optimized for Internet bandwidth usage, Remote Desktop Services are often used to limit it: no data is exchanged between the application and the server but only screen changes.

The standard architecture

When a MultiPress Client application connects to a MultiPress Server application, it checks that the application source code on the client side is the same as on the server side. If necessary, the MultiPress Client application then downloads the application source code from the MultiPress Server and stores it in the user folder

\Users\{UserAccount}\AppData\Local\MultiPress\MultiPress_IPsessionID\
E.g. C:\Users\John Doe\AppData\\Local\MultiPress\MultiPress_192_0_0_1_19813_180\

So, when several users open the same MultiPress Client merged application on a Windows server with Remote Desktop Services, local resources are downloaded by each user in its own user folder. There is then a copy of the same files in each user folder.

New architecture as of version 5401

To improve storing and transferring local data, a new option has been integrated into this latest version of MultiPress.

As of this release, the MultiPress Client will use the local resources placed in this shared path:

\ProgramData\MultiPress\MultiPress_IPsessionID\
e.g. C:\ProgramData\MultiPress\MultiPress_192_0_0_1_19813_948\

Keep in mind

So keep this modification in mind, in case Remote Desktop Services is used the users need permissions to access the ProgramData folder, need read, write and modify permissions on this shared folder. So always announce this to your IT party before the upgrade takes place to avoid downtime after the upgrade.