The Marxio Login Logger program was designed to be a non-visible application that allows you to see who was using your computer when you were out. What time someone logged into computer and when he logged out.
It can work at home computer or in Active Directory environment or (probably) in Terminal Services using simple Windows user Startup group for running programs or starting it from Windows Group Policy (GPO).
It has no visible window and does not reside on taskbar or trayicon area. Once started, becomes invisible for any user and the only way to close it is to....logoff from computer, restart or shut it down.
Configuration file(s) can be global or for every computer. You can customize log file path and name and what it will contain.
Here is a short list of what can be logged using MLL
%T - current date and time with seconds
%D - date only (yyyy-mm-dd)
%E - day of the year (001-365)
%k - week of the year (1-53) Start week from Monday
%K - week of the year (1-53) Start week from Sunday
%u - username
%d - user domain name
%U - domain name and username
%n - computer NetBIOS name
%c - computer domain or workgroup name
%C - computer domain or workgroup name, and computer name
%1 - computer IP address - first found
%2 - computer IP address - second found
%3 - computer IP address - third found
%0 - computer IP address - all IP's found ;
%W - Windows OS
Log files and their content can be customized using markers above.
This is a 2-file-program. It consists of two files a) application executable and b) config file - config.ini by default. Config file must be placed in the same folder as executable. Moreover, config file can be machine dependent - you can set a separate file for every computer machine by just adding its NetBIOS name:
Example:
config-workstation005.ini where workstation005 is computer name.
There can be many files - for every machine, but only one global config.ini file. The order of processing ini files is: computer ini file and global file. It means that when you workstation name is comp001 then the program will first search for config file named config-comp001.ini. When this file not exists then default config file will be used - config.ini. Note that only one file will be processed. Machine specific or global one. Settings in these files are not overwriten. You set global config file (config.ini) for computers that do not have their own (config-comp001.ini). At last, you can use just one config file - config.ini.
When program is run, there is no sign of his activity. It only resides on processes list and does not show up in taskbar ir in tray icon (bottom right corner of the screen). It's....as if it didn't even run. It also has no window, no messages are displayed in case of aby error - writing config file, error file, etc.
