KnowledgeBase Event Repository

This site is the central interface to the Adiscon Event Repository

  • Details for this entry
  • Eventlog Type:
    Security
    Eventlog Source:
    Security
    Event ID:
    636
    Full Description:
    Security Enabled Local Group Member Added
    Parameter Description:
    Security Enabled Local Group Member Added:%n
    %tMember Name:%t%1%n
    %tMember ID:%t%2%n
    %tTarget Account Name:%t%3%n
    %tTarget Domain:%t%4%n
    %tTarget Account ID:%t%5%n
    %tCaller User Name:%t%6%n
    %tCaller Domain:%t%7%n
    %tCaller Logon ID:%t%8%n
    %tPrivileges:%t%9%n
    More Informations:
    Cause

    This audit record indicates that a new member has been added to a local group. This event also occurs when a user account is created and added to the built-in None group used internally by Windows 2000. There is no Failure Audit form of this audit event record. Adding members to groups can have security implications. This is especially true when a user is added to the Administrator group.

    Search for this Event::
    Search in Knowledge Base  •  Search in this Forum  •  Search on Windows-Expert.com
  • Software Vendor: Microsoft
    Accessed: 2465

Discuss the Event

Discussion for KB Entry 40 - Event ID 636

by knowledgebase on Fri May 30, 2008 12:02 am

This is the discussion thread for the Knowledge Base Entry 40

Eventlog Type: Security
Eventlog Source: Security
Event ID: 636
Link to KB Entry

Short Description:
Security Enabled Local Group Member Added
User avatar
knowledgebase
Frequent Poster
 
Posts: 101
Joined: Wed May 28, 2008 10:09 am


About the KnowledgeBase Event Repository

This is a repository of known Windows Events, hopefully together with a description of what it means, when it appears and how to troubleshoot it. The event repository was initially provided as a tool for parser creation but has since evolved. It is now part of the overall knowledgebase in the hope that it provides a useful service to the community. Please add your comments and questions (which we try to answer), as this increases the event repository usefulness for all of us.

Return to

cron