Just to follow up on this, we found some errors that could indicate that TLS settings were not configured properly to allow the systems to communicate with New Relic servers.:
NewRelic.ServerMonitor.exe System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation
More info on how to configure these settings:
Another possibility is that this was a certificate issue. If the below test fails, it could indicate that a required certificate either on the web server or proxy server (if being used) will need to be updated.
You will need the
DigiCert Global Root CA certificate. You can use this resource to confirm you’re utilizing the correct certificate.
You can also verify this is the issue by testing this endpoint in Powershell:
Invoke-WebRequest -Verbose -Uri https://connection-test.newrelic.com
Finally, you can also try disabling SSL on the agent.
Servers for Windows includes a Configuration utility shortcut in the Windows Start menu’s New Relic Server Monitor folder. Use the Configuration utility to:
Stop or restart the Servers for Windows monitoring service.
Create labels and categories to manage groups of servers.
Use SSL when communicating with the New Relic collector.
Specify a different logging level.
Configure a proxy URL by using the HTTP proxy address, user name, and password.
I hope that helps anyone else experiencing similar errors.