jvogel ✭✭✭✭✭

I was of the same mind, surely it was a trick and the answer wouldn't be that they won't do any of [that one thing] when the doc clearly outlined it was a specific type of [that one thing] that was excluded.

This was my reasoning too.

mrs.alterego​ Shoot, question shows as completed now (in both browsers). Thanks. Back to lurking.

Reasonable end-users

Worked for me in Vivaldi, even with built-in blocker, privacy badger, and UbO enabled.

There's so much whinging in this thread. Let's not forget none of this is owed to us. Also, in addition to the promotional material (disguised as 'hints') provided with each question, we have the internet, which is pretty good at answering questions and doing other things.

I'd think these things are planned out a bit in advance, and they'd likely stick with the stereotypical geek culture just the same. Most months I wait until the end to answer the questions and skip the last one so there's no chance of winning anything.

Well, it's a bit redundant to have the word "support" in your answer. Reread the question: "...includes support for Access Control Lists, firmware upgrades, and [multi-context support] support on Cisco ASA devices." Same goes for those who put "Cisco ASA multi-context" or "ASA multi-context". The original question/answer…

This was in Firefox. Opened it up in Chrome, and everything looks the same: Question shows as unanswered, but the poll shows as completed. Don't make me try it in IE D:

There are several correct answers in the hint, but only one of them is also represented in today's question. Given the context of the other answers, that isn't a typo.

I'm getting the same page as bleggett on all questions.

I voted (and commented, thinking that may trigger the completion), but today's question is still showing as incomplete.

Local execution. The case continues: Support gave me a test script (below) to create a test template, and it's doing the same thing (bouncing between "up" and "unknown", saying "failed to deserialize probe"). So maybe it is a platform issue. $proc = (Get-Process | Sort-Object -Property CPU -Descending)[0]; $info =…

I told support what the problem was, for whatever that's worth. It's clearly something on SW's end, so I'd put in a ticket or something. Thankfully we can live without PS transcription. There is a workaround that just wasn't sufficient for us: You can change the monitor template to remote execution rather than local. I…

bobmarley​ Figured it out. As expected, it was something stupid... The IP of my CentOS host was reused, and the previous device that had its IP in SW, but in an 'unmanaged' state. I guess Syslog Viewer ignores messages sent from unmanaged devices. Thanks for the suggestions.

No, I've tried disabling all rules (and firewalls), and have been playing with a catch-all rule, but so far it's caught nothing from the CentOS server.

Yes, and Syslog Viewer is and has been displaying the messages from all of the devices pointing directly to the NPM server since I configured them a few months ago.

Support thinks it's a problem with the template and not a SW software issue, so I guess we'll live in this limbo until someone smarter than me runs into this problem and figures out how to fix it.

Yes, Case 00208193. Gathering up some requested information for it right now.

Sorry to see you're having the problem too. Did it just show up, or have you recently run an update too? Unfortunately, I made this post over a month ago, so it doesn't look like anyone has a fix, but I have submitted a ticket to see if SW support has any ideas.

Hmm, thanks for that. This seems right (and obvious, can't believe that hadn't occurred to me), but when I enable the alert, I get ~46 emails about various devices that say they're overheating (testing on a similar scenario above, but using a UnDP for Xirrus device's internal temperature). But if I run the UnDP with…

We figured it out! Per support's request, we tried updating to SAM 6.7.0 HF6, but this didn't help. However, during the process we found a folder on the C: of our Orion server "C:\debug". Within this folder was a sub-folder for every day of the year since we migrated to this new Server 2016 server, and each sub-folder…