Scripting Big Changes With Small Risk
summary
Shows concrete PowerShell patterns: enumerate affected accounts, export their current settings to CSV, make the change, then reimport that CSV to revert if needed. Examples include disabling POP/IMAP in Exchange Online and moving AD objects for 6,000 users in a 50,000‑object directory, all driven from SCCM lists. The claim is that capturing outputs as reversible putbacks lets teams fail fast fail well — scripts and CSVs make rollbacks practical and the approach demonstrably works.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:15What Is the Guiding Mantra
- 4:39A Fictitious Phishing Campaign
- 12:51Inputs Outputs and Putbacks
- 23:33Active Directory Structure
- 24:32Major Active Directory Change
- 37:19What's a Big Change
related talks
40mFrom Chaos to Clarity: Taming Data with PowerShell
51mDon't do that, do this instead: PowerShell worst practices and..
01h 00mThe Enterprise Scripting Workshop
46mFrom Script to Tool: Building Robust, Meaningful Tools with PowerShell
37mUsing Windows PowerShell to create scripts your users want to use
47mThe Human Side of PowerShell Scripting
48mUnexplained phenomena: powerful tricks you likely didn't know were even possible
47mTempting Fate: Patterns & practices for shareable scripts and functions