With the assisted install of the infrastructure agent for Windows, you can make the changes you need to the installation script we provide so you can adapt it to your environment. Before installation, make sure to check the compatibility and requirements.
Install the agent
To install the agent:
Download the packaged agent file or use the following command that automatically fetches a specific version of the agent, its checksum and verifies it after download. Replace
$arch=amd64with desired architecture (amd64, 386) and$v=1.27.4with latest or specific version.bash$$v="1.27.4"; $arch="amd64"; $url="https://download.newrelic.com/infrastructure_agent/binaries/windows/$arch/newrelic-infra-$arch.$v.zip";@("$url", "$url.sum") | ForEach-Object { Invoke-WebRequest -Uri $_ -OutFile $_.Split('/')[-1] }; write-host 'Checksum:' $(If (Select-String -Path "$url.sum".Split('/')[-1] -Pattern (Get-FileHash $url.Split('/')[-1]).Hash -Quiet) {"Ok"} Else {"Fail"})Unpack the file.
Make sure the file unpacks with the following structure:
Once it's unpacked, access and edit the installation PowerShell script
installer.ps1.Update your .
Optional: Update any other parameters.
Execute
installer.ps1with admin rights.
Did this doc help with your installation?
Configure your installation
Important
Make sure any custom folder defined in the installation settings has permissions limitations properly defined. The infrastructure agent might execute any integration defined in the NRIA_PLUGIN_DIR directory with Administrator permissions.
You can configure the following parameters during the assisted install for Windows:
Variable | Description |
|---|---|
Required at agent startup. | The agent home directory. Default: |
| This configures the data directory to store inventory and other agent files. Default: |
Required at installation. | The agent configuration file's location. Default: |
Only configuration option required at startup. | The New Relic . |
Required at agent startup. | The location where the agent will log. Default: |
| By default and for security reasons, Windows does not install a service if there's another service with the same name already installed. To bypass this check, make sure this setting Default: |
Required at agent startup. | The directory containing the configuration files of the integrations. Default: |
| This provides the name for the Windows service. |
What's next?
You may also want to:
- Add custom attributes to annotate your infrastructure data.
- Connect your AWS account if your servers are hosted on Amazon EC2.
- Add other New Relic infrastructure integrations to collect data from external services.
- Manually start, stop, restart, or check the agent status.