Recommended Posts

Downloaded tonite the appliance. Applied synobootfix. 

Running on ESXi 6.7 U3, Gigabyte Aorus M, 16 GB Kingston Predator, AMD 2600X, Custom ESX Installer Image to enable onboard Network Adapter, gforce 1030 (without passthrough) and (at the moment) only one nvme Kingston 256 GB in Fractal Design Node 804


Just wanted to leave a big "thank you man" here @armazohairge. Saved me quiet some time. I did the same "dry" with a local vmware a few weeks ago. Actually I wanted to purchase some Intel CPU but ended up with the physical AMD structure as mentioned above. 


Up until now everything was quiet charming. ok the Synology ID Login thing, but that has nothing to do your appliance but the general approach which is understandable and fine for me.


At one or two boots internet (pakets) seemed not to be available, but fine now. thx again man.

Link to post
Share on other sites
On 11/17/2020 at 6:47 PM, XPEuser2 said:



Perhaps I have misunderstood


The file here -->


Is this appliance ready for ESXi 7 or is this only ready for VMware Workstation? I am using ESXi 7 and would like very much to get this to work.  I left everything as default, and after it boots to the loading screen where it says "welcome to Jun's Mod, please go to"  I can't find it on any LAN no matter what adapter I connect to it, and yields nothing.   Any help would be greatly appreciated!



EXSI 7.0 Update: Working


Hi everyone,  For everyone who would like to the pre-made ova appliance file in ESXi 7.0 this is how I got it to work: 


1. Create / Register New Virtual Machine

2. Choose "Deploy a Virtual Machine from an OVF or OVA file"

3. Upload the file from the Mega.NZ link in the above quoted post

4. leave everything as default and at this point it should boot up and run.

5. you won't be able to access it on the network and the won't work (in my tests this was true)

6. turn off the vm from the web based Esxi interface. 

7.  Edit the settings of the vm and go to network adapters. 

8. Change the adapter type to E1000e, and set the mac address to manual, and change it to 00:11:32:2C:A7:85

9. Boot up the Vm guest and go to


Lastly as a side note: your CPU and processor/threads won't show up properly in the control panel/info, but the image will be using the correct number of cores/threads from the correct processor. You can verify this by logging into your Vm with SSH and issuing the command "cat proc/cpuinfo'" (don't use quotes)

These steps worked for me. Best of luck to everyone else, I hope this helps. 

Edited by XPEuser2
Link to post
Share on other sites
  • 2 weeks later...
On 12/9/2020 at 3:14 PM, Chuck12 said:

Just wanted to let those interested v6.2.3-25426-Update 3 works fine on this VM. The update was applied to the original upload (synobootfix applied) and not the updated appliance.

thanks for sharing this!! after the synofix boot i too was able to upgrade to v6.2.3-25426-Update 3

Edited by niekniek89
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.