There are two methods of manually adding AppInsight for IIS to server (that i'm aware of, and i'm not counting when it gets added during a network sonar scan...that's automated).
1) Manage the node, click List Resources, wait for the list to populate, select the AppInsight Applications -- Microsoft IIS item, click Submit. Go to My Dashboard -- Applications -- SAM Summary, expand the AppInsight for IIS tree item, locate the node you just added it to, expand it, click Microsoft IIS, there's a popup for configuring the remote server to work with AppInsight, pick the credentials (I use <Inherit credentials from node>), test credentials, assuming that works, click configure and wait for it to finish. In my environment, this process works.
2) Go to Manage Applications, locate AppInsight for IIS, select it and click Assign to Node, on the next page click Browse... and select the node, the server IP address is populated in Server IP Address field, choose credentials (again, here I use >Inherit credential from node>) and click Test Connection....this is where it goes off the rails for me (see screenshot).
So my question is, what's the difference between the two methods? Why would the first work while the second fails? Does the second method just require manually configuring the server, as alluded to in the "Configuring the IIS Server" tip shown to the right of the config section in the screenshot...and if so, again...why? Why doesn't it work the same way as option 1?
All nodes are all polled via WMI.