> 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/installation/2pxe-post-installation-checks.md). # Post-installation Checks ### Review Installation Files The 2PXE service can be installed to any location, but it is recommended that it be installed in the default directory. Once the service is installed, the following files should be present in the installation folder: * Main Service Executable: **TwoPint.TwoPxe.Service.exe** * Configuration editor: **TwoPint.ConfigEditor.Wpf\TwoPint.ConfigEditor.Wpf.exe** (launched from the **Configure 2PXE** Start menu shortcut; settings are stored in the registry, see [Configuring 2PXE Server](/2pxe-server/4.0/configuration/2pxe-config-file.md)) * Main DLL: **TwoPint.TwoPxe.Service.dll** * PowerShell scripts for managing the PowerShell Extension * **Readme.txt** * End User License Agreement file * Boot folder with iPXE boot loader files & wimboot binary ### Check the 2PXE service The Windows Installer package installs the 2PXE service. Typical reasons for the service failing to start are that the license key is invalid or expired (or, without a license key, that StifleR does not report a valid 2PXE license), or that something else is using the ports that 2PXE is trying to use. Check the 2PXE event logs described below. > NOTE: Remember to press F5 (refresh) in the Services console: the service might show as running when it is not. ### Check the RemoteInstall Folder The **RemoteInstall** folder is created in the **%ProgramData%\2Pint Software\2PXE** folder, as shown below: ![](https://content.gitbook.com/content/FSXaKC2Zqibd4KXt4dvD/blobs/KFUccQjuaTUNEL6BXyWd/28.png) > Note: These files are left behind when 2PXE is uninstalled, but are removed if the PowerShell removal script is used. The RemoteInstall folder contains more folders with default and temporary files. These files are managed by the service and normally do not require any further configuration. The figure below shows the root of the RemoteInstall folder, which hosts the boot files used for TFTP transfers. The only folder that requires attention is **Sources**, from which the WinPE boot images are accessed. Boot images need to be copied here to allow booting with the PowerShell request handler. If you are using the PowerShell request handler with regular Windows boot loaders, the Sources folder is also where you place your boot images. ![](https://content.gitbook.com/content/FSXaKC2Zqibd4KXt4dvD/blobs/KPL1zpoEF8LLecmT4iSo/29.png) ### 2PXE event logs 2PXE writes its events to Windows event logs. In Event Viewer, they are under **Applications and Services Logs** > **TwoPintSoftware** > **iPXEAnywhere.2PXE**. Check the **Main** > **Operational** log for errors after the service starts, for example licensing, certificate or port problems. See [Logs and events](/2pxe-server/4.0/troubleshooting/overview.md#logs-and-events) for details of all the logs. ### Adding Boot Images {% hint style="danger" %} **Configuration Manager compatibility** Configuration Manager integration is not currently supported by 2PXE Server 4.0. The MEMCM settings and examples on this page are retained for reference only. {% endhint %} The Configuration Manager integration handles its own boot image process and requires no configuration of boot images. If boot image retrieval and distribution was working before 2PXE was installed, it should continue to work afterward. For adding boot images when using the PowerShell request handler, see [PowerShell Request Handler](/2pxe-server/4.0/configuration/2pxe-config-file/powershell-request-handler.md). --- # 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/installation/2pxe-post-installation-checks.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.