> 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/whats-new-and-upgrades/upgrading-to-ipxe-ws-4.0.md).

# Upgrading to iPXE Anywhere Web Service 4.0

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

If your deployment relies on Microsoft Configuration Manager (ConfigMgr/SCCM) PXE integration, do not upgrade 2PXE Server to version 4.0. 2PXE Server 4.0 is not currently compatible with Configuration Manager. Upgrading iPXE Anywhere Web Service does not change this limitation.
{% endhint %}

{% hint style="danger" %}
**A direct upgrade to iPXE Anywhere Web Service 4.0 is not supported.** You must uninstall the existing 3.x version before installing 4.0. Alternatively, you can install iPXE Anywhere Web Service 4.0 on a new server.
{% endhint %}

The same applies to 2PXE Server: a direct upgrade to 2PXE Server 4.0 is not supported either, so plan to move both components to 4.0 together.

## Before uninstalling the existing version

Back up the following items, and store the backups outside the installation folder:

* **Configuration**: make a copy of the **iPXEAnywhere.Service.exe.config** file from the installation folder, and export the `HKEY_LOCAL_MACHINE\SOFTWARE\2Pint Software\iPXE Anywhere Web Service` registry key, which contains the license key, ports and database connection string. Use them as a reference when you configure 4.0.
* **Customized scripts**: copy the **Scripts** folder from the installation folder (by default `C:\Program Files\2Pint Software\iPXE AnywhereWS\Scripts`) if you have created or changed any scripts.
* **Database**: note the name of the iPXE Anywhere SQL database (typically `iPXEAnywhere35` in 3.x; it is in the `ConnectionString` registry value), and back it up. Uninstalling the web service does not remove the database, and version 4.0 can keep using it.
* **Certificates**: if you use your own HTTPS certificate, note its thumbprint or subject name.

## Remove the previous installation

1. Uninstall the existing iPXE Anywhere Web Service from **Apps** (or **Programs and Features**).
2. Check the installation folder (by default `C:\Program Files\2Pint Software\iPXE AnywhereWS`), and remove any files and folders that are left behind, after confirming that they are backed up. In particular, remove any leftover **Scripts** folder: iPXE Anywhere Web Service 4.0 only copies its default scripts to the **Scripts** folder when that folder has no subfolders (see [Updating the Scripts Folder](/ipxe-ws/4.0/configuration/updating-the-scripts-folder.md)).
3. Check whether the `HKEY_LOCAL_MACHINE\SOFTWARE\2Pint Software\iPXE Anywhere Web Service` registry key still exists. Version 4.0 stores its settings in the same key, so remove any values left behind by the previous version after confirming that they are backed up.

## Install iPXE Anywhere Web Service 4.0

Perform a clean installation by following the [iPXE Anywhere Web Service Install](/ipxe-ws/4.0/installation/ipxe-anywhere-web-service-install.md) or [Unattended Installation](/ipxe-ws/4.0/installation/unattended-installation.md) instructions. Review the [Permissions](/ipxe-ws/4.0/planning/permissions.md) page first: in 4.0, the service creates the database when it starts, so the service account (not the installation account) needs SQL Server permissions.

## Configure iPXE Anywhere Web Service 4.0

Version 4.0 is configured with the **Configure iPXE WS** configuration editor instead of the **iPXEAnywhere.Service.exe.config** file. Use your backed-up `.config` file and registry export as a reference, and enter the corresponding values in the editor. Some settings have changed or been replaced, so do not assume that every setting maps directly to a 4.0 setting. See [Configuring the iPXE Web Service](/ipxe-ws/4.0/configuration/configuring-the-ipxe-web-service.md), including the Settings that changed from 3.x table.

To keep using the 3.x database, set the **Database settings** in the editor to point to it: enter its SQL Server instance in **SQL Server instance**, and its name in **SQL Server database**. The default database name in 4.0 is `iPXEAnywhere`, while 3.x typically used `iPXEAnywhere35`, so change the name if needed; otherwise, the service creates a new, empty database. When the service starts, it updates the existing database to the 4.0 version. The service account needs permissions on the existing database (see [Permissions](/ipxe-ws/4.0/planning/permissions.md)).

On the 2PXE Server, configure the integration with the web service in the **Configure 2PXE** editor. See [Integrating with 2PXE Server](/ipxe-ws/4.0/configuration/integrating-with-2pxe-server.md).

## Verify the new installation

Before restoring any customized scripts, verify that the web service works correctly with its default scripts. This helps distinguish installation issues from problems introduced by old scripts or settings. Check the event logs for errors (see Troubleshooting).

## Restore customized scripts

Once the new installation is working, restore only the customized scripts that are still required, to the **Scripts** folder in the installation folder. Compare them with the new default scripts first, because the default scripts have changed in 4.0.

Scripts now run in PowerShell 7.6 instead of Windows PowerShell, so test each restored script. Scripts written for Windows PowerShell 5.1 may need changes (see [How the scripts run](/ipxe-ws/4.0/configuration/updating-the-scripts-folder.md#how-the-scripts-run)).


---

# 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/whats-new-and-upgrades/upgrading-to-ipxe-ws-4.0.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.
