Skip to content
CapaSystems Docs

OS Deployment

The following is a description of the OS Deployment tool, its functionality and its purpose. The CapaInstaller OS Deployment solution (OSD) is a process-oriented solution that gives you the possibility to fully manage a distributed environment and at the same time keep track of every single object.

Within the solution, it is possible to define numerous OS Deployment points to support a process where the OS is built, tested, and implemented in separate environments.

OS Deployment with CapaInstaller OSD - an example of the client process

How OS Deployment fits together

Section titled “How OS Deployment fits together”

CapaInstaller OSD is built around one central object — the OS Deployment point — with runtime servers in front of it and a client boot process that ties everything together.

flowchart TB
  CapaOne["CapaOne portal"] -. "Deployment Templates (synced in)" .-> P

  subgraph P["Development point (build and test)"]
    direction TB
    IMG["Images (.wim)"]
    MDL["Models"] --> DRV["Drivers"]
    SCR["Scripts"]
    DSK["Disk configuration"]
    WPE["WinPE (boot image)"]
  end

  P ==>|"Promote content"| PROD["Production point<br/>(live deployment)"]
  PROD -->|"hosted at runtime by"| SRV["OS Deployment server<br/>TFTPD + sync service"]
  SRV --> PXE["PXE server<br/>DHCP + TFTPD"]
  PXE --> F1

  subgraph FLOW["OSD client process (deploy time)"]
    direction TB
    F1["1. PXE boot, load WinPE<br/>(+ injected NIC drivers)"] --> F2["2. Select Image + Disk configuration"]
    F2 --> F3["3. Partition, apply image,<br/>inject Model drivers, run Scripts"]
    F3 --> F4["4. Install CapaInstaller agent, then boot into OS"]
  end

  classDef container fill:#e7f0f8,stroke:#1f6fb2,color:#16202c;
  classDef flow fill:#eef6ee,stroke:#4a8f5a,color:#16202c;
  class P container;
  class PROD container;
  class FLOW flow;

Content managed on a point

  • OS Deployment point — the container that holds all deployable content. A typical setup uses at least two points: you build and test on a Development point, then Promote the content to your Production point.
    • Images — the .wim operating-system images.
    • Models — per-hardware groupings of Drivers.
    • Scripts — customization scripts run at defined phases of the deployment.
    • Disk configuration — how the target disk is partitioned.
    • WinPE — the boot environment (boot image).

Runtime infrastructure

  • OS Deployment server — hosts a point’s content at runtime (images, models, drivers, WinPE) plus a TFTPD and a synchronization service. A point can also hold the server role.
  • PXE server — answers network-boot requests (DHCP + TFTPD) and presents the boot menu that hands the client its WinPE boot image.

Deploy-time flow — the OSD client process

  1. The client PXE-boots and loads WinPE (with injected NIC drivers).
  2. An Image and a Disk configuration are selected (manually, or automatically via a profile).
  3. OSD partitions the disk, applies the image, injects the Model drivers, and runs the phase Scripts.
  4. The CapaInstaller agent is installed and the client boots into the new operating system.

Related mechanisms

  • Deployment Templates — deployment definitions authored in the CapaOne portal, synchronized into the on-prem installation, and resolved against points, Business Units, or Installation Types.
  • Import / Export — move portable objects (images, models, drivers, scripts) between installations. Points, servers, and PXE servers cannot be moved.
  • Network Boot Profiles — target specific devices (by MAC address or vendor) at boot time.

In this section

Section titled “In this section”