phil3

To clarify what I said above, the LEM Manager can be configured to push automatic updates to connected LEM Agents. The initial deployment is handled outside of the LEM Console using either a local installer or the Remote Agent Installer. The latter can use either NetBIOS to "discover" available hosts or a text file that…

Did you check the Windows audit policy on that computer?

Hi, Eric. In the CMC interface (via SSH or vSphere), enter appliance at the cmc> prompt. Then, at the cmc::acm prompt, enter viewnetconfig. One of the last lines will show you the hostname and IP address of your LEM Manager. Thanks.

Can you elaborate more on this? How would one go about configuring appliances as network sensors or logging servers? Those KB articles seem to only reference a raw log (nDepth) appliance. The KB articles cited above refer to the processes for configuring the nDepth database, not a separate appliance. The Manager and both…

That switch only shows up if your appliance is configured to store original log messages. Did you go through the steps in the other article linked in that one?

I checked with Dev and read through the "PackageBoot" section of the doc linked above, and I think that's just what you'll need. To enable PackageBoot for an update package: * Start the Package Wizard for the new package. * On the Select Package screen, select Use the Package Boot Helper program..., and then click the icon…

I'll pass your feature requests over to product management. Regarding the Last Connected column in the Nodes view, I just have one point of clarification: This date/time reflects the last time the Agent established a connection with your LEM Manager, not necessarily the last time the two communicated. It sounds like you…

Think of adding nodes as an outside-in sort of process. You will either install a LEM Agent on a computer (server, workstation, etc.), or you'll configure some other sort of device to log to the LEM appliance (a firewall, for example). If you let me know what you have in mind, I will probably be able to link you to some…

I got some feedback from Support and Engineering, and they say it looks like your syslog configuration is an a nonstandard format. The connector is confused because the "Local2.Warning" is being logged before the IP address. Do you know if this has been altered at all from the default configuration? * If you've modified…

I'm checking with Support to see if there are any known issues with this connector, but you will likely have to open a case to do more targeted troubleshooting. If you open a ticket, please post the ticket number here and keep us posted if you come to a resolution.

On my Windows 7 computer, I see Crystal Reports v11 Runtime in my Programs and Features list. Try reinstalling the runtime as Administrator using the link in the following KB article. Additional Evaluation Downloads In the meantime, I'll check with Sales Engineering to see if they have anything else you should try. Thanks.

I saw a few others in the case notes that you might try: * Data Security Logs * System Logs * Default Proxy Logs * Updater Logs I'm very interested to know your outcome. Hopefully I'll be able to document this so the next person in your shoes doesn't have the same problems. :)P.S. When you get these logging, try pointing…

Are you running the latest service pack for EOC 1.3? I'm not sure if that will fix your issue either, but when you mentioned the time not changing, it reminded me of this thread: EOC 1.3.0.803 - Clock displaying incorrect time on refresh Thanks.

Ah...when it asks for the IP address, it's asking for the IP address for the LEM appliance, not the VM server it's installed on. To see the IP address for the LEM appliance, log onto your VMware client, and then look at the "console" view for the LEM VM. You should see a blue screen that notes the LEM IP address.

Here you go, Todd. http://www.solarwinds.com/support/ticket/ Thanks. Phil

Yeah...if you're seeing the InternalNewToolData alerts, the connector update case is the next step. The feature request case is good too in case the updated connector doesn't get you what you need. Thanks for the suggestions.

Hi, there. Do you have name resolution set up correctly - that is, can the server resolve the hostname for the appliance? Here are a few KB articles to check out: SolarWinds Knowledge Base :: Using the SolarWinds LEM Remote Agent Installer SolarWinds Knowledge Base :: Troubleshooting LEM Agent Connections I hope these…

Also, here are a few KBs (with videos) that might be helpful while implementing my suggestions above. Creating Rules from Your LEM Console to Take Automated Action Cloning, Enabling, and Activating NATO5 Rules Thanks again.

You'll also want to be sure you have quotation marks around your argument, but not the /l. Incidentally, if you want to test your task without waiting for it to fail on schedule, you can right-click on it in Task Scheduler and then select Run. HTH

I'll check with Dev to see if I can get something for you. In the meantime, to start to answer both of your questions, check out the following doc: Third Party Updates Local Publishing Administration Guide (June, 2011) Hope that helps.

Were you able to verify the settings I mentioned previously? I wasn't able to reproduce any issues on my end, so if you still can't get the connector started, you should probably open a Support ticket. Sorry I couldn't be more help.

Here's a link to a KB article that describes the issue and Lawrence's workaround in more detail: http://knowledgebase.solarwinds.com/kb/questions/4238/. Thanks. Phil

My pleasure.

Thanks for the clarification. The icon next to that value specifies that it's looking for a Directory Service Group. If you don't have a DS Group with the same name and/or haven't set up DS Groups on your LEM Manager, you'll see this error. Here's a KB to help you get set up if you're not already: How to Configure the…

OK. Thanks. For general troubleshooting steps for this sort of issue, try this KB article: Troubleshooting LEM Rules and Email Responses. Since your rule works intermittently, these are the most immediate things that come to mind: * Check whether or not the rule correlations include a Time of Day Set. * Check the time…

The login as should be cmc, not admin. The password, then, is one you set when you ran the activate command after purchasing your LEM license. If you can't remember the password you set for cmc, you can open a Support ticket and we can help get you reset. Thanks.

Thanks, Mark. Just one more thing to verify before I refer you to Support: When you said above that you were able to run reports manually, did you test that with the user account you set up to run the scheduled reports? If not, please log onto your Reports computer with that user account and try running the reports. If…

No, the consoles aren't licensed, but that brings up a good point. Each console requires a security certificate from the LEM appliance. After you have exported this certificate once (during your initial deployment), you can save it to a network or local share to distribute as needed. For information about exporting and…

This question was addressed in the following thread: LEM Event and Log Correlation. Thanks.

I appears that the agent is required for event log collection on domain controllers. Is this accurate? I ask because I'm aware of other products that don't have this requirement just for event log collection. That's correct. The benefit of the LEM Agent in this regard is that it collects, normalizes, and sends these log…