All modules disabled after upgrade 15->16

fwconsole sa activate xxxxx

If you are prevented due to a hardware lock, see: https://wiki.freepbx.org/display/FPG/How+to+Move+a+Deployment+ID+to+a+new+PBX

If you are out of resets, you can request one from a Customer Service and billing ticket: https://wiki.freepbx.org/display/FPAS/How+To+Open+A+Support+Ticket

xxxxx is the deployment ID on the Sangoma portal?
i activated the free version with the current ID - do i have to de-activate or anything before proceeding?

Maybe read what was linked?

i have read them
as i stated above i see ‘Hardware not locked, please activate’ at the bottom of the screen, not ‘Reset Hardware Lock’
i’m not sure what that means?
does it mean i have used all my resets?

So, did you ‘activate’ ?

no not yet
still not sure what i am trying to accomplish
i think i want my freepbx16 to have the same deployment ID as 15 had - i am assuming it would have if the upgrade had gone as planned
not sure that clicking the ‘activate’ button on the Sangoma portal is going to accomplish that
i am assuming that ‘fwconsole sa activate xxxxx’ with xxxxx being the original deployment ID will accomplish that??

That’s correct.

that fixed it - thanks
i think everything is back
i’ll switch over from my backup & check it out

FYI - it’s always a good idea to set your VM mac address in hyperV to static instead of dynamic. Your mac address could have changed during a reboot, which would break your licensing.

1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.