> 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/2pxe-server/proof-of-concept/objectives-and-prerequisites.md).
# Objectives & Prerequisites
It is recommended that a 2PXE POC be conducted in a test lab environment. If a test lab is unavailable, a POC can be executed in a production environment with minimal risk, but it should be limited to specific subnets from which you want clients to boot.
The objective for a 2PXE POC is to demonstrate how 2PXE can provide iPXE boot services to network clients.
It’s important that the POC is driven from clear requirements. These requirements should be clearly defined and include test plans for validation.
## Prerequisites
We recommend that all testing of 2Pint Software components should be installed and verified in a separate lab environment before implemented in a production environment. Once tested and verified in the lab, in can then be tested in the production environment. If a test lab is unavailable, the POC can be executed in a production environment in a controlled manner.
Review the following page prior to installing 2PXE:
* [ ] [Planning Your Implementation](/2pxe-server/planning/planning-your-implementation.md)
{% hint style="info" %}
The PXE protocol is a broadcast based network protocol. On any given subnet, it is important that only one PXE server should be servicing clients which attempt to PXE boot.
{% endhint %}
### Lab Testing Environment
A lab environment is typically the best environment to test 2PXE. If possible, the server in which you plan on installing the 2PXE service should be on the same subnet in which you plan to PXE boot clients. The reason for this is because PXE is a broadcast based protocol which is not routable. For PXE booting clients to reach a PXE server on another subnet, [IP Helpers](/2pxe-server/configuration/dhcp-configuration/using-ip-helpers.md) have to be added to your router configuration, or [DHCP Scope Options](/2pxe-server/configuration/dhcp-configuration/using-dhcp-scope-options/overview-dhcp-scope-options.md) must be added to your DHCP scope to redirect clients to the IP of the PXE server.
All major Virtual Platforms such as Hyper-V and VMWare will support PXE booting clients, but using physical client hardware which represents the makes and models of hardware you support, will be a far more conclusive test.
### Production Testing Environment
It is possible to test 2PXE in a production environment, but as mentioned above, it is important to only test on subnets which will not be impacted by installing a new PXE server.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://documentation.2pintsoftware.com/2pxe-server/proof-of-concept/objectives-and-prerequisites.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.