Alright, I already opened a case about it (986774) but I don’t think Hugo understands the problem - and maybe it is just not possible, but it seems like it should work - Here is the sequence of events that I am doing over and over again - most of the machines I have moved have only had 2-3 Connect clients on them, so it was not terrible to have to re-deploy them, but the machines I have left to move have a LOT of SC clients and it would be a huge waste of time (and annoy the clients) to have to re-deploy them.
Back Up machine with Working Connect Clients.
De-Activate old Machine and Activate New Machine.
Restore Backup from Old Machine to New
There are no errors thrown during the Backup or the Restore having anything to do with SC or Zulu - it “looks” like it worked fine, but the SC clients won’t re-connect to the new instance until they are re-invited.
I control all the DNS for my machines - and all the Clients (and setup for that matter) is set to the friendly name - so when I back the machine up and de-activate it, I switch the friendly name over to the new install, and it “becomes” the old machine - all the phones swing over automatically. This part is working perfectly.
Am I just doomed to have to re-initialize and re-install SC for every move?
Hey - I finally figured out how to fix this - here is the trick in case anyone else runs into it.
Once you have restored, you will have the extensions defined in Sangoma Connect, but their app’s will not register - go into User Management and under the Connect Tab, turn them off - do not submit - and then turn them back on and THEN submit.
This puts the special “bits” back and the App will once again register - you really shouldn’t have to do this, but whatever - this is the fix!
So it will show already on - turn it off - do not submit - and then turn it back on and THEN submit and like magic, the App will register and work again!
