Appinsight for IIS / DMZ

Question

I am having problems getting the Appinsight for IIS to work with my DMZ servers.  I am getting the following error.

Error code 16013 unable to access remote admin share.  The help takes me to the following link.  Error Code 16013

Previous post have mentioned using an agent to connect.  While this is an option, I would prefer to go agentless.  I have a poller in the DMZ.  When configuring it, shouldn't that poller be used?  If so, I would think that the poller has all of the access that it needs.  Am I missing something about how the SAM polling works?

aLTeReGo · Answer

AppInsight's Zero Config requires access via SMB/CIFS to the administrative share to copy over a configuration script which configures WinRM automatically for you. If that protocol is blocked (can't map a drive to the administrative share on that computer from the orion server) then your only option is to configure WinRM yourself manually or install an Agent on that machine.

mprobus · Answer

For those that may run into the issue.  After I went through the manual configuration steps, I noticed that everything was polling except the 3 monitors that are categorized as Custom WMI (SSL Certificate Monitor, Site Log Directory Monitor, and Site Directory Info Monitor).  Since I had already manually configured the server, I was able to go in and use the Auto Configure, which fixed the polling on the last 3 items.

mprobus · Answer

I was able to get it to work by configuring manually.  I had tried it previous, but could not get it to work.  Turns out that was my mistake as I was trying to run the winrm config from powershell instead of a command prompt.

I am still curious as to why the Auto Configure doesn't work.  It seems that the primary app server is trying to do the configuration instead of relying on the APE to carry out the task.