Your approach is correct. Only open up port 8888 to allow the endpoints to communicate, keeping the ui and api locked down to just the internal network.

Have you watched this video?
https://www.youtube.com/watch?v=Ubgeck7hVP8

Can you attach the logs found in c:\program files\Theopenem\Toems-UI\private\logs and c:\program files\Theopenem\Toems-API\private\logs

Just create the image on the new server from the ui with the same name. Then copy the image from your local storage path images folder to the new server local storage path images folder.

The permanent deploy feature was removed. I tried to scale back on features that only most people were using. However, the model match feature may work for you if you are using the same image based on models. I mean if a single model always gets the same image, it could work for you.

Sure, your other option is to set the partition type to standard in the image profile, which should save you from needing to recreate the image. It will create a standard partition table for you. You just need to select the correct windows partition when asked.

Your issue is that Extended partitions are being used, which is very strange. Did you create this partition layout or did it come that way from the factory? Theopenem doesn't really support extended partitions. The working one works because the hard drive is the exact same size as the original, the other one requires that partition table to be dynamically created. If you need more than 4 partitions, an EFI layout would be the way to go.

Newer machines are having trouble booting the older version of grub. When you generate your usb, disable the option for secure boot support. This will create the usb with a newer version of grub. Obviously you will then need to disable secure boot on your machine.

It looks like the multiple efi loaders still isn't quite resolved. I'll look at this again.

The multicast permission is the only permission you need. It shouldn't be blank. If you don't have access it should display a message. Can you attach screenshot?

@sesam
What version are you using

After you copy the the iso to your usb drive, just modify EFI\boot\grub.cfg and change set timeout to 0 and set default to 1

It isn't a model issue. It's an efi / legacy issue. Your original image was legacy so when it's deployed, Theopenem configures the machine for legacy to match the original. But since it's an efi machine that's not going to work. Setting the partition method to standard tells Theopenem to ignore the original image and match the destination machine type. That's how a single image can be used for both efi / legacy, using the standard partition type.