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
Get-WinEvent reads the event log. The builder drafts a filter by log name, id, or time. It does not connect to a host and it does not clear a log.
Clearing the security log is not a troubleshooting step. An empty log is a finding, not a goal. The filter asks one question: this id, or this hour.
Do not query a machine you do not administer. Redact account names if the ticket does not need them. The event-id page explains what an id means. This page only builds the filter.
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.
- Name the host and the log.
- Write the id or the time window.
- Draft the filter.
- Do not include a clear command.
- Do not run it during the reading.
- Stop.
Mistakes that outlive the command
Querying Windows Event Logs with PowerShell goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The log cleared.
- A host you do not administer.
- Every log dumped into the ticket.
- Account names filed without a need.
- A second question added to the same filter.
Decisions to write down
One decision for Querying Windows Event Logs with PowerShell: One log. One id or one window. No clear command. The host is yours. And the draft was not run yet.
Checks before you call it done
Confirm this before you call the change done: The log name is written. The id or the time is written. No clear is in the draft. The host is yours. And nothing was run. If one of those fails, stop.
# One filter.
# Do not clear the log.
# A host you administer.Before you leave the host
Querying Windows Event Logs with PowerShell 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.