The 2PXE service can be installed to any location, but we recommend it to be installed in the default directory. Once the service is installed, the following files should be present in the installation folder:
Main Service Executable 2Pint.2Pxe.Service.exe
Configuration File 2Pint.2Pxe.Service.exe.config
Main DLL 2Pint.2Pxe.dll
License file License.cab
License file License.nfo extracted from License.cab
Microsoft .net dependency dlls
PowerShell scripts for managing the PowerShell Extension
Readme.txt
End User License Agreement file
Boot folder with iPXE boot loader files & wimboot binary
Important: Ensure that the License.nfo file has been created and that the license information inside the file looks correct by opening it up in notepad.
The Windows Installer file will install a service called 2PXE which it will also start during the install. Typical failures to start can be that the license file is wrong, or that something is using the ports that 2PXE is trying to use.
NOTE: Don’t forget that F5 (refresh) button, the service might show as running but is it really?
The RemoteInstall directory is created within the 2Pint Software\2PXE \ProgramData folder as per below:
Note: These files are left behind after an msi uninstall of 2PXE, but will be removed if the PowerShell removal script is used.
Inside the RemoteInstall folder you have more folders with default and temporary files. These files are managed by the service and normally don’t require any further configuration.
Figure 8 shows the root of the RemoteInstall directory used for hosting the boot files used by the TFTP transfer. The only file that requires attention is the Sources, from where the WinPE boot images are accessed. Images needs to be copied to here to allow booting using PowerShell extensions.
If you are using the PowerShell extension with regular Windows Boot Loaders the Sources folder is where you place your boot images.
At service start up 2PXE checks for and if not present will create a Windows Event log.
Note: The log is located under the Application and Services Logs in the Event Viewer. This log is not removed as a part of the uninstallation.
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 then it should work after.
For adding images when using PowerShell integration, please refer to the 2PXE PowerShell Mode Guide.
