HCL

HCL Sametime 11
Installation and Administration Guide

Updated
1-22-2020
Contents
System Requirements ................................................................................................................................... 2
Installation (Servers) ..................................................................................................................................... 2
Sametime Community V11 Server Install ..................................................................................................... 2
Install Domino V11 ........................................................................................................................................ 2
Set up Domino .............................................................................................................................................. 4
Steps to Set up Domino ............................................................................................................................ 4
Install MongoDB............................................................................................................................................ 5
Configure MongoDB...................................................................................................................................... 6
Install the Sametime Community Server .................................................................................................... 13
Before you begin ..................................................................................................................................... 13
Procedure................................................................................................................................................ 13
Install the V11 Sametime Community Server ............................................................................................. 13
Results ..................................................................................................................................................... 25
Windows ............................................................................................................................................. 26
HCL Sametime Proxy Server ........................................................................................................................ 26
Installation .................................................................................................................................................. 28
Installation .............................................................................................................................................. 28
Configuration .......................................................................................................................................... 29
URL to use for webchat ............................................................................................................................... 30
Modifying the Sametime Proxy Server’s default configuration.................................................................. 30
Configure policy to allow/disallow users to use the new persistent chat features.................................... 26
Configure Sametime Community Server to enable chat logging ................... Error! Bookmark not defined.
Configure Sametime Chat Logging to point to MongoDB........................................................................... 27
Update TTL index for chatlogging.ini ...................................................................................................... 27
Steps:................................................................................................................................................... 27
Sametime Community Server ..................................................................................................................... 28
New Client ID’s for Sametime V11 .............................................................................................................. 28
Policy Administration .............................................................................................................................. 31
Migration ................................................................................................................................................ 31
Installation (Clients) .................................................................................................................................... 32
System Requirements

Refer to the HCL Sametime 11 System requirements article.

Installation (Servers)

The new Domino installation platform is InstallAnywhere(IA). The installers functionality is

similar to that of V10, but with minor differences in the UI.

NOTE: A fresh installation of Sametime 11 is required. Upgrades from an earlier release are
not supported.

Sametime Community V11 Server Install

Install Domino V11

Installing Domino on Windows
If you are installing a new HCL® Domino® server for your HCL Sametime® server, use these
general directions for the necessary steps to install Domino. This procedure assumes that you
have a working knowledge of Domino administration.
Procedure
1. When adding a server to an existing Domino domain, register the server as an additional
before installing Domino. The registration process creates a server document in the
domino directory. Specify the following settings during registration:
• Store the server ID file that is created during registration somewhere else on the
system where you will configure the sametime sever. Record the path name; you
need to specify it when you configure the Sametime server.
• Use the same network as the first Domino server in the Domino domain.

2. On the computer where you will install the Domino Server, log on as the system
administrator (Microsoft Windows).

3. Run the Domino installation program (setup.exe).

4. Read the Welcome window and click Next. Then read the license agreement and click
Yes.
 5. Enter the administrator’s name and the company name. Do not elect to install Domino on
partitioned servers.

6. Select the program and data directory in which to copy the software. Make note of the
locations that you provide for the Domino program and data directories. You need this
information when you install Sametime. Click Next.

7. Select Domino Enterprise Server as the server type.

8. Click Next to accept all components.

9. Specify the program folder or accept the default location (such as HCL\Domino) for the
program folder.

10. Click Finish.

11. Click the HCL Domino Server desktop icon or click Start > Programs > HCL
Applications> HCL Domino Server to start the Server Setup program. Answer the
questions to finish setting up the Domino server.
Installing Domino® on Unix™
This topic guides you through the steps for installing Domino® interactively on a UNIX™
system.
You can install Domino® on a UNIX™ system by following this procedure, or you can perform
a silent installation of a local server.
Procedure
1. Before you install the Domino® server program files on a UNIX system, do the
following:
• Temporarily disable any screen savers and turn off any virus-detection software.
• Complete any pending reboot actions.
• Make sure that all other applications are closed.

2. As the root user, run the install program ./install available in the software package.

Note: This step runs the installation in console mode. Graphical mode is not available.
3. Read the Welcome screen and click Next.
4. Read the license agreement, accept the terms, and click Next.
5. Optional: Choose Install Data Directories Only.
Note: Choose the Data Directories Only option when migrating a single server install to
a multiple server install. If you are adding multiple partitions, select the option to install
 partitioned servers when specifying the corresponding program files directory name. Or,
