Yes, our agent can track usage of the Lotus Notes client by monitoring whether or not this executable is actively running on a machine. If the Lotus Notes client is detected as running, the agent will automatically track whether the Lotus Notes client is being looked at and whether the Lotus Notes client is being interacted with.

The agent sends out information to the cloud using the system account. You can configure it to work with a different account than the system account but we advise against that. Once you install the agent you need to make sure that the system account is able to POST to:

1. US customers https://collectit.softwatch.com:443
2. EU customers: https://cloudit-eu.softwatch.com:443

(You can identify the located server by the ending letters of your company identifier)

If your organization uses a proxy server please make sure that the system account can access through the proxy.

We understand that this is sometimes quite difficult to change proxy configurations so we suggest that you bypass the proxy for our address altogether. If you can – that would be the easiest option. Simply add either (US) https://collectit.softwatch.com or (EU) https://cloudit-eu.softwatch.com to the exclusion list and the connections to that address will not be proxied.

Our lightweight agent supports Internet Explorer(IE) and Google Chrome. IE don’t require anything but the agent, but Google Chrome analysis requires installing a simple Chrome extension. The easiest way to accomplish this is by using a group policy that will enable you to gain control over several Chrome settings, including pushing out Extensions and making sure they stay enabled on the users’ browsers. If you are just testing the agent on several machines and would prefer to manually install this Chrome extension please do so from this link.

• SoftWatch generates real usage analysis as opposed to a simple inventory, or open/close information on MS Office applications.

• SoftWatch distinguishes between four categories of users:

  • Those who never ran the application

  • Those who ran the applications but used it for viewing purposes only

  • Those who use it only for very light editing

  • Those who are heavy users

• SoftWatch is a standalone tool that doesn’t require, or rely on that Active Directory, such as SCCM and SMS

• SoftWatch is deployed very straightforwardly and quickly

• SoftWatch collects usage data through a non-intrusive software agent

The only way to track real software usage is with an agent. It is the only way to successfully track focus, keyboard and mouse activities.

On average, the thin client’s CPU’s usage is ~0.00001%.

The agent collects:

• Inventory of installed software

• Data running applications:

  • Application name and ID

  • CPU and memory values

  • Mouse activity

  • Keyboard movements (no key logging)

  • Window focus information

• The agent does not scan the registry. It reads a set of specific keys. This dramatically reduces network load.

• Running processes are constantly monitored and are reported on every eight minutes by default

• Hardware and software inventory is reported every 24 hours and only if the agent detects changes

The agent has minimal interaction with the operating system. This ensures virtually no adverse effect on performance. The average report size is only 10KB once every 8 minutes. All the reports, analyses and calculations run on the server. Nothing is done on the agent side in order to keep the client as thin as possible.

Yes. The agent’s unique inner topology consists of two elements. One will run on a system level, once per machine, and will provide data on all the running processes. The other will run once per logged on user, and provide data on usage, such as mouse, keyboard and focus information. This means that no matter how many users are connected to a single machine every session is monitored separately. Once the information is parsed by the SoftWatch server, it will be broken down according to user for each individual process.

Yes. We use SSL encryption to secure the data in transit and we offer optional MD5 encryption for data at rest.

Here’s how the data encryption works:

To encrypt the data (username, machine name, domain name) we:

1) capitalize the data (so User and UsEr == USER)
2) MD5 the capitalized string and send that data to the system from the agent. The result is that instead of username / machine name / domain name we will have some encrypted string and the web UI will show that string as the username / machine name / domain. No one will be able to make sense of it.
Now all the data is encrypted even before it leaves the agent.
In order to make sense of the data the customer can create a spreadsheet with a list of usernames in column A and then another column with an MD5 on the capitalized data from column A. The customer can download the data from our web UI to a spreadsheet and run a vlookup to cross-match based on the MD5 strings that should be identical in both Spreadsheets.