bartsigler

I couldn't agree more. Having the ability to monitor through multiple layers of security outbound to cloud based Orion data collectors makes the SW Agent invaluable. All monitoring functionality through the agent should be the direction Solar Winds takes.

I agree that this is a Microsoft Registry Key but I think the agent is writing to it which is why it hit on my search of the registry for "solarwinds". Here is a snip of the Data inside the key under solarwinds. Its rather lengthy. It It may not be of any value regarding this issue but I think its worth a look. Solarwinds:…

Hi prawij, Here is a screen shot for you.

I did just as you suggested and then some. I even removed the node from Orion. I uninstalled the Agent and cleaned the server registry of all entries called "solarwinds" then I reinstalled the agent manually. Within minutes of the agent reinstall SWJobEngineWorker2.64.exe had chewed up 1GB of RAM and continued before I…

I did open a case on this with support. I did these steps in Order and the problem stopped. I'm puzzled about the results but my case has been closed out. 1.) Removed applinsight for IIS from the Node in Orion 2.) Removed the QOE sensor from the Node in Orion 3.) Removed the Node from Orion completely 4.) Uninstalled the…

I agree with aLTeReGo's response in this specific scenario. I would like to add that The primary reason we went with SolarWinds over other products was because of the Agent and its ability to initiate outbound communications that are Encrypted and Secure. Also the Agent initiated communications didn't require us to open…