> 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/whats-new-and-upgrades/upgrading-to-2pxe-server-4.0.md). # Upgrading to 2PXE Server 4.0 {% hint style="danger" %} **A direct upgrade to 2PXE Server 4.0 is not supported.** You must uninstall the existing version and perform a fresh installation. Alternatively, you can install 2PXE Server 4.0 on a new server. {% endhint %} Before proceeding, make sure you have backed up everything you may need from your existing installation. The steps below apply when moving from a previous 2PXE Server version to 4.0. ## Before uninstalling the existing version Back up the following items: * **2PXE and 2PXE WS configuration** — save the configuration for both components. * **Certificates** — back up the certificates used by your existing configuration, including any associated files you may need to restore. * **Customized scripts** — save any scripts that you have created or modified. * **ProgramData contents** — review the existing 2PXE and 2PXE WS ProgramData folders and copy any files you need to retain. Make sure these backups are stored somewhere outside the installation and ProgramData folders that will be removed. ## Remove the previous installation 1. Uninstall the existing 2PXE Server version and the related components that you are replacing. 2. After uninstalling, review the relevant ProgramData folders. 3. Remove any leftover files from the previous installation before installing version 4.0. {% hint style="warning" %} **Important:** Do not copy the old ProgramData contents into the new installation at this stage. Keep the required files in your separate backup location until the new installation has been verified. {% endhint %} ## Install 2PXE Server 4.0 Perform a clean installation of 2PXE Server 4.0 by following the [Manual Installation](/2pxe-server/4.0/installation/installation-and-configuration.md) instructions. If you are setting up a new server, prepare it for a fresh installation and follow the same installation guidance. ## Verify the new installation After installation, first verify that 2PXE Server 4.0 works correctly with its default, clean configuration. We recommend completing the basic functionality checks before changing configuration or restoring files from the previous installation. This helps distinguish installation issues from problems introduced by old configuration or files. ## Restore the required files and configuration Once the clean installation is working correctly, review your backups and restore only the items that are still required. Pay particular attention to **certificate handling**. Restoring old certificate files or related data too early may interfere with the new installation. Confirm that the new installation is functioning correctly before restoring certificate-related files, and restore only what is required. ## Configure 2PXE Server 4.0 Version 4.0 uses a UI-based configuration experience, similar to DeployR. The previous configuration-file approach is no longer used. If you are moving from 2PXE Server 3.x, you can use the values in your backed-up **2Pint.2PXE.Service.exe.config** file as a reference when setting up the new configuration in the **Configure 2PXE** editor. Review the old settings and enter the corresponding values in the editor where applicable. Some settings have changed or been replaced, so do not assume that every setting maps directly to a 4.0 setting. For details, see [Configuring 2PXE Server](/2pxe-server/4.0/configuration/2pxe-config-file.md), including the settings reference. For a new setup, we recommend using the **PowerShell integration method** and completing the configuration from there. See [PowerShell Request Handler](/2pxe-server/4.0/configuration/2pxe-config-file/powershell-request-handler.md) for details. --- # 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/whats-new-and-upgrades/upgrading-to-2pxe-server-4.0.md?ask=&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.