Search the Community

Showing results for tags 'WIndowsServer'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • From LogicMonitor
    • General Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 2 results

  1. Hello, Nowadays, we are migrating from CA IM to Logic Monitor platform, when it comes to the event logs monitoring we've some doubts on how to replicate those. Currently at IM we pick what we want to monitor (by creating profiles that look into the Severity, Source, ID, Message, etc...). I do understand this is possible within LM but, from what I checked it would require us to create a different event source every time the source changes (& we are talking about >100 variations). With that in mind, using that method we would create a huge load on the collectors, correct (due to WMI limitations, etc...)? Not sure if this was raised in the past but, is there any other approach/method we could try in order to accomplish this? Appreciate the feedback. Thank you!
  2. Hello to everyone, I've problems when monitoring windows server 2003, always the collector tells me that it can not connect to port 135, but doing the tests locally the WMI service with some tools like WBEMTEST or PORTQRY seems working properly. please help me to verify if this problem is in general with the version windows server 2003 or I must do something else. thanks