The problem is solved.
As reported, updates were carried out on the deploy notebook and the BIOS was also updated. After the BIOS on the other notebooks has also been updated, it works again.
Question: After each image download, a new Windows bootloader seems to be set up (Pic. 1 = Deploy notebook; Pic. 2 = after Image download) The current version 1.3.3 of Theopenem is installed.
How do you proceed if the image is only to be updated?
Pic 1
Pic 2
@theopenem_admin Version 1.3.3. In the meantime I have completely deleted the old image and created and uploaded a new image. Unfortunately the same effect.
The first image could be successfully downloaded to 20 notebooks and everything ran very stable even in connection with Reboot RX.
Today the image was updated (Windows updates, software installations). After the download, the clients no longer work. Here is the result in the video (30 sec)
https://photos.app.goo.gl/HyEDWC4wMACkfX9B6
The devices start and then hang in a loop. Where could be the problem. The upload log is attached.
@theopenem_admin Great. Is there a donation box somewhere where we can deposit something?
@theopenem_admin Perfect!
Is there a way to tell the devices to shut down after the image download.
@theopenem_admin Thanks for the fast respond. Currently only 5 devices can download the image at the same time. Can this limit be controlled?
@sesamAs already mentioned, the image is very large and covers the entire size of the hard disk. Could this be related to the installed rollback solution "Remote RX". Here is the upload log file.
@theopenem_admin Thanks for the new release. In the meantime, we were able to successfully download the image of 20 Dell Latitude 3150s via PXE.
It was noticed here that the image is very large (240 GB). However, this jump did not show up until a rollback software was installed: Reboot RX. Could it be related? Tomorrow I will upload the upload log file here.
@theopenem_admin The accumulation of boot loaders is inexplicable. We therefore set up a brand new notebook: After deleting all partitions, installed Win10. Uploaded the image and successfully installed it on a new client. An update of the image that had already been carried out also worked without any problems and could be distributed. The upload log is attached.
Thank you for your support. In the next step, we test the distribution of the images via PXE.
@sesam Sorry, that was the old upload log. Here is a new upload log without Ubuntu with the same Error.