Upon popular request I would like to explain the current possibilities and limitations of time cockpit in advanced multi-user scenarios like using Remote Desktop Services or sharing workstations (using user switching).
Besides the basic features (creating several users in one account, setting up multiple devices per user...) different scenarios of concurrent sessions on one pc, workstation or server are possible. The basic rule is if you are using different windows accounts (domain or local) everything should work as expected.
After installing time cockpit on a machine (running a Windows server or client operating system) every user can set up time cockpit using completely independent configurations and database file locations. Multiple users can be logged in and running time cockpit at the same time. There are only a few minor limitations which may apply:
- Only one version of time cockpit can be installed per machine.
- We currently do not support sharing workstations when using the same domain user or local windows account. Every user has to log in using a different account.
- If two users on the same machine track a common folder (e.g. C:\Data\Shared) using the file system signal tracker we cannot determine which user or process is causing a certain file system operation and it will show up in the signals of both users. This is a limitation of the currently used API. We chose the simple API which is available in .NET and does not require any unmanaged code or higher privileges. In the future we might look into creating an optional file system filter driver which would provide more detailed information for these advanced scenarios.
comments powered by