Monitoring Agent for Windows OS

The Monitoring Agent for Windows OS offers a central point of management of Windows-based environments

The Monitoring Agent for Windows OS provides a comprehensive means for gathering exactly the information you need to detect problems early and to prevent them. Information is standardized across all systems, and you can monitor servers from a single workstation. The Cloud Pak Software Monitoring Portal lets you easily collect and analyze specific information.

Troubleshooting

Note the following troubleshooting issues and resolutions when using the monitoring agent for Windows OS.

Password changes in Administrators group might block data from monitoring agent

When the Administrator password is changed, metrics data for the Windows virtual machine cannot be retrieved from the monitoring agent.

To resolve the problem, run the following command on each virtual machine of your deployment every time you change the Administrator password: updatelocalacct.cmd  -u/--user <user> -p/--password <password>, where <user> and <password> are the name and password of the user in the Administrators group.

The C:\Windows\Setup\ibm\updatelocalacct.cmd script file is provided by IBM to help sync passwords between the Administrators group and virtual machines and virtual systems.

If you have changed the password but have not run the updatelocalacct.cmd command, you will see the following symptoms:
  • The virtual machine has a green Running state with a blue question mark that indicates the following status: Running and the health status is unknown.
  • Virtual machine monitoring loses all or some metrics data.
  • The Cloud Pak Software Monitoring Portal for the virtual machine loses all or some metrics data.