If you still need it, the Mac Address is visible in the screenshot of the Syno Assistant: 00:11:32:12:34:56

Do not try to update your DSM in a Virtual Machine… It usually breaks the VM.

Thanks.

Have a look here if it helps : https://www.beatificabytes.be/customize-mac-serial-of-xpenology-images-to-run-synology-in-vmware/

I see .. thanks !

It seems I messed it up and always ended up having an img which I was not able to properly convert to an esxi usable vmdk although I was able to convert and use it but only in virtualbox.

Wow… no, no, I did not create the vmdk myself 😀
It comes from https://xpenology.club/downloads/
I mainly spent time on creating the dsm.ovf file which makes the instantiation in VMWare more straightforward.
I also did mount the synoboot.img partition 0 with osfmount x64 to fine tune the grub config (https://www.osforensics.com/tools/mount-disk-images.html)

Followed the steps and it also works on esxi 7.0 ! For those who what to ran it on esxi and allow dsm to manage the disks itself either use a dedicated SATA controller and passthrough the controller to esxi or use raw disk mapping as instructed here: https://kb.vmware.com/s/article/1017530 , the disavantage for the later is that it cannot use tHDD SMART function. The advantage for both is that you can plug out the disks from the esxi machine and throw them into a real synology nas and should work.

Before finding your explanations I tried to set it up from scratch, but I had troubles creating a working vmdk from the xpenology bldr image. Please could you tell me which tool you’ve used to create the vmdk ?