CapaInstaller Utilization Index (CUI) is a module in CapaInstaller that uses Performance Guard (PG) technology to monitor the resource utilization on all client PC's.
To use the CUI module you must
- Acquire a CapaInstaller license for the CUI module
- Deploy a "PerformanceGuard" CapaInstaller software package to the clients
What is deployed
The software package deployed to end-user clients will run the script "PerformanceGuard.cis" which will
- Install a Performance Guard agent to client PC
- Configure the Performance Guard agent to run in standalone mode (without access to a PG server)
- Start the Performance Guard Agent
What is configured
The PG agent configuration is located in the Windows registry at the following location:
Registry Key Name
The following registry parameter values are set explicitly by the CUI installation script:
What is measured
The Performance Guard agent will measure information about
- PC Startup Time (Time of Boot and Duration of Boot Sequence)
- User Login Time (Time of Login and Duration of Login)
- Startup Report Ressource usage report for all processes started during the PC boot sequence
- Utilization Index (a value from 0% to 100%) representing the percentual utilization of CPU, Disk, Network, and Memory resources
Where is the data located
The measured information will be stored in XML-files on the local disk. The file is named PFDatannnnnnnnn.xml where nnnnnnnnn is a timestamp.
The files are being placed here by default:
Client Operation System
Data File Location
C:\Documents and Settings\All Users\Application Data\CMS
Hers's an example XML file: PFData1304352120.xml
Using CUI in a PG environment
When using CUI in a mixed CapaInstaller and PG environment, the PG agents must first be deployed using the standard deployment procedure for PG agents. This is because the agents must be configured to use a PG server.
When the PG agents are deployed and connected to the PG server you can roll out the CUI package. When using CUI in a PG environment you may take control over the CMS parameters from the PG web console. If you go to Administration -> Agent -> Configuration and edit an agent configuration you will the following options:
Problem: There's no startup time or login time data available in CMS
Solution: In PG agents prior to version 5.8 there was a bug that caused some clients to fail to measure startup and login. Make sure to upgrade to a CUI package with a newer version of the PG agent.
Problem: Even when using a new PG agent there's still no startup time available in CMS.
Solution: Due to a bug in the CUI installation script you must upgrade to the CUI package available from CMS Service Update 2 - 2011. More specifically the startup condition was never met because the agent was configured to monitor the wrong service name for the PG agent service.
Problem: Startup time shows as 300 seconds in CMS
Solution: Due to a bug in the CUI installation script you must upgrade to the CUI package available from CMS Service Update 2 - 2011. More specifically startup times of 300 seconds (the timeout value) was reported to CMS in all cases where the startup measurement failed. Related to the above issue.