> 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/operations/licensing.md).

# Licensing

When the end of the license term or trial period happens, iPXE Web Service will need to be re-licensed in order for it to keep working.

Once you have obtained the new license keys, use the following steps to update the exiting license.

{% hint style="info" %}
NOTE: The iPXE Web Service license key is different from the 2PXE Server license key.
{% endhint %}

The iPXE Web Service license key is configured in the registry. Open the registry and navigate to **HKEY\_LOCAL\_MACHINE\SOFTWARE\2Pint Software\iPXE Anywhere Web Service**. Edit the **LicenseKey** value and enter in the new license key.

<figure><img src="https://2876852860-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdPQYwSRdBiXGQUCntFwx%2Fuploads%2FhzuZEfOnvI5p4WEmkXCf%2Fimage.png?alt=media&amp;token=68b58ed1-fa5c-4963-9632-a0afac3013e3" alt=""><figcaption></figcaption></figure>

Restart (or start) the 2Pint Software iPXE Anywhere Web Service in order to apply the new license key.

<figure><img src="https://2876852860-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdPQYwSRdBiXGQUCntFwx%2Fuploads%2FVwvSyXKkc1CgYhCyUgSk%2Fimage.png?alt=media&amp;token=fcc92a72-3d6b-4ee8-bbeb-d88810724f1d" alt=""><figcaption></figcaption></figure>

Once the service starts, the license key will be validated, and an event will show the new license period.

<figure><img src="https://2876852860-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdPQYwSRdBiXGQUCntFwx%2Fuploads%2FoyAeYfJmFJz5JGZTRNQt%2Fimage.png?alt=media&amp;token=2e5c8507-9ecb-4a31-aeae-6360131b368b" alt=""><figcaption></figcaption></figure>

If there is an issue with the license key (expired, wrong license key, etc.), the following event will be displayed: Service has stopped due to licensing issues!

<figure><img src="https://2876852860-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdPQYwSRdBiXGQUCntFwx%2Fuploads%2FzbuEAWZIU0pKfqINBQVq%2Fimage.png?alt=media&amp;token=1dc67a7c-d3f2-4c8a-aac4-662ff48a33e4" alt=""><figcaption></figcaption></figure>


---

# 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/operations/licensing.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.
