Changes for page Network Boot Service

Last modified by Sabrina V. on 2026/10/07 08:17

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Children
- Content

From version 1.1

edited by Steffi F
on 2025/11/07 07:15

Change comment: There is no comment for this version

To version 6.1

edited by Sabrina V.
on 2026/10/07 08:17

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.SF
++XWiki.SV

Content

@@ -5,11 +5,11 @@
  The Network Boot Service is the central point responsible for the network boot of client computers.
  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.
--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.
++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.
  (% style="text-align:center" %)
--[[image:XWiki.Images.WebHome@hmfile_hash_f12bc69d.png||alt="14.1 - Server eintragen" height="311" width="399"]]
++[[image:XWiki.Images.WebHome@hmfile_hash_f12bc69d.png||alt="14.1 - Server eintragen" data-cmp-info="10" height="311" width="399"]]
  Enter server name and server port
  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,7 +16,7 @@
  = Configuration of the Network Boot Service =
--Navigate to the configuration in the ACMP Console to //System > Settings > OS Deployment > Network Boot Service//.
++Navigate to the configuration in the acmp Console to //System > Settings > OS Deployment > Network Boot Service//.
  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:
  * Only import Network Boot requests
@@ -41,7 +41,7 @@
  {{/aagon.infobox}}
  (% style="text-align:center" %)
--[[image:XWiki.Images.WebHome@hmfile_hash_d5ec0f48.png||alt="14.2 - Bindungen bearbeiten" height="384" width="512"]]
++[[image:XWiki.Images.WebHome@hmfile_hash_d5ec0f48.png||alt="14.2 - Bindungen bearbeiten" data-cmp-info="10" height="384" width="512"]]
  Bindungen des Network Boot Services bearbeiten
  All network cards of the Client are displayed. Enable the checkbox only for the IP address that is to use the Network Boot Service.
@@ -52,7 +52,7 @@
  Please note that this option may affect Thin Clients and IP phones, depending on the configuration.
  {{/aagon.infobox}}
--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.
++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.
  = Firewall settings =
@@ -63,13 +63,13 @@
  == Inbound Rule ==
  |(% style="width:150px" %)**Field**|(% style="width:1213px" %)**Indication**
