Configure universal keystrokes

In PSM, you can further refine the settings for universal keystrokes audits and recordings.

Configure keystroke recording and auditing

  1. Log on to PVWA.

  2. Go to Administration > Configuration Options > Options > Connection Components.

  3. For each connection component that you want to add universal keystroke capabilities, configure the audit and text recording capabilities:

    1. Go to Target settings and right-click on Supported Capabilities. Under Add capability, add the following IDs:

      • KeystrokesTextRecorder

      • KeystrokesAudit

  4. Click Apply to save your changes.

Configure universal keystrokes for Windows connections when an additional language is used

Universal keystrokes recording is configured by default to support Windows sessions in which a single language is used.

If you use an additional language in your Windows sessions (for example, if you use both English and French keyboards), you must configure the universal keystrokes.

 

Universal keystrokes that are configured to support an additional language are not recorded when connecting to 32-bit target servers.

Prerequisites and limitations when additional language support is enabled

On the target machine, PSM requires the following:

  • A share called admin must be available on the target server.

  • Make sure the SERVER Windows service is running.

  • In the firewall, open TCP port 445.

  • The account used to access the target machine must belong to the Administrators Group.

     

    To enable universal keystrokes for Windows sessions when additional language support is enabled, PSM installs a service on the target machine. The service starts when a new session is initiated, and stops immediately after the session is established.

  • Add the additional language as an extra keyboard for the target account user on the target machine.

On the PSM server, PSM requires the following:

  • Set the system locale to the additional language.

By default, single language support for capturing Universal Keystrokes for Windows sessions is configured at system level. This setting can be overridden at system or platform level, enabling you to customize additional language support according to your preferences.

  1. Click ADMINISTRATION and click Platform Management to display a list of supported target account platforms.

  2. Select the platform to configure and click Edit. The settings page for the selected platform appears.

  3. Expand UI & Workflows and expand Connection Components.

  4. Right-click the Windows connection component to configure. By default, the Windows connection component is PSM-RDP.

  5. From the Connection Component pop-up menu, select Add Override target settings. A new set of Override target settings are added to the Connection Component.

  6. Expand Override target Settings, right-click Client Specific parameters, and select Add Parameter. A new parameter is added.

  7. In the Properties list, in the Name property, specify WindowsKeystrokesSingleLanguage.

  8. In the Properties list, in the Value property, specify No.

     

    To revert to single language support, change this Value to Yes.

  9. To save your changes, do one of the following:

    • Click Apply to apply the new configurations.
    • Click OK to save the new configurations and return to the System Configuration page.

Separate keystroke records

You can define a list of keys that indicate when a keystrokes audit record ends. This list can be defined for each connection component and can be overridden for a specific platform. Whenever the user strikes a key on the keyboard from this list, PSM creates a new audit record that contains the group of keys that were typed up to this point.

 

In an environment where support for multiple languages is configured, in PSM-RDP connections the only separator key is Enter and it cannot be changed. For more information, refer to Configure universal keystrokes for Windows connections when an additional language is used.

    1. in the PVWA, click Administration , and click Platform Management.

    2. Select the platform to configure and click Edit. The settings page for the selected platform appears.

    3. Expand UI & Workflows,and expand Connection Components.

    4. Right-click the connection component to configure and select Add Override target settings from the pop-up menu. A new set of Override target settings are added to the Connection Component.

    5. Expand Override target Settings, right-click Client Specific parameters, and select Add Multiline Parameter. A new parameter is added.

    6. In the Properties list, in the Name property, specify the name of the multiline property. Specify KeystrokesRecordSeparator.

    7. Click the Value property. An edit box appears to enable you to specify the list of keys that indicate when a keystrokes audit record ends. As this is a multiline parameter, each line represents a single key. Any key can be specified in this list, although special characters must be enclosed with parentheses and are case sensitive. For example, [Tab] or [RCtrl]. The default value is the Enter key.

      Specify any regular character or any of the following special characters: [RAlt] [LAlt] [LShift] [RShift] [LCtrl] [RCtrl] [F1] [F2] [F3] [F4] [F5] [F6] [F7] [F8] [F9] [F10] [F11] [F12] [Esc] [Home] [Delete] [Insert] [End] [PageUp] [PageDown] [Pause/Break] [LWinKey] [RWinKey] [Menu] [Tab] [LeftArrow] [RightArrow] [UpArrow] [DownArrow] [Backspace] [CapsLock] [NumLock] [ScrollLock] [Enter]

    8. Click OK. The list of keys that indicate when a keystrokes audit record ends is displayed in the Value property as one line.

    9. Save your changes.