martian_monster · Lead System Engineer · ✭✭✭✭✭

I went through and deleted the AWS account and was able to add it back with no issues. I went through to Edit the account and am getting the same error now. Some kind of bug?

So after you hit fixed disc you need to Add a Double Value Comparison and that allows the trigger condition that I was looking for. You had be on the right track my brain just did not put them together.

It has been awhile so maybe it was not a floating point custom property. Essentially it lets me adjust per volume instead of the entire node. 

This is what i am looking for. I have this configured and working in my Orion environment. I am working on setting this up with a company we acquired and I cannot get this trigger condition to show up. I have had this alert setup for quite some time and of course the notes I have on this do not mention this part. 

Figured out how to fix this with the Probes staying in Netpath Find node in Node Manager Change from Agent to WMI Leave the Agent installed on the machine Let the node poll via WMI Go back to the node in Node Manager Change it from WMI to Agent Let the node poll BOOM! Fixed the Agent stuck at update and Netpaths are…

This also fixes odd issues with AppInsights for IIS. I will be adding this to my Solarwinds Orion update process. 

Looks like I may have found a bug in 2023.3. I updated my APE to 2023.3 and the PowerShell monitors are dead again. I really miss 2020.2.6.

Can I just update the APE from the console?

Odd fun thing. Everything is working fine this morning. BUT I just discovered it looks like my MPE was updated to 2023.3 correctly when I ran the update on 9/12. I checked the APE and it looks like the update never made it that far it is still on 2023.2. 

So Windows Firewall decided the other night to block Netflow. No windows updates or anything. It just decided to stop blocking the port

That is what we are doing. Setup the script to run via PowerShell from both Polling engines and it worked. Tried to run the same script with the same account in Solarwinds and it times out. WMI is connecting just fine the issue is something with Solarwinds and the PowerShell monitor.

I worked with the System Engineering team to try and figure out the issue and it looks like the issue is something with Solarwinds trying to run the PS script. This issue cropped up roughly 2 days after updating to 2023.3 last month. We have a MPE and APE Tested Monitor through Edit Template in SAM. This failed about 90%…

I found this link - View online Received an update from Support and made the following changes which appears to correct the issue. These changes were done on the APEs and the Primary server. File: %SolarWinds Install Directory%\SolarWinds\Orion\SolarWinds.APM.Probes.dll.config Backup the file above Launch Notepad.exe in…

Port 5985 is open but Port 5986 is not. At this point that is the only thing so far that I can figure out. 

I am trying to figure out if something was changed or udpated in PowerShell. The stage monitor started acting up earlier in September but it was not doing the same odd things that I found on Prod this morning. I know it is 'something' with PowerShell doing something with the node. Once I find that something I will make…

Node is up and polling just fine via WMI. 

Polling via WMI. I have a handful of Agents on nodes. I normally only do agents for Netpath. 

Set as Remote Host. Local host does not generate the correct data. I think this is what you were looking for. I am very green when it comes to PowerShell and Solarwinds.

This issue raised its head again today but it took out a server in the process. To the best of my knowledge nothing changed on these nodes. I working on checking out what patches were applied this month to see if MS had its hand in this. I logged in this morning and one of my nodes was showing two monitors as unknown and…

I think there is an issue with this particular node and it not liking monitors with PowerShell scripts in it. I was looking at a Folder Stats monitor and I tested on the Stage node and it failed with unknown user name and password. I tested against Prod and it worked just fine. It has something to do with PowerShell..…

That setting is disabled currently. I think it is a one off issue with the users PC. I really fun issue but I think we have it solved. 

Deleted and recreated account and the issue is still happening. We had him login on a different PC and it worked. So it might be something on his PC. 

There are not duplicate accounts in the database - his regular account and admin account (which are different) are both listed. 

Do you know which logs in Orion that this writes to?

Two separate accounts. 

AD users via LDAP. The user has two separate accounts one for dashboards and one for Admin access. So I might need to go in and delete his Admin account and add it back?

I think this is what I will need to do -support.solarwinds.com/.../Turn-off-HTTP-traffic-in-DPA-Port-8123

Yaay Microsoft. Thank you and everyone else for your assistance.

So after testing and changing the application the one that worked was application/json. 

Thank you!!!! You really are Nate The Great. I will do some updating and testing. Odd thing - One of my alerts started firing off to Teams two days ago but just one of my Teams alerts. Yaay MSFT. lol