Wiki source code of Network Boot Service
Last modified by Sabrina V. on 2025/11/26 07:21
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{aagon.floatingbox/}} | ||
| 2 | |||
| 3 | = General information = | ||
| 4 | |||
| 5 | The Network Boot Service is the central point responsible for the network boot of client computers. | ||
| 6 | Components of the Network Boot Service are a DHCP Proxy Service, which responds to DHCP requests from Boot Clients, and a TFTP Service, which is responsible for downloading files through the TFTP Client of the Network Boot Clients. | ||
| 7 | |||
| 8 | The installation file for the Network Boot Service can be found on the ACMP share in the NetworkBoot directory. Executions the file ACMP Network Boot Service.msi to start the installation. First enter the name of the ACMP Server and the port. | ||
| 9 | |||
| 10 | |||
| 11 | (% style="text-align:center" %) | ||
| 12 | [[image:XWiki.Images.WebHome@hmfile_hash_f12bc69d.png||alt="14.1 - Server eintragen" height="311" width="399"]] | ||
| 13 | Enter server name and server port | ||
| 14 | |||
| 15 | Once you have confirmed your details by clicking on //Next//, you can start the installation. Once the installation is complete, the Network Boot Service that has just been installed is entered and must be configured. | ||
| 16 | |||
| 17 | = Configuration of the Network Boot Service = | ||
| 18 | |||
| 19 | Navigate to the configuration in the ACMP Console to //System > Settings > OS Deployment > Network Boot Service//. | ||
| 20 | The upper area of the window deals with general settings for the Network Boot. Firstly, specify whether Clients should be imported automatically. Choose between the following options: | ||
| 21 | |||
| 22 | * Only import Network Boot requests | ||
| 23 | |||
| 24 | Only Clients for which the network boot has been performed are imported. These are displayed in the inventory with the computer name [NetworkBoot]. | ||
| 25 | |||
| 26 | * Import all DHCP requests | ||
| 27 | |||
| 28 | All devices are imported. It is irrelevant whether the PXE boot was performed or not. | ||
| 29 | |||
| 30 | * Disable | ||
| 31 | |||
| 32 | No Clients are imported. | ||
| 33 | |||
| 34 | |||
| 35 | You can also enter MAC addresses from which the network boot should ignore all requests. To create a filter, select //Add// and enter the address mask. You can use '*' (asterisk key) as a wildcard to specify address patterns. You can also enter an explanatory description. The filter is only applied after you enable it. You can enable the filter directly in the overview or select the //Edit// button when the filter is selected. | ||
| 36 | |||
| 37 | The Client on which you have just carried out the installation appears in the Network Boot Service area at the bottom. Select the entry and click on //Edit//. A file repository must be integrated to use the Network Boot Service, which you can integrate here. | ||
| 38 | |||
| 39 | {{aagon.infobox}} | ||
| 40 | The file repository used must be of the "network share" type. Only these are supported for use in OS Deployment. | ||
| 41 | {{/aagon.infobox}} | ||
| 42 | |||
| 43 | (% style="text-align:center" %) | ||
| 44 | [[image:XWiki.Images.WebHome@hmfile_hash_d5ec0f48.png||alt="14.2 - Bindungen bearbeiten" height="384" width="512"]] | ||
| 45 | Bindungen des Network Boot Services bearbeiten | ||
| 46 | |||
| 47 | All network cards of the Client are displayed. Enable the checkbox only for the IP address that is to use the Network Boot Service. | ||
| 48 | |||
| 49 | Always send boot response is used if no Rollout has been started for boot requests from Clients. A timeout is prevented. | ||
| 50 | |||
| 51 | {{aagon.infobox}} | ||
| 52 | Please note that this option may affect Thin Clients and IP phones, depending on the configuration. | ||
| 53 | {{/aagon.infobox}} | ||
| 54 | |||
| 55 | Confirm your customisations and save the changes. You will be prompted to restart the Network Boot Service on the Client. You will find the service in the local services with the name ACMP Network Boot. | ||
| 56 | |||
| 57 | = Firewall settings = | ||
| 58 | |||
| 59 | The firewall must be configured accordingly for the Network Boot Service to function properly. No additional information is required when using the Windows firewall. All items are already entered during the installation of the Network Boot Service. | ||
| 60 | |||
| 61 | If you are using a firewall from another manufacturer, the following information must be entered. | ||
| 62 | |||
| 63 | == Inbound Rule == | ||
| 64 | |||
| 65 | |(% style="width:150px" %)**Field**|(% style="width:1213px" %)**Indication** | ||
| 66 | |(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service Proxy DHCP (UDP) | ||
| 67 | |(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service | ||
| 68 | |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP | ||
| 69 | |(% style="width:150px" %)Local Port|(% style="width:1213px" %)67,4011 | ||
| 70 | |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any | ||
| 71 | |(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service TFTP Server (UDP) | ||
| 72 | |(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service | ||
| 73 | |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP | ||
| 74 | |(% style="width:150px" %)Local Port|(% style="width:1213px" %)69 | ||
| 75 | |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any | ||
| 76 | |||
| 77 | == Outbound Rule == | ||
| 78 | |||
| 79 | |(% style="width:150px" %)**Field**|(% style="width:1213px" %)**Indication** | ||
| 80 | |(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service (TCP) | ||
| 81 | |(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service | ||
| 82 | |(% style="width:150px" %)Protocol|(% style="width:1213px" %)TCP | ||
| 83 | |(% style="width:150px" %)Local Port|(% style="width:1213px" %)Any | ||
| 84 | |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)2106 (You specified this port during the installation of the Server) | ||
| 85 | |(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service Proxy DHCP (UDP) | ||
| 86 | |(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service | ||
| 87 | |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP | ||
| 88 | |(% style="width:150px" %)Local Port|(% style="width:1213px" %)67,4011 | ||
| 89 | |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any | ||
| 90 | |(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service TFTP Server (UDP | ||
| 91 | |(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service | ||
| 92 | |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP | ||
| 93 | |(% style="width:150px" %)Local Port|(% style="width:1213px" %)69 | ||
| 94 | |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any | ||
| 95 | |||
| 96 | = NBS in Subnets = | ||
| 97 | |||
| 98 | There are different scenarios in which the NBS is used. Two common cases are described below. | ||
| 99 | |||
| 100 | == Operation in another subnet == | ||
| 101 | |||
| 102 | If you have multiple subnets / VLANs, you must set up IP helpers on the routers/switches, which forward the DHCP requests to the NBS in addition to your DHCP Server. This ensures that the blocked broadcasts are forwarded to the subnets according to the IP helper configuration. | ||
| 103 | |||
| 104 | {{aagon.infobox}} | ||
| 105 | Please note that no option 66 or 67 must be set on the DHCP Server. | ||
| 106 | {{/aagon.infobox}} | ||
| 107 | |||
| 108 | Alternatively, an NBS must be installed in each subnet in which you want to roll out. This ensures direct communication between the NBS and the ACMP Server. | ||
| 109 | |||
| 110 | However, if you do not have the option of forwarding multiple broadcast requests across the subnet and configuring them, you can install the NBS on the DHCP Server directly. | ||
| 111 | |||
| 112 | {{aagon.infobox}} | ||
| 113 | This option should only be used if the IP Helper/DHCP Relay settings cannot be set! Make sure that the Network Boot Service is configured to "automatic (delayed start)" so that the DHCP Server always starts before the Network Boot Service. | ||
| 114 | {{/aagon.infobox}} | ||
| 115 | |||
| 116 | For this to be possible, the DHCP area options 60 and 66 must be configured. Option 66 can be set in the DHCP GUI. Option 60 is not displayed in the DHCP GUI by default. It must therefore be enabled via CMD. | ||
| 117 | |||
| 118 | |||
| 119 | The commands for this are: | ||
| 120 | |||
| 121 | netsh | ||
| 122 | |||
| 123 | dhcp server | ||
| 124 | |||
| 125 | add optiondef 60 PXEClient STRING 0 comment=//Option added for PXE support// | ||
| 126 | |||
| 127 | set optionvalue 60 STRING PXEClient | ||
| 128 | |||
| 129 | set optionvalue 66 STRING (Hostname DHCP Server) | ||
| 130 | |||
| 131 | exit | ||
| 132 | |||
| 133 | |||
| 134 | The host name of the DHCP Server must be inserted in the row, unless option 66 has already been set accordingly in the GUI. | ||
| 135 | |||
| 136 | == Operation at another location == | ||
| 137 | |||
| 138 | To be able to operate the NBS at a different location, you must first create a deployed file repository ([[Verteiltes File Reposititory>>doc:ACMP.69.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]) You install an NBS at this location. | ||
| 139 | |||
| 140 | The NBS of the location is configured to the deployed file repository. This saves your bandwidth and requests are edited more quickly. | ||
| 141 | |||
| 142 | = Error messages during Rollout via the Network Boot Service = | ||
| 143 | |||
| 144 | If the ACMP OS Deployment does not run correctly via the Network Boot Service and the client does not load a boot image despite the assigned rollout, there may be several reasons for this. | ||
| 145 | |||
| 146 | General possible reasons: | ||
| 147 | |||
| 148 | * The Network Boot Service is not configured correctly. In this case, check the settings of the service on the server. | ||
| 149 | * The client assigned to the rollout is not in the same network segment as the Network Boot Service. Make sure that both systems are either on the same network or can communicate with each other via a correctly configured IP helper. | ||
| 150 | * In the network, there are continuing boot services that also respond to DHCP options 66/67. This can cause the client to receive an incorrect boot image or no response at all. | ||
| 151 | |||
| 152 | Make sure in advance that these possible errors are excluded. | ||
| 153 | |||
| 154 | If you see specific error messages on the rollout client, you must open the command line in the foreground of your screen using the key combination “SHIFT + F10”. If you are working with a notebook, you may need to press the “FN” key in addition to the shift key (“SHIFT” + ‘FN’ + “F10”). | ||
| 155 | |||
| 156 | Then find the appropriate error message and follow the suggested solutions to correct the problem. | ||
| 157 | |||
| 158 | |**Error message**|**Description**|**Problem identification**|**Proposed solution** | ||
| 159 | |"Error while downloading OSInstaller" | ||
| 160 | \\(network card driver missing)|For example, if you want to transfer an operating system to a new Client via a Rollout Templates, the error message "Error while downloading OSInstaller" may appear. This message indicates that a driver is missing from the Boot Images.|((( | ||
| 161 | Use the command line (SHIFT + F10) to call up the command "IPCONFIG /ALL" and check whether the network card has been assigned an IP address. | ||
| 162 | |||
| 163 | If this is not the case, the driver is missing. | ||
| 164 | )))|Download the manufacturer's network card driver and integrate it into the Boot Images. Recurrence the Rollout by starting it again. | ||
| 165 | |"Error while downloading OSInstaller" | ||
| 166 | \\(Naming scheme of the ACMP Server is not correct)|((( | ||
| 167 | An error occurred when downloading the OSInstaller. This may be due to the name not being stored correctly and therefore not working. | ||
| 168 | |||
| 169 | Once you have ensured that an IP address has been assigned to the Client, the next step is to check whether the ACMP Server can be reached via the network. The information is stored in the Settings.ini in the Boot Images. | ||
| 170 | )))|Open the command line ("SHIFT + F10") and enter the command "notepad X:\Settings.ini". This can be used to determine which server name is stored. The "Ping" command is then used to check whether the Client can be reached with the specified name. If this is not the case, you can try the ping again with the FQDN and the IP address. | ||
| 171 | \\Computer name:((( | ||
| 172 | [[image:63_OS Deployment_Network Boot Image_Computername_379.png||data-xwiki-image-style-alignment="center"]] | ||
| 173 | |||
| 174 | IP-Adress: | ||
| 175 | |||
| 176 | [[image:63_OS Deployment_Network Boot Image_CIP Adresse_381.png||data-xwiki-image-style-alignment="center"]] | ||
| 177 | |||
| 178 | FQDN: | ||
| 179 | |||
| 180 | [[image:63_OS Deployment_Network Boot Image_FQDN_379.png||data-xwiki-image-style-alignment="center"]] | ||
| 181 | )))|((( | ||
| 182 | To enable the client to reach the ACMP server, the Settings.ini must be adjusted so that the server can be reached via the IP address or the FQDN. | ||
| 183 | The Settings.ini is located in the "<ACMPServer>\Clients" directory and under "\OsdRepo\OSD\{41646469-7469-6F6E-616C-46696C657300}\AdditionalFiles\$1\Acm pAgentInstall". | ||
| 184 | |||
| 185 | The Settings.ini is copied into a boot image when it is created in the ACMP Console. | ||
| 186 | ))) | ||
| 187 | |"Error while downloading OSInstaller" | ||
| 188 | \\(Incorrect time stamp (date/time) in the BIOS)|((( | ||
| 189 | An error occurred when downloading the OS installer. This may be due to an incorrect date or time being stored in the BIOS. | ||
| 190 | |||
| 191 | Similar to the previous source of error, it is possible that the client has been assigned an IP address and can also reach the name stored in Settings.ini, but an incorrect date and/or time is set in the BIOS. If there is a difference between the server and client, the server certificate is not recognised as valid and the client cannot establish a connection. | ||
| 192 | )))|Open the BIOS of the client and check whether the current time stamp, which is also displayed in the boot image, matches. | ||
| 193 | |Adjust the date and time so that the certificate check can work correctly. | ||
| 194 | |"PXE Boot - Request does not arrive at the Network Boot Service"{{aagon.infobox}}The error mentioned here is system-wide and refers to the fact that a rollout template was assigned to the client via the MAC address, but the computer does not boot via the network. The client's PXE boot request times out and the normal boot process continues.{{/aagon.infobox}}|((( | ||
| 195 | The request sent by the booting client does not reach the Network Boot Service. | ||
| 196 | |||
| 197 | This may be the case, for example, if you want to roll out to a new subnet in your company and the client cannot send the PXE broadcast to the ACMP Network Boot Server via a router. | ||
| 198 | )))|There may be several reasons why the request does not arrive. | ||
| 199 | Either the request from the booting client does not reach the Network Boot Service or the response from the Network Boot Service is not sent to the booting client. | ||
| 200 | Use the "Wireshark" application to retrieve all connections and requests. This allows you to check where exactly the request is not arriving: | ||
| 201 | If you start a Wireshark on the computer on which the Network Boot Service is installed, you can check whether the request arrives there and whether it sends a response. | ||
| 202 | If a Wireshark is started in the network segment of the booting client, you can see whether the DHCPOFFER of the Network Boot Service arrives there.|To ensure that the request arrives, you can either configure an IP helper on the switches or install an additional network boot service in the respective subnet. | ||
| 203 | |“Interactive Rollout Selector” is displayed on the client|After PXE boot, the client displays the “Interactive Rollout Selector” or does not start an assigned rollout, even though a rollout is stored in ACMP. | ||
| 204 | This often occurs when the client is connected via a docking station or USB network adapter and MAC address pass-through is enabled. | ||
| 205 | Depending on the BIOS settings, the client may use a different MAC address during PXE boot than in the running boot image, resulting in an incorrect rollout assignment.|Check in the ACMP Console whether a rollout is stored for the displayed MAC address of the client. | ||
| 206 | Use the command line (SHIFT + F10) to enter | ||
| 207 | ipconfig /all | ||
| 208 | to determine which MAC address is currently being used. | ||
| 209 | Compare this with the MAC address displayed during PXE boot. | ||
| 210 | Check in the client's BIOS/UEFI whether MAC address pass-through is enabled.|((( | ||
| 211 | Depending on the cause, the following variants are possible: | ||
| 212 | |||
| 213 | 1. PXE boot with client MAC, boot image uses adapter MAC: The client receives the boot image correctly, but then switches to the MAC of the adapter, for which no rollout exists. Assign the same rollout to this MAC address or disable MAC pass-through in the BIOS. | ||
| 214 | 1. PXE boot with adapter MAC, rollout only available for client MAC: The boot image cannot be loaded because the PXE server does not recognize a rollout for this MAC. Assign rollout for adapter MAC as well or disable MAC pass-through. | ||
| 215 | 1. Swapped or changing address usage: If client and adapter MAC alternate, the ACMP server cannot clearly assign the rollout job. Either assign the same job to both addresses or disable MAC pass-through. | ||
| 216 | ))) | ||
| 217 | |"PXE-E55“ – „Proxy DHCP service did not reply to request on port 4011“|The proxy service is not responding to the request for port 4011.|Check whether options are set on the DHCP server that are related to ACMP. |((( | ||
| 218 | The Network Boot Service does not support DHCP options, which is why you must either configure an IP helper on the switches or install another Network Boot Service in the respective subnet. | ||
| 219 | ))) | ||
| 220 | |"PXE-E53“ – „No Boot Filename Received"|((( | ||
| 221 | No boot file name was recipients. | ||
| 222 | )))|Check whether the Network Boot Service is installed on a domain controller or another Server with DHCP service.|The Network Boot Service (NBS) is a DHCP proxy that works on port 67. If you have installed the NBS on a host with an active DHCP service, the following configurations must be set in the DHCP service on the host or the NBS must be installed on another device. | ||
| 223 | Configure the DHCP range with Options 60 and 66. | ||
| 224 | Option 60 is not displayed in the DHCP GUI by default and must be enabled via CMD. | ||
| 225 | Option 66 can be set by you in the DHCP GUI. The problem occurs when both options are set and the DHCP must be forwarded to the port. | ||
| 226 | The required commands are | ||
| 227 | \\netsh | ||
| 228 | dhcp server | ||
| 229 | add optiondef 60 PXEClient STRING 0 comment="Option added for PXE support" | ||
| 230 | set optionvalue 60 STRING PXEClient | ||
| 231 | set optionvalue 66 STRING (Hostname DHCP Server) | ||
| 232 | exit | ||
| 233 | \\If option 66 has not yet been set via the GUI, insert the host name of the DHCP Server in the row.{{aagon.infobox}}The Network Boot Service should be configured to "delayed automatic start" so that the service always starts after the DHCP service in future. This is necessary for the port to bind.{{/aagon.infobox}} | ||
| 234 | |Windows Setup Failed | ||
| 235 | (Hard drives are not recognised) |An error occurred during Windows setup.|Use the command line ("SHIFT + F10") to call up the "Diskpart" and "List Disk" commands. You can use these two commands to check whether the disk is recognised.|If no disk is recognised, you must integrate a hard drives controller driver into the Boot Images. This is often SCSI. With Dell devices, the error can also be rectified if the settings for RAID ON are set in the BIOS. | ||
| 236 | |Windows Setup Failed | ||
| 237 | (No correct partitions) |The Windows setup has failed although a disk has been recognised. This may be because the settings in the response file do not match.|((( | ||
| 238 | Open the command line ("SHIFT + F10"). If a hard drive has been recognised, you can enter the commands "set disk 0""list part" to display the partitioning of hard drive 0. | ||
| 239 | |||
| 240 | This allows you to check whether this corresponds to the settings in the response file. | ||
| 241 | )))|If the settings do not correspond to the response file or the Client's prior configuration is identical to the new setting, it may not be possible to recognise whether the partitioning has been applied correctly.enter the "clean" command after entering "sel disk 0", which will cleanup the partition and allow the Rollout to be tested again. Alternatively, you can change the response file to a DiskPart script execution in the tab //[[Partitioning>>https://learn.microsoft.com/de-de/windows-hardware/manufacture/desktop/oem-deployment-of-windows-desktop-editions-sample-scripts?preserve-view=true&view=windows-10]]// | ||
| 242 | |||
| 243 | = Updating the Network Boot Service = | ||
| 244 | |||
| 245 | After installation of an ACMP Updates, it may be necessary to update the Network Boot Service. | ||
| 246 | |||
| 247 | {{aagon.infobox}} | ||
| 248 | Refer to the [[ACMP Release Notes>>https://www.aagon.com/produkte/ueberblick/release-notes-acmp/]] to find out whether and which additional components you need to update. | ||
| 249 | {{/aagon.infobox}} | ||
| 250 | |||
| 251 | If a new version of the Network Boot Service is available in the ACMP Updates, you can update your existing installation as follows: | ||
| 252 | |||
| 253 | 1. Navigate to the installation file on the ACMP share in the NetworkBoot directory. | ||
| 254 | 1. Executions the file //ACMP Network Boot Service.msi//. | ||
| 255 | 1. After the update, check the status of the Network Boot Service by navigating to //System > Settings > OS Deployment > Network Boot Service// in the ACMP Console. If the configuration has been completed correctly and the Network Boot Service is active, it will be displayed with a green tick. |