Summary for Patch 1071 (Verified)

Version 5.1.0.1

Summary	Process Accounting cumulative patch that includes 1056, 1064 and 1066.
Platform	Windows
Category
Requires
Server Required Patch/es
Supersedes	1066, 1064, 1059, 1056, 1052, 1050
Superseded by	1077 : Cancelled / Not hidden
Affects	Client: System Analyzer
Last Updated	September 30, 2009

Download now

Download_red Patch1071.zip

Description

Will provide Windows client support for the new Process datatype, which
contains information about cpu usage, memory usage, I/O and process
elapsed time - for selected processes.

This patch requires Patch481 to be installed on the server.
You must specify which processes to account for, since this functionality
is rather costly in terms of system resources.
To specify processes, edit the appusage_process_rules_rel.conf file on
the server, which is then distributed to the clients.

Also, this patch introduces selective module logging. You need to install
patch #493 on the server, to enable this option.
To specify modules, edit the appusage_modpoller_rel.conf file on the
server, which is then distributed to the clients.

Windows Application Usage (AppUsage) would log a value of 1 in the 'count' measurement
field for each record, and multiple records could be logged for the same application
(if it ran for long enough). This could result in a 'count' of more than 1 when records
for the same application were added on the server. After this patch, subsequent redcords
will be logged with a 'count' of zero. This will make the sum total 1 on the server when
multiple records for a single application are added. (But a side effect is that some
records may show a 'count' of zero, when not added. Records with zero count must be
interpreted as 'count' = 1, but they started prior to the report period.

Supersedes Patch Description

Expand all

Patch 1066 — Update/fix to Windows Application Usage collection

Windows Application Usage (AppUsage) would log a value of 1 in the 'count' measurement
field for each record, and multiple records could be logged for the same application
(if it ran for long enough). This could result in a 'count' of more than 1 when records
for the same application were added on the server. After this patch, subsequent redcords
will be logged with a 'count' of zero. This will make the sum total 1 on the server when
multiple records for a single application are added. (But a side effect is that some
records may show a 'count' of zero, when not added. Records with zero count must be
interpreted as 'count' = 1, but they started prior to the report period.

Patch 1064 — Upgrade Windows client with support for Process accounting.

Upgrade to patch 1056, with corrected data type (Process accounting) details.

Patch 1059 — Upgrade AppUsage

AppUsage has been partly rewritten to better conform to Microsoft standards
(which is important with respect to accuracy and for running on 64 bit).

Also, this patch introduces selective module logging. You need to install
patch #493 on the server, to enable this option.
To specify modules, edit the appusage_modpoller_rel.conf file on the
server, which is then distributed to the clients.

Patch 1056 — Upgrade Windows client with support for Process accounting.

Will provide Windows client support for the new Process datatype, which
contains information about cpu usage, memory usage, I/O and process
elapsed time - for selected processes.

This patch requires Patch481 to be installed on the server.
You must specify which processes to account for, since this functionality
is rather costly in terms of system resources.
To specify processes, edit the appusage_process_rules_rel.conf file on
the server, which is then distributed to the clients.

Also, this patch introduces selective module logging. You need to install
patch #493 on the server, to enable this option.
To specify modules, edit the appusage_modpoller_rel.conf file on the
server, which is then distributed to the clients.

Patch 1052 — Fixed bug in AppUsage process handling

Because of an algorithmic error in AppUsage, some processes just starting
could be logged as just ended, if the process information could not be
accessed right away. This has now been fixed.

Patch 1050 — Fixed bug in AppUsage process handling

Because of an algorithmic error in AppUsage, some processes just starting
could be logged as just ended, if the process information could not be
accessed right away. This has now been fixed.

Installation

Unpack the zip file anywhere on the machine to patch. Run the InstallPatch.exe
application. Once the patch has been installed, you may delete the unpacked
patch directory.

NOTE: The patch will reset debug level for AppUsage to 0.

NOTE: The patch must be installed by a user with administrator rights.

Corresponding Unix Patches

No corresponding Patches available.

Back to Version 5.1.0.1