Unbinding Existing License Key From Old FQDN

[EliteIT]

Cut a long painful Christmas Eve story short - I've managed to get a client of mine up and running on V20 after their old on-premise 3CX v18 server died a death today.

It's currently on a 30 day trial license however the client does have an existing full license key available but it's linked to their old FQDN.

How do we go about releasing it from the old system please when it's no longer available - to add insult to injury there's a chance that the old license key maybe linked to their old support company 3CX account who they fell out with and thus no longer deal with.

However they are able to prove ownership of the license since they independently bought it through Webmate themselves.

Any help gratefully received.

Thanks

 

[SteveITS]

Can you just restore to the new trial server from backup? That will restore the key, FQDN, and everything else.

Can they log in as the license holder email account in the 3CX customer portal?

 

[EliteIT]

I'm a little hesitant to try that restore to be honest - system appears to be currently up and running perfectly other than the licensing issue - trying to avoid rocking the boat as it were. I already had to faff around adding the "system_owners" flag into the XML backup file because when I tried to do the first restore from v18 it obviously wiped out the V20 system owner that was initially created as part of the install which then locked me out of the admin side of v20.

Also, I couldn't post on this forum without adding in a trial system to this account etc so don't really want to lose that facility and revert things back to linking to their old providers 3cx account.

Also, they don't have the last providers 3cx account credentials - I'd also imagine they would have a whole host of other clients' 3cx systems on their account too.

 

[SteveITS]

If they are OK reconnecting everything to the new FQDN they could just buy a new license as that can replace a trial key.

Sounds like they were not even on the latest v18.

FWIW the license holder email can be changed from the server dashboard. If the server is running.

The partner is not supposed to be linking to their own email.

 

[EliteIT]

Unfortunately they had only just renewed their subscription so spending circa £900 again is out of the question.

They were on v18.0 Update 9 (Build 35) which as far as I'm aware was the latest update since it was set to automatically update. I did try and re-install v18 but there's no install package for Build 35 which meant that I couldn't then restore the V18 backup so I took the view that it was a good time to change over to v20 for them.

Hmmm.....interesting regarding being able to update the license holder email - might take a look if I'm feeling brave after Christmas!

When you say they aren't supposed to be linking to their own email address - there does appear to be the facility to add multiple systems to a 3CX account?

 

[SteveITS]

Hmm the last couple v18 versions required a system owner. Maybe no one logged in to see that?

If the v18 isn’t working you can’t log in there anyway..? But it was possible. One can also link to a new partner with their ID, like my sig.

AFAIK license keys should be registered with a customer email. If you can prove ownership of the key you might use the 3CX site contact form to ask if they will update the email or move the key to a new account? Check their blog for their holiday hours.