Home
Welcome to the HCL Sametime® 11.6 administration documentation
Administering
This section provides information on administering HCL Sametime 11.6 environments.
Changing user names
When you change user or group names in the directory, the change is not reflected in HCL® Sametime Community Server databases. In order to synchronize the directory names with the names in the Community Server databases, you must run the name conversion utility.
Preparing for changing names
Before you can run the name conversion utility, you need to perform the following tasks:
Creating a Name Change task
Create a name change task on the HCL® Sametime® Community server.

Welcome to the HCL Sametime® 11.6 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.6 and Sametime® Meetings 11.6.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Encryption usage in Sametime
  HCL® Sametime® uses several types of encryption to protect data.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.6.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.6.
- Securing
  This section provides information on securing HCL Sametime 11.6 environments.
- Administering
  This section provides information on administering HCL Sametime 11.6 environments.
  - Managing Sametime clients
    This section provides information on managing HCL Sametime clients.
  - Starting and stopping servers
    This section provides information on starting and stopping HCL Sametime 11.6 servers.
  - Managing policies
    Sametime policies allows administrators to control user access to features.
  - Configuration files
    There are a number of configuration files that a backup copy should be retained after the server configuration is complete.
  - 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
    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.6 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.
  - Changing user names
    When you change user or group names in the directory, the change is not reflected in HCL® Sametime Community Server databases. In order to synchronize the directory names with the names in the Community Server databases, you must run the name conversion utility.
    - Preparing for changing names
      Before you can run the name conversion utility, you need to perform the following tasks:
      - Creating a comma-separated value file
        A comma-separated value (CSV) file created in a text editor provides the name conversion utility with the information it needs to make a name change to user contact, privacy, and alert-me-when lists. The CSV file includes the type of change and typically provides details such as the old name and the new name, and optionally, the display name.
      - Creating a Name Change task
        Create a name change task on the HCL® Sametime® Community server.
    - Running the name conversion utility
      To run a name change task, start the name conversion utility. The name conversion utility uses the CSV file to update user contact and privacy lists with the latest directory changes.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Creating a Name Change task

Create a name change task on the HCL® Sametime® Community server.

Before you begin

Before you create a name change task, create a comma-separated value (CSV) file of the name changes in the Sametime Community Server directory.

About this task

A name change task is not actually a scheduled program; its timestamp merely indicates when the task was created and not when it will be run. The list of tasks is ignored until you run the stnamechange.cmd program, which then operates on all of the tasks in the list, using the .CSV files specified in the Name Change page.

Follow these steps to create a name change task.

Procedure

Using a notes client open the stnamechange.nsf database on the Community server.
From the Notes or Administrator Client menus, select Create > Name Change Task.
Provide a Name and optional Description.
Specify the cvs file location and the name of the cvs file.
Save and Close.
The name change task appears in the list of scheduled tasks.
All tasks listed here run when the stnamechange.cmd is run.

Results

After you have completed these steps on one Sametime Community server, it is necessary to repeat this process on other servers in distributed environment.

For a clustered environment, create this task on one server per cluster. All other servers receive the changes through the cluster replication process.

You choose the servers or cluster on which the name change task runs on a regular basis using general scheduling tools. The application does not run by default; you must run the task manually.

Remove all irrelevant CSV tasks from stnamechange.nsf before running the stnamechange.cmd program. This ensures that only tasks you want to run are included when you run the program. To delete a name change task, select a name change document, and then click Delete. If any name changes are entered incorrectly, you can import a new CSV file.

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.