This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
An event id is a label. The lookup explains ids that admins meet: a logon, a failed logon, a user created, a user deleted, a lockout, a member added to a group, and a cleared security log. The tool does not connect to a domain.
1102 means the security log was cleared. You record that it happened. You do not clear the log to make a symptom go away. 4625 is a failed logon you already see. It is not a list of passwords to try.
This is not an attack guide. You use it on a domain or a host you administer, for an id that is already in your log. 192.0.2.10/24 and example.com are documentation. They stay in the note.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Copy one id from a log you hold.
- Look it up.
- Write the plain sentence.
- If the id is 1102, record the clear. Do not perform one.
- Do not turn a 4625 into a password guess.
- Stop.
Mistakes that outlive the command
Important Windows Event IDs List goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The log cleared to tidy a ticket.
- Failed logons used as a guess list.
- An id from a domain you do not administer.
- A pile of ids with no sentence.
Decisions to write down
One decision for Important Windows Event IDs List: One id. The sentence is operational. No log was cleared. No password was guessed. And the log is one you hold.
Checks before you call it done
Confirm this before you call the change done: The id is written. The sentence is written. The hostname or domain is one you administer. No clear was done. And no credential was tested. If one of those fails, stop.
| Id | Plain meaning | What you do |
|---|---|---|
| 4624 | A logon succeeded | Record the account and the time if the ticket asked |
| 4625 | A logon failed | Record the count. Do not guess passwords |
| 4720 | A user was created | Record who, if your log says |
| 4740 | An account was locked | Record the account. Do not spray it |
| 1102 | The security log was cleared | Record it. Do not clear a log yourself to hide a symptom |
# Look up an id you already have.
# 1102 is recorded, not performed.
# 4625 is not a password list.Before you leave the host
Important Windows Event IDs List ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.
- Pillar: PowerShell Scripting Basics
- Comparison: CMD vs PowerShell
- How-To: Robocopy Guide
- Comparison: NTFS vs Share Permissions
Companion: Security: Log Analysis for Security.