Licensing on dual boot

[alFrame]

Hi there,

Firstly, thank you for creating this software! I am a 25 year AllwaySync client and was happy, even after they switched to SaaS. But now I am moving to Linux. Gradually, that's why my question came up.

And sorry if this has been asked. Tried to search the forum, but was either blind, or unable to find an answer. AI also told me two different things...

I read in the licensing, that I will need a business license, since I do make money as a freelance running my onw business and that the license is per device.

Since I am switching to LINUX, I wonder if I need two licenses, if I run in dual boot on the same hardware? At least for now. I hope to replace Windows in the longer run for good.

Thanks & Cheers,
Alex

[alFrame]

Hate to do this, but ...bump...

Thanks for considering to answer this.

[alFrame]

So, I finally got my answer. Why no-one would answer this here is beyond me tbh...

I finally got around installing it on Linux on the same hardware and now I get a dialog where I can:
1. Activate via internet now: (doesn't work)
2. Retrieve an offline activation key (URL)

But it seems that one device means one OS, not one device...

I am sorry, but THAT's exactly why I asked here weeks ago, but one device to me is one device, not OS dependent.

Any chance this can be remedied and run the same license on one device with dual boot?? Or do I need to purchase a second license?

Don't get me wrong, I have nothing against buying a second license. But, it would be nice if this was clearly stated in the licensing terms, or if I would get an answer on this here...

[Zenju]

Yes a second license is required. But that's mostly due to a technicality, because it's not easily possible to identify the "same device" from different operating system.

[alFrame]

Hi Zenju, thanks for your answer.

Don't get me wrong, still not against buying a second license, I actually just did.

But I have to push back a tad on "not easily possible to identify the same device from different operating systems".

The motherboard/system UUID sits in the firmware (SMBIOS), not in either OS. So reading it doesn't depend on Windows or Linux at all.

Same physical machine, same UUID, either way:
Windows: wmic csproduct get uuid
Linux: cat /sys/class/dmi/id/product_uuid

It would be great if this made it into the roadmap, unless there's a good reason it hasn't, but either way, "device" should probably say "OS install" in the license terms, because right now it reads like "physical machine," and that's how most people will understand it.

Cheers,
Alex

[homiline]

See this thread: viewtopic.php?t=12778

Basically, what is missing is an additional licensing model for business customers: a per-user Business license.

The existing per-device license could remain unchanged, while a per-user option would provide more flexibility for users working with multiple devices or operating systems — even at a higher price.

[jujo_am]

Same physical machine, same UUID, either way:
Windows: wmic csproduct get uuid
Linux: cat /sys/class/dmi/id/product_uuid

(in home use context, well maybe both)
On virtual systems BIOS passthrough should keep this easy and static(hypervisors make this programmable field). But then there is the possibility of cheap exotic motherboards that may have whatever on this field and detection code should be very robust. However it is planned to work, it is easiest for us when it's said out loud.

Dual boot is very important feature that many of us use, as well are virtual machines.

Some of us may decide not to install it, if the situation is unclear, since in practice all licensing is a trust-based system anyway, where payment is voluntary gatekeeping / voluntary supporting.


Maybe if there is number of license changes that would make it harder to scale but would stop foul play and would allow fast switch few times per month / week.