chadsikorra

Not yet, as I'm actually leaning towards it being the way in which the servers are configured that's making the issue worse. It's also pretty sporadic, so by the time I log a ticket and actually get a support person to talk to the issue might be gone. I should open a case the next time it happens though.

Still not on the radar for 2019?

Too late for me...I'm already all in! Well, I do have snapshots and DB backups if things really go sideways. It also bugs me a bit that the versioning doesn't really follow semver. A patch version is supposed to be bug fixes...not new features that introduce bugs and issues.

Another interesting thing I've noticed. This only seems to be happening to servers set to "Agent Initiated Mode". All of the agents I have in "Server Initiated Mode" are updating fine without getting stuck in the "Update in Progress" state.

No, that's not the case in this instance. We patch at a set time every month for production/test. All of these servers were already fully patched and rebooted. However, what does "fix" the issue when it's stuck in a "update in progress" is if you install updates on the target machine and it then needs a reboot. The status…

Just some extra notes...I have an additional web server in my environment, but it still needs the primary poller to be up for the site to work on the additional web server. However, I do not have any additional polling engines in my environment.

You could setup an alert for when an application goes into an unknown state, then trigger an email for it. Unfortunately whenever I've submitted a support request to SolarWinds for issues like this, as soon as I mention in the ticket that I restarted the agent and the issue was resolved (or that a restart of the server…

I think that's for the "Asset Inventory" section of the resource selection list for a server. The application dependency mapping seems to be referred to as "SAM.ADM" in most places. That's what I originally tried, and it ran successfully but did not change the "Application Dependency Polling Enabled" checkbox.

Good idea, can't believe I overlooked that. Would I have to use a custom node property and define the property for each node then? Seems like a lot of possible duplication.

The agent has worked pretty well for us. We started out with SNMP. I have seen some cases of weird issues with the agent, but nothing show-stopping. And apparently some of the issues causing us grief with the agent are supposedly fixed in SAM 6.3. I would definitely recommend the agent over SNMP/WMI in a hosted environment…

What do you mean by misconfigured server initiated agents taking down the poller?

This version just keeps getting better. On our team here at work we were discussing the prospects of switching all of our servers to the agent method but didn't want to lose historical information. We were considering just doing it anyway. Good to know we just need a little more patience.

Yeah, currently the only method for switching the polling method over is editing the node and switching it manually. The downside is I think you end up losing historical information for certain things when you do that. One thing to watch out for as you switch many servers over to the agent method: Issues with agents…

Could you clarify what that means exactly? Does that mean if your Central/Additional Polling Server is a Windows 2008 R2 Server, then any server in your environment using the Windows Agent in agent initiated mode will need to communicate to the poller via TCP 17791?

Are there any updates on this that you're able to share? Kinda sad that it's being left like this for so long considering all the additional support that is getting added into SRM

I second this. Having HP LeftHand P4xxx support in the SRM Orion Module would be great.

Do you mean NPM 12.0.1? I see that available as RC3 from the customer portal, but I haven't seen 12.1 mentioned anywhere yet.

User access is granted by AD security groups for us. Why would that cause the issue though?

It would be nice to actually see an expected ETA on this sort of feature. Looks like that idea has been around for quite some time! I ended up implementing a powershell script using the Orion API to automatically set an "InMaintenance" custom property on nodes for their maintenance windows based off of WSUS group…

There's a distinct lack of features being worked on here. But there are all sorts of feature requests that have lots of votes. So what's going on exactly? Is SolarWinds not actively working on this product anymore beyond bug fixes essentially?

I created a template to do some basic monitoring on them at the moment, but I can't find any SAM templates that cover things like failover status, Virtual Server health, etc.

Network Insight for Cisco ASA - Covering things like VPN tunnel monitoring, ACL visibility, and improved platform health (H/A status, hardware health). Bummer, was hoping that was going to end with "Citrix Netscaler", not Cisco ASA I can't even find a feature request for Cisco ASA.

We recently started moving off Patch Manager to SCCM due to this feature not being available. It wastes too much of our time baby-sitting patching tasks to make sure all the patches get installed.

Are any of the features listed in this article being actively worked on? We are using this product but not being able to just patch a server until there are no patches left leaves a lot of manual effort to a patching process. I see that this feature is on the list...but there aren't a whole lot of updates going on here,…

Same issue here...but with an XR630. Doesn't seem like there are any community pollers for Xirrus either. Has anyone come up with a solution?

The method I devised is a Powershell script that uses the Orion SDK/WSUS API calls. The script runs every hour, checks if a specific maintenance window is active, and toggles a custom property on the nodes called "inMaintenance" (True/False). When the maintenance window starts it toggles it to true. Then I have a check in…

I just did an upgrade from SAM 6.2.1 to SAM 6.2.3 in our environment on Monday. We are at NCM 7.4 and NPM 11.5.2 (with the latest hotfixes). I haven't upgraded to NPM 11.5.3 yet. I haven't had any of the issues you're experiencing yet. The only issue I noticed is that all of our servers with the Agent (which is about 75 at…

I've run into this a few times as well. I noticed that what seems to force it to remanage is if you edit the node and change its name. Afterwards you can change it back. But that seems to workaround whatever the problem is. I've also seen it resolved by running back through the configuration wizard. Edit: Actually, this…

Sorry to bump such an old thread, but I could not find any good information on this. So just in case someone stumbles across this for the answer: The "Hewlett-Packard Server Updates Catalog" in Patch Manager stopped getting updated mid 2012. If you want to get the latest HP SPPs for ProLiant you need to add the following…

I just ran into this too. How does something like this go unresolved and ignored for so long? I can see why the line breaks are likely included from a developer perspective, at least for those attempting to create very simple HTML emails or for cases where someone doesn't understand how HTML works. But there should really…