Check PowerShell Scripts for Syntax Errors Without Running Them
Use PowerShell's own parser to catch typos and broken brackets in a whole folder of scripts, before anything runs.
EXPLORE THE NOTEBOOK
Notes from the command line, the workbench, and the vintage computer shelf.
Use PowerShell's own parser to catch typos and broken brackets in a whole folder of scripts, before anything runs.
I know WordPress inside and out, and I still didn't use it for this site. What I compared, and why I landed on Sveltia CMS.
My brand-new blog got an F on a security header scan. Here's why, what actually matters for a static site, and the fixes that work on DigitalOcean App Platform.
A dry run that quietly lies to you. Why ForEach-Object's property shorthand returns nothing under -WhatIf, and the one-line fix.
Find out which resource groups are eating your Azure budget, straight from PowerShell, no portal clicking required.
One script that locks a departing user out, cleans up their groups and licenses, and keeps their mail, with a CSV record of every step.
Put a domain group into the local Administrators group on a list of computers (or take one out) over PowerShell remoting, with a result for every machine and -WhatIf first.
One object per update deployment with targeted, compliant, failed and unknown counts, so you can spot the deployments that need you.
Find the updates the most machines are actually missing, bundle them into a group, and deploy them to a pilot collection, with a WhatIf preview first.
Install a product key, activate it and confirm the edition actually changed, without the key ever landing in a script file or a log.
Turn "wrap this script in a package and push it to the DPs" into one command, with a dry run before anything gets created.
When Graph cmdlets start throwing assembly errors, it's almost always mixed module versions. This removes every copy and puts back one matching set.