Install the infrastructure monitoring agent for Windows

With New Relic's infrastructure monitoring agent for Windows, you can monitor individual servers and also analyze how your service performs as a whole. The Windows agent can run on your own hardware or in cloud systems such as Amazon EC2 or Windows Azure.

The infrastructure monitoring agent supports Windows Server and Windows 10. You can also install with Chef.

To use infrastructure monitoring and the rest of our observability platform, join the New Relic family! Sign up to create your free account in only a few seconds. Then ingest up to 100GB of data for free each month. Forever.

Install for Windows Server and Windows 10 using our wizard

Before installation, be sure to review the requirements. Then, to install the infrastructure monitoring agent for Windows, you can use our launcher, or follow the instructions in this document to complete a basic installation.

amazonlinux.png
Windows

If you don't have a New Relic account yet, or prefer to follow the procedure manually, follow our step-by-step tutorial, which follows.

To install the infrastructure monitoring agent, use our PowerShell script, or follow the step-by-step instructions:

PowerShell install
  1. Review the agent requirements and supported operating systems.
  2. Open the PowerShell as administrator and run the following command:
    32-bit Windows
    $LICENSE_KEY="YOUR_LICENSE_KEY"; `
    (New-Object System.Net.WebClient).DownloadFile("https://download.newrelic.com/infrastructure_agent/windows/386/newrelic-infra-386.msi", "$env:TEMP\newrelic-infra.msi"); `
    msiexec.exe /qn /i "$env:TEMP\newrelic-infra.msi" GENERATE_CONFIG=true LICENSE_KEY="$LICENSE_KEY" | Out-Null; `
    net start newrelic-infra
    64-bit Windows
    $LICENSE_KEY="YOUR_LICENSE_KEY"; `
    (New-Object System.Net.WebClient).DownloadFile("https://download.newrelic.com/infrastructure_agent/windows/newrelic-infra.msi", "$env:TEMP\newrelic-infra.msi"); `
    msiexec.exe /qn /i "$env:TEMP\newrelic-infra.msi" GENERATE_CONFIG=true LICENSE_KEY="$LICENSE_KEY" | Out-Null; `
    net start newrelic-infra

For a scripted installation, you can pass in configuration parameters. You must first add GENERATE_CONFIG=true and LICENSE_KEY=YOUR_LICENSE_KEY. You may then add these optional config settings:

  • DISPLAY_NAME=YOUR_DISPLAY_NAME
  • PROXY=http://YOUR_PROXY_SERVER:PROXY_PORT
  • CUSTOM_ATTRIBUTES="{'ATTRIBUTE_1':'VALUE_1','ATTRIBUTE_2':'VALUE_2'}"

The following example sets the license key and configures a proxy server for outbound communication, as well as adding one custom attribute:

msiexec.exe /qn /i PATH\TO\newrelic-infra.msi GENERATE_CONFIG=true LICENSE_KEY=YOUR_LICENSE_KEY PROXY=http://YOUR_PROXY_SERVER:PROXY_PORT CUSTOM_ATTRIBUTES="{'ATTRIBUTE_1':'VALUE_1'}"
Step-by-step install
  1. Review the infrastructure monitoring agent requirements and supported operating systems.

  2. Download the latest .MSI installer image from:

    32-bit Windows
    https://download.newrelic.com/infrastructure_agent/windows/386/newrelic-infra-386.msi
    64-bit Windows
    https://download.newrelic.com/infrastructure_agent/windows/newrelic-infra.msi
    

    Do not double-click the installer. This will not fully install the local agent and can result in permissions issues.

  3. In an admin account, run the install script using an absolute path.

    32-bit Windows

    To install from the Windows command prompt, run:

    msiexec.exe /qn /i PATH\TO\newrelic-infra-386.msi
    
    64-bit Windows

    To install from the Windows command prompt, run:

    msiexec.exe /qn /i PATH\TO\newrelic-infra.msi
    
    Scripted installation

    For a scripted installation, you can also pass in configuration parameters. You must first add GENERATE_CONFIG=true and LICENSE_KEY=YOUR_LICENSE_KEY. You may then add these optional config settings:

    • DISPLAY_NAME=YOUR_DISPLAY_NAME
    • PROXY=http://YOUR_PROXY_SERVER:PROXY_PORT
    • CUSTOM_ATTRIBUTES="{'ATTRIBUTE_1':'VALUE_1','ATTRIBUTE_2':'VALUE_2'}"

    The following example sets the license key and configures a proxy server for outbound communication, as well as adding one custom attribute:

    msiexec.exe /qn /i PATH\TO\newrelic-infra.msi GENERATE_CONFIG=true LICENSE_KEY=YOUR_LICENSE_KEY PROXY=http://YOUR_PROXY_SERVER:PROXY_PORT CUSTOM_ATTRIBUTES="{'ATTRIBUTE_1':'VALUE_1'}"
  4. Add your New Relic license key to the license_key attribute in newrelic-infra.yml, located in C:\Program Files\New Relic\newrelic-infra\. When finished, the contents of newrelic-infra.yml should resemble the following:

    license_key: YOUR_LICENSE_KEY
  5. Start the newrelic-infra service. To start from the Windows command prompt, run:

    net start newrelic-infra

Wait a few minutes, then view your server in the Infrastructure UI. If no data appears after waiting a few minutes, follow the troubleshooting steps.

As of version 1.4.0, the infrastructure monitoring agent package includes newrelic-infra-ctl, which is used to help troubleshoot a running agent. We recommend adding it to PATH.

What's next?

The only required configuration option is the license_key setting, which is created as part of the installation procedures. You may also want to:

Install using zip files

For custom setup scenarios, you can install the infrastructure monitoring agent using our zip files in assisted or manual modes. This is especially useful when you need to adapt the default installation settings to your environment.

Installing the infrastructure monitoring agent using zip files is not supported.

Update the agent

To upgrade to the latest version, follow standard procedures to update the infrastructure monitoring agent.

For more help

If you need more help, check out these support and learning resources: