|
|
 |
|
For technical auditing, security or whatever your requirements are you can log the date, time, application, username of the current
user logged in, machine name and success/failure of each of IntraLaunch's uses to a custom log file of your choice.
If the log file does not exist it is created. See below for an example log file.
Variable substitution is supported for this path. Logging is a silent operation. If there is any problem at any time writing or opening the log file there will be no generated error dialogs or messages. Multiple IntraLaunch objects on multiple workstations can all specify the same log file. The following object will log all events/uses to an IntraLaunch.log file in the users My Documents folder. If the log file does not exist it will automatically be created.
The following is a sample log file that would be generated. 'Ok' is specified in the fifth column if the application executes properly and 'Er' if there was an error. 'Re' means it was refocused instead of executed because of the RecallApp parameter. If the user or machine name cannot be determined they will be set to "(Unknown)". This typically happens if the workstation does not have Client for Microsoft Networks installed.
==============================================
= IntraLaunch :: Execution Log File = = Date: Thursday February 14, 2002 = Time: 12:09:53 AM = Log File: C:\My Documents\IntraLaunch.log ============================================== 02/14/2002 12:10:07 AM Administrator THINKPAD Ok explorer.exe /e,/root,C:\Folder 02/14/2002 12:10:14 AM Administrator THINKPAD Ok IntraLaunch:FindApp(excel.exe) 02/14/2002 12:10:27 AM Administrator THINKPAD Ok IntraLaunch:AddPrinter 02/14/2002 12:10:53 AM Administrator THINKPAD Er C:\Program Not Found.exe 02/14/2002 12:10:27 AM Administrator THINKPAD Re notepad.exe |
|||||||||||||||||||||||||||||
  |
|
 |
Web services provided by Extreme Hosting |