Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. Windows Security Events

Windows Security Events

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 41.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I
    I
    IT-Finn
    wrote on last edited by
    #1

    Hi,

    I'm new to NetXMS and I'm trying to get Windows Server 2008 R2 security events to appear in NetXMS event log. I'm able to get application and system events to appear, but for some reason not the security events. I've tested the same configuration on Windows XP and it works. Do you need some additinal configuration on 2008 R2? I'm using version 1.2.6.

    Agent configuration:

    SubAgent = logwatch.nsm
    *LogWatch
    Parser = C:\NetXMS\System_parser.xml
    Parser = C:\NetXMS\Application_parser.xml
    Parser = C:\NetXMS\Security_parser.xml

    Security_parser.xml:

    <parser>
      <file>*Security</file>
      <rules>
        <rule>
          <level>8</level>
          <match>(.*)</match>
          <event params="1">100006</event>
        </rule>
        <rule>
          <level>16</level>
          <match>(.*)</match>
          <event params="1">100007</event>
        </rule>
      </rules>
    </parser>

    Best regards,
    Roger

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi!

      In Windows Vista/2008 event log API was changed significantly, and all security events now have priority Informational. This is why your filter doesn't work. I just found an article that describe these changes: http://www.eventlogblog.com/mt/mt-search.cgi?tag=Vista Event Log Changes&blog_id=1. As a workaround, you can remove "level" filter. For future releases I'll implement simulation of old behavior.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • V
        V
        Victor Kirhenshtein
        wrote on last edited by
        #3

        Followup: just fixed it. Agent version 1.2.7 will pass 8 and 16 to log parser as level values for audit success and audit failure events.

        Best regards,
        Victor

        1 Reply Last reply
        0
        • I
          I
          IT-Finn
          wrote on last edited by
          #4

          Hi,

          Thank you very much. I'll test it when I get back to work.  🙂

          Best regards,
          Roger

          1 Reply Last reply
          0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          Powered by NodeBB Contributors
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups