# 2PXE Server Configuration File

The 2PXE Server configuration file is used to configure global settings for the 2PXE server. The config file (**2Pint.2PXE.Service.exe.config**) is located within in the program files directory in which the server was installed. The settings below are located within the \<appSettings> section of the file:

```
Example: 
<appSettings>
    <add key="Setting Key Value Name" value="some value"/>
</appSettings>
```

> Note: Not all values in the 2Pint.2PXE.Service.exe.config file are documented here.  Please contact 2Pint Support prior to making changes to undocumented settings.&#x20;

You must restart the "2Pint 2PXE Server" service for the changes in the configuration file to take effect. \
In general, numerical value 0 = False and 1 = True.\
Individual values are to be considered default.

<table><thead><tr><th width="382.90352220520674">Setting Key Value Name</th><th>Values and Descriptions</th></tr></thead><tbody><tr><td>AcceptBootKeyBIOS</td><td><strong>Value:</strong> 0x000a (any key)<br><strong>Description:</strong> The code used to control the key to be pressed in order to boot from the network.<br>For a list of supported key codes, see <a href="https://ipxe.org/cmd/prompt">this article</a>.</td></tr><tr><td>AcceptBootKeyEFI</td><td><strong>Value:</strong> 0x000a (any key)<br><strong>Description:</strong> The code used to control the key to be pressed in order to boot from the network.<br>For a list of supported key codes, see <a href="https://ipxe.org/cmd/prompt">this article</a>.</td></tr><tr><td>AcceptBootTextBIOS</td><td><strong>Value:</strong> "Please Press Enter For Network Boot..."<br><strong>Description:</strong> This is the string of text which is displayed to the user when prompting to PXE boot for BIOS enabled clients. </td></tr><tr><td>AcceptBootTextEFI</td><td><strong>Value:</strong> "Please Press Enter For Network Boot..."<br><strong>Description:</strong> This is the string of text which is displayed to the user when prompting to PXE boot for EFI enabled clients. </td></tr><tr><td>BindToIP</td><td><strong>Value:</strong> &#x3C;IP Address><br><strong>Description:</strong> The local IP Address in which the 2PXE Service will send and receive UDP traffic.</td></tr><tr><td>BypassKeyPressforOptionalDeployment</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> Controls the key prompt for optional deployments. </td></tr><tr><td>CacheTFTPFilesInMemory</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> </td></tr><tr><td>CertificatesPath</td><td><strong>Value:</strong> %PROGRAMDATA%\2Pint Software\2PXE\Certificates<br><strong>Description:</strong> The local path in which self-signed certificates are stored. </td></tr><tr><td>ColorOptions</td><td><p><strong>Value:</strong> </p><pre><code> colour --rgb 0x000001 7 ||     colour --rgb 0xfffff1 1 ||     cpair --foreground 7 --background 1 1 ||     cpair --foreground 6 --background 4 2 ||     cpair --foreground 6 --background 0 3 ||     
</code></pre><p><strong>Description:</strong> Specifies the color scheme of the PXE user interface.</p></td></tr><tr><td>ConfigMgrSQLConnectionString</td><td><strong>Value:</strong> Server=&#x3C;CMDBServer>\&#x3C;InstanceName>;Trusted_Connection=Yes;DATABASE=&#x3C;CMDatabase><br><strong>Description:</strong> Connection string to connect to the ConfigMgr database. This is used when the SQL Connections is used by setting the <strong>EnableSCCMSQLConnection</strong> value set to 1. To allow access to the SQL, add the machine account of the 2PXE server to the local group on the ConfigMgr site server: <strong>ConfigMgr_DViewAccess</strong>.The format of the string is a typical .Net connection string URI so port and other items can be specified. For more information please refer to: <a href="https://msdn.microsoft.com/en-us/library/vstudio/system.data.sqlclient.sqlconnection.connectionstring(v=vs.100).aspx">https://msdn.microsoft.com/en-us/library/vstudio/system.data.sqlclient.sqlconnection.connectionstring(v=vs.100).aspx</a></td></tr><tr><td>CustomCAThumbprint</td><td><strong>Value:</strong> &#x3C;thumbprint><br><strong>Description:</strong> When not using CM, a thumbprint that can be validated by a third party signatory, specify the thumbprint to use and bind the HTTPS ports with, otherwise leave blank.</td></tr><tr><td>CustomVarDataGeneration</td><td><strong>Value:</strong> 1<br><strong>Description:</strong> Improved handling of .var creation.</td></tr><tr><td>DebugBeforeBoot</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> Enables the debugger prior booting.</td></tr><tr><td>DebugLogPath</td><td><strong>Value:</strong> %PROGRAMDATA%\2Pint Software\2PXE\2PXE.log<br><strong>Description:</strong> This log will be fairly verbose, so remember to set it to "0" to switch it off afterwards. Errors and warnings will always be logged to the 2PXE event log. Ensure that the service account has access to the path if no log is appearing.</td></tr><tr><td>DefaultExitString</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>DownloadBackground</td><td><strong>Value:</strong> Downloading.png<br><strong>Description:</strong> The image file displayed during the time when a boot image is being downloaded. The file can be found on the 2PXE server under: <em>&#x3C;InstallationFolder>\2Pint Software\2PXE\Boot</em>.</td></tr><tr><td>EnableDebugLog</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> Enables debugging. See the <strong>DebugLogPath</strong> setting for the location of the debug log file.</td></tr><tr><td>EnableiPXEAnywhereWebService</td><td><p><strong>Value:</strong> 0 (default) or specific value as referenced below. <br><strong>Description:</strong> Specifies to use iPXE Anywhere Web Service.</p><p><strong>BootRequest</strong> = 1<br>Main request, minimum value required when using authentication <br><strong>Syslog</strong> = 2<br>Not implemented yet <strong>ReportBootConfiguration</strong> = 4 <strong>ReportDLStart</strong> = 8 ReportDLComplete = 16 <strong>ReportDLBoot</strong> = 32</p><p><strong>RunCmdLineWinPE</strong> = 64 </p><p><strong>ExtraFile</strong> = 128 <br><strong>WinPEShl</strong> = 256 <br><strong>Config</strong> = 512</p><p><strong>RunCmdLineWinPEEnd</strong> = 1024 <strong>ReportPEEnd</strong> = 2048</p><p>When using all values, you need the sum: 1+4+8+16+32+64+128+256+512+1024+2048 = 4093 <br>Default value is: 1+4+8+16+32+512 = 573 </p></td></tr><tr><td>EnableiPXEBootLoaders</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Specifies to use iPXE boot loaders instead of any Windows boot loader. When used, iPXE boots the .wim images directly from the DP, when using SCCM and from HTTP server when using the PowerShell or default request handler. iPXE uses HTTP instead of TFTP from the RemoteInstall Directory.</td></tr><tr><td>EnableiPXEUSBSupport</td><td><strong>Value:</strong> 1 (default) or 0<br><strong>Description:</strong> </td></tr><tr><td>EnableMenuCountdown</td><td><strong>Value:</strong> 10000<br><strong>Description:</strong> Sets the countdown for when only non-mandatory (optional) task sequences are targetting the computer. After countdown the computer exits to next boot device on the computer. A value of 0 (zero) disables this feature and the menu will prompt until a task sequence is selected. Value in milliseconds but keep the value above 1000 otherwise it might fail.</td></tr><tr><td>EnablePowerShellExtension</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> Enables the PowerShell Extension, allow control of the boot process via the PowerShell script specified in the PowerShellExtenstionScript setting. This will move over the boot object to PowerShell which will return the correct actions for the machine booting via the PowerShell script.</td></tr><tr><td>EnableSCCMDebugShell</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> Enables the ConfigMgr command shell access (F8) in WinPE without modifying the boot image.</td></tr><tr><td>EnableSCCMExtension</td><td><strong>Value:</strong> 0 or 1<br><strong>Description:</strong> Enables the SCCM Extension, can be used in conjunction with the PowerShell Extension<strong>. This requires the service to be installed on a CM Distribution Point</strong> and that you have access to Configuration Manager.</td></tr><tr><td>EnableSCCMMandatoryCountdown</td><td><strong>Value:</strong> &#x3C;value in ms> or 0 or -1<br><strong>Description:</strong> Sets the countdown when one or multiple mandatory task sequence deployments are targetting the computer. A value of -1 (minus one) disables this feature and the menu will prompt until a task sequence is selected. A value of 0 (zero) disables this feature and the computer will boot the mandatory task sequence targeted deployment with the highest deployment creation time, just like ConfigMgr does with the PXE Service Point. Value in milliseconds, zero or -1.</td></tr><tr><td>EnableSCCMMenuCountdown (not included in .config file by default)</td><td><p><strong>Value:</strong> ”0” to disable and boot last deployed mandatory TS and above “1000” to enable and wait 1 second, “3000” waits for 30 seconds etc.</p><p><strong>Description:</strong> Sets the countdown for when only non-mandatory (optional) task sequences are targeting the computer. After countdown the computer exits to next boot device on the computer. A value of ”0” (zero) disables this feature and the menu will prompt until a task sequence is selected. Value in milliseconds but keep the value above ”1000” otherwise it might fail.</p></td></tr><tr><td>EnableSCCMSQLConnection</td><td><strong>Value:</strong> 0 or 1<br><strong>Description:</strong> Specifies to use a SQL connection to the ConfigMgr Database and boots the boot.wim images directly from the DP. If you don’t use this option, 2PXE will use HTTP to get the boot request just like the ConfigMgr PXE Service Point and can only return one boot image per client. SQL connection is recommended for ConfigMgr integration.</td></tr><tr><td>EnableSCCMUnknownMachinesSupport</td><td><strong>Value:</strong> 0 or 1<br><strong>Description:</strong> Enables ConfigMgr unknown computer support.</td></tr><tr><td>EncryptionKey</td><td><strong>Value:</strong> &#x3C;A 32-bit string><br><strong>Description:</strong> Used to encrypt the requests in case of server restarts or clustered/load balanced multi server installs. The string must translate to 32 bytes from UTF8.</td></tr><tr><td>ExternalFQDNOverride</td><td><strong>Value:</strong> &#x3C;string value><br><strong>Description:</strong> Overrides the default hostname used to set URLs for PXE request (URL for iPXE to connect to) as well as request to get data from if this is a DP. Set to "" if not in use, which then uses default FQDN hostname.</td></tr><tr><td>FailureBackground</td><td><strong>Value:</strong> Error.png<br><strong>Description:</strong> The image file displayed when there is an error condition detected during the PXE boot process. The file can be found on the 2PXE server under: <em>&#x3C;InstallationFolder>\2Pint Software\2PXE\Boot</em>.</td></tr><tr><td>FWDHCP</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Enables a Windows Firewall rule at service startup for DHCP, port 67.</td></tr><tr><td>FWHTTP</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Enables a Windows Firewall rule at service startup for the 2PXE web service, port 8050.</td></tr><tr><td>FWPROXYDHCP</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Enables a Windows Firewall rule at service startup for the 2PXE proxy DHCP service, port 4011.</td></tr><tr><td>FWTFTP</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Enables a Windows Firewall rule at service startup for TFTP, port 69.</td></tr><tr><td>HostCertificateThumbprint</td><td><strong>Value:</strong> &#x3C;thumbprint><br><strong>Description:</strong> When using public certificates that can be validated by a third party signatory, specify the thumbprint to use and bind the HTTPS ports with, otherwise leave blank.</td></tr><tr><td>HttpHostNameBindings</td><td><strong>Value:</strong> https://<em>:8050,http://</em>:8049<br><strong>Description:</strong> The binding that the client uses to connect to the 2PXE server. This can also be set to use http:</td></tr><tr><td>iPXEAnywhereWebServiceURI</td><td><strong>Value:</strong> http(s)://<br><strong>Description:</strong> Specifies the address and port to the iPXE Anywhere Web Service. Please see the iPXE Anywhere Web Service information on how to configure this.</td></tr><tr><td>iPXEErrorHandlingText</td><td><p><strong>Value:</strong> </p><pre><code>      :error                    set lasterr:hex ${errno:hex}                    echo Error has occured...                    sleep 5                    colour --basic 0 3 ||                    cpair --foreground 3 0 ||                    console --picture ${failimage} ||                    echo The call to iPXE failed...                    cpair 1                    echo                    echo The ${component} failed with error ${lasterr}, we do apologize on its behalf. ||                   echo                    echo For a detailed error description please go to: http://ipxe.org/${lasterr:hexraw} ||               echo Boot Info URL: ${BootPackagePathWithNoPwd} ||          echo Last Command: ${lastcmd} ||          echo Retries: ${retries} ||                   echo                     ifstat ||                    profstat ||                    params --name report                    param --params report statusid ${statusid}                    param --params report tokenid ${tokenid}                    param --params report uuidguid ${uuid:guid}                    param --params report component ${component}                    param --params report lastcmd ${lastcmd}                    param --params report requestid ${requestid}                    param --params report errno ${lasterr:hexraw}                     echo                    initrd --name errorscript.ipxe ${reportErrorURL}##params=report errorscript.ipxe ||                     echo                     chain errorscript.ipxe ||                    echo                    colour --basic 1 7 ||                    cpair --foreground 7 0 ||                    cpair 0 ||                    prompt --key 0x02 --timeout 30000 Press Ctrl-B for iPXE prompt, or wait for boot retry... &#x26;amp;&#x26;amp; shell || goto retryonerror                    reboot                    :retryonerror                    imgfree                    goto retrypoint
</code></pre><p><strong>Description:</strong> Specifies the script to manage errors in the environment.</p></td></tr><tr><td>iPXEF12PromptTimeout</td><td><strong>Value:</strong> 10000<br><strong>Description:</strong> How long until the F12 timeout for iPXE loaders for non mandatory CM deployments (in milliseconds).</td></tr><tr><td>iPXEWSOnly</td><td><strong>Value:</strong> 0 or 1<br><strong>Description:</strong> Redirects to the iPXE Anywhere Web Service only, requires no license as the iPXE Anywhere web service will check for licensing. It is required to also set the <strong>iPXEAnywhereWebServiceURI</strong> value as well. This is MSI property INSTALLTYPE 3.</td></tr><tr><td>LeanAndMeanMode</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> Lean and mean, if the machine is not in ConfigMgr, we boot the latest mandatory or latest offer available, no questions asked.</td></tr><tr><td>LicenseKey</td><td><strong>Value:</strong> &#x3C;2PXEServerLicenseKey><br><strong>Description:</strong> The 2PXE server license key. </td></tr><tr><td>LoginBackGround</td><td><strong>Value:</strong> Login.png<br><strong>Description:</strong> The image file which is displayed when the client is configured to signin prior to PXE boot. The file can be found on the 2PXE server under: <em>&#x3C;InstallationFolder>\2Pint Software\2PXE\Boot</em>.</td></tr><tr><td>ManagementPoint</td><td><strong>Value:</strong> &#x3C;FQDN of MP><br><strong>Description:</strong> Overrides the default MP retrieval from the registry, AD, or DNS with a static MP. For IBCM implementations, this is the same as your InternetBasedManagementPointFQDN that is set on clients. Set to "" if not in use.</td></tr><tr><td>MandatoryFlags</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Controls the way to treat Mandatory flags, 1= Allow rerun, 0=No rerun.</td></tr><tr><td>MenuDisplayFormat</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>MenuDisplayFormatDeployed</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>MenuSelectLine</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>MenuWelcomeLine</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>OptionBlockSizeAllowed</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> </td></tr><tr><td>port</td><td><strong>Value:</strong> <br><strong>Description:</strong> </td></tr><tr><td>PowerShellExtensionAllowBootScript</td><td><strong>Value:</strong> &#x3C;InstallFolder>\PowerShellExtensionAllowBoot.ps1<br><strong>Description:</strong> Specifies the path to the PowerShell script that manages reply to the client, if any. Note that this script does not return the boot image itself, and that this script can run multiple times per boot of each client. This will only return true or false and then the initial loader will contact the PXE server again with architecture info etc. It will not be created if it doesn't already exist. You should always enter a local path, or use environment variables for a local path.</td></tr><tr><td>PowerShellExtensionBootImagesScript</td><td><strong>Value:</strong> &#x3C;InstallationFolder>\PowerShellExtensionBootImages.ps1<br><strong>Description:</strong> Specifies the path to the PowerShell script that manages reply, boot files and images. It will not be created if it doesn't already exist. You should always enter a local path, or use environment variables.</td></tr><tr><td>PowerShellExtensionVarDataScript</td><td><strong>Value:</strong> &#x3C;InstallationFolder>\PowerShellExtensionAddVariables.ps1<br><strong>Description:</strong> Specifies the path to the PowerShell script that manages reply to the client, if any. Note that this script does not return the boot image itself, and that this script can run multiple times per boot of each client. This will only return true or false and then the initial loader will contact the PXE server again with architecture info etc. It will not be created if it doesn't already exist. You should always enter a local path, or use environment variables for a local path.</td></tr><tr><td>PreferredAdvertID</td><td><strong>Value:</strong> &#x3C;CMAdvertisementID><br><strong>Description:</strong> This defined ConfigMgr Advertisement ID (deployment ID) will be run if targeted to the machine. This setting will ignore any other advertisement targeted to the client. Make sure you set the <strong>EnableSCCMMandatoryCountdown</strong> to a value of higher than 0 to avoid stalling at the boot menu.</td></tr><tr><td>ProcessBackground</td><td><strong>Value:</strong> Wait.png<br><strong>Description:</strong> The image file which is displayed during a PXE boot request is waiting for a request. The file can be found on the 2PXE server under: <em>&#x3C;InstallationFolder>\2Pint Software\2PXE\Boot</em>.</td></tr><tr><td>RemoteInstallPath</td><td><strong>Value:</strong> %PROGRAMDATA%\2Pint Software\2PXE\Remoteinstall<br><strong>Description:</strong> Specifies the path to the RemoteInstall folder that contains boot files and images. It will be created if it doesn't already exist. You should always enter a local path, and can use environment variables. Sub-directories "Boot", "Tmp" and "Sources" must be present immediately below this folder or they will be created by the service, so ensure you specify a path to which the service account has access.</td></tr><tr><td>RunHttpServer</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> 2PXE has a built-in WebService for iPXE integration. If you are using the iPXE Anywhere Web Service, you can disable this setting. The HTTP WCF service only allows access to files under the RemoteInstall directory, and cannot transfer files outside this location.</td></tr><tr><td>RunOnDhcpPort</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> By default, 2PXE answers on both the DHCP (67) port and PXE (4011) port. This setting can be disabled if the machine also acts as a DHCP server.</td></tr><tr><td>RunOnHttpPort</td><td><strong>Value:</strong> 8050<br><strong>Description:</strong> 2PXE has a built-in WebService for iPXE integration. You can set the port for this service to a unique value and also set the IP Address or hostname to bind to. Please specify without port and use port setting above instead.</td></tr><tr><td>RunOnPxePort</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> By default, 2PXE answers on both the DHCP (67) port and PXE (4011) port. You can control this by setting the values to "0" for off or "1" for on below, for instance if this machine also acts as a DHCP server.</td></tr><tr><td>RunTftpServer</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> 2PXE has a built-in TFTP server, written by Jean-Paul Mikkers. You can switch it off by setting the <strong>RunTftpServer v</strong>alue to "0" below, for instance if you have your own TFTP server.</td></tr><tr><td>SCCMCAThumbprint</td><td><strong>Value:</strong> &#x3C;thumbprint><br><strong>Description:</strong> When using public certificates with CM, that can be validated by a third party signatory, specify the thumbprint to use and bind the HTTPS ports with, otherwise leave blank.</td></tr><tr><td>SCCMReportState</td><td><strong>Value:</strong> 1 (default) or 0<br><strong>Description:</strong> Instructs 2PXE to send CM status messages for mandatory deployments. 1 to send, 0 to not send. Set this to 0 when using a Rubicon step in the task sequence.</td></tr><tr><td>SetSMSTSPreferredAdvertID</td><td><strong>Value:</strong> &#x3C;CMAdvertisementID><br><strong>Description:</strong> If not set, a menu will be displayed in WinPE to select which advert to use.</td></tr><tr><td>SplashBackground</td><td><strong>Value:</strong> 2PintLogo.png<br><strong>Description:</strong> The image file which is displayed during the PXE boot process. The file can be found on the 2PXE server under: <em>&#x3C;InstallationFolder>\2Pint Software\2PXE\Boot</em>.</td></tr><tr><td>StartBackground</td><td><strong>Value:</strong> Start.png<br><strong>Description:</strong> The image file which is displayed during the start of the boot process. The file can be found on the 2PXE server under: <em>&#x3C;InstallationFolder>\2Pint Software\2PXE\Boot</em>.</td></tr><tr><td>TftpBlockSize</td><td><strong>Value:</strong> 768<br><strong>Description:</strong> Tweak the values below to decrease image download times. Note that PXE BIOS, routers and other network equipment may limit these settings further. Set TftpBlockSize to 512, 1024, 1456, 2048, 4096, 8192 or 16384. Default value is 768.</td></tr><tr><td>TftpFilter</td><td><strong>Value:</strong> boot*;\tmp*;\boot*;tmp*;\Sources*;Sources*<br><strong>Description:</strong> These are the folders beneath <strong>RemoteInstallPath</strong> that the TFTP server will serve files from. Specify one or more relative wildcard paths separated by a semi-colon.</td></tr><tr><td>TftpWindowSize</td><td><strong>Value:</strong> 4<br><strong>Description:</strong> Tweak the values to decrease image download times. Note that PXE BIOS, routers and other network equipment may limit these settings further. <br>Set TftpBlockSize to 512, 1024, 1456, 2048, 4096, 8192 or 16384. Default value is 1200 to avoid issues over WAN and VMWare. <br>Set TftpWindowSize to the number of packets to send without waiting for acknowledgement. Maximum is 32, default is 4. <br>TftpWindowSize is only used when using Windows Network Bootloaders use BCD data for configuration.</td></tr><tr><td>UseEmbeddedBootSDI</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Specifies to use an embedded boot.sdi image inside the boot.wim file under the \sms\boot\boot.sdi folder. This is always present in Configuration Manager images, so then 2PXE always uses embedded boot.sdi file regardless of this setting. For non-Configuration Manager installations, you may use a default WinPE image, and this file is not present unless added. If you cannot add this file to the boot.wim make sure this value is set to "0".</td></tr><tr><td>UseHighPerformanceRestartableThreads</td><td><strong>Value:</strong> 0 or 1 (default)<br><strong>Description:</strong> Better thread management for large organizations that do a lot of PXE requests, this requires <strong>BindToIP</strong> setting to be set.</td></tr><tr><td>UrlReplace</td><td><strong>Value:</strong> https://servername/path;http://servername/path, otherparam;newparam<br><strong>Description:</strong></td></tr><tr><td>UseiPXENativeDrivers</td><td><strong>Value:</strong> 0 (default) or 1<br><strong>Description:</strong> Determines whether to use the iPXE native drivers. The value 1 will enable this setting, a value of 0 will configure the client to use the 2PXE provided drivers.</td></tr><tr><td>Username</td><td><strong>Value:</strong> &#x3C;Domain\Username><br><strong>Description:</strong> Username and domain name to use to access content in form of DOMAIN\Username, password is stored in the Password.config file in the same folder as this file.</td></tr><tr><td>wimbootParams</td><td><strong>Value:</strong> Ex: gui, pause, pause=quiet, rawbcd, index=x<br><strong>Description:</strong> Specifies the command line to wimboot. For additional options, see:<br><a href="http://ipxe.org/appnote/wimboot_architecture">http://ipxe.org/appnote/wimboot_architecture</a></td></tr><tr><td>x64WinPEShlConfiguration</td><td><p><strong>Value:</strong> &#x3C;disabled by default></p><p><strong>Description:</strong> Can be used to launch additional commands after WinPE x64 has been downloaded, but before we hand over control to the ConfigMgr OSD Client. This is commonly used to launch custom frontends etc. See example below to launch a command prompt in WinPE:</p><pre><code>[LaunchApps]
<strong>%SYSTEMDRIVE%\sms\bin\x64\TsProgressUI.exe,/register:winpe
</strong>%windir%\system32\iPXEWinPEClient.exe,/NetworkInit
%windir%\system32\iPXEWinPEClient.exe,/SkipNetworkInit
%SYSTEMDRIVE%\sms\bin\x64\TsBootShell.exe"/>
%windir%\system32\cmd.exe /c start &#x26;quot;Paused TS: Close this to continue&#x26;quot; /wait cmd
</code></pre></td></tr></tbody></table>

#### Valid Configuration Combinations

The following list can be used to find supported and unsupported configuration combinations in this release, green indicating the “really” supported scenarios that we would like people to test:

![](https://content.gitbook.com/content/5nkrKH5nKL8LvEgvw7HO/blobs/4NpKJ8h616RJyaz9A1tF/valid_ipxe_configs.png)

The preceding table shows the different valid options, if you are unsure of your scenario, please contact <support@2pintsoftware.com>.