Home
Welcome to the HCL Sametime® 11.5 administration documentation
Administering
This section provides information on administering HCL Sametime 11.5 environments.
Managing Sametime clients
This section provides information on managing HCL Sametime clients.
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.
Configuring Sametime® client preferences with the Expeditor managed settings framework
You can configure and manage the user's Sametime® client preferences for capable clients using the Expeditor managed settings framework. The Sametime clients that are Expeditor based include the Sametime client for Windows or Mac, and the HCL® Notes embedded Sametime client for Windows or Mac. This excludes the PWA, web and mobile clients.
Updating client preferences with the managed-settings.xml file
Sametime rich clients such as the embedded Sametime client in HCL Notes and the full Sametime standalone client are based upon the Eclipse framework. These clients can process a managed-settings.xml file to receive new or updated preferences automatically. The managed-settings.xml file is policy based, and each policy can define a different xml file to apply preferences to different groups of users.
Defining preferences in the managed-settings.xml file
Follow these instructions to define preferences in a managed-settings.xml file.
Deploy managed-settings.xml or managed-community-configs.xml file to a web server
Once the xml file(s) is ready to be deployed to users, the file must be placed on a web server to host it. This can be any web server the users can reach.

Welcome to the HCL Sametime® 11.5 administration documentation
- 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.
- What's new in HCL Sametime
  This section describes what's new in HCL Sametime® 11.5 and Sametime® Meetings 11.5.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.5.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.5.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.5.
- Securing
  This section provides information on securing HCL Sametime 11.5 environments.
- Administering
  This section provides information on administering HCL Sametime 11.5 environments.
  - Managing Sametime clients
    This section provides information on managing HCL Sametime clients.
    - Managing client types and logins
      You can manage the manner and order of client logins to HCL® Sametime®.
    - Connecting the Sametime® Connect client to the Sametime® Community Server
      The Sametime® Connect Client uses Server Communities preferences to connect to the Sametime Community 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.
      - Sametime® client preferences
        This section lists the preferences that can be managed for the HCL® Sametime® Connect Client and Sametime Embedded Client for Notes®.
      - Selecting preferences in the client
        In the Preferences dialog of the HCL® Sametime® Connect Client and the Notes® client, users can choose any Sametime preferences that have not been locked by the administrator.
      - Configuring Sametime® client preferences with the Expeditor managed settings framework
        You can configure and manage the user's Sametime® client preferences for capable clients using the Expeditor managed settings framework. The Sametime clients that are Expeditor based include the Sametime client for Windows or Mac, and the HCL® Notes embedded Sametime client for Windows or Mac. This excludes the PWA, web and mobile clients.
        Configuring Sametime® Connect Client preferences in the plugin_customization.ini file
        Defining a settings file in the plugin_customization.ini file is an alternate method for distributing preferences to the Sametime® Connect Client. Unlike the managed-settings.xml file posted on an update site, this method does not provide any policy-based distribution of preferences.
        Updating client preferences with the managed-settings.xml file
        Sametime rich clients such as the embedded Sametime client in HCL Notes and the full Sametime standalone client are based upon the Eclipse framework. These clients can process a managed-settings.xml file to receive new or updated preferences automatically. The managed-settings.xml file is policy based, and each policy can define a different xml file to apply preferences to different groups of users.
        Defining preferences in the managed-settings.xml file
        Follow these instructions to define preferences in a managed-settings.xml file.
        Deploy managed-settings.xml or managed-community-configs.xml file to a web server
        Once the xml file(s) is ready to be deployed to users, the file must be placed on a web server to host it. This can be any web server the users can reach.
        Updating the client policy to include the managed settings or managed community configs URL
        Once the xml file(s) is ready to be deployed to users, the file must be placed on a web server to host it. This can be any web server the users can reach.
        Changing the update interval for managed preferences
        If you want to change the update interval for managed preferences, you can update the existing settings XML file.
        Discontinuing managed preferences
        To stop setting preferences through the Expeditor managed settings framework, remove the reference to the managed-settings.xml or managed-community-configs.xml file(s) and unlock any previously read-only settings.
      - Configuring Sametime preferences using HCL Notes policies
        To configure preferences for the HCL Sametime Embedded Client for Notes, you can also use the Domino® Desktop policy settings document. These policies are applied when a Notes user logs into their home mail server and retrieves their desktop policy. These settings will not apply to any other client.
      - Updating connectivity settings with the managed-community-configs.xml file
        You can distribute updates to HCL® Sametime® client communities automatically using a managed-community-configs.xml file. The managed-community-configs.xml file is policy-based, so you can control communities for different user groups.
      - Creating a community provisioning URL for mobile users
        This section describes how to create a provisioning URL that automatically creates an HCL Sametime® community definition on mobile devices running Google Android or Apple iOS, so users can easily connect to Sametime.
  - Starting and stopping servers
    This section provides information on starting and stopping HCL Sametime 11.5 servers.
  - Managing policies
    Sametime policies allows administrators to control user access to features.
  - Meeting Server Configuration Files
    Meeting servers are deployed on Docker or Kubernetes. Review the appropriate section for your deployment.
  - Adding additional Sametime administrators
    Sametime Community server is installed on top of a Domino server. There are some administration and installation tasks that must be performed using the HCL Notes Client or HCL Notes Administrator client.
  - Enabling multi-tenancy on the Sametime Community Server
    Multi-tenancy allows multiple organizations to be part of the HCL 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.
  - Disabling persistent chat and MongoDB requirements
    HCL Sametime 11.5 deploys with persistent chat enabled which requires MongoDB. It is possible to remove the MongoDB requirement if persistent chat and chat logging is disabled.
  - 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.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Deploy managed-settings.xml or managed-community-configs.xml file to a web server

Once the xml file(s) is ready to be deployed to users, the file must be placed on a web server to host it. This can be any web server the users can reach.

About this task

The web server that hosts the managed-settings.xml and/or managed-community-configs.xml must allow these two files to be accessed anonymously.

Procedure

Procedure

Prior to placing the managed-settings.xml and/or managed-community-configs.xml on the web server, open the file using a browser and ensure it is not producing any syntax errors. If errors are present, they should be resolved first.
If choosing Domino for the web server it must be running the http task. Place the managed-settings.xml file in the Domino web server directory:
For windows:
```
c:\Program Files\HCL\Domino\data\domino\html
```
For Linux:
```
/local/notesdata/domino/html 
```
Example resulting URL:
```
http://www.example.com/managed-settings.xml 
```

The managed-settings.xml file must be named “managed-settings.xml”.

If you require more than one managed-settings.xml file, they can be placed in different folders on the web server, for example (on Windows):

c:\Program Files\HCL\Domino\data\domino\html\default\managed-settings.xml 

c:\Program Files\HCL\Domino\data\domino\html\nomeetings\managed-settings.xml

Example resulting URLs:

http://www.example.com/default/managed-settings.xml 

http://www.example.com/nomeetings/managed-settings.xml

The Sametime server will look in the folder specified in the URL for both a managed-settings.xml and a managed-community-configs.xml. If you are using both types of files, your URL defined in the policy must be scoped to the folder path where the two files reside.
For example:
```
http://www.example.com/default 

http://www.example.com/nomeetings 
```
Note: Do not use the following special characters in your folder names
- Ampersand (&)
- Apostrophe(‘)
- Quotation mark (“)
- Greater than character (>)
- Less than character (<)
- backslash character (\)
- Forward slash (/)
- spaces ( )
- hash symbol (#)

What to do next

Updating the client policy to include the managed settings URL.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.