Managing the operation logs

Asset Information Manager can use operation logs to manage the operations that occur in managed devices. This section explains the types of operation logs that are used, and how different operation logs are managed. By acquiring operation logs, you can monitor illegal program usage and Internet usage. You can also obtain the status of each group by totaling up the operation log information.

By acquiring operation logs, Asset Information Manager can monitor illegal program usage and Internet usage. Furthermore, should an information leak occur, the operation logs can be used to trace and investigate the removal of files from the organization, name changes, and other suspicious activities.

Operation logs can be acquired when Asset Information Manager is linked to JP1/Software Distribution.

Organization of this subsection: (1) Operation log types; (2) Difference in management methods

How an operation log is managed; that is, which job menus are used and how the operation logs are acquired, differs depending on the program product version. Therefore, check these items when designing an asset management system.

When linked to JP1/Software Distribution 08-00 or later
You can manage the operation logs collected by JP1/Software Distribution by using the Operation Log List and Operation Log Total job menus.
Because the JP1/Software Distribution database is directly referenced, you can always reference the latest information using the Operation Log List job menu without having to load the information into the asset management database. You can also trace the preceding and subsequent operations from the operation logs. For details about how to centrally manage operation logs, see 2.2.3 Managing operation logs by linking to JP1/Software Distribution.
Additionally, you can use the Operation Log Total job menu to check the status for each group.
When linked to JP1/Software Distribution 07-50
Of the operation logs, only the program startup information and window title change information collected by JP1/Software Distribution can be managed using the job menu items Program Execution History and Window Title Update History.
When using the job menu items Program Execution History and Window Title Update History, you need to use the Take operation history task registered in the Windows task scheduler to load the history information into the asset management database on a regular basis. Therefore, you need to allocate sufficient space in the asset management database. For details about how to estimate the database size, see C.2 Disk space requirements. For details about how to load information using the Take operation history task, see 5.9.1 Types of tasks.

2.1.3 Managing the operation logs

(1) Operation log types

(2) Difference in management methods