I Also would like feature added. This is essential in the education environment.

@daodio2

Does the host server need to be on a domain to use LDAP

@sesam
You may have to create A new image, but this doesn't need to be a norm going forwards.

If you create a Universal Image then you can start collecting driver packages and use that one image for every machine using that OS version/edition (windows 10 pro, windows 10 home, windows 11 pro, etc), at least for Windows.

to summarize the video:

Make a VM in Hyper-V (I can't speak to other hypervisors)

Install the OS on it, using the latest installation media (w10-22h2, w11-23h2)

Do all the updates
3.1 do some shinanigans
3.2 probably you should install TOEC

Sysprep & generalize it

Take the image

Deploy the image to one machine of a given model

Install all the drivers for it

Collect the drivers using

powershell> Export-WindowsDriver -online -destination <URI>

Put the drivers in a zip file and upload them via the Theopenem web interface as a Filecopy Module configured to unzip and install them as drivers

On the image, clone the default profile, name it appropriately, and configure it to use that file copy

Now when you deploy this profile to machines you have a driver package set up for, they can all use the same base image. I have skimmed over a lot of details, the video tutorial linked at the top covers them. There are a lot of caveats like you may need an answer file, and the image will not retain preconfigured network profiles.

TOEC seems great, my usecase is really annoying so it creates a lot of problems that I don't have time to solve right now, and TOEC is not strictly required for this workflow.

Next Tuesday is Update Tuesday so either doing this now is a little extra work you don't have time for, or a great test run, because next week you'll be able to re-update that VM (remember to checkpoint before you sysprep) and update the image for every model in one go.

You need to use a script module:
https://docs.theopenem.com/ui/modules/script/script.html

@cycy

it seems that double-commander msi installer simply unpacks it's files in to C:\Program Files\Double Commander\
I does not create shortcuts or registry entries. I doesn't show in the "installed apps" or "Programs and features" section of control panel.
That's why i was lost.

thank you very much for your assistance.

@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"

View documentation:
https://docs.theopenem.com/endpointmanagement/first-policy.html

Thanks for your answer,

First couldn't see detailed information about the script actions / errors in any of these logs.
So I asked where exactly should the standard output / errors be logged to find it.

I know all of these four log files of course, but couldn't see and find where the detailed information about the script operations / outputs were logged exactly.

Now I just wanted to do another clear test and finally saw this line, where those two infos are indeed logged:

2023-11-18 01:52:50,404 INFO [29] ModuleScriptManager - {"ExitCode":1,"StandardError":"Ungltige Option - "y".\r\n\r\n","StandardOut":"\r\nC:\Program Files\Toec\AppData\094fc44f-8836-4f8c-819e-98c07afee93e>echo This should be any output. \r\nThis should be any output.\r\n\r\nC:\Program Files\Toec\AppData\094fc44f-8836-4f8c-819e-98c07afee93e>del C:\nopath\nofile.txt /y \r\n\r\n"}

Is this information also checkable directly in the webUI somewhere? So I mean the content of StandardError and StandardOut without the need to dig through the toec client log?

Figured out the problem. When building the WIE I had put the Universal Imagining Token. I remade the WIE and left the Universal Token blank and now it prompts for a users username and password.

@matiit
https://docs.theopenem.com/imaging/toec-image-prep.html
Example Sysprep Answerfile: https://docs.theopenem.com/imaging/toec-image-prep.html#sysprep-tab