After upgrading to v16 last year our 3CX management console didn't show any further update so we just assumed we were running the latest version.
But when new versions were officially announced we wondered why we wouldn't get the opportunity to install them through the management console.
This was the time we had to find out that the update servers couldn't be contacted and we are already running an outdated version of the PBX.
Digging deeper we found out that the PBX is trying to automatically determine the way to the Internet which in our case is either via user GPO or DHCP WPAD; as it happened an enterprise setting which we were not responsible for set WPAD for whole forest leaving clients not being configured via a user GPO or DHCP WPAD entry trying to contact a proxy server which wasn't available hence our 3CX management portal did not show any update at all. Gladly sometimes we got an error message that made us curious.
They way 3CX works on a Windows (Server 2016 in our case) is that as it doesn't support a manual proxy setting in the configuration just uses the user setting of the account the service runs under which is LOCALSYSTEM so we had to set the proxy correctly for this account.
A legacy tool is still availabe to do this: bitsadmin.exe
It showed LOCALSYSTEM is using the setting AUTODETECT so we just had to change it to NO_PROXY:
bitsadmin.exe /Util /SetIEProxy LOCALSYSTEM NO_PROXY
No reboot necessary, worked right away - had to issue this command on all of our 3CX servers in Europe and finally updates were being pulled from 3CX again.
I wasn't able to find this information here in the 3CX Community which is why I wanted to contribute to make it easier for the next one trying to find a solutuion for the same problem
But when new versions were officially announced we wondered why we wouldn't get the opportunity to install them through the management console.
This was the time we had to find out that the update servers couldn't be contacted and we are already running an outdated version of the PBX.
Digging deeper we found out that the PBX is trying to automatically determine the way to the Internet which in our case is either via user GPO or DHCP WPAD; as it happened an enterprise setting which we were not responsible for set WPAD for whole forest leaving clients not being configured via a user GPO or DHCP WPAD entry trying to contact a proxy server which wasn't available hence our 3CX management portal did not show any update at all. Gladly sometimes we got an error message that made us curious.
They way 3CX works on a Windows (Server 2016 in our case) is that as it doesn't support a manual proxy setting in the configuration just uses the user setting of the account the service runs under which is LOCALSYSTEM so we had to set the proxy correctly for this account.
A legacy tool is still availabe to do this: bitsadmin.exe
It showed LOCALSYSTEM is using the setting AUTODETECT so we just had to change it to NO_PROXY:
bitsadmin.exe /Util /SetIEProxy LOCALSYSTEM NO_PROXY
No reboot necessary, worked right away - had to issue this command on all of our 3CX servers in Europe and finally updates were being pulled from 3CX again.
I wasn't able to find this information here in the 3CX Community which is why I wanted to contribute to make it easier for the next one trying to find a solutuion for the same problem
