Title: [Article] I wanted a safer way to run the boring Windows admin jobs · Issue #291 · PowerShellOrg/PowerShellOrgWebsite · GitHub
Open Graph Title: [Article] I wanted a safer way to run the boring Windows admin jobs · Issue #291 · PowerShellOrg/PowerShellOrgWebsite
X Title: [Article] I wanted a safer way to run the boring Windows admin jobs · Issue #291 · PowerShellOrg/PowerShellOrgWebsite
Description: Article Title I wanted a safer way to run the boring Windows admin jobs Author Name Jeff Friedler Affiliation: Fusion Technology Strategies Submission Type Draft: Full article included below Description Windows administration is rarely d...
Open Graph Description: Article Title I wanted a safer way to run the boring Windows admin jobs Author Name Jeff Friedler Affiliation: Fusion Technology Strategies Submission Type Draft: Full article included below Descri...
X Description: Article Title I wanted a safer way to run the boring Windows admin jobs Author Name Jeff Friedler Affiliation: Fusion Technology Strategies Submission Type Draft: Full article included below Descri...
Opengraph URL: https://github.com/PowerShellOrg/PowerShellOrgWebsite/issues/291
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Article] I wanted a safer way to run the boring Windows admin jobs","articleBody":"### Article Title\n\nI wanted a safer way to run the boring Windows admin jobs\n\n### Author Name\n\nJeff Friedler\n\nAffiliation: Fusion Technology Strategies\n\n### Submission Type\n\nDraft: Full article included below\n\n### Description\n\nWindows administration is rarely difficult because a command is unavailable. The harder problem is controlling what runs, what happens after an interruption, and what evidence remains. This article explains the guardrails behind Windows Admin Toolkit, including preflight checks, bounded retries, policy profiles, signed distribution, and interruption-safe orchestration.\n\n### Category\n\nPowerShell for Admins\n\n### Tags\n\nPowerShell, Windows administration, WinRM, automation, RMM\n\n### Summary / Pitch\n\nI built this after seeing the same operational problem repeat across support, MSP, and RMM work. Running a command is usually the easy part. The difficult part is proving what was authorized, limiting what can happen, handling interrupted work safely, and leaving behind evidence another technician can understand. The article focuses on those design decisions rather than presenting a list of commands.\n\n### Article Content\n\nThere are plenty of Windows administration scripts online. The problem is not finding one that can restart a service or pull an event log. The problem is knowing what else it might change, what happens when the network drops halfway through, and what evidence is left when the work is over.\n\nThat is the problem I wanted Windows Admin Toolkit to solve.\n\nThe toolkit is a single PowerShell file with twenty common administration workflows. It can collect system and hardware information, inspect disks and networking, query event logs and the registry, review updates, manage services and processes, schedule a reboot, and handle a few other jobs that come up constantly in support work.\n\nThe list of actions is useful, but it is not the interesting part. The guardrails are.\n\nThe default remote transport is WinRM. The optional PsExec path accepts only a current Microsoft-signed Sysinternals build and does not pass an alternate password on the command line. State-changing work uses PowerShell approval controls and exact confirmation phrases. Read-only work can be retried within a limit, while a state change is never repeated automatically just because a connection failed at an awkward moment.\n\nThe toolkit also has a preflight mode. It checks whether an action is ready without executing the requested action. That sounds simple, but it makes a big difference when the same workflow will eventually run through an RMM platform or against more than one endpoint.\n\nFor automation, each named action can return a stable JSON envelope and a useful exit code. Optional policy profiles can narrow the available actions, target modes, transports, runtime limits, and supported inputs. They cannot broaden the built-in behavior.\n\nAudit records are deliberately conservative. They keep useful action summaries and target identifiers without recording passwords, custom source text, or raw custom-command output. Change plans bind the action, inputs, ordered targets, transport, policy, and safety settings before approval. If a run is interrupted, the resume logic does not quietly repeat a target left in an uncertain state.\n\nThe current public release is Authenticode-signed. The repository includes a verification-first installation path that checks the expected file hash, the complete approved signer identity, and the timestamp before the script is installed.\n\nIf you want to look at it, start with the guarded automation diagram and the sanitized examples. You can run the catalog and preflight paths without pointing it at a production endpoint. That is the right place to decide whether the operating model fits your environment.\n\nRepository: https://github.com/fusiontechstrategies/Windows-Admin-Toolkit\n\nLatest signed release: https://github.com/fusiontechstrategies/Windows-Admin-Toolkit/releases/latest\n\n### Author Website or Social Link\n\nhttps://github.com/fusiontechstrategies\n\n### Submission Agreement\n\n- [x] This is my original work and I grant PowerShell.org permission to publish it.\n- [x] I understand the article may be edited for clarity and formatting.\n","author":{"url":"https://github.com/fusiontechstrategies","@type":"Person","name":"fusiontechstrategies"},"datePublished":"2026-09-29T11:07:17Z","url":"https://github.com/PowerShellOrg/PowerShellOrgWebsite/issues/291"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:0a12363c-7f84-be7c-813a-38b888fa84e4 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 90C2:357787:863D73:B7766B:6AFD1B0A |
| html-safe-nonce | ef66b06a6b8db24f4a1fd0bb28f71f982dd267e2de7de2881e41ecc792e42295 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5MEMyOjM1Nzc4Nzo4NjNENzM6Qjc3NjZCOjZBRkQxQjBBIiwidmlzaXRvcl9pZCI6IjMxMzg1NjM4MTkyMjY0Njc5NCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 2354882fa91e1dec9007850d76296fc6d7a6008f01038d1ffbd68e10e3c4eccb |
| hovercard-subject-tag | issue:5629523049 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShellOrg/PowerShellOrgWebsite/291/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c3a533a0920ea72205009c0f18d1516024f88e1617d494fbd311dfbdb1dd3b65/PowerShellOrg/PowerShellOrgWebsite/issues/291 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c3a533a0920ea72205009c0f18d1516024f88e1617d494fbd311dfbdb1dd3b65/PowerShellOrg/PowerShellOrgWebsite/issues/291 |
| og:image:alt | Article Title I wanted a safer way to run the boring Windows admin jobs Author Name Jeff Friedler Affiliation: Fusion Technology Strategies Submission Type Draft: Full article included below Descri... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | fusiontechstrategies |
| hostname | github.com |
| expected-hostname | github.com |
| None | 065128366c233a9d57ff68ab6c96e25b99dd1b0ab70d23b70873d3dd6b5e4f19 |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShellOrg/PowerShellOrgWebsite git https://github.com/PowerShellOrg/PowerShellOrgWebsite.git |
| octolytics-dimension-user_id | 4895314 |
| octolytics-dimension-user_login | PowerShellOrg |
| octolytics-dimension-repository_id | 1050540633 |
| octolytics-dimension-repository_nwo | PowerShellOrg/PowerShellOrgWebsite |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1050540633 |
| octolytics-dimension-repository_network_root_nwo | PowerShellOrg/PowerShellOrgWebsite |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 941021edf0c2ec58298f4a2c8f27ae507d129c92 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width