> 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/quick-start/deployr-suite-evaluation-lab-kit.md).

# DeployR Suite Evaluation Lab Kit

The **DeployR Enterprise Evaluation Lab Kit** is a fully self-contained Hyper-V-based lab environment designed to help organizations evaluate the capabilities of DeployR Enterprise in a safe, isolated, and repeatable manner. The lab kit automates the deployment of a complete test environment, allowing administrators, consultants, and engineers to quickly explore DeployR features without impacting production systems.

The lab requires a Hyper-V host with **nested virtualization** enabled. During deployment, the lab kit creates a **parent server virtual machine** (2PINT-LABKIT) that serves as the foundation for the environment. Once the parent VM is provisioned, it automatically builds the supporting infrastructure, including **two server child virtual machines** (DC and DEPLOYR) and **up to three client VM shells** (PC01, PC02, and PC03) that can be used for deployment, testing, and validation scenarios.

The first server VM, DC, is configured as the lab's core infrastructure server, providing **Active Directory Domain Services, DHCP, and DNS**. This creates a fully functional enterprise-style network that supports device deployment and management workflows. The second server VM, DEPLOYR, hosts the DeployR solution stack, including **iPXE Anywhere**, **DeployR Enterprise**, and the **StifleR Dashboard**, which is a required component for DeployR Enterprise functionality and reporting. DeployR Enterprise integrates deployment, PXE boot services, task sequencing, content management, and advanced deployment capabilities into a single platform.

Once deployed, the lab provides a realistic environment for evaluating key DeployR Enterprise capabilities, including operating system deployment, PXE boot scenarios, task sequencing, content distribution, deployment automation, analytics, and integration with the broader 2Pint Software ecosystem. Because the environment is isolated and self-contained, administrators can freely experiment with configurations, deployments, and recovery scenarios without affecting production infrastructure.

Whether you are evaluating DeployR Enterprise for the first time, validating deployment workflows, demonstrating product capabilities, or building a proof of concept, the DeployR Enterprise Evaluation Lab Kit provides a fast and repeatable way to stand up a complete enterprise deployment environment within Hyper-V. The best part about the DeployR Enterprise Evaluation Lab Kit is that it is all built using DeployR.


---

# 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/quick-start/deployr-suite-evaluation-lab-kit.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.
