Production helpdesk / SysAdmin toolkit for Windows and macOS, with a unified catalog GUI, risk labels, logging, and HTML reports.

Author: Allester Padovani

Catalog shape: Platform → Role → Theme → Category (NN_Name) → Scripts.

IT-Repair-Scripts/
├── IT Repair & Diagnostic Toolkit.exe
├── IT Repair & Diagnostic Toolkit.app          # after Mac build (optional until built)
├── IT Repair & Diagnostic Toolkit-macOS.command
├── Build-MacApp.sh
├── MASTER-MENU.ps1
├── MASTER-MENU-GUI.py
├── README.md · LICENSE · RISK-INVENTORY.md
├── Install & Deployments/         # local launchers + Intune / Jamf / AD packages
│   ├── Run Locally Windows/
│   ├── Run Locally macOS/
│   ├── Run On Active Directory Windows/
│   ├── Run On Active Directory macOS/
│   ├── Run On Cloud Intune Windows/
│   ├── Run On Cloud Intune macOS/
│   └── Run On Cloud Jamf macOS/
├── Windows/
│   ├── SysAdmin/NN_Category/*.ps1
│   └── ITSupport/NN_Category/*.ps1
└── macOS/
    ├── SysAdmin/NN_Category/*.{sh,ps1}
    └── ITSupport/NN_Category/*.{sh,ps1}

Menus discover only scripts in the category root (non-recursive). Imported Tech Support binaries live once under Windows/SysAdmin/65_Imported-Tech-Support-Tools/_Tools/; IT Support Launch-*.ps1 wrappers point there.

Windows

1. Keep IT Repair & Diagnostic Toolkit.exe next to MASTER-MENU.ps1.
2. Double-click the exe → choose Platform + Role → Open Toolkit.
3. Or: powershell -NoProfile -ExecutionPolicy Bypass -File .\MASTER-MENU.ps1 -Gui

macOS (technicians — no Python)

1. Double-click IT Repair & Diagnostic Toolkit.app (must sit next to Windows/ and macOS/).
2. Or double-click IT Repair & Diagnostic Toolkit-macOS.command (prefers the .app if present).

Theme preference is stored locally in toolkit-theme.cfg (created automatically; do not redistribute that file).

Apple requires a Mac to produce a .app. You cannot generate IT Repair & Diagnostic Toolkit.app from Windows.

cd /path/to/IT-Repair-Scripts
chmod +x Build-MacApp.sh
zsh Build-MacApp.sh

Output: IT Repair & Diagnostic Toolkit.app in the toolkit root (same folder as the Windows .exe).

You need access to a Mac (physical, borrowed, or cloud Mac) to run Option A once. There is no Windows-side way to produce the .app.

• Copy IT Repair & Diagnostic Toolkit.app + Windows/ + macOS/ to helpdesk Macs.
• Technicians open the .app — no Python install.
• On Windows, if the EXE finds IT Repair & Diagnostic Toolkit.app in the root, the “FIRST TIME” build warning is skipped.

• Prefer interactive password prompts; avoid USER_PASSWORD / CERT_PASSWORD in env/argv on shared hosts.
• trustRoot certificate install requires TRUST_ROOT=YES and CONFIRM=YES.
• Review RISK-INVENTORY.md before running Dangerous scripts.
• Toolkit binaries are not Authenticode-signed by default — pin via AppLocker / Gatekeeper policy in enterprise.

Proprietary — see LICENSE. Third-party tools under nested _Tools (Imported Tech Support Tools) keep their own licenses.