Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'd like to keep a tab on what time my staff logs in for, uhhh, 'morale' purposes.

share|improve this question
up vote 1 down vote accepted

I am no Sametime guru, but it looks like one of Sametime's logging features could help you out here. Take a look at this page.

Community Login/Logout information1

Each of these three options - Login/Logout by Time, Login/Logout by User, and Failed Logins by Time - contains some or all of the following information about user attempts to log in to a Sametime community:

  • User ID - A Lotus Notes User ID (canonical name, such as cn=John Smith, ou=West, o=Acme), a User Name as specified in the Person document of the Sametime directory, or a Distinguished Name from an LDAP directory. Anonymous users are identified by numbers.
  • Time - The date and time that a user logged in or logged out.
  • Event Type - The type of event being logged: Community Login, Community Logout, or Failed Login.
  • IP Address - The IP address of the user's computer.
  • Application Type - The type of application from which a user logged in:
    • Connect: Sametime Connect for the desktop. Indicates a user is authenticated.
    • Connect for browser: Sametime Connect for browsers. Indicates a user is authenticated.
    • Web: The Sametime Meeting Room, the Sametime Meeting Center, the Sametime Administration Tool, or an application created with the Sametime Java Software Development Kit.
    • Sametime links: An application created with the Sametime Links Software Development Kit.
    • DB: An application created with the C++ Software Development Kit.
    • Unknown type: Appears when the Application Type cannot be determined.
  • Client Version - The user's client version.If "Pre V3.1" or "Post 3.1" appears in this field, then the precise version of the client could not be detected.
  • Connectivity - The connectivity method used by the client:
    • Direct
    • HTTP polling
    • HTTP tunneling
  • Failure Reason - The reason a login failed.
  • Reason - The reason a login failed. Also indicates if a user was able to log out normally.

The administrator can use the "Successful logins" and "Failed logins" options in the Community Server Events to Log settings to record information in the Community Logins/Logouts section of the log.

To access the Community Logins/Logouts section of the Sametime log, select Logging -> Community Logins/Logouts in the Sametime Administration Tool.

I hope this helps you on your quest =)


share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .