Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Installing Analyzer Windows probe

Analyzer Windows probe collects performance and configuration data from the Windows host and Hyper-V machines. You can install this probe using Analyzer Windows probe installer.

Installing the Analyzer Windows probe

Install the Analyzer Windows probe by using the installer.

  1. Run the Analyzer Windows probe installer.

  2. To continue installation, click Next.

  3. In the Log on Information window, type the Domain Administrator or Local user name and password for the Windows machine in the format specified in the window, and click Next.

    NoteThe user must have the Administrator privileges and Logon as a Service permission.
  4. In the Choose Destination Location window, browse to select the installation folder, and click Next.

  5. In the Ready to Install the Program window, click Install to complete the installation.

  6. Click Finish.

    NoteIf you deselect the Launch Ops Center Analyzer Windows Probe check box, double-click the Ops Center Analyzer Windows Probe icon on the desktop. If you do not see the icon on the desktop, then open a command prompt and enter the following to refresh the icon in the database:

    ie4uinit.exe –ClearIconCache

  7. In the License tab, browse to the license file and click Submit to register the license.

Data collection method

You can use the following method to collect data using the Analyzer Windows probe:

Data collection using Perfmon API and WMI query

  • Performance and configuration data is collected from individual machines using the Perfmon API and WMI query.

Prerequisites

  • The probe machine and the target machines must be part of either the same workgroup or the same domain.

  • Firewall exceptions must be added for the WMI and Perfmon on the target machine. To add the firewall exceptions, run the following commands on the target machine:

    • netsh firewall set service RemoteAdmin
    • netsh firewall set service type=fileandprint mode=enable profile=all scope=all
  • To connect to Windows machines remotely, the following must exist:

    • The remote registry service must be running on the target machine.

    • The Local Service on the target machine must have read permissions for the following registry key:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
  • Users designated for this method must be added to the Local Group Policy on the target machine and the machine on which the Analyzer Windows probe is installed:

    Execute the Local Group Policy Editor (gpedit.msc), select Computer Configuration Windows Settings Security Settings Local Policies User Rights Assignment, and then add the users to the Log on as a service and Allow log on locally policy settings. In addition, make certain that the users are not present in the Deny log on locally setting (which would prevent them from logging in).

    In addition, make sure that the following default rights (policy settings) are assigned to the designated user:

    • Access this computer from the network
    • Adjust memory quotas for a process
    • Allow log on through Remote Desktop Services
    • Back up files and directories
    • Bypass traverse checking
    • Change the system time
    • Change the time zone
    • Create a pagefile
    • Create global objects
    • Create symbolic links
    • Debug programs
    • Enable computer and user accounts to be trusted for delegation
    • Force shutdown from a remote system
    • Impersonate a client after authentication
    • Increase scheduling priority
    • Load and unload device drivers
    • Log on as a batch job
    • Manage auditing and security log
    • Modify firmware environment values
    • Perform volume maintenance tasks
    • Profile system performance
    • Profile single process
    • Remove computer from docking station
    • Restore files and directories
    • Shut down the system
    • Take ownership of files or other objects
  • The authentication information (user name and password) on the Analyzer Windows probe server and the monitoring target server must match.
  • Distributed COM must be enabled in Component Services on the target machine and the machine on which the Analyzer Windows probe is installed. To enable distributed COM, perform the following procedure:

    Execute Component Services (dcomcnfg.exe), and then select Component Services Computers. When My Computer is displayed, right-click My Computer, and then select Properties. After that, select the Default Properties tab, and then select Enable Distributed COM on this computer.

  • For domain computers: A user with the Domain Administrator role or local administrator group of the target machine and the machine on which the Analyzer Windows probe is installed.

  • For workgroup computer: The following settings are required if you are not using the built-in administrator for connections:

    • You must be a user who has been assigned the Domain Administrator role and has permission to access WMI namespaces (ROOT\WMI, ROOT, and ROOT\CIMV2) on the target host.

      Execute Methods and Remote Enable permissions are required for the namespaces.

    • Change the settings for the Remote User Account Control (UAC) LocalAccountTokenFilterPolicy registry entry. For more information, see http://support2.microsoft.com/kb/942817/en-us.

    • The Computer Browser service must be running on the target machine.

Configuring Analyzer Windows probe

After installing the Analyzer Windows probe, you must configure a collection method, set up an HTTPS server, and start the service of the probe.

Configuring the data collection method

You must register the Analyzer Windows probe and select the data collection method for that Analyzer Windows probe.

  1. On the Analyzer Windows probe console, click the Collection tab, and configure the collection method settings:

    Data collection through WMI and PerfMon

    1. In the Performance section, select Use Perfmon.

      This enables the Use WMI option automatically.

    2. Type the following details for Use Perfmon and Use WMI options:

      1. User name (Administrator):

        • In Workgroup environment: Machine Name\User

          Computer Name: Machine name on which the Analyzer Windows probe is installed.

          User: A user with an Administrator role.

        • In the Active Directory environment: Domain Name\User

          Domain Name: Name of the domain.

          User: A user with the Domain Administration role.

      2. Password

    3. In the Performance section, select the Collect Process Data box if you want to collect process data.

  2. On the Collection tab, in the right-most side section:

    • Click Discover Hosts to discover the hosts available in the current domain. You can then select the target host that you want to monitor.

    • Click Add Hosts and type the host names manually. The Add Hosts window opens. Enter a comma-separated list of Windows machines (host names or IP addresses).

  3. Click Validate & Save to establish the connection, and click OK.

Configuring the HTTPS server

You must configure the HTTPS server for the Windows-based probe to send data.

  1. On the Analyzer Windows probe console, click the Upload Settings tab.

  2. On the Upload Settings tab, select HTTPS.

  3. Type the following details:

    • Protocol: HTTPS
    • Port: The port number is 443.

    • User: meghadata

    • Password: Enter the meghadata password obtained from your Hitachi Vantara representative.

  4. To use a proxy server, select the Use Proxy check box and type the following details:

    • Proxy Server: Name or IP address of the proxy server.

    • Proxy Type: Proxy type of the proxy server HTTP or SOCKS5

    • Port: Proxy port.

    • Login and Password: User name and Password of the proxy server.

  5. Click Validate & Save.

  6. Start the Analyzer Windows probe service.

    NoteThe Analyzer Windows probe must be installed on a Windows machine with the System Locale as English.

Starting the Analyzer Windows probe service

Start the probe service from the Status tab in the Analyzer Windows probe console.

  1. On the Analyzer Windows probe console, click the Status tab.

    The Status tab list the details of the upload information and service information.
  2. Verify the upload and service information, and click Start.

    NoteWhen you change the time zone of the Windows machine on which the Analyzer Windows probe is installed, restart the Analyzer Windows probe console to update the Analyzer Windows probe with this new time zone.

Downloading the Analyzer Windows probe diagnostic data

The Analyzer Windows probe collects various log files that are useful for troubleshooting. The Diagnostic Data feature provides the facility to download these files in an archive file. If you cannot resolve the problem, send the generated data file with the error messages to customer support for analysis.

Before you begin

  • To download diagnostic data, you must have the Administrator privileges.
  • Make sure that minimum 1 GB free disk space is available on the C drive.

Procedure

  1. On the Analyzer Windows probe console, click the Diagnostic Data tab.

  2. Click Download.

    The diagnostic data generation process begins.
  3. In the Save As window, choose any location to save the file and then click Save.

    Sample diagnostic data file name: Analyzer-Windows-probe_diag_20190611192343.zip

Initial setup after adding a probe

After adding a probe, check if Analyzer detail view is collecting data.

Procedure

  1. Log on to Analyzer detail view.

  2. Click the Server Status icon.

  3. Verify that the added probe appears in the Last Configuration Import Time and Last Performance Import Time of Data Import Status, and that data is collected.

    NoteAfter a probe is added, it might take some time before the probe appears in Analyzer detail view.
  4. Log on to Analyzer SaaS.

  5. In the Administration tab, select Resource Management.

  6. Verify that the resources monitored by the probe appear and are ready to be analyzed by Analyzer SaaS.

    NoteAfter a probe is added, it might take some time before the registered resources appear in Analyzer SaaS.

Uninstalling the Analyzer Windows probe

To remove the Analyzer Windows probe, use the uninstall function of Windows.

  1. Go to the Control Panel of the Windows machine.

  2. In Programs, click Uninstall a program.

  3. Select the Analyzer Windows probe to uninstall.

    To uninstall the Analyzer Windows probe, you must have the Domain Administrator or Local user with Administrator privileges.
  4. Click Uninstall/Change.

  5. Confirm the uninstall by clicking Yes.

  6. When the completion status message is shown, confirm it by selecting OK.

    The following files of the Analyzer Windows probe are not deleted after uninstalling the probe. (You can remove them manually.)
    • C:\Temp\HDCA\ProbeDataStatus.properties
    • C:\Temp\WindowProbeInstallerOutput.txt
    • C:\Temp\Collected configuration and performance files which are not uploaded

 

  • Was this article helpful?