Thanks for your suggestion, I'm always up for community support. However, i'm not really marketing this as server management tool. The client isn't really compatible with Windows server. Don't let it stop you from making other suggestions though.
Honestly I really like this idea, I used to do this with TRK (Trinity Rescue Kit), make a master machine, then use TRK to make a temp PXE boot, make the fresh machine the master, then it cloned it's drive to the other in the mcast session. Worked pretty good until EFI cam around.
@theopenem_admin if something like this were implemented, id imagine it would be a matter of pointing to a file share or local drive on the server that contains the .inf file and drivers.
Thanks again for an awesome product you have built.
@theopenem_admin I think I've not found the documentation I need. Every time I turn around I find out there's more I can do. I just have to learn the language.
I can look into it for the next release, I prefer to keep the UI locked down to only specific ip's and just keep the toec-api open for endpoint communication. Even with 2FA I would be very hesitant to open up the UI. That's a lot of power if someone gets into it.
I think if you could manually add a station for cloning ,PC name, MAC, only in TheOpenEM in the GUI like in CloneDeploy that would be awesome. My use case is I image machines on 2 networks, Staff machines and Public used machines. I keep TheOpenEM on the same network at the public PCs since they are imaged more often (quarterly) the Toec client is great for these. The staff machines I only connect to that network when I am pushing the imaging. So possibly only once in that machines lifetime.