Question for the masses. I’ve had some issues in the past as we were initially experimenting with Google Compute Engine (various changes to hardware ended up resetting ZendID) so I’ve had to have the nice folks at FPBX reset it (since we ate our 3 resets). During my conversations with them about that, I specifically said how frustrating it was that I couldn’t use the DEACTIVATE button to “check back in” the licenses so they could be reactivated on a different box, and I was told that’s just kinda how it was. I specifically stated that if that’s true, it kinda makes the deactivate button pointless.
I’m looking at that button right now, and it specifically says what I had hoped it would represent (the ability to check-in for moving to another box).
“You only need to use this button if you want to move this deployment to another, different, server.”. I recalled trying it once and although it deactivated the current box, it did not allow reactivation on another box.
So, here’s my question. We have a customer who is currently running FPBX13 on VMWare, but we now want to load it on it’s own box (as the other VMs have been migrated off that VM Host). When we do this, we’ll obviously be wiping the drive, but more importantly, moving FPBX from a virtual to physical machine, the hardware IDs will certainly change and it will be considered a different installation instance. IF I deactivate before wiping, and then reactivate after I’m done with the reinstall, should I be able to activate without a Zend Reset? We’re out of Zend Resets on that instance (because of the previously-mentioned migration/moving, etc (we also had such an issue when initially loading this in VMWare when we installed it). What I don’t want to have happen is we deactivate it, then try to activate it after it’s been rebuilt and can’t, but then have no way to contact support to have it reactivated until the following week. I really want to understand the DEACTIVATE button’s true function, as I’ve got an email thread that seems to conflict with the button’s own labeling.