How proxb/poshpaig works
Project type and purpose
• PoshPAIG is a Windows-based administrative tool written entirely in PowerShell.
• It provides a graphical user interface (UI) for auditing and pushing WSUS updates to local and remote machines.
File structure
• Top-level scripts:
• Start-PoshPAIG.ps1: Launches the UI
• Options.ps1: Contains global configuration and settings
• Exempt.txt, PSexec.txt: Sample or external-tool references
• /Scripts folder: Core operational modules
• Get-ComputerRebootState.ps1, Get-PendingUpdates.ps1, Get-UpdateLog.ps1, Install-Patches.ps1
• Each script encapsulates a discrete function (audit, report, install)
• /HelpFiles: Inline help and documentation modules (About.ps1, HelpOverview.ps1)
• /GitHub_Images & /Images: UI screenshots and assets
• README.md: Project overview and sample UI screenshot
README for additional insights
• Confirms the objective: GUI front-end for WSUS tasks
• Implies use of Windows Forms or WPF for UI (PowerShell-based)
• No external database; uses WSUS API and WinRM/CIM sessions for remote operations
a. Main components
• User Interface (UI) – a PowerShell host window with forms and controls
• Core Script Engine – the PowerShell runtime loading modules and functions
• Operational Modules – the .ps1 files in /Scripts that perform WSUS queries and patch deployments
• Configuration Store – Options.ps1 and Exempt.txt that define preferences and exclusions
• Remote Management Layer – WinRM/CIM sessions used to connect to target endpoints
• WSUS Server – the upstream update source and API endpoint
• Target Systems – local or remote Windows machines receiving queries and patch instructions
b. Relationships and interactions
1. UI invokes Start-PoshPAIG.ps1
2. Core Script Engine imports configuration (Options.ps1)
3. User actions (buttons/menus) call specific scripts in /Scripts
4. Each script uses WinRM/CIM to gather data from or send commands to target systems
5. For patch metadata or downloads, scripts call the WSUS Server API over HTTP/HTTPS
6. Results and logs flow back into the UI for display or written to local log files
c. Architectural patterns and design principles
• Modular design: each core functionality lives in its own script
• Separation of concerns: UI, configuration, and business logic are physically separated
• Extensibility: new scripts can be dropped into /Scripts and automatically invoked
• Thin-client orchestration: no database; relies on existing WSUS infrastructure and WinRM
d. Key technologies and frameworks
• PowerShell v5+ (Runspaces for UI)
• .NET Windows Forms or WPF libraries (loaded via Add-Type)
• WSUS API (Microsoft.UpdateServices.Administration namespace)
• WinRM / CIM sessions for remote calls
• File-based configuration