How cadubarbosabr/windows10wimclone works
Project's Purpose and Components
• The project is not a full-stack web application but rather an automation and deployment tool. Its purpose is to assemble a series of scripts (primarily batch files) and instructions into a cohesive system that can create a WinPE flash drive, perform sysprep on a Windows installation, capture a .wim image with DISM, and then deploy (apply) that image using other automated steps.
• Main components include:
• Environment Preparation: Files like “Preparando o ambiente (Server de laboratório)” mentioned in the README for setting up, plus the ADK setup executables (adksetup.exe and adkwinpesetup.exe).
• WinPE Creation: Steps to create a bootable WinPE flash drive (using WinPE commands like copype and MakeWinPEMedia).
• Image Capture Module: The process using sysprep and DISM for capturing the Windows image (.wim).
• Image Deployment Module: Batch files such as LimparDisco.bat, Clonar.bat, and Recuperar.bat that handle disk cleanup, cloning the image, and recovery steps.
• Supporting Tools and Documentation: Text files and links that provide instructions and reference the use of external resources (e.g., Microsoft Docs, YouTube videos).
File Structure
• The top-level files are a mix of batch scripts (ApplyImage, Clonar, LimparDisco, etc.) and text documentation. The repository does not follow a nested directory structure; its flat file layout emphasizes scripts and documentation.
• Notice the presence of multiple variants of similar scripts (for example, ApplyImage variants targeting different scenarios or OS environments) that indicate conditional flows depending on hardware/firmware configurations (BIOS vs UEFI).
• Alongside the scripts, there are executables (ADK setup, adkwinpesetup) and a ZIP file (Scripts_DefaultMS.zip) which suggests additional batch resources might be bundled separately.
Key Architectural Relationships and Workflow
• ADK and WinPE tools are installed using the provided executables.
• The system prepares the WinPE boot environment on a flash drive.
• Navigation to Sysprep and Image Capture:
• The README instructs to run sysprep on the Windows installation and then boot from WinPE to capture the image using DISM.
• Data flows here from the original Windows system to the captured .wim file stored externally.
• Image Deployment Phase:
• Once the image is captured, several scripts are used in sequence to clean the target disk (LimparDisco.bat), clone the captured image (Clonar.bat), and in case of issues, perform recovery steps (Recuperar.bat).
• Components such as disk partitioning scripts are referenced in text files (e.g., CreatePartitions-BIOS-UEFI variants) indicating that partition layout is an integral part of the process.
• External Dependencies:
• The system relies on running in a WinPE environment, connecting to an external HD for image storage, and using a flash drive as a bootable tool.
Final Advice
• The goal is to provide a “big picture” view that makes it clear how a system administrator or engineer would progress through building the WinPE environment through to final image deployment.