Changes for page Network Boot Service

Last modified by Steffi F on 2025/04/24 08:23
From version 6.1
edited by Sabrina V.
on 2024/10/11 07:53
Change comment: There is no comment for this version
To version 10.1
edited by Sabrina V.
on 2024/10/23 06:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -140,7 +140,7 @@
140 140  
141 141  == Operation at another location ==
142 142  
143 -To be able to operate the NBS at a different location, you must first create a deployed file repository ([[Verteiltes File Reposititory>>doc:ACMP.65.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]) You install an NBS at this location.
143 +To be able to operate the NBS at a different location, you must first create a deployed file repository ([[Verteiltes File Reposititory>>doc:ACMP.67.ACMP-Solutions.System.Verteilte File Repositories.WebHome]]) You install an NBS at this location.
144 144  
145 145  The NBS of the location is configured to the deployed file repository. This saves your bandwidth and requests are edited more quickly.
146 146  
... ... @@ -166,18 +166,15 @@
166 166  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.
167 167  )))|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.
168 168  \\Computer name:(((
169 -(% style="text-align:center" %)
170 -[[image:63_OS Deployment_Network Boot Image_Computername_379.png]]
169 +[[image:63_OS Deployment_Network Boot Image_Computername_379.png||data-xwiki-image-style-alignment="center"]]
171 171  
172 172  IP-Adress:
173 173  
174 -(% style="text-align:center" %)
175 -[[image:63_OS Deployment_Network Boot Image_CIP Adresse_381.png]]
173 +[[image:63_OS Deployment_Network Boot Image_CIP Adresse_381.png||data-xwiki-image-style-alignment="center"]]
176 176  
177 177  FQDN:
178 178  
179 -(% style="text-align:center" %)
180 -[[image:63_OS Deployment_Network Boot Image_FQDN_379.png]]
177 +[[image:63_OS Deployment_Network Boot Image_FQDN_379.png||data-xwiki-image-style-alignment="center"]]
181 181  )))|(((
182 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 183  The Settings.ini is located in the "<ACMPServer>\Clients" directory and under "\OsdRepo\OSD\{41646469-7469-6F6E-616C-46696C657300}\AdditionalFiles\$1\Acm pAgentInstall".
... ... @@ -218,12 +218,12 @@
218 218  exit
219 219  \\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}}
220 220  |Windows Setup Failed
221 -(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.
218 +(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.
222 222  |Windows Setup Failed
223 -(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.|(((
220 +(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.|(((
224 224  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.
225 225  
226 -This allows you to check whether this corresponds to the settings in the response file.  
223 +This allows you to check whether this corresponds to the settings in the response file.   
227 227  )))|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]]//
228 228  
229 229  = Updating the Network Boot Service =
© Aagon GmbH 2025
Besuchen Sie unsere neue Aagon-Community