> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/start-here/quick-start.md).

# Quick start

This path creates deployment media with the minimum required configuration and deploys one test device.

## 1. Open Foundry OSD as an administrator

Administrator permissions are required to install deployment components and create boot media.

## 2. Prepare Windows ADK and Windows PE

Open **ADK** in Foundry OSD. Review the detected status and use the installation button if a required component is missing or reported as incompatible. The built-in workflow installs Windows ADK and Windows PE Add-on `10.1.26100.9457`.

See [Windows ADK and Windows PE](/foundry-osd/adk.md).

## 3. Review general configuration

Open **General configuration** and confirm the deployment settings. Review the [Password protection scope](/foundry-osd/general.md#password-protection) and enable it for the deployment data you need to protect. Embedded network credentials remain accessible without the technician password. Follow the organization’s removable-media policy for every deployment image.

## 4. Configure only what you need

* Add Wi-Fi or Ethernet 802.1X settings when the target cannot use an open wired network.
* Choose Windows customization options required by the organization.
* Configure Windows Autopilot only when the device must be registered or receive a profile.
* Alternatively, configure [Domain Join](/foundry-osd/domain-join.md). It replaces the active Autopilot mode. Zero-touch Domain Join requires Password protection; Interactive does not.

## 5. Create deployment media

Open **Start**, resolve every blocking readiness item, and create an ISO or USB drive.

{% hint style="danger" %}
USB creation can erase the selected drive. Verify the device identity and capacity before confirming.
{% endhint %}

## 6. Boot the target device

Boot the device from a [prepared USB drive](/foundry-osd/media/create-usb.md), attach a validated [ISO](/foundry-osd/media/create-iso.md) as virtual media or virtual-machine media, or use [existing PXE infrastructure](/foundry-osd/media/pxe-deployment.md) where applicable. Foundry Connect verifies network readiness before Foundry Deploy begins.

## 7. Deploy Windows

In Foundry Deploy:

1. Select the target disk.
2. Select a Windows release, language, edition, and license channel.
3. Select a compatible driver pack.
4. Configure Windows Autopilot when JSON profile or zero-touch upload media displays that step. Interactive upload runs later during Windows OOBE.
5. For Domain Join, complete the [Domain join step](/foundry-deploy/domain-join.md) when the wizard shows it.
6. Review the summary and start deployment.
7. Verify the success page before rebooting.

For Domain Join, a successful deployment means the join was prepared. It runs after the restart; check that the computer joined the domain before handing it over.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.foundryosd.com/start-here/quick-start.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.