# OS Deployment
> Overview of the CapaInstaller OS Deployment (OSD) solution for building, testing, and deploying operating systems across managed environments.
Source: https://docs.capaone.com/capainstaller/the-capainstaller-console/os-deployment/
Product: CapaInstaller — a separate CapaSystems product; do not apply this page to any other.
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
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](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/os-deployment-points/)** — 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](/capainstaller/the-capainstaller-console/os-deployment/how-to-use-osd/promote-items/)** the content to your **Production** point.
- **[Images](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/images/)** — the `.wim` operating-system images.
- **[Models](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/models/)** — per-hardware groupings of **[Drivers](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/drivers/)**.
- **[Scripts](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/scripts/)** — customization scripts run at defined phases of the deployment.
- **[Disk configuration](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/disk-configuration/)** — how the target disk is partitioned.
- **[WinPE](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/winpe/)** — the boot environment (boot image).
**Runtime infrastructure**
- **[OS Deployment server](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/os-deployment-servers/)** — 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](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/pxe-servers/)** — 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](/capainstaller/the-capainstaller-console/os-deployment/getting-started-with-os-deployment/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](/capainstaller/the-capainstaller-console/os-deployment/deployment-template/)** — deployment definitions authored in the CapaOne portal, synchronized into the on-prem installation, and resolved against points, Business Units, or Installation Types.
- **[Import / Export](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/import-in-os-deployment/)** — move portable objects (images, models, drivers, scripts) between installations. Points, servers, and PXE servers cannot be moved.
- **[Network Boot Profiles](/capainstaller/the-capainstaller-console/os-deployment/how-to-use-osd/network-boot-profiles/)** — target specific devices (by MAC address or vendor) at boot time.
## In this section
- [Deployment Template](/capainstaller/the-capainstaller-console/os-deployment/deployment-template/) - Create, edit, and assign deployment templates.
- [Getting started with OS Deployment](/capainstaller/the-capainstaller-console/os-deployment/getting-started-with-os-deployment/) - Step-by-step setup of the OSD solution.
- [How to use OSD](/capainstaller/the-capainstaller-console/os-deployment/how-to-use-osd/) - Guides for configuring and operating OS Deployment.
- [Prerequisites for OS Deployment](/capainstaller/the-capainstaller-console/os-deployment/prerequisites-for-os-deployment/) - Software and hardware requirements.
- [What is OS Deployment](/capainstaller/the-capainstaller-console/os-deployment/what-is-os-deployment/) - Descriptions of the individual OSD elements.