Get the latest news about SolarWinds Security Event Manager (SEM)
As the title says i have tried LEM 6.6 and 6.7 RC, both fail at the deploy ova step with no error message. has anyone got this working, if so any tips?
Is there a way to export all data from LEM so that it can be imported into a different system? Thanks in advance for any responses!
Hello, Within the Explore-nDepth, when I try to refine fields, most of the username section says Unable to resolve usernames. Is there a quick fix for this? I'm also not sure which version I'm running as I am brand new to this product and still using a demo version. Thanks in advance,
I'm brand new to LEM and I'm struggling to create a rule that would send an email notification after X failed login attempts originate from the same source machine in Y seconds. Is anyone using LEM to combat password spraying attacks? We're a Windows shop with
My LEM system is have some file system issues so I want to migrate it to a different machine with the current config, DB and license that I will upgrade the new machine to the latest version. I have run backupconfig and restored it on the new system, but it appears that the admin accounts did not make it across. Is there a…
Are there any compatibility issues if I upgrade to 6.7 RC2 and my agents are still version 6.3? I would upgrade these as well, I just wondered if I'd encounter issues immediately. Edit: This was answered by jhynds elsewhere -- there is no issue and the agents upgrade automatically with the appliance.
In case you missed it elsewhere, LEM 6.7 RC2 is available on your Customer Portal. Head on over to the RC Forum to see what's included in the RC! Log & Event Manager Release Candidate
LEM running for a couple of years, DB getting full, slow. How do I manually or automatically trim the logs to 6 months?
Rule: Source: Destination: They are blank. I used the defaults along the way in the rules creation. Nice that the email does work. Also, when googling this and following links to possible solutions, the main web site shoots me to the success center. From there I tried searches but sent me to manuals an such and not related…
I noticed that when other syslog nodes (non agent) are detected in a syslog, they are automatically added to the node list and consume a license. How do I prevent it from adding the the list and consuming the license. I would like to manually add nodes to the list
It looks like you're new here. Sign in or register to get started.