aLTeReGo ✭✭✭✭✭

* Navigate to solarwinds.leapfile.com. * Click Secure Upload. * Enter <a class="jive-link-email-small" href="mailto:support@solarwinds.net">support@solarwinds.net</a> in the Recipient Email field. * Click Start. * Complete the Secure Upload form and click Select files to send (Regular Upload). * Click Choose File and…

The inclusion of minor revisions in the drop down is a bug which will be addressed before we GA. The 'official" supported distributions at this time include. * RHEL 6, 7 * CentOS 5, 6, 7 * Ubuntu 14 The next Beta should include support SuSE and Amazon Linux AMI. Was there any particular distribution you were looking for?

That will mostly depend upon the number of bugs found during beta. Beta 3 is currently available, and a beta 4 may be released in the next week or two.

Never soon enough.

is correct. Many customers who own NPM and SAM manage their servers via SNMP so they can monitor network interface statistics on their servers. This is something SAM is working to natively support so you can continue to monitor network interfaces on your Windows servers for WMI managed nodes.

AppInsight for IIS and any new product features introduced in SAM 6.2, (as well as those in NPM 11.5, SRM 6.0, VMAN 6.2, WPM 2.2) and any other introduced in the future will only support the new Web Based Alert Manager. The Legacy Win32 Advanced Alert Manager remains available only for backwards compatibility with previous…

NPM uses SNMP to collect data so that typically does not require specific permissions beyond a read-only SNMP community string.

The agent in indeed performing the job locally, but it must connect to WMI somehow to collect information. Can you attempt the same task on the machine where the agent is running using wbemtest.exe and connecting to the machine's IP address reference above?

As a possible workaround if you manage to catch this at the right time when the pop-up occurs you can enable X/Y mode to click the "X" in the top right of the popup. This should close the window when/if it appears and have no effect on the rest of the recording if it doesn't. Then disable X/Y mode and continue recording…

If you are monitoring a node that's in a workgroup (non-domain), you need to disable remote User Account Control (UAC). Disabling remote user account control does not disable local UAC functionality. To disable remote UAC for a workgroup computer: Using an administrator account, logon the computer you want to monitor. Go…

That is true. Personally I blame Bronx‌.

I got bit by this too. It seems in the posting found here that the link for production isn't hot, and the link for the eval is. So breezing through I naturally clicked the hot link and installed. DOH!

I'm not sure I follow, but what I believe you're asking is how can you assign application templates to nodes based on dynamic groups? If that is indeed your question, SAM does not yet support assignment of application template to groups.

SAM has no such limitation. The only limitations related to parallel PowerShell session limits come from the Windows operating system itself. They are designed to limit potential misuse by worms/viruses, control resource consumption, and can be altered to increase this limit as needed on a machine by machine basis.

PowerShell scripts can take longer to startup (spawn the PowerShell.exe process) load the necessary cmdlets, and execute than you've allowed with 1 minute polling. This is especially true where WinRM is involved. It's also important to note that the timeout value applies the the application as a whole, and not just one…

Maybe something like this? -> Automatic Dependencies Based On Custom Properties (Node Location)

There is no need to specify the alert parameter.

There is a workaround for WPM 2.2.1 which can be located here > WPM cannot open a new database connection using Windows Authentication - SolarWinds Worldwide, LLC. Help and Support

kproterra, if you haven't already, please open a case with support and post your case number here. We are tracking each of these cases trying to determine if there are any commonalities or trends. 

hendershotn wrote: @aLTeReGo What's next? Are these going to be incorporated into an Orion update and after we update they will show up as we listed them? Typically the way these are handled is that we collect all submission, validate and incorporate them into the next major release of the Orion Platform.

frankmuhlstadt wrote: I just upgraded to 2019.2 HF1. that device is still "Unknown". the MIB.CGF is dated 6/21/2019. Update to the lates MIBs db created 7/12/2019. Rediscovered the device ... Still in the unknown folder. Advise? Ahh, I see what happened. It appears that SysObjectID was added to our database by another…

frankmuhlstadt wrote: I figured it was more in keeping with sysObjectID sysObjectID(2).0 (OBJECT IDENTIFIER) sreg-ERS-2500-26T-PWR(2) The Value for that particular SysObjectID is '2526T-PWR Ethernet Routing Switch'

pratikmehta003 wrote: aLTeReGo So would that resolve the hardware health unknown issue? we are currently on 2017.3 NPM 12.2.... This thread is about Orion properly identifying the make/model/manufacturer of a device based upon their unique SNMP SysObjectID. It is not at all related to Hardware Health of a given device. If…

xr64t wrote: Hi aLTeReGo , Any update on CORE-10706 for those Aruba devices please? This was implemented in Orion Platform 2018.4, which is included in NPM 12.4.

What's the SysObjectID

Tracking Internally under CORE-11880.

SysObjectID mappings are updated in the product itself, not in the MIB file. So you will need to upgrade to the latest release to have the most up-to-date SysObjectID mappings.

Once printed, the SAM Administrators Guide must be registered local authorities as a deadly weapon.

dustin.ampania wrote: Running the latest in my test environment and the hardware status for the HP/Aruba's is still unknown. Thanks for the updates. This thread is specific to identifying unknown devices. Hardware Health support for a specific make/model/manufacturer would be a feature request you would need to create in…

So what if the 'Machine Type' for devices with a SysObjectID of '1.3.6.1.4.1.476.1.42' simply showed as 'Veritiv/Emerson/Liebert'?