> 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/4.0/planning/prerequisites.md).

# Prerequisites

This page describes the requirements for installing and running 2PXE Server 4.0. Review these requirements before starting the installation.

## Operating system

* Windows Server 2019 or later.

## Microsoft .NET components

Install all three of the following Microsoft .NET 10 components, version 10.0.14 or later. They are available from the [.NET 10.0 download page](https://dotnet.microsoft.com/download/dotnet/10.0):

* .NET Runtime 10.0.14
* .NET Desktop Runtime 10.0.14
* ASP.NET Core Runtime 10.0.14

Microsoft .NET Framework 4.8 or later is also required by the **Configure 2PXE** configuration editor. It is included with Windows Server 2022 and later. On Windows Server 2019, it must be [installed separately](https://dotnet.microsoft.com/download/dotnet-framework/net48).

## Visual C++ Runtime

The Visual C++ Runtime for Visual Studio must be installed on the server.

## Installation account and permissions

The account used to install 2PXE must have administrator rights.

Review the [Permissions](/2pxe-server/4.0/planning/permissions.md) page for additional permission requirements and security considerations.

## Licensing

A 2PXE license is required. You can provide a license key in the **Configure 2PXE** configuration editor, or use a 2PXE license provided through StifleR. For details, see [Licensing](/2pxe-server/4.0/configuration/2pxe-config-file.md#licensing).

## Optional components

### Windows BranchCache

Install and configure the Windows BranchCache feature if clients should download files served by 2PXE (boot files and boot images for the PowerShell request handler) from BranchCache peers. For configuration instructions, see [BranchCache Setup](/2pxe-server/4.0/configuration/branchcache-setup.md).

### iPXE Anywhere Web Service

The 2PXE server can operate without the iPXE Anywhere Web Service. The Web Service is optional and provides additional functionality, including logging, reporting, StifleR integration, and custom scripting. See [Planning Your Implementation](/2pxe-server/4.0/planning/planning-your-implementation.md) for more information.

## Antivirus exclusions

On the 2PXE Server, it is recommended that antivirus real-time scanning exclusions be put in place so that scanning does not interrupt file handling and service operations. Exclude the service process and the following folders:

**Process:**

`TwoPint.TwoPxe.Service.exe`

**2PXE program files:**

`<Installation Dir>\\2Pint Software\\2PXE\\`

**ProgramData:**

`C:\\ProgramData\\2Pint Software\\2PXE`

## Network and firewall considerations

Review [Firewall Considerations](/2pxe-server/4.0/planning/firewall-considerations.md) and confirm that the required network traffic is permitted in your environment.

If you use certificates for HTTPS communication, review [Certificate Considerations](/2pxe-server/4.0/planning/certificate-considerations.md) before installation.

{% hint style="danger" %}
**Configuration Manager compatibility**

Microsoft Configuration Manager integration is not currently supported by 2PXE Server 4.0. Configuration Manager-specific requirements and instructions elsewhere in this documentation are retained for reference only and do not describe a supported 4.0 deployment.
{% endhint %}


---

# 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/2pxe-server/4.0/planning/prerequisites.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.