> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/your-deployr-guide.md).

# Introduction

Welcome to the DeployR documentation site. DeployR is a modern OS deployment platform from 2Pint Software, built to perform bare metal OS deployments using a flexible task sequence-based engine that allows for scale and efficiency. DeployR uses a web-based console for centralized management.

DeployR gives the power back to the IT team, allowing complete management of the whole imaging and provisioning lifecycle, whether that is deploying to hundreds of branch offices or in a lab environment. DeployR provides the tools and the framework to do this consistently and accurately.

In this documentation, you will find everything you need in order to properly deploy DeployR into your own environment, from infrastructure considerations and installation through to production deployments.

## Two editions, same platform

[DeployR Enterprise](https://documentation.2pintsoftware.com/deployr/deployr-enterprise/prerequisites) is a fully-supported platform with advanced capabilities; [DeployR Community](https://documentation.2pintsoftware.com/deployr/deployr-community/prerequisites) is supported through the community itself. The installation and configuration processes are different between the two: while DeployR Enterprise is designed for the utmost flexibility, DeployR Community is intended for those who need simplicity. Follow the appropriate setup documentation for the edition that you are using.

Of course the upgrade process from DeployR Community to DeployR Enterprise is easy, so if you need more advanced capabilities and support from the 2Pint Software experts, just let us know.

## Browse the documentation

* [What's new & Upgrades](https://documentation.2pintsoftware.com/deployr/whats-new-and-upgrades/release-notes)
* [Quick Start](https://documentation.2pintsoftware.com/deployr/quick-start/bare-metal-with-hyper-v)
* [DeployR Community](https://documentation.2pintsoftware.com/deployr/deployr-community/prerequisites)
* [DeployR Enterprise](https://documentation.2pintsoftware.com/deployr/deployr-enterprise/prerequisites)
* [Content Management](https://documentation.2pintsoftware.com/deployr/content-management/creating-a-content-item)
* [Task Sequences](https://documentation.2pintsoftware.com/deployr/task-sequences/creating-a-task-sequence)
* [Deployment Methods](https://documentation.2pintsoftware.com/deployr/deployment-methods/configuring-pxe-booting)
* [Automation & PowerShell](https://documentation.2pintsoftware.com/deployr/automation-and-powershell/scripting)
* [Customization](https://documentation.2pintsoftware.com/deployr/customization/2pxe-boot-menu-configuration)
* [Integrations](https://documentation.2pintsoftware.com/deployr/integrations/microsoft-graph-api-access)
* [Monitoring & Reporting](https://documentation.2pintsoftware.com/deployr/monitoring-and-reporting/monitoring-task-sequences-in-the-dashboard)
* [Troubleshooting](https://documentation.2pintsoftware.com/deployr/troubleshooting/task-sequence-debugging)
* [Reference](https://documentation.2pintsoftware.com/deployr/reference/step-definitions)


---

# 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://documentation.2pintsoftware.com/deployr/your-deployr-guide.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.