Sametime clients

HCL Sametime 11 deployments support the following Sametime client types

HCL Sametime Community

  • Standalone rich client
  • Embedded rich client in HCL® Notes

HCL Sametime Proxy

  • Browser based client
  • Embedded clients in HCL Verse, HCL iNotes, HCL Connections, HCL Digital Experience
  • Mobile Clients for iOS and Android

Review the following considerations before deploying the HCL® Sametime® Connect client or the Sametime Embedded client to your users.

The Sametime Connect or Embedded client must be installed on a user's workstation by someone with administrative privileges on that computer. Before installing the client, review the following points:

  • Internet passwords required

    Internet passwords are required to log on to Sametime Connect or Embedded clients when single sign-on is not configured. Each user must have an Internet password in their Person Document in the Domino® Directory or stored in the LDAP directory. You might need to inform users of their Internet passwords.

  • Password character restrictions

    In addition to non-English characters, the following characters must not be included in passwords used by Sametime:

    : \ } ’ " &

  • IPv6 addressing

    Supporting the IPv6 protocol in a Sametime deployment requires you to upgrade Sametime clients to release 9 or later to ensure they can communicate with Sametime servers that use IPv6 addresses.

    If you support only IPv6 addressing, older clients will not generate error messages but will appear "broken" to users because they cannot communicate with the IPv6–enabled servers.

    If you support both IPv4 and IPv6 addressing, all Sametime clients can communicate with the IPv6–enabled servers; just be sure to configure the servers to listen for IPv4–format addresses as well as IPv6–format addresses.