Were the trial key restrictions and limitations recently modified?

 

I run a mirrored UnRaid boot USB in an attempt for closer to near instant fail-over in the event of a USB drive loss. It seems however you can no longer have an existing config present on the USB to request a trial key? Is the key verification performing some sort of date or timestamp verification now as you can request a trial on a fresh USB but cannot if the contents of config predate the request date? Reason for the trial is to prevent burning my 1x yearly automated key migration on a spare USB key. 

Pretty sure that the config restriction has been in place for quite a while now.

 

AFAIK it has always been like that.

To further the research it appears you cannot use a fresh USB, apply a trial and then back apply the previous config either? Is it simply checking super.dat / config modification date or a field within?

Just now, DiscoverIt said:

apply a trial and then back apply the previous config either?

Correct, trials are for fresh installs only, you can reassign the devices as they were.

5 minutes ago, JorgeB said:

Correct, trials are for fresh installs only, you can reassign the devices as they were.

 

Bummer, just adds even downtime. Is there any basis for continuing the 1x yearly migration when its handled via the new web portal now?

1 hour ago, DiscoverIt said:

Is there any basis for continuing the 1x yearly migration when its handled via the new web portal now?

Not sure I follow, do you mean you replace a flash drive every year?

On 11/27/2024 at 11:36 AM, JorgeB said:

Not sure I follow, do you mean you replace a flash drive every year?

IIRC a user can only migrate their key once yearly via the web portal. Was curious if the change in activation backend would allow additional changes per year.

15 minutes ago, DiscoverIt said:

Was curious if the change in activation backend

What change?

The new way keys are handled via Connect?

You don't need Connect, just an Unriad.net account.