choose this option when you are upgrading only one partition on a multiple-partitioned
server.
6. Choose the program directory and choose whether you are installing partitioned servers.
(You can install up to eight partitioned servers.) Click Next.
7. Specify the data directory in which to copy the software. If you are installing a
partitioned server, specify a data directory for each partition.
Note: For partitions, use the Add button to add each of the data directories to the list. If
they are not added to the list, they will not be installed.
8. Specify a UNIX™ username and UNIX™ group name.
9. Required: If you are installing to a directory other than /opt/hcl/domino, you must
create the /opt/hcl/domino soft link.
10. Choose a server setup option.
Note: The server setup options are not available for servers with multiple partitions.
11. Select the server type you acquired:
• Domino Utility Server -- Installs a Domino® server that provides application
services only, with support for Domino® clusters. The Domino® Utility Server
removes client access license requirements. Note that it does NOT include support for
messaging services. See full licensing text for details.
• Domino Messaging Server -- Installs a Domino® server that provides messaging
services. Note that it does not include support for application services or Domino
clusters.
• Domino Enterprise Server -- Installs a Domino® server that provides both
messaging and application services, with support for Domino clusters.
• Customize -- Allows you to select the features you want to install.
Note: All installation types support Domino® partitioned servers.
12. Review the summary information and click Next to begin installing files.
13. Click Finish to complete the install program.

Set up Domino
Steps to Set up Domino
To configure Domino, do the following:
1. At the admin user screen, specify a unique name that is not in the LDAP directory.
2. At Internet Services, select web browsers and deselect LDAP.
3. Make sure the hostname is fully qualified and that it resolves locally to IP and not
localhost.
 4. When setup is complete, start Domino, let it run for a few minutes, and stop it before you
install the Sametime Community Server.

Install and Configure MongoDB on Windows

To install MongoDB on Windows, do the following:
1. Download 3.6.5 from the MongoDB site: https://fastdl.mongodb.org/win32/mongodb-
win32-x86_64-2008plus-ssl-3.6.5-signed.msi.
2. Follow GUI to install and disable the “Install MongoDB Compass” option.

3. Download and install the Compass addon separately from:

https://www.mongodb.com/download-center/compass

Note: You must select the Version and Platforms as mentioned below:
o Version as latest (Stable) from the Version drop-down menu.
o Platforms as Windows 64-bit (7+) from the Platforms drop-down menu.

Note: You can select the Platforms as either Windows 64-bit (7+) or Windows 64-bit
(7+) (Zip).
 Reference: https://docs.mongodb.com/v3.6/tutorial/install-mongodb-on-windows
4. Create the default MongoDB data path before starting MongoDB – default is
“c:/data/db”.
5. Create the logs directory “c:/Program Files/MongoDB/logs/”.
6. To start the MongoDB server, open a command prompt and navigate to the MongoDB
install directory/bin folder and execute “mongod.exe”.
7. To start a MongoDB console, open a command prompt and navigate to the MongoDB
install directory/bin folder and execute “mongo.exe”.

Configure MongoDB on Windows

Complete the following steps to Configure MongoDB:
1. Update the MongoDB schema version value to version = 3. Depending on the version of
MongoDB, this value may not be present.

Use the following commands to update this value.

> use admin

> db.system.users.remove({})

> db.system.version.find()

Note: These are three separate commands

If the following output is returned:

{“_id”: "featureCompatibilityVersion", "version”: "3.6”}

