RemoteApp program does not save settings in roaming profile

Issue: A RemoteApp application does not retain settings when users have roaming profile.

To reproduce the issue: Start the application, make changes and exit out. Next time you start it, it will not retain the settings.

 

Solution: Remoteapp default setting is to disconnect the session whenever a user closes out the application by click on the X at top right corner. The best thing is to exit the Remoteapp program from its menu (Ex: File > Exit)

Or, Group Policy can be  configured to change the default behaviour of Remoteapp.

Enabled the following policy on your Windows 2008 Terminal Server:

Computer configuration > Administrative templates > Windows component > Terminal 
Services > Terminal server > Session Time Limit = ‘Immediately’

 
Set the value to ‘Immediately’

 

Explanation:

This policy setting allows you to specify how long a user’s RemoteApp session will
remain in a disconnected state before the session is logged off from the terminal
server.
By default, if a user closes a RemoteApp program, the session is disconnected from
the terminal server.
If you enable this policy setting, when a user closes a RemoteApp program, the
RemoteApp session will remain in a disconnected state until the time limit that you
specify is reached. When the time limit specified is reached, the RemoteApp session
will be logged off from the terminal server. If the user starts a RemoteApp program
before the time limit is reached, the user will reconnect to the disconnected
session on the terminal server.

If you disable or do not configure this policy setting, when a user closes a
RemoteApp program, the session will be disconnected from the terminal server.