Environment
Reflection Desktop (including Pro, for IBM, or for UNIX and OpenVMS) 16.0 or higher
Situation
When trouble-shooting issues with Reflection Desktop 16 in a Terminal Server / Citrix Server environment, be aware of the effect of Windows Roaming Profiles on the configuration and settings in this environment.
Many times a single Administrative account is used to install and manage Reflection Desktop on a variety of servers (Terminal or Citrix Servers). If this Administrative account is set up to use Windows Roaming Profiles, and used to install and run Reflection Desktop, the Roaming Profile can cause settings to be migrated from one server to another server unexpectedly.
Reflection Desktop 16.1 uses the C:\Users\<adminuser>\Appdata\Roaming\Micro Focus\Reflection\Desktop\v16.1 folder to store important configuration files (application.settings, frame.settings, etc.) and these can get copied to the Roaming Profile of the Administrative user account when it is connected to one server. Then when the Administrative account is logged into another server, the same set of configuration files in the \AppData folder would get reused (since they “roam” with the user from the first server). This will not be a problem, if all the servers and Reflection Desktop is being set up exactly the same. But if the servers and Reflection Desktop are NOT intended to be setup the same, this can lead to incorrect settings and confusion about why Reflection Desktop is not configured and operating as expected.
Resolution
Possible Solution:
Turn off Roaming Profiles for the Administrative account used to manage Reflection Desktop.
Turn off Roaming Profiles for the Administrative account used to manage Reflection Desktop.
Additional Information
Duplication Instructions:
In this example:
Server #1 has Reflection Desktop to be set with Trusted Locations set to ONServer #2 has Reflection Desktop to be set with Trusted Locations set to OFF
1. The Administrative account with Roaming Profile turned on logs into Server #1.
(if this is the first time that Server #1 is accessed by this account, the settings in the C:\Users\<adminuser>\Appdata\Roaming\Micro Focus\Reflection\Desktop\v16.1 folder will not exist)
3. The Administrative account opens the Reflection Workspace.
4. The Administrative user sets the Reflection Workspace settings for Trusted Locations to be ON. (default value)
5. The Reflection Workspace settings are saved and the Reflection Workspace is closed.
6. The Administrative account logs out of Server #1.
8. The Administrative account logs into Server #2.
9. The values saved in the Roaming Profile are copied to the C:\Users\<adminuser>\Appdata\Roaming\Micro Focus\Reflection\Desktop\v16.1 folder on Server #2.
10. The Administrative account opens the Reflection Workspace.
11. The Administrative user sets the Reflection Workspace settings for Trusted Locations to be OFF.
12. The Reflection Workspace settings are saved and the Reflection Workspace is closed.
13. The Administrative account logs out of Server #2.
15. The Administrative account logs into Server #1 again to check the settings.
16 The values saved in the Roaming Profile are copied to the C:\Users\<adminuser>\Appdata\Roaming\Micro Focus\Reflection\Desktop\v16.1 folder on Server #1.
17. The Administrative account opens the Reflection Workspace.
(this is because the application.settings file “roamed” from Server #2 to Server #1 with the Administrative account’s Roaming Profile)