--|(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service Proxy DHCP (UDP)
--|(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service
++|(% style="width:150px" %)Name|(% style="width:1213px" %)acmp Network Boot Service Proxy DHCP (UDP)
++|(% style="width:150px" %)Group|(% style="width:1213px" %)acmp Network Boot Service
  |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP
  |(% style="width:150px" %)Local Port|(% style="width:1213px" %)67,4011
  |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any
--|(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service TFTP Server (UDP)
--|(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service
++|(% style="width:150px" %)Name|(% style="width:1213px" %)acmp Network Boot Service TFTP Server (UDP)
++|(% style="width:150px" %)Group|(% style="width:1213px" %)acmp Network Boot Service
  |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP
  |(% style="width:150px" %)Local Port|(% style="width:1213px" %)69
  |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any
@@ -77,18 +77,18 @@
  == Outbound Rule ==
  |(% style="width:150px" %)**Field**|(% style="width:1213px" %)**Indication**
--|(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service (TCP)
--|(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service
++|(% style="width:150px" %)Name|(% style="width:1213px" %)acmp Network Boot Service (TCP)
++|(% style="width:150px" %)Group|(% style="width:1213px" %)acmp Network Boot Service
  |(% style="width:150px" %)Protocol|(% style="width:1213px" %)TCP
  |(% style="width:150px" %)Local Port|(% style="width:1213px" %)Any
  |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)2106 (You specified this port during the installation of the Server)
--|(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service Proxy DHCP (UDP)
--|(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service
++|(% style="width:150px" %)Name|(% style="width:1213px" %)acmp Network Boot Service Proxy DHCP (UDP)
++|(% style="width:150px" %)Group|(% style="width:1213px" %)acmp Network Boot Service
  |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP
  |(% style="width:150px" %)Local Port|(% style="width:1213px" %)67,4011
  |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any
--|(% style="width:150px" %)Name|(% style="width:1213px" %)ACMP Network Boot Service TFTP Server (UDP
--|(% style="width:150px" %)Group|(% style="width:1213px" %)ACMP Network Boot Service
++|(% style="width:150px" %)Name|(% style="width:1213px" %)acmp Network Boot Service TFTP Server (UDP
++|(% style="width:150px" %)Group|(% style="width:1213px" %)acmp Network Boot Service
  |(% style="width:150px" %)Protocol|(% style="width:1213px" %)UDP
  |(% style="width:150px" %)Local Port|(% style="width:1213px" %)69
  |(% style="width:150px" %)Remote Port|(% style="width:1213px" %)Any
@@ -105,7 +105,7 @@
  Please note that no option 66 or 67 must be set on the DHCP Server.
  {{/aagon.infobox}}
--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.
++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.
  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.
@@ -135,13 +135,13 @@
  == Operation at another location ==
--To be able to operate the NBS at a different location, you must first create a deployed file repository ([[Verteiltes File Reposititory>>doc:ACMP.68.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]) You install an NBS at this location.
++To be able to operate the NBS at a different location, you must first create a ([[deployed file repository>>doc:ACMP.610.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]) You install an NBS at this location.
  The NBS of the location is configured to the deployed file repository. This saves your bandwidth and requests are edited more quickly.
  = Error messages during Rollout via the Network Boot Service =
--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.
++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.
  General possible reasons:
@@ -163,26 +163,26 @@
  If this is not the case, the driver is missing.
  )))|Download the manufacturer's network card driver and integrate it into the Boot Images. Recurrence the Rollout by starting it again.
  |"Error while downloading OSInstaller"
--\\(Naming scheme of the ACMP Server is not correct)|(((
++\\(Naming scheme of the acmp Server is not correct)|(((
  An error occurred when downloading the OSInstaller. This may be due to the name not being stored correctly and therefore not working.
--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.
++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.
  )))|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.
  \\Computer name:(((
--[[image:63_OS Deployment_Network Boot Image_Computername_379.png||data-xwiki-image-style-alignment="center"]]
++[[image:63_OS Deployment_Network Boot Image_Computername_379.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  IP-Adress:
--[[image:63_OS Deployment_Network Boot Image_CIP Adresse_381.png||data-xwiki-image-style-alignment="center"]]
++[[image:63_OS Deployment_Network Boot Image_CIP Adresse_381.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  FQDN:
--[[image:63_OS Deployment_Network Boot Image_FQDN_379.png||data-xwiki-image-style-alignment="center"]]
++[[image:63_OS Deployment_Network Boot Image_FQDN_379.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  )))|(((
--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.
++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.
  The Settings.ini is located in the "<ACMPServer>\Clients" directory and under "\OsdRepo\OSD\{41646469-7469-6F6E-616C-46696C657300}\AdditionalFiles\$1\Acm pAgentInstall".
--The Settings.ini is copied into a boot image when it is created in the ACMP Console.
++The Settings.ini is copied into a boot image when it is created in the acmp Console.
  )))
  |"Error while downloading OSInstaller"
  \\(Incorrect time stamp (date/time) in the BIOS)|(((
@@ -194,15 +194,15 @@
  |"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}}|(((
  The request sent by the booting client does not reach the Network Boot Service.
--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.
++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.
  )))|There may be several reasons why the request does not arrive.
  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.
  Use the "Wireshark" application to retrieve all connections and requests. This allows you to check where exactly the request is not arriving:
  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.
  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.
--|“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.
++|“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.
  This often occurs when the client is connected via a docking station or USB network adapter and MAC address pass-through is enabled.
--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.
++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.
  Use the command line (SHIFT + F10) to enter
  ipconfig /all
  to determine which MAC address is currently being used.
@@ -212,9 +212,9 @@
 . 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.
 . 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.
--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.
++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.
  )))
--|"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.  |(((
++|"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.  |(((
  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.
  )))
  |"PXE-E53“ – „No Boot Filename Received"|(((
@@ -242,14 +242,14 @@
  = Updating the Network Boot Service =
--After installation of an ACMP Updates, it may be necessary to update the Network Boot Service.
++After installation of an acmp Updates, it may be necessary to update the Network Boot Service.
  {{aagon.infobox}}
--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.
++Refer to the [[acmp release notes>>https://www.aagon.com/produkte/ueberblick/ueberblick-ueber-die-release-notes-von-acmp/]] to find out whether and which additional components you need to update.
  {{/aagon.infobox}}
--If a new version of the Network Boot Service is available in the ACMP Updates, you can update your existing installation as follows:
++If a new version of the Network Boot Service is available in the acmp Updates, you can update your existing installation as follows:
--1. Navigate to the installation file on the ACMP share in the NetworkBoot directory.
--1. Executions the file //ACMP Network Boot Service.msi//.
--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.
++1. Navigate to the installation file on the acmp share in the NetworkBoot directory.
++1. Executions the file //acmp Network Boot Service.msi//.
++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.