{“_id”: "authSchema", "currentVersion”: 4}

Then the following commands will update the authSchema value to the required version
of 3.

> var schema = db.system.version.findOne({"_id":

"authSchema"})

> schema.currentVersion = 3

> db.system.version.save(schema)

If the following output is returned (without authSchema):

{“_id”: "featureCompatibilityVersion", "version”: "3.6"}

Us the following command to insert the correct authSchema value:

> db.system.version.insert({ "_id" : "authSchema",

"currentVersion" : 3 })

Restart the MongoDB server and exit the console to pick up the new schema version
change. To exit the MongoDB console use “exit”. To shut down the MongoDB server
use “CTL+C” in its command window.
2. Use the Compass UI to create a database called “chatlogging”. Create with an initial
collection called “SESSIONS” and create an additional collection called EVENTS.

Under New Connection, select "Fill in connection fields individually". Leave the
defaults, unless the MongoDB server is on another host.

3. Start the MongoDB console (mongo.exe) and create 'sametimeUser' in MongoDB

with the following commands.

Note: The user and password specified below are examples and can be changed at this
time if desired. If changing, use the new values when you configure the Sametime
Community server in a later step.

> use admin

> db.createUser({user:"sametimeUser", pwd:"sametime",

roles:[{role:"readWrite",
db:"chatlogging"},{role:"userAdminAnyDatabase",
db:"admin"}]})
 Note: The expected output will be a “successfully added user” message and
details.

4. Exit the MongoDB Console and stop the MongoDB Server.

5. Create the mongod.cfg file in the path referenced above in the MongoDB installation
path (C:\Program Files\MongoDb\Server\3.6\) with the following
contents:
systemLog:
destination: "file"
path:"c:\\Program Files\\MongoDB\\logs\\log.txt"
storage:
dbPath: "c:\\data\\db"
net:
bindIpAll: true
replication:
replSetName: rs0

Note: You can copy/paste the instructions from the document. However, the format of
the instructions is critical and must remain the same.

6. Create MongoDB service – This assumes the default installation path:

sc.exe create MongoDB binPath="\"C:\Program

Files\MongoDB\Server\3.6\bin\mongod.exe\" --service --
config=\"C:\Program Files\MongoDb\Server\3.6\mongod.cfg\""
DisplayName= "MongoDB" start= "auto"
 Note: The above default installation path when copied/pasted at the command prompt
should not have any line breaks.

The result will be “[SC] CreateService SUCCESS”.

7. Start the MongoDB service from the Windows Services panel.

8. Using the MongoDB console, use rs.initiate() to initiate the replica set.

9. The replica set is now operational. To view the replica set configuration, use
rs.conf(). To check the status of the replica set, use rs.status().

Install and Configure MongoDB on Linux

This document will cover steps for a Centos or RHEL environment as an example. MongoDB
supports using multiple Linux OS and there are many optional configuration items that may
apply to your environment. See https://docs.mongodb.com/v3.6/administration/install-on-linux/
for additional details. The following instructions assume you are using ROOT or an account with
SUDO privileges.

To install MongoDB on Linux

Create a repository file to use YUM to install MongoDB:

In /etc/yum.repos.d use VI to create the repository.

>vi mongodb-org-3.6.repo

And paste in the following contents:

[mongodb-org-3.6]

name=MongoDB Repository
 baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-
org/3.6/x86_64/

gpgcheck=1

enabled=1

gpgkey=https://www.mongodb.org/static/pgp/server-3.6.asc

After saving/exiting the file (:wq), execute YUM to install the MongoDB package.

>yum install mongodb-org

This will install the mongodb components, create the mongod user and default log and data
directories. You can validate this by checking that the following two directories exist and are
owned by ‘mongod'

/var/log/mongodb

/var/lib/mongo

To modify the default directories, consult the online documentation for MongoDB as referred to
earlier.

Start MongoDB using the provided service

>Service mongod start

Access the MongoDB shell by typing “mongo” at the prompt

>mongo

And then execute the following commands to configure your instance.

> use admin

 > db.system.users.remove({})

> db.system.version.insert({ "_id" : "authSchema","currentVersion" :

3})

> db.createUser( {

user: "sametimeUser",

pwd: "sametime",

roles: [ { role: "readWrite", db: "chatlogging" },

{ role: "readWrite", db: "ST_OFFLINE_DB" },

{ role: "userAdminAnyDatabase", db: "admin" }

});

> use chatlogging

> db.events.insertOne({"_id" : "dummy"})

> db.sessions.insertOne({"_id" : "dummy"})

> rs.initiate()

Note: this last command should indicate that the node was not started with replSet option, this is
expected as you will set that up in the next step after you exit the shell with
> exit

Use VI to edit the mongod.cfg file located at /etc/mongod.cfg and add the following two lines
after the bindIp line and above #security
replication:

replSetName: rs0

Using the prior lines in the cfg file as a guide for format.
Save the mongod.cfg file (:wq) and then restart the mongod service
>service mongod restart

And then restart the shell to confirm the replica set is available – If the rs.initiate does not return
with an error, exit the console. If there is an error, recheck the mongod.cfg file.
>mongo
 >rs.initiate()

>exit

Install the Sametime Community Server

File name: Extract the Sametime 11 Community Server .zip file provided in the package and
install the Sametime 11 Community Server.
Run the HCL® Sametime® Community Server installation program.

Before you begin

• The computer must already have HCL Domino® installed.
• Close all applications on the computer, including the Domino server administrator and
the web browser.
• Stop all Domino services.

Procedure

Install the V11 Sametime Community Server

For Windows Based installs

• Extract the Sametime_11.0_CommunityServer_Win64 archive to your local drive and
execute the ‘install.exe’ located in the Server subdirectory.
• If you plan to use TLS for your LDAP connections, you must also install the GSKit,
located in the GSKit subdirectory

For Linux Based installs

• Extract the Sametime_11.0_CommunityServer_Linux64 archive to your disk
• In the Server subdirectory, make the install.bin executable
• If you plan to use TLS for your LDAP connections, you must also install the GSKit,
located in the GSKit subdirectory
• If you installed Domino to alternate directories other than /opt/hcl/domino, or
/local/notesdata you should create /opt/hcl/domino and /local/notesdata
soft link(s).

• In order to install, there are 2 options

Graphical Install
Login to the Desktop of your Linux environment and then execute the ‘install.bin’
located in the Server subdirectory. If you do not have a desktop environment, it is
possible to use VNC to access the graphical install – steps would be
• In a linux SSH session, Run VNCServer (we used TigerVNC for this
example)
• As root – export DISPLAY=:x – where x is the port you will connect to VNC (eg
- :1 == port 5901)
• Connect to the VNCServer with VNCViewer
• As root – execute ./install.bin - The installanywhere GUI should display in the
VNCViewer window.

Silent Install
As root -
• Use VI to create a file named “installer.properties” in the same directory as the
‘install.bin’ executable, with the following contents

# This file was built by the Replay feature of

InstallAnywhere.
# It contains variables that were set by Panels,
Consoles or Custom Code.

DataInstallDir=/local/notesdata
UNIX_UserName=notes
UNIX_GroupName=notes
UNIX_ServerName=<hostname of the server you are
installing on>

#Directory Selection
#-------------------
DIRECTORY_TYPE_DOMINO=1
DIRECTORY_TYPE_LDAP=0
LDAP_SERVER=
 LDAP_PORT=
ADVANCED_LDAP_CONFIG=0
ST_BRANDING_INFO=<standard> or <entry>

#Install
#-------
-
fileOverwrite_/tmp/156305.tmp/stnotesinstallutilities_
linux64=Yes
-
fileOverwrite_/tmp/156305.tmp/stnotesinstallutilities.
jar=Yes
-
fileOverwrite_/tmp/156305.tmp/stnotesinstallutilities.
dll=Yes
-
fileOverwrite_/tmp/156305.tmp/stinstallutilities.dll=Y
es
-fileOverwrite_/tmp/156305.tmp/vcredist_x64.exe=Yes
-
fileOverwrite_/tmp/156305.tmp/UnixSetNotesFieldValue.s
h=Yes
-fileOverwrite_/local/notesdata/_HCL Sametime Server
11.0.0_installation/Change HCL Sametime Server 11.0.0
Installation.lax=Yes to All

• Notes:
• DIRECTORY_TYPE should be set as applicable to your environment. If you set
LDAP to 1, be sure to set DOMINO to 0 and add the appropriate
LDAP_SERVER and LDAP_PORT information.
• ST_BRANDING_INFO should be ‘entry’ or ‘standard’ as applicable to your
environment
• All of these entries are on a single line, so be sure that copy/paste does not break
them
• If you copy/paste - be sure there are no spaces at the end of the line(s).
 • In the Server subdirectory, execute ‘./install.bin -i silent’

Note: If needing to specify the properties file location, use -f <filename_and_path>.

• HCL Sametime v11 do not support the console based install in this release. If you are
attempting to do the Graphical install using VNC and you see the console option start,
this means that you were not successful in exporting the display – most common reason
would be that you are not running as root.

Installation Steps -

1. On the computer where you will install the HCL Sametime Community Server, the
InstallAnywhere install shield will guide you through the installation process. Click
Next.

2. The license agreement screen displays. Click Next.

3. Select the Directory type you wish to use,
• if using the local Domino directory, click Next
• If you select the LDAP Directory radio button.
o In the LDAP Server Name text box, enter the hostname of your LDAP server.
o In the Port Number for LDAP text box, enter the appropriate port for your
LDAP server
• Click Next.
4. Select the radio button option in the License Information screen to configure the
license. Click Next.

Note: You can choose either Standard or Limited depending on your license. Currently
the Dynamic model option, where you can enter the flex net url is not supported for this
release.
5. The Pre-Installation Summary displays. Click Install.
6. The installation begins.
7. Confirm the installation is performed without error.
Note: You must restart the system to complete the installation. Select the radio button Yes,
restart my system and then click Done.

8. The installation is complete.

Results
The Domino_data_directory\stsetup_exit_status.txt file contains a zero (0) if
the installation is successful. If the installation was not successful, look at the installation logs for
more information. Fix the problem, then try installing again. The installation logs are stored in
the following locations.
Domino data directory
SametimeInstall.log
stsetup.log
stsetup_exit_status.txt
SametimeIniParser.log
This log can be in /tmp or in the Domino data directory.
Console connection log
/tmp/SSCLogs/ConsoleUtility0.log
Windows
The default Domino data directory is c:\program
files\hcl\lotus\domino\data\ and the Domino program directory is
c:\program files\hcl\lotus\domino.
Domino data directory
SametimeInstall.log
stsetup.log
stsetup_exit_status.txt
Domino program directory
stsetup_exit_code_windows.txt
SametimeIniParser.log
This log can be in %TEMP% or in the Domino data directory.
Console connection log
Documents and Settings\username\Local
Settings\Temp\SSCLogs\ConsoleUtility0.log

Configure Sametime Community Server to enable chat logging

Use a Notes Client to open stconfig.nsf on the server and modify the communityservices doc and
set chat logging to ‘relaxed’ mode.
Note: This step is required for the new chat client to function properly.

Configure policy to allow/disallow users to use the new persistent chat

features
By default, the policy for this feature is enabled. You will need to manually update the policy to
disable it for users (‘default’ or ‘anonymous’).

To do this, you would edit ‘policies.users.xml’ file and modify the ‘current-value’ of
im.persistentChatEnabled to “0” (for false) and save the file. More details on updating policy
settings is provided at the end of the document.

Note: In order to use the new webchat client the persistent chat feature must be enabled.
Configure Sametime Chat Logging to point to MongoDB
If you followed the examples in the “Install MongoDB” section, the defaults should work
without any modifications. If you used a different username or password or installed MongoDB
on a separate machine, you will need to update the following settings in sametime.ini and
chatlogging.ini as appropriate.
The following shows the default settings.
Sametime.ini -
[stconvomap]
MONGO_URI=mongodb://127.0.0.1:27017

Chatlogging.ini –
CL_MONGO_HOST=127.0.0.1
CL_MONGO_PORT=27017
CL_MONGO_USER=sametimeUser
CL_MONGO_PASSWORD=sametime

Update TTL index for chatlogging.ini

The ‘Time To Live’ (or TTL) setting in the sametime.ini defines how long to store chathistory in
the database.

To change the TTL from the default 90 days, you must rebuild the TTL index in MongoDB.

Steps:

1. Shutdown the Sametime Community server.

2. Modify the chatlogging.ini and set the CL_MONGO_HISTORY_TTL value to the
preferred setting.
3. In the MongoDB Compass UI, access the chatlogging EVENTS table and select the
indexes tab; then, hit the DROP icon to the right of the TTL index.
4. Restart the Sametime Community server. This will create the new TTL index with the
new value.
Sametime Community Server configuration files

The primary methods for configuration are:

• Stconfig.nsf
• sametime.ini
• chatlogging.ini

If you have an existing environment and have settings that are specific to it (LDAP tuning, for
example) those settings can be copied to stconfig.nsf and sametime.ini as they still apply.
Note: Do not duplicate or overwrite any current setting.

New Client ID’s for Sametime V11

If VPS_ALLOWED_LOGIN_TYPES is set in the Sametime Community server’s sametime.ini,
Sametime v11 client IDs will need to be added. By default this setting is not in the sametime.ini.
Refer to the following article for these client IDs.

Table of Client types that are connecting to a Sametime server

https://hclpnpsupport.hcltech.com/csm?id=kb_article&sysparm_article=KB0024444

HCL Sametime Proxy Server

The HCL® Sametime® Proxy Server enables browser-based clients and mobile devices to
participate in Sametime instant messaging and 3rd party meeting services.
In addition, the Sametime Proxy Server works with Sametime Community Server to enable the
business card and live names awareness to other web-based applications.

Installation
File name: Extract the Sametime 11 Proxy Server archive file to the desired install location.
(example: C:\sametimeproxy or \opt\sametimeproxy)

Installation
• Open a command prompt and navigate to the location that you placed the extracted files.
• Run the command install.bat (install.sh) to view and accept the license.
 • Simple prompts will ask for the address of the Sametime Community and MongoDB
servers.
Note: If you don’t have an IDP server, leave it blank.
• A few files will be created as well as a ‘self signed’ certificate for the server.
• The installation is competed with:
Proxy server configured successfully

Configuration
Based on the responses during installation, settings will be stored in the following files:
• sametimeproxy\setenv.bat (setenv.sh)
• sametimeproxy\conf\stproxyconfig.xml
• sametimeproxy\conf\dbconfig.properties
After installation, these configuration files can be manually edited to alter the server's
configuration.
Note: Changes to stproxyconfig.xml are automatically read, without needing a server
restart but may take up to 30 mins. If you have an existing Sametime Proxy server (v9 or V10)
with settings specific to your environment, those settings can be copied to the new
stproxyconfig.xml as needed.

To start the server:

sametimeproxy\bin\startup.bat (startup.sh)

To stop the server:

sametimeproxy\bin\shutdown.bat (shutdown.sh)
Note: If the server hangs during shutdown, kill the process.

Note: If MongoDB is running on Windows, it may be required for the Windows server’s domain
name to be in the proxy server’s DNS hosts file. For example, if the Windows server’s domain
name is, “WIN-SERVERNAME” then the Sametime Proxy should add this in its host file.
Example:
# mapping the windows domain name of the MongoDB to this
uservers hosts file, so redirects will work

10.123.55.55 WIN-SERVERNAME

URL to use for webchat

The default ports for the Sametime Proxy are 8080 (http) and 8443 (https). The server will
automatically redirect users from http to https.

https://<sametimeProxyHostname>:8443/chat

Modifying the Sametime Proxy Server’s default configuration

The server’s configuration is located in the ‘server.xml’ file located in the conf/ folder.
To modify the ports to use defaults 80 and 443, you would edit the ‘server.xml’ and update the
default references of 8080 and 8443 to 80 and 443 respectively.
To use a new SSL Certificate for the server, you would edit this section of the server.xml - and
modify the “keystoreFile” and “keystorePass” as appropriate. This example uses a default “Java
Keystore” (or jks file) with a password of “sametime”.
<Connector port="443" protocol="org.apache.coyote.http11.Http11NioProtocol"
sslProtocol="TLS" clientAuth="false" keystorePass="sametime"
keystoreFile="conf/sametime.jks" SSLEnabled="true" secure="true" scheme="https"
maxThreads="200"/>
Sample Documentation for common reference

LDAP Server Config stconfig.nsf

• https://support.hcltechsw.com/kb_view.do?sysparm_article=KB0024812

File Transfer Settings

• https://support.hcltechsw.com/kb_view.do?sysparm_article=KB0040617

Forcing a non-Sametime System Console, Sametime server with multiple NICs to bind to the correct IP
address

• https://support.hcltechsw.com/kb_view.do?sysparm_article=KB0037695

Sametime server is binding to the wrong NIC (IP address)

• https://support.hcltechsw.com/kb_view.do?sysparm_article=KB0039463

Configuring Sametime Community Server to use SSL encryption

• https://help.hcltechsw.com/sametime/10.0/config/st_adm_security_ssl_ov_t.html?hl=configuri
ng%2Csametime%2Ccommunity%2Cserver%2Cuse%2Cssl%2Cencryption

Policy Administration

• For an example of how to configure policies in the new system – see this document
which talks about using the managed settings feature
o https://hclpnpsupport.hcltech.com/sys_attachment.do?sys_id=c79e28d71be0809083cb
86e9cd4bcb9c
• For a complete list of Policy IDs – see
https://help.hcltechsw.com/sametime/10.0/admin/admin_policy_im_ids.html?hl=instant%2Cm
essaging%2Cpolicy%2Cids

Migration

Here are best practices for migration from an earlier Sametime release.
 • Build the new system in Parallel.

• If you built the new system as part of the same Community.

o Block via firewall 1516 to prevent confusion as to which server users are on for
testing/validation of new feature set.

• Point test users to new system.

o Make sure that vpuserinfo.nsf is replicating, or plan for a copy at cutover time.

• Once satisfied that V11 is working for the test users,

o do a DNS flip so that existing users silently move over to the new system at the
next login.

o If something goes awry – use DNS to flip back.

Installation (Clients)

Both Windows and Mac clients are supported.

If you are installing a new Sametime client, please note that all directories and registries will be
HCL branded. If you are upgrading an existing Sametime client to version 11, you can use
prior (IBM) directory paths.
NOTE: For this release, upgrades on Windows and Mac are supported from a Sametime 11
client. Upgrades from a 9.0.1 or earlier versions on Windows are not supported. If you run
a version of Sametime that is not supported for upgrades, you
must uninstall that version and then install Sametime 11.