You can update specific settings in workspace files and session document files without affecting other settings in those files.

Workspace updates are available with Reflection Desktop version 16-2 and greater. Session document file updates are available in Reflection Desktop version 17-0 and greater.

Audio Transcript:

0:05 - 0:28 This video shows how to update specific settings in workspace files and session document files without affecting other settings in those files. Deploying Settings files can overwrite settings that users have customized. Reflection Updates solve this problem. Using Update files, you can change a setting without affecting the other settings that users have configured. 0:30 - 0:34 You can deploy Updates for workspace files and for session document files. 0:35 - 0:50 Let’s take a look at how to set up an update for a workspace file first. We’ll use Reflection Desktop’s Installation Customization Tool, called the ICT for short, to create a workspace update that adds a network share as a trusted location. 0:50 - 1:07 In Modify user settings, select to Update Workspace Settings and then click Define. Then in the workspace settings, select to Specify Trusted Locations. Because we’re adding a network share, we’ll need to select the option that allows this before we add the share. 1:09 - 1:20 The Reflection ICT tool automatically sets the location for the settings update. When you’re done, save this file in a companion file that you can deploy to users. 1:24 - 1:45 Now let’s take a look at a couple of ways to deploy updates to Session document files. When you deploy an update to a user’s workstation, These settings are applied to all existing and new session document files that have the same terminal type as the update. So if you apply a 3270 update, it is applied to all 3270 session documents. 1:47 - 1:54 We’ll set up an update for some TLS settings. First, you’ll have to change permissions on your administrative desktop that allow you to create update files. 1:58 - 2:02 Then open Reflection Desktop and create a session. 2:00 - 2:10 We need to be careful to add only the settings we want to change. We need to change the port but we don’t need to change the host address. 2:19 - 2:23 Now we’ll set up Security Settings to use TLS 1.2. 2:30 - 2:48 We’ll cancel this setting, because we don’t want to change the host address. And then save the file as a session update file with a special name of Update. Now you can deploy this file to users, just like you would a regular session document file. 2:50 - 3:11 Now we’ll look at another way to deploy session updates so that they apply only to specific sessions. First, you’ll need to place the update file you created on a server instead of deploying it to users. Then create sessions that include references to this file and deploy these files. When the files with the references open, they get the update settings. 3:17 - 3:29 To add reference to a session document, Open the Settings window and then select Session Update Settings on the window breadcrumbs. You’ll need to use your administrative rights to change currently disabled settings. 3:30 - 3:47 Then just add a UNC path to the update file you have placed on the server. We should note that this path must be a trusted location. We’re using the same location that we added earlier. Now save the file as a regular session document file that you can deploy to users.