m-milligan ✭✭✭✭✭

Yes, there's a Perl version here: Unmanage nodes Perl script for Linux

Glad it's working with a Solarwinds account. I have this working with an Active Directory account. When I created the credential file, I did not include the domain name in front of my username, i.e. I spelled it "username" instead of "DOMAIN\username". I haven't tested it with the domain name. Can you try omitting the…

I was able to reproduce this error by creating a credentials file with a misspelled password. Please re-create the credentials file and try the script again. Thanks for catching those errors in the script examples. I've fixed them in this document and in the scripts.

I've just uploaded a new version of this script that supports mute/unmute (suppress/resume alerts). To mute all items in a group you would use these parameters: -G <groupname> -suppress -minutes <number of minutes to mute alerts starting now>

I have not. Now that I know I should be able to see something, I'll open a ticket. Thanks!

I'm on 2019.4 and when I click on "Updates & Evaluations" I see... nothing. Do I have to configure something in my Orion environment before this works?

That script should also work in SQL Server 2016 and later.

sp_adduser and sp_addrolemember are both deprecated in newer versions of SQL Server. Newer versions need to use this instead: USE master GRANT VIEW SERVER STATE TO "Domain\AppInsightUser" GRANT VIEW ANY DEFINITION TO "Domain\AppInsightUser" CREATE USER 'Domain\AppInsightUser' GRANT EXECUTE ON xp_readerrorlog TO…

What version of Solarwinds are you using? Solarwinds' handling of time in the unmanage/remanage/suppress/resume functions was inconsistent when I wrote this (some functions expected UTC, some expected local time). My code accommodated that. Perhaps those functions have been revised so they're more consistent. I'll take a…

The script only handles a single node on the command line. However, you can put several nodes in a Solarwinds group and then specify that group on the command line. If you do that, the script will work on all nodes (or other items) in the group.

I may do this in the future. For now you can do this my adding the selected app monitor(s) to a group and then muting the group. The script will loop over all items in the group and mute them.

If you search for SWUnmanage.exe*, does Window find anything at all? What happens if you explicitly choose the "run as administrator" option with Setup.exe?

You can install this on any server from which you want to run the program. If you're using the program with scheduling software (e.g. Windows Schedule), you'd install it on the server that runs the scheduler.

Posted update. Updates: * Corrected command line syntax. -D is required to disable notifications and management. Leaving off the -D will enable notifications and management. * Increased maximum value of -t from 65535 to 4294967295 (int16 to int32)

Thanks! This will save us a lot of wasted scrolling and clicking.

Good catch! I've swapped the queries.

dlepi, were you ever able to get this to work? For testing, there's no reason you shouldn't be able to hard code the values you need.

I looked at the code in Encrypted.pm. This error is thrown when the key file doesn't begin with the string "SSH PRIVATE KEY FILE FORMAT 1.1". Does your key file contain this string? Is it a different format?

The script only acknowledges the alert. It doesn't clear it. I second adbs98 - check your alert reset configurations to see if they're set to clear themselves after a few minutes.

That's a cool idea. I can look at working that into the next version. Maybe require "unman" followed by the number of minutes to unmanage (or indefinitely if there's no number)?

What version of SAM are you using? If you're using the newest version, you should be able to search for the Alert Notes widget when you click the Customize Page icon, like this: If you're using an older version, you can search for the Alert Notes resource. Click the Customize Page icon and then click the Add resource icon:…

I haven't come up with a fix for this yet. I could probably do something where the email includes a warning to "comment above this line" and then truncate anything below the line. There is an "Alert notes" widget that I added to the Alert Details page in my SW implementation, and that's where the ack comments show up. Does…

I got similar errors when they changed the load balancer configuration for our email server pool. I had to change the URL to point to a specific server in the pool. Are you also dealing with a load balancer? Can you try changing the URL to point to a specific server?

Sorry, I meant can you show me the contents of the variable that is called $inbox in the script when you run it. I wonder if the script isn't getting a valid response from your email server. "ack" is the correct response to the Solarwinds email. Make sure your reply email includes all of the stuff in brackets [] at the…

Can you dump the contents of $inbox? Does it look it ought to be valid XML, or is it obviously not?

Can you paste line 297 from your code here? I'm not having problems with it on my system. You can also try replacing it with this line: Write-Host "Number of unread messages in",$($inbox.DisplayName),":",$($inbox.UnreadCount)

The Active Object ID is different depending on the kind of object. For nodes, I just use the NodeID, like this: For applications, I use the ApplicationID: For disk volumes, I use the VolumeID: I like your approach better, though - it's more universal, so it can be cut & pasted without regard for the type of object in the…

Thanks for coming up with this fix. What version of SAM and Orion are you using? Acknowledgements appear to be working properly for my installation using the code I posted. I just want to be sure this isn't related to the version of SAM or Orion before updating the instructions for all versions. Thanks.

I'm monitoring it, but we aren't using O365 so I can't answer your question. jkrenzien​ , did you get this to work with your Office 365 environment?

I haven't run into this error before, but it looks like this is usually a problem with SSL. One workaround is here: EWS Api problem connecting Inbox (look for Glen's reply about halfway down the page).