Configuring Sametime to send announcements to users with old clients

Configure an announcement that users receive when they log in to the IBM® Sametime® Community Server with clients that are older than the allowed version level.

About this task

The ST_OLD_CLIENT_VERSION_WARNING_MESSAGE setting configures the Sametime Community Server to automatically send an announcement when users attempt to log in using clients that are older than the allowed version level. The message you specify functions as either a warning message or a disconnection notification, depending on whether the value of the ST_MINIMAL_CLIENT_VERSION setting allows logins from earlier clients. If the ST_MINIMAL_CLIENT_VERSION setting allows logins, use the text of the message to warn users that they need to upgrade and to explain how to obtain and install the client upgrade. If the ST_MINIMAL_CLIENT_VERSION setting does not allows logins, use the text of the message to explain why login was denied.

By default, the server waits one second before sending the announcement to users who attempt to log in to the server from IBM Sametime clients running versions earlier than what is allowed by the specified minimum version level. This pause is needed since the full initialization time for some client versions is longer than the others, and without the pause the announcement would reach the client before it could handle it. To ensure that all clients receive the announcement, you can configure a longer delay before the announcement is sent.

Procedure

  1. Edit the STSecurity.ini file and provide text for the announcement by completing the following steps:
    1. Open the STSecurity.ini file in a text editor.

      By default, the file is located in the Sametime installation folder, for example, C:\Domino\STSecurity.ini.

    2. Locate the ST_OLD_CLIENT_VERSION_WARNING_MESSAGE setting. This setting only occurs in the STSecurity.ini file if someone has added it. The ST_OLD_CLIENT_VERSION_WARNING_MESSAGE setting is not in the STSecurity.ini file by default.
    3. Fill in the text of the announcement.

      The ST_FORCE_LOGOUT_OLD_CLIENT_VERSION setting determines whether users of old clients are allowed to stay logged in to the community. By default, when this setting is true (a value of 1), old client versions are disconnected. When the setting is false (a value of 0), the users of old clients remain online an usually a message is sent to them.

      If the ST_FORCE_LOGOUT_OLD_CLIENT_VERSION setting is set to 0 (allow logins from client versions earlier than the specified minimum), and you provide a value for ST_OLD_CLIENT_VERSION_WARNING_MESSAGE, the text you provide serves as a warning message. The server allows the login and then sends the specified text. You can use the message to provide users with information on upgrading. For example, you can include an address that specifies the location of a download site. After receiving the announcement with the address link, users can click the address link to open the link location.

      Note: The VP_SECURITY_ALLOW_USER setting was renamed ST_FORCE_LOGOUT_OLD_CLIENT_VERSION in Sametime 8.5. To smooth migration, ST_FORCE_LOGOUT_OLD_CLIENT_VERSION overrides VP_SECURITY_ALLOW_USER from prior versions. If it is not present, then its default value will be 1 and VP_SECURITY_ALLOW_USER or its own default value takes affect.
    4. Save and close the file; be sure to use UTF-8 character encoding if your message text or sender name includes non-ASCII characters (for example, accented characters).
  2. Edit the sametime.ini file and configure a delay before the announcement is sent by completing the following steps:
    1. Open the sametime.ini file in a text editor.

      By default, the file is located in the Sametime installation folder, for example, C:\Domino\sametime.ini.

    2. In the [Config] section, locate the VP_SECURITY_PAUSE_INTERVAL setting. This setting does not reside in the sametime.ini file by default. The VP_SECURITY_PAUSE_INTERVAL setting resides in the sametime.ini file only if someone has added it.
    3. Specify the number of milliseconds that the Community Server waits before sending the announcement.
    4. Save and close the file.