We had issues with network drivers for Dell Precision 3460. Followed the steps in old Clonedeploy docs and created a new Kernel (6.6.7). Sharing if you need it or create your own.
https://www.cyberciti.biz/tips/compiling-linux-kernel-26.html
http://clonedeploy.org/docs/custom-linux-kernel/
You can copy the kernel to C:\Program Files\Theopenem\tftpboot\kernels and use it to create the ISO.
Remember to turn off Secure Boot Support when you create ISO to avoid issues.
@theopenem_admin Apologies for not being clear. I wasn't aware of the feature where we can image without touching the computer. What is that option called?
Because of the IT security restrictions we cannot enable PXE boot in our classrooms. Currently we boot these devices from USB and image them. It takes a lot of time and effort for this repetitive process.
Thank you for looking into this.
Just an idea! Not sure if this could be done.
Is it possible to image automatically without using a USB or PXE?
For example select a group (for example a lab) and push a new image to them. It can avoid manual work of going to individual devices to boot from a USB to re-image.
https://learn.microsoft.com/en-us/answers/questions/563319/setup-bcd-to-boot-pe-from-ram.html
@theopenem_admin We are experiencing slow imaging when we tried wim file format imaging. It took 60 minutes to complete imaging.
Then, we attempted to mount the SMB and tried copying, which was much faster (approximately 4 minutes).
We also tried changing to FFU, and the imaging process sped up significantly (approximately 4 minutes).
What could be wrong with the WIM format imaging? Are there any logs I can check to troubleshoot?
We had issues with network drivers for Dell Precision 3460. Followed the steps in old Clonedeploy docs and created a new Kernel (6.6.7). Sharing if you need it or create your own.
https://www.cyberciti.biz/tips/compiling-linux-kernel-26.html
http://clonedeploy.org/docs/custom-linux-kernel/
You can copy the kernel to C:\Program Files\Theopenem\tftpboot\kernels and use it to create the ISO.
Remember to turn off Secure Boot Support when you create ISO to avoid issues.
Getting this error when tried to switch from SMB imaging to http. Please advise.
[ERROR] The WIM being read from file descriptor 0 is not pipable!
ERROR: Exiting with error code 44:
The WIM was not captured such that it can be applied from a pipe.
Updated Boot Order
The boot configuration data store could not be opened.
The system cannot find the file specified.
** Closing Active Task **
@eruthon Checked multicast functionality after disabling SMB, and set a queue size of 2. However, imaging started without waiting for the second PC and failed, as indicated in the screenshot below.
11-21-23 12:24 Starting Multicast Session With The Following Command:
cmd.exe /c ""C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part2.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log & "C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part3.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log & "C:\Program Files\Theopenem\Toec-API\\private\apps\udp-sender.exe" --file "D:\toems_local_storage\images\dev_01_MyApps_Win11_CP941\hd0\part4.winpe.wim" --portbase 9028 --min-receivers 2 --ttl 32 --interface 10.38.40.113 --mcast-rdv-address 224.0.0.1 --log D:\multicast.log"
@eruthon does that mean, to make multicast working, we have to configure SMB to "Non-direct" mode? In our current setup, we followed these steps and have a SMB share on the D drive.
@eruthon Thank you very much for your reply. Sorry for my ignorance. if we disable SMB, what other transmission protocol can we use? HTTP? Also, after enable multicast in the server side. how those client workstations know which multicast address to join?
@theopenem_admin could you please help with multicasting. I've checked other posts, and there are various combinations of things to try. Do I need to specify any arguments for multicasting? When I attempted multicasting, it became stuck. Normal imaging via SMB is functioning correctly. Any additional documentation you can provide would be greatly appreciated.
What are the optimal server specifications needed to handle 3000 clients on a Hyper-V Windows Server 2022? Specifically, how much RAM and CPU are necessary? Additionally, if there are multiple locations, is it advisable to set up several COM servers or maintain separate stand-alone servers for each location? If the choice is multiple COM servers, how can you ensure that clients connect only to the COM server specific to their location for imaging? We use the server only for imaging.
@theopenem_admin my bad! I made a mistake in the IP. Modified it the correct ip now. Do I need to do anything on the server side for it to take effect?