tjkru · System Engineer · ✭✭✭✭✭

I will open a case with support including the MIB file. I will also want to make custom pollers based on the OIDs.

@"itengineer" wrote:What about the alert polling interval, do you need to configure it as well? For our purposes this was mainly to generate a report stating what servers rebooted when. Any Windows servers that reboots will trip this monitor. Ours are set to reset the monitor shortly after it is tripped. As long as the…

I had this same issue. Found a solution that worked of me. I am using Server 2016 both on the Solarwinds nodes and the host that had the issue. This host was managed using an agent. Found the solution in the another Thwack post. I basically removed and re-added the failing SAM application from the specific node it was…

Thanks for the update. I had to change my view to the legacy view to find what I was looking for. Guess the new view was what was causing the confusion. 

Create a monitor to look for Event ID 6006 in the Windows System Log. This will be placed there when the server comes back up. I had to take this rought for the same reason you stated.

I have found the answer to this issue. There are two different layers in ePO 10.6 that have to have exceptions applied. Both must include the path that the SOLARWINDS.BUSINESSLAYERHOSTX64.EXE file exist in.

Thanks for the information. That is what I thought I was going to find out. 

Selecting Add Widget to a view and then selecting a Custom Table will allow you to add a report as a widget. Great if it does not display to much data and consume the complete UI. I was able to make a Agent Version widget to monitor the deployment of the new Solarwinds Agent after the upgrade. This avoids the need to open…

Found the issue. Apparently this is a generic error. All of these machines could be pinged etc. One was not properly joined to the domain. One did not have the proper rights for the user selected to perform the installation with. 

Thanks for the update that this is not supported. I think I have found a workaround that will work in my case. The Machine Type field is only populated via the agent. There for attempting to filter for nodes that are monitored by the agent I need to look for ones with a value for the Machine Type field. Not what I was…