Hi There,
I just used this script 5 days ago and the user interface I ended up with was PBXact.
I ran the following on a fresh Debian 12 install on google cloud instance.
wget https://github.com/FreePBX/sng_freepbx_debian_install/raw/master/sng_freepbx_debian_install.sh -O /tmp/sng_freepbx_debian_install.sh
and it installed - PBXact 17.0.19.25
Is this by design?
Thanks.
That seems…odd. I will do a test install today…this should not be happening…as far as I know…
So you get the PBXact branding, but I assume, no associated PBXact licensing?
Weird, but you might be able to fix it by fwconsole ma delete oembranding
I am testing as we speak. I am just running the FreePBX 17 install script, and then I will report back. Just want to see if I can reproduce it.
I cannot reproduce it:
Hi There,
Yes it has all the OEM branding of PBXact and correct that the licensing is a bit weird.
I can send you the deployment ID if that helps via direct message? I also can’t see the deployment in my sangoma portal so not sure which user it registered against.
I followed the instructions from here: https://sangomakb.atlassian.net/wiki/spaces/FP/pages/230326391/FreePBX+17+Installation
I have the install log file as well if that would help?
I can restart from a new clean install if need be but I have put a reasoinable amount of time into configuration to date so would be a bit annoying if this is what you recommend.
I ran this command it has correctly changed everything over to “FreePBX” branding instead of “PBXact”.
This is what my System Admin looks like after running:
fwconsole ma delete oembranding
However I can not Change Owner. I get the following error when I click on the change owner button.
Jackpot! Looks like you managed to get a deployment ID that has PBXact licensing already applied to it (how?) and along with it, a whole lot of commercial modules 
Since it shows 60 extension licenses this ID was probably connected to a 60-user PBXact appliance.
Open a support ticket.
