We've got a large number of boxes that we'd like to apply AppInsight templates to, specifically, AppInsight for IIS. Will the AppInsight templates support communications over HTTP transport (not HTTPS transport)? As you can probably tell, we're trying to avoid the additional workload of properly configuring the HTTPS transport. For the node that we'd like to assign the AppInsight template, does it need to be monitored via WMI or will monitoring through SNMP be sufficient?

Never mind, we got it working. I had to enable the WinRM service on the poller and then add the remote hosts to the list of TrustedHosts. Again, this is only seems to be required for AppInsight over HTTP. I have another question but I'll post a new thread about this since it's no longer related to AppInsight requirements.

This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

AppInsight requirements?

qle over 8 years ago

We've got a large number of boxes that we'd like to apply AppInsight templates to, specifically, AppInsight for IIS.

Will the AppInsight templates support communications over HTTP transport (not HTTPS transport)? As you can probably tell, we're trying to avoid the additional workload of properly configuring the HTTPS transport.
For the node that we'd like to assign the AppInsight template, does it need to be monitored via WMI or will monitoring through SNMP be sufficient?

Top Replies

aLTeReGo over 8 years ago +1

You can configure the URL AppInsight uses to collect data via PowerShell so that it uses HTTP rather than HTTPS. Alternatively you can use our free Remote Execution Enabler for PowerShell ‌ tool to easily…

0 aLTeReGo over 8 years ago

You can configure the URL AppInsight uses to collect data via PowerShell so that it uses HTTP rather than HTTPS. Alternatively you can use our free Remote Execution Enabler for PowerShell‌ tool to easily configure secure WinRM in masse/bulk instead. Once this tool is used, no further configuration is required to monitor those servers using AppInsight for IIS.
Cancel
Vote Up +1 Vote Down

Cancel
0 qle over 8 years ago in reply to aLTeReGo

aLTeReGo‌, thanks, I'm glad to hear that. We actually have it configured for HTTP on port 5985 but we're having trouble assigning AppInsight for IIS to a node. During the assignment, when I attempt to test the conection, I get the following error message:
"Timeout occurred during long operation. Retry last operation again please."
No matter how many times, I've tested, I still get the same message. I've confirmed that the credentials and connection does work. Using Powershell on the SAM poller, I'm able to create a remote PowerShell session to the remote node using the same credentials I'm trying to apply to the AppInsight template. Any idea what I am probably doing wrong?
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 8 years ago in reply to qle

Using HTTP vs HTTPS doesn't negate the need for some degree of configuration on each endpoint, as well as the Orion server itself. What if any configuration have you completed to allow WinRM over HTTP? Also, it's important to note that Microsoft does not allow WinRM over HTTP between hosts that are in different domains. E.G. if the Orion server is in Domain "A" and the Exchange is running in Domain "B", WinRM over HTTP is not allowed. HTTPS must be used.
Cancel
Vote Up 0 Vote Down

Cancel
0 qle over 8 years ago in reply to aLTeReGo

aLTeReGo‌, thanks for the response. Once the automatic configuration failed, we attempted the manual route as outlined in the SAM manual. This is on Windows Server 2012 R2. Of the six steps to manually configure AppInsight for IIS‌, we skipped the step for the certificate since we're trying to get this working over HTTP. Attempting to apply the IIS AppInsight template still results in the same error message.
Cancel
Vote Up 0 Vote Down

Cancel
0 qle over 8 years ago in reply to qle

Never mind, we got it working. I had to enable the WinRM service on the poller and then add the remote hosts to the list of TrustedHosts. Again, this is only seems to be required for AppInsight over HTTP.
I have another question but I'll post a new thread about this since it's no longer related to AppInsight requirements.
Cancel
Vote Up 0 Vote Down

Cancel
0 muckman over 8 years ago in reply to aLTeReGo

Is there any way to replace the self signed certificate used in the Remote Execution Enable for Powershell tool or the Zero Configuration Wizard? We have to apply AppInsight monitors to hundreds of servers and its great that you have utilities to simplify the deployment process but it appears to only work with your self signed certificate. We we like to use our own certificate from our CA. Is there anyway to do that in bulk without manual deployment to each server?
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 8 years ago in reply to muckman

There is no requirement to use the included self-signed certificate, but you will need to configure the server for WinRM manually using the steps outlined in the link below, excluding step #3.
http://www.solarwinds.com/documentation/en/flarehelp/SAM/default.htm#samagappinsiisadvconfig.htm
Cancel
Vote Up 0 Vote Down

Cancel
0 cmazko over 6 years ago in reply to qle

The link provided in the original post for manually configuring AppInsight for Exchange is outdated. Please see Configure AppInsight for Exchange on nodes - SolarWinds Worldwide, LLC. Help and Support instead.
Cancel
Vote Up 0 Vote Down

Cancel