> 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/ipxe-ws/4.0/ipxe-anywhere-web-service-overview.md).

# iPXE Anywhere Web Service Overview

This is the iPXE Anywhere Web Service 4.0 (current) release documentation. For other versions, select the version from the drop-down list at the top left.

The iPXE Anywhere Web Service is a powerful network booting solution.

2Pint Software took iPXE, a popular open-source network boot firmware, and added the “Anywhere” functionality by providing a proxyDHCP/TFTP/HTTP server called 2PXE Server. Additional functionality and control can then be added with a web service component, called "iPXE Anywhere". These server components make iPXE sing and dance by allowing communication and control over the iPXE client software as well as providing reporting functionality.

The iPXE Anywhere Web Service is an optional add-on to 2PXE Server.

## iPXE Anywhere Web Service

iPXE Anywhere Web Service is a web service that the iPXE Network Boot Program can be configured to talk to through 2PXE Server. The iPXE Anywhere server uses HTTP to talk with the clients and SQL to talk to the iPXE Anywhere SQL database. It offers extended functionality during the boot process, such as updating the BIOS, interacting with Microsoft MDT, and creating custom iPXE menus.

### iPXE Web Service Features

#### SysLog Server

Syslog is a way for network devices to send event messages to a logging server, usually known as a syslog server. The syslog protocol is supported by a wide range of devices and can be used to log many different types of events. For example, a router might send messages about users logging on to console sessions, while a web server may log access denied events.

The iPXE Anywhere Web Service includes a built-in TLS syslog server that receives syslog messages from the iPXE Network Boot Program. It is used by the remote console, and only runs when **Enable remote console** is turned on (see [Configuring the iPXE Web Service](/ipxe-ws/4.0/configuration/configuring-the-ipxe-web-service.md#syslog)).

#### StifleR Integration

StifleR is a powerful network bandwidth control and reporting tool from 2Pint Software. The web service can be configured to feed progress data to StifleR to allow for early detection, visibility and reporting of client boot activity.

#### StifleR Error Handling

Because the StifleR service can retrieve messages from the web service, the web service can also provide full error details directly to StifleR for troubleshooting.

#### Reporting

The iPXE Anywhere Web Service can be configured to track your PXE boot requests and progress. This can be useful for keeping track of all your PXE boot attempts globally, tracking errors and failures, and tracing any errant activity. You can also view historical reports (management folks seem to like these stats), and create your own reports, because the reports are based on SQL Server Reporting Services (SSRS).

#### Custom Actions & Menus

One of the most powerful features of the iPXE Anywhere Web Service is the ability to execute PowerShell code on the server in order to perform further, more complex actions on the system, or query other systems in your enterprise. Some examples:

* Automatically create a support ticket when a boot fails
* Query an MDT database for computer details and eligibility before proceeding
* Present a custom technician menu for troubleshooting
* Check the system BIOS version and remediate if necessary
* Order pizza if it is really late (seriously, it is PowerShell, so anything is possible!)


---

# 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/ipxe-ws/4.0/ipxe-anywhere-web-service-overview.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.
