Comment on page
Installation and Configuration
The following items must be installed and configured on the 2PXE Server regardless of which handler you will be using (Configuration Manager or PowerShell)
- The .NET Framework 4.6.2 or above must be installed.
- If you want to use Configuration Manager the 2PXE Software must be installed onto a CM Distribution Point.
As stated previously, in an ideal setup, a dedicated Configuration Manager Distribution Point (DP) will be installed to handle all iPXE Anywhere PXE Booting.
- BranchCache has been configured in your environment
- DO NOT install WDS or a PXE Service Point on this system. The 2PXE server replaces that functionality and operate on the same ports (69 and 4011).
Allowing Access to the Configuration Manager SQL Database
2PXE uses SQL as the fastest way to retrieve boot actions for a system. Add the service account (default the machine account of the Distribution Point) to the ConfigMgr_DViewAccess local group on the Configuration Manager Site Server. Members in this group have the required access for using distributed views against the Configuration Manager database. The account only requires read rights and can be further locked down if necessary.
Figure 6 shows the local group for accessing SQL, the SQL reporting group provides sufficient SQL rights.
If you are not using Configuration Manager then the only security related issue is to ensure that the boot URL returned from the PowerShell command is accessible with anonymous security or by using an ACL and the iPXE Network Access Account.
The installer is an MSI, which adds a Windows service for hosting the proxyDHCP and the TFTP service. There are two versions. One each for x86 and x64.
Installation requires administrative rights, as does running the service as it needs to create BCD files.
There is no way to avoid the requirement around full admin rights, so the recommended installation is always on a server system and not on desktop devices.
Licensing for iPXE Anywhere is provided via a Licensing .cab file which will have been sent to you as part of the 2Pint registration and download process. The license file will contain your company information and is used to validate the installation.
Figure 7 shows the contents of a typical installation source folder. One x86 installer and one x64 installer plus a default license file.
The 2PXE Server and iPXE Anywhere is licensed per network bootable node. When using Configuration Manager this is verified shortly after service startup and at a timely interval. The following SQL query will be used to check the number of devices in the database:
select Count(*) As LiveSystems from v_R_System where ResourceType = 5 AND
AgentEdition0 = 0 OR /* Windows Desktop or laptop computer */
AgentEdition0 = 1 OR /* Windows ARM-based device (running Windows RT) */
AgentEdition0 = 5 OR /* Mac computer */
AgentEdition0 = 6 OR /* Windows CE */
AgentEdition0 = 7 OR /* Windows Embedded */
AgentEdition0 = 12 OR /* Intel System On a Chip */
AgentEdition0 = 13 /* Unix and Linux servers */
This means that you can still have a large number of users and other device types that are non PXE bootable like iOS devices & iPAD’s in your hierarchy.
NOTE: All the iPXE Anywhere installers can be run manually or automated (silent). See the appendices for further information on command line switches.
Once completed, hit the “Finish” button to exit the installer. You are now done!