3CX Desktop app 18.10.461.0 GPO install

[lverge]

Hello,
For several weeks, we have noticed malfunctions with the "3CX Desktop App" application. It started with the appearance of the error message "error 401".
On my workstation, I noticed that I had 2 icons for the same application: - A "working" application on the path: "C:\Program Files\3CXDesktopApp\" - A "not working" application " on the path: "C:\Users\<username>\AppData\Local\Programs\3CXDesktopApp\"
The 2 applications are in version 18.10.461.0
Another curious thing is that the deployment is done by GPO via the "Computer" configuration ". Suddenly, this installation on my user profile appeals to me. (my colleague has the same thing on her post). As a result, having the 2 applications installed blocks the use of 3CX on the workstations where the "not working" version is launched first.
Have you ever encountered this problem and have you solved it?

Cordially.

 

[Charles_3CX]

I would advise removing the desktop apps from the computers first individually if they have been installed on the workstations via the webclients, as the 401 error you are receiving is to be expected if the system was updated from U3 to U4, then U5 but the desktop apps were not updated between U3 and U4, and due to some new security enhancements in U5, desktop apps that are still on the version for U3 will not connect or update.

Then if you would like to deploy via GPO, use this guide: https://www.3cx.com/docs/desktop-app-gpo/

 

[lverge]

When the installation is done by GPO, should the installation folder be:
- C:\Program Files\3CXDesktopApp\
or
- C:\Users\<username>\AppData\Local\Programs\3CXDesktopApp\

Thanking you in advance.

 

[Charles_3CX]

Regarding your question, with GPO deployment, the desktop app will be under - C:\Program Files\3CXDesktopApp\

 

[Grant Moxom]

I'm currently facing this issue too - I have every single user in our company now with two versions of the app, one getting the 401 and one working. For some reason the app didn't update correctly and instaleld a new version. It's causing chaos because the 401 app has a "Retry" button, and if the user clicks that 3 times then their IP gets blocked.
Worst part is if the user uninstalls the old version of 3cx it deletes the application handlers meaning the default click to call is removed unless the user reinstalls the latest version again... Any ideas what we can do? This is super messy and causing a huge disruption

 

[Charles_3CX]

I'm currently facing this issue too - I have every single user in our company now with two versions of the app, one getting the 401 and one working. For some reason the app didn't update correctly and instaleld a new version. It's causing chaos because the 401 app has a "Retry" button, and if the user clicks that 3 times then their IP gets blocked.
Worst part is if the user uninstalls the old version of 3cx it deletes the application handlers meaning the default click to call is removed unless the user reinstalls the latest version again... Any ideas what we can do? This is super messy and causing a huge disruption

Uninstall both versions, then re-install using the webclient to ensure the correct version is installed.

 

[Grant Moxom]

Uninstall both versions, then re-install using the webclient to ensure the correct version is installed.

Yeah that's a solution but for 500 people that's a big problem. Is this going to happy for all updates? Because that's a big problem if it doesn't recognise that it's the same program. How can we fix this properly?

 

[Charles_3CX]

Yeah that's a solution but for 500 people that's a big problem. Is this going to happy for all updates? Because that's a big problem if it doesn't recognise that it's the same program. How can we fix this properly?

If updates are needed and previous versions require updating don’t skip the updates.

So all 500 of your users pressed no when update was required when the system went from update3 to 4? then you rolled out the app via GPO? And without uninstalling the older version?

 

[JosIPVG]

In some managed workspaces people are not allowed to update the 3CX client by the admin policies , we have had this too luckily on a fairly small pbx.

 

[Grant Moxom]

If updates are needed and previous versions require updating don’t skip the updates.

So all 500 of your users pressed no when update was required when the system went from update3 to 4? then you rolled out the app via GPO? And without uninstalling the older version?

We updated directly from 3 to 5 - we were waiting for 6 people there's an issue that was introduced for us in version 4 that won't be fixed until 6 so we were planning to wait. Unfortunately we had to do the update due to the certificate topic. Therefore as we skipped version 4 users never got the update request. If we have to avoid versions in the future due to compatibility issues how can we resolve this? It would be fine if we were able to run the update on all computers via GPO/similar however if this happens again we will just start getting loads of different versions of the application sitting around on all computers.