19 Replies Latest reply on Apr 29, 2014 10:21 AM by grahambird1980

    Problems getting AppInsight for Exchange working

    grahambird1980

      Hello,

       

      I am trying to get the AppInsight for Exchange working by following the Online Help.

       

      1. So far I have checked that the service account we use for SolarWinds has the correct permissions on Exchange, which it does.

       

      2. I have used the PowerShell script provided to generate a self-signed Cert, Before I go any further I would just like to check a few things.

           a. This script needed to be run on the Exchange server I want to connect to?
           b. To locate the Certificate Thumbprint I opened an MMC on the Exchange server and added the Certificates Add-in (connected to the local computer), then found the Cert under the Personal Certificates.
               I should point out that I only found this by running the script a few times and watching for the additional certificates being created (I deleted the old ones)
              

           Is it correct that the Certificate should show as;
                 Issued To = [not available]
                 Issued By = [not available]
                 Frendly Name = <none>

       

           If this is the case I will put a suggestion to SolarWinds technical support to have the Online Help updated

       

      3. So if I have done the Cert part correctly this is where I am running in to issues, I am not able to get the configuration of the WinRM 2.0 to work.

       

      PS C:\Scripts> winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="10.10.14.200_Solarwinds_Exchange_Zero_Configuration";CertificateThumbprint="2eae0667dfcaee1d1fc4ff0cbdbf72930b1fcb7a"}

       

      Error: Invalid use of command line. Type "winrm -?" for help.

       

      I have run the above command using a Powershell session (run as admin) and if I run it in a standard command prompt (run as admin) I get the following error

       

      C:\>winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="10.10.14.200_Solarwinds_Exchange_Zero_Configuration";CertificateThumbprint="2eae0667dfcaee1d1fc4ff0cbdbf72930b1fcb7a"}
      WSManFault
          Message
              ProviderFault
                  WSManFault
                      Message = An internal error occurred.

      Error number:  -2147023537 0x8007054F
      An internal error occurred.

       

      Thinking it might have been that winrm was not setup I ran the following;

       

      C:\>winrm quickconfig -q
      WinRM already is set up to receive requests on this machine.
      WinRM already is set up for remote management on this machine.

       

      So I am at a bit of a loss as to why this is failing, a Google of the Error number is not overly helpful ether.

       

      Has anyone else experienced issues like this?

        • Re: Problems getting AppInsight for Exchange working
          Jonathan Angliss

          My first question would be to check if the auto-configure option works? It took me a little bit to figure out where to find it, but if you add the AppInsight to the host, then edit the application, you have a button to configure it...I wrote up a quick blog post on it the other day.

           

          http://jon.netdork.net/2014/04/17/solarwinds-application-monitor-automatically-configuring-appinsight-for-exchange/

           

          If you don't want to do the auto-configure route (give it a shot if you can, you can always remove the admin access after), then there are some caveats to doing it manually.  In answer to your questions:

           

          1. Excellent, that's the easy bit

          2. Certs

                a) Yes, I didn't find this clear in the instructions, but it gets run on the Exchange server

                b) Yes, the missing information is correct.  The PowerShell script they provide creates a self-signed certificate.  If you wanted to make it all "legit" you can manually create a certificate and sign in by your certificate authority on your domain if you have one, but it's not needed for this purpose.

           

          3. This got me too. The command won't run as is in a PowerShell window.  This is because some of the characters (for example the { and }) are special for PowerShell.  The quickest solution is to pop open a command prompt window with elevated access (run as admin).  Paste the command in there, and you should be off to the races.

           

          If you've already run the quickconfig what you'll find is it setup an HTTP listener, while SAM is trying to setup and HTTPS listened.  You can verify this by doing the following:

           

          winrm e winrm/config/listener
          

           

          Try running your command again in a command window, and then run the above again, and you should now see an HTTP and HTTPS listener.

           

          Before autoconfigure/manual configure (but after quickconfig)

           

          PS C:\> winrm e winrm/config/listener
          Listener
              Address = *
              Transport = HTTP
              Port = 5985
              Hostname
              Enabled = true
              URLPrefix = wsman
              CertificateThumbprint
              ListeningOn = 10.0.0.65, 10.5.22.63, 127.0.0.1
          
          

           

          After autoconfig/manual config

           

          PS C:\> winrm e winrm/config/listener
          Listener
              Address = *
              Transport = HTTP
              Port = 5985
              Hostname
              Enabled = true
              URLPrefix = wsman
              CertificateThumbprint
              ListeningOn = 10.0.0.65, 10.5.22.63, 127.0.0.1
          
          
          Listener
              Address = *
              Transport = HTTPS
              Port = 5986
              Hostname = 10.5.22.63_Solarwinds_Exchange_Zero_Configuration
              Enabled = true
              URLPrefix = wsman
              CertificateThumbprint = E798FE9DD46D3EA0CE971EA9E44B99B3DE8BD5AB
              ListeningOn = 10.0.0.65, 10.5.22.63, 127.0.0.1
          
          

           

           

          I hope that helps a bit.

          • Re: Problems getting AppInsight for Exchange working

            This will be the new addition, hopefully making things a bit easier.

            new.png