Home
HCL Sametime® Administration Guide 12
Administering
This section provides information on administering on Sametime environments.
Managing Sametime clients
This section provides information on managing Sametime clients.
Managing client types and log-ins
You can manage the manner and order of client connections to Sametime.
Configuring the preferred login list
By default, persistent chat enables a user that is logged in to multiple clients to receive instant messaging sessions across all clients concurrently. In an environment that does not support persistent chat and where the single login type feature is disabled, Sametime uses a default login order to determine which client type should receive the instant messaging session. A preferred login list allows you to override the default order.

HCL Sametime® Administration Guide 12
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- New features in Sametime 12
  The current version of HCL Sametime and HCL Sametime Premium includes new features and enhancements.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime and HCL Sametime Premium.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime and HCL Sametime Premium.
- Configuring
  This section provides information on configuring the HCL Sametime server.
- Securing
  This section provides information on securing your HCL Sametime environments.
- Administering
  This section provides information on administering on Sametime environments.
  - Managing Sametime clients
    This section provides information on managing Sametime clients.
    - Managing client types and log-ins
      You can manage the manner and order of client connections to Sametime.
      - Configuring allowed client types
        You can define the types of clients that can connect to the Sametime server.
      - Configuring the preferred login list
        By default, persistent chat enables a user that is logged in to multiple clients to receive instant messaging sessions across all clients concurrently. In an environment that does not support persistent chat and where the single login type feature is disabled, Sametime uses a default login order to determine which client type should receive the instant messaging session. A preferred login list allows you to override the default order.
      - Sametime Client IDs
    - Connecting the Sametime Connect client to the Sametime server
      The Sametime Connect client uses Server Communities preferences to connect to the Sametime server for presence and chat features.
    - Sametime client configuration options
      There are several methods to customize the user experience for Sametime clients. This section covers Expeditor based clients that are capable of leveraging the Expeditor Managed Settings framework. These clients include the Sametime client for Windows or Mac, and the HCL Notes embedded Sametime client for Windows or Mac. This does not apply to the PWA, web or mobile clients.
  - Managing file transfer data
    As with meeting recordings and reports, files that are shared in the chat are stored in a Docker volume or a Kubernetes persistent volume. By default, you can download these files within 90 days.
  - Testing Sametime chat and meeting clients
    This article assumes that you have successfully installed and configured Sametime or Sametime Premium.
  - Starting and stopping the Sametime server
    Starting and stopping the Sametime server involves starting and stopping the Sametime services running in the container management system.
  - Starting and stopping MongoDB
  - Managing policies
    Sametime policies allows administrators to control user access to features.
  - Configuration files
    Configuration files are used to maintain information used by the Sametime server for various reasons. In Sametime v12, configuration files are generated on demand based on information in the container management configuration file based on the whether you are using Docker or Kubernetes.
  - Enabling multi-tenancy
    Multi-tenancy allows multiple organizations to be part of the Sametime community. With multi-tenancy, Sametime users can chat, add users and groups to contact lists, and have awareness of users in their organization or in other organizations that are configured to be visible to them.
  - MongoDB
    This section provides information relating to administering MongoDB.
  - Managing Sametime Meetings
    This topic explains the features you can enable or disable for meetings. Currently, the settings that you can change are global settings that apply to the entire server. User policies cannot control the settings.
  - Managing file transfer data
    As with meeting recordings and reports, files that are shared in the chat are stored in a Docker volume or a Kubernetes persistent volume. By default, you can download these files within 90 days.
- Troubleshooting
  This section provides information on troubleshooting and supporting Sametime environments.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Migrating and Upgrading
  This section provides information on migrating data from an earlier release to Sametime 12.
- Notices

Configuring the preferred login list

By default, persistent chat enables a user that is logged in to multiple clients to receive instant messaging sessions across all clients concurrently. In an environment that does not support persistent chat and where the single login type feature is disabled, Sametime uses a default login order to determine which client type should receive the instant messaging session. A preferred login list allows you to override the default order.

About this task

By default, once persistent chat is disabled, the Sametime server depends on the default list of client types, each of which has a predefined weight. Login order for each user depends upon the login-type weight. The first login type, having minimal weight, is the one provided for the incoming instant messaging session.

Default order of login types on Sametime:

Sametime connect clients
Sametime mobile clients
Sametime proxy clients

The Sametime server is installed with a pre-defined list of client IDs for preferred login types. Use the below steps to customize this list and include Sametime clients as necessary.

Procedure

As administrator, open a text editor on the Sametime server.
Open the sametime.ini file located in the Sametime server installation directory. The default directory in Windows is C:\program files\HCL\domino.
In the Config section, specify the order of the login types that overrides the default order. If a user is logged in to multiple clients, offline messages are delivered to the client running the latest release, if available. If that release of the client is not available, offline messages are delivered to the client based on this default order.
```
VPS_PREFERRED_LOGIN_TYPES=login_type1, login_type2
```
For example, VPS_PREFERRED_LOGIN_TYPES=130C,130B,130A,1308,1306,1304,1436,1435,1434,1433,1432,1431,1430,14A3,14A2,14A1,14A0
Save the sametime.ini file.
Restart the Sametime server to allow the changes to take effect.