Docs
Powered by

# Project Idea

  • Purpose
  • Scope
  • Key Outcomes

# Purpose

Automate and validate the build process for Windows devices, during imaging, and post-imaging - by speeding up Intune enrolment, and ensuring all required software, settings, and configurations are completed, validated, and installed; plus providing documentation for quality control, compliance, and documentation of same in an appropriate ticketing system.

# Scope

  • Modular, colour-coded CLI menus for clear navigation and accessibility
  • Robust, separate logging for user actions and session transcript
  • Accessible output and error handling for all users
  • User journey: From main menu, users can manage deployment configs, export scripts, view logs, or access help/documentation, all with clear feedback and logging
  • Command-line CLI, to perform all functions and activities
  • Script generation
    • Storage of current configuration
    • Build script based on most current configuration, or a past configuration
    • Ability to give a name and generation/last update date to a configuration, for ease of reference and review during configuration selection process
    • Version control and backup of current and past configurations and configuration scripts
    • User-driven configuration and export of OOBE and post-deployment scripts
      • Customise what exact steps are to be done in the post deployment phase
    • Robust validation and error handling
    • Robust logging of activities, including --Logverbose option when running CLI, to understand exactly what was done at any point
  • Pre deployment scripts
    • Creates a single script, accessible from within Powershell during OOBE, to connect to Intune and enrol device for Autopilot
    • Robust fallback for autopilot enrolment, regardless of code run in PowerShell 5 or 7
  • Post deployment scripts
    • Will automate process as much as possible for installation and configuration not handled elsewhere
    • Validation and documentation of all steps along the way
    • Session and progress persistence: If an incomplete build session is detected when running the post deployment script, it will detect the incomplete session, and provide option to continue on with script, whilst also not repeating any steps already confirmed as successfully completed (important if neeeding to reboot device)
    • Build certificate in post-deployment script
      • Generation of a text-based Build certificate, stored at a user-defined location
      • Copying of build certificate to clipboard, for ease of transmission to other systems
  • Modular, maintainable PowerShell 7 codebase

# Key Outcomes

For organisations where an IT staff is responsible for preparing and delivering devices - these scripts will enable you to deliver employees ready-to-go devices, with no further steps on your or the users part, and minimising the time and effort needed on your part to achieve it.

  • Reliable, repeatable device builds
  • Reduces staff time and effort during device configuration and delivery activities
  • Compliance with organisational and ITSM requirements
  • Accessible, well-documented scripts and processes

# CLI/Menu Requirements (2025-07-28)

  • The CLI must support robust, accessible, and dynamic configuration editing, including multi-toggle, tabbed navigation, paging, and real-time “changed” state feedback.
  • All menu and state logic must be modular, extensible, and regression-resistant.
  • Configuration options must be extensible via JSON, and the CLI must always reflect the latest schema.
  • Robust error handling, user feedback, and accessibility (screen reader, colour fallback, etc.) are required.
  • All state changes must be immediately and accurately reflected in the UI, with no stale or duplicated messaging.