This page describes how to install Windows using ZIP with bundled JRE.
For some versions of Windows Server 2008 and Windows Vista, the Avg Read and Write Time disk metrics are reported as 0. This is due to a known Microsoft Windows bug. See Microsoft Knowledge Base
If this affects you, download the available hotfix. This refers to the following metrics:
Hardware Resources|Disks|<mount_point>|Avg Read Time (ms)
Hardware Resources|Disks|<mount_point>|Avg Write Time (ms)
Install the Agent
Before installing, see Install the Machine Agent
Install all available Windows updates.
If you have not restarted your machine recently, you must restart it. Failure to do so may cause your machine to experience a CPU spike when you start the Machine Agent.
- Download and unzip the Windows ZIP bundle. Extract the contents to the agent installation directory <machine_agent_home>.
- Gather your configuration details and configure the agent by editing the <machine_agent_home>/conf/controller-info.xml file or by adding system properties to the JVM startup script file.
See Plan the Machine Agent Configuration
- (Required) Configure the Controller host name, port number, and account access key.
- (Required for Multi-Tenant Mode or SaaS installations) Configure the Agent Account Information. See Controller Accounts (Multi-Tenancy)
- (Optional) Review memory requirements. See Machine Agent Requirements and Supported Environments
- (Optional) Configure the agent to use SSL. See Enable SSL for Standalone Machine Agent
- (Optional) Configure the agent to use proxy settings. See Standalone Machine Agent Configuration Properties
- (Optional) Determine if you need to specify an application name and tier name. See Standalone Machine Agent Installation Scenarios
However, if you are installing the Standalone Machine Agent on the same server with any APM app agent, do not specify the application name and tier name.
- Start the agent. If no
-Doptions are required on the command line, you can run the following .vbs scripts by selecting them from Windows Explorer.
As a Windows Service - Administrative privileges are required. You can specify AppDynamics-specific
-Doptions from the command line or edit the controller-info.xml. You can also add other JVM properties as needed.
Open a terminal window and enter:
You can now start or stop the Appdynamics Machine Agent service from Windows Services.
From an application in the terminal window, enter:
The usage parameters for
The following is an example of machine-agent.vbs: