CMD Scripts
Your command-line library for admin tasks, quick fixes, automation snippets, cleanup routines, and reusable support commands.
Open section →JCI Knowledge is built as a sleek directory for practical technical notes, command-line references, troubleshooting steps, scripts, and repeatable support tasks. Start with CMD content now, then expand into Python, tools, networking, and Azure later.
Keep the first version clean and practical. Each category can later grow into its own dedicated page, searchable collection, or filter view.
Your command-line library for admin tasks, quick fixes, automation snippets, cleanup routines, and reusable support commands.
Open section →Centralise your DNS, IP, connectivity, and adapter troubleshooting commands so they are fast to find when handling common support issues.
Planned section →Build a clean reference area for system scans, disk checks, service resets, recovery commands, and device health workflows.
Planned section →Add lightweight utility scripts later for log parsing, automation, reporting, and repetitive service desk tasks.
Future section →Store common issue patterns, quick resolutions, escalation notes, and standard troubleshooting checklists in one place.
Future section →Create a curated area for internal tools, useful websites, diagnostic utilities, and frequently used admin resources.
Future section →These homepage cards make the site feel immediately useful. They can later become clickable entry pages with copy buttons, related notes, and search filtering.
Useful when testing name resolution issues, refreshing stale DNS entries, or troubleshooting device connectivity problems.
Run from an elevated CMD session to scan and repair protected Windows system files when system behaviour looks unstable.
Schedule a disk repair pass on restart when a drive needs checking for corruption, file system issues, or bad sectors.
This version feels more like a real product and less like a draft page. It is cleaner, darker, easier to scan, and better aligned to the style you shared.
Your next step should be turning cmd-scripts.html into a fully matching library page with filters, command cards, copy buttons, and better structure.
Continue to CMD Scripts