Synology Product Serial Number

1. Synology Login
2. Synology Assistant

If I already own a synology NAS or buy a cheap second hand one could I use its SN and MAC on my xpenology build to install a legitimately purchased license?Sure, you can, but first read license agrements. IMO, since license is given to a particual hardware, which is identified by pair of serial with mac, by using serial and mac on xpenology and using survillance licence you will violate license agrements. But it is just my opinion and you can ask synology support about that.Let say synology will find a way to identify that you have installed extra license on xpenology, and will revoke all extra licenses with no refund? What will you do? If I already own a synology NAS or buy a cheap second hand one could I use its SN and MAC on my xpenology build to install a legitimately purchased license?Sure, you can, but first read license agrements. IMO, since license is given to a particual hardware, which is identified by pair of serial with mac, by using serial and mac on xpenology and using survillance licence you will violate license agrements.

Synology Login

But it is just my opinion and you can ask synology support about that.Let say synology will find a way to identify that you have installed extra license on xpenology, and will revoke all extra licenses with no refund? What will you do?You're already violating ToS by using XPEnology, so. Thanks,I was under the impression that xpenology was leveraging open source software (or at least not completely proprietary) and not an infringement of Synology license.

Is that not so?That's why I was curious about the surveillance package as it is quite clearly an 'add-on' synology sell and should be compensated for.Yes, the Xpenology is really only the Linux kernel with some mechanisms in-place to combat the checks done by the Synology OS, extra drivers and it emulates the device that has serial number. But the real problem starts when you download the PAT file and use the proprietary parts of the Synology OS on the box that wasn't licensed for it. Technically, in some countries its illegal to bypath the mechanisms that prevent you from running on a non-licensed hardware, so the bootloader would also be illegal. Thanks,I was under the impression that xpenology was leveraging open source software (or at least not completely proprietary) and not an infringement of Synology license.

Synology Assistant

Is that not so?That's why I was curious about the surveillance package as it is quite clearly an 'add-on' synology sell and should be compensated for.Synology's DSM is Linux, with their own proprietary additions (funny thing, they do break GPL with their synobios kernel module!), including the app system, volume system, and the web UI.What we do is take this specifically licensed product (because this together is a product), break that license and ToS, and install it on our hardware. Then we circumvent the protection employed by Synology to make it work (and also we add some extra stuff (kernel drivers for support, mostly).So yes, we are infringing the license of DSM, because it says it can only be used on Synology hardware (hardware it is sold on). Coming back to the initial question with some answers and no solutionI have bought a licence for the 3-rd cam which worked well on DS112 box.The same licence worked also on baremetal Xpenology 6.02.Now I have gone over to ESXi based environment and the licence does not activate anymore, giving the 'connection failed' errorI have tried SN and MAC pair generated by the excel file available in the net.I have also tried the original MAC and SN from the DS112, with still the connection failed message at activation the licence.Might be that there are some detection mechanisms for non genuine HW.

I also tried to fall back to the oldest possible surveillance station with no success.My workaround: I am running separate Xpenology instance on ESXi for every pair of cameras. Not very convenient as they have separate timelines.Still looking for a more permanent solution, and I'm ready to buy more licences if I get it working.

Coming back to the initial question with some answers and no solutionI have bought a licence for the 3-rd cam which worked well on DS112 box.The same licence worked also on baremetal Xpenology 6.02.Now I have gone over to ESXi based environment and the licence does not activate anymore, giving the 'connection failed' errorI have tried SN and MAC pair generated by the excel file available in the net.I have also tried the original MAC and SN from the DS112, with still the connection failed message at activation the licence.Might be that there are some detection mechanisms for non genuine HW. I also tried to fall back to the oldest possible surveillance station with no success.My workaround: I am running separate Xpenology instance on ESXi for every pair of cameras. Not very convenient as they have separate timelines.Still looking for a more permanent solution, and I'm ready to buy more licences if I get it working.The reason it no longer works is because Synology have changed their T&C's around moving licences, even on genuine hardware.