Can't provision the Windows app

[r831]

I've been trying to log into the Windows 10 desktop app through the 3CX Web Client at my local connection, I can install the windows app normally but I can't log into the app because I hit the "Provision" button and nothing happens. I already added 3cx to my firewall, and the default protocol app is configured correctly. Also tried to get the URL but it didn't worked. What I should do?

 

[SteveITS]

Just a followup note, this would mean the Desktop App can't self-upgrade for any user account that hasn't logged on between update 3 and update 5. (vacation, rarely used account, etc.)

 

[Charles_3CX]

Correct if they have not been updated, update skipped, they will need to be uninstalled and reinstalled.

 

[Chris Fella]

I have found that if you completely shutdown the app. then go back to the webclient and click the provision button. The desktop app starts and then provisions.

My customer was on 18.0 update 4. As of Sunday they were on update 5. I do not believe this made any difference as when it did provision it stated that it need to upgrade. I did so and all was fine.

 

[accentlogic]

I am really hoping that 3CX can add some code to the Desktop App to resolve this type of situation in the future. It generates way too many frustrated users and support calls.

 

[Charles_3CX]

Just to clarify, it's quite simple. If you do not keep the apps up to date, as in from updates 3 to 4, and the app was not updated when the 3cx system was updated to update 4, in other words, the update of the desktop app was skipped, then 3cx system updated to update 5 there will be no update as this would cause a 401 error, when the desktop app is opened, simply because the version of the app is still the version for update 3, it will not work with update 5, and the desktop app will need to be uninstalled and the new version installed.

 

[accentlogic]

Just to clarify, it's quite simple. If you do not keep the apps up to date, as in from updates 3 to 4, and the app was not updated when the 3cx system was updated to update 4, in other words, the update of the desktop app was skipped, then 3cx system updated to update 5 there will be no update as this would cause a 401 error, when the desktop app is opened, simply because the version of the app is still the version for update 3, it will not work with update 5, and the desktop app will need to be uninstalled and the new version installed.

Yes, I understand that. The problem is when you have thousands of users and hundreds of locations to manage they don't all update every time. And this type of situation generates unnecessary support and dissatisfied users.

There can be legitimate reasons to skip an update, or the user may say No. Either way, the app should check for this situation and handle it programmatically, rather than require an uninstall, reinstall and reprovision - especially for minor point releases.

 

[chaney]

Does anyone know of a way to automate the provisioning? We have lots of clients as well and manually updating them seems like a ridiculous answer. How are we supposed to manually update 100's of desktop app installs?

 

[SteveITS]

Does anyone know of a way to automate the provisioning? We have lots of clients as well and manually updating them seems like a ridiculous answer. How are we supposed to manually update 100's of desktop app installs?

If you haven't already installed update 5 (or 4), you can manually upgrade to 4, wait a week or two for at least most apps to self-update, then enable automatic upgrades in 3CX to upgrade to 5. (automatic upgrades also install OS updates)

Alternatively it's MSI based so it should work to uninstall it (MsiExec.exe /X {0ED137FD-F7F8-4841-8060-1156F8CACC14}) so the employee can log in to the web client to reinstall/reprovision. Possibly need to do that as the user, since it installs into %AppData%...I haven't actually tried to uninstall it like that, now that I think about it.

I've been working from home so just realized while writing this I forgot to update my work PC.

Also, I see the app version number updates now...I seem to recall that was not the case a while back? So software inventories will show which PCs still have the older version.

 

[chaney]

OK so update from our side.

The original admin did push through PDQ Deploy as well for v18.3 which is why I believe it never updated. It was installed as an administrative user and our users do not have local admin rights. I have now created a new deploy package that will install as a local logged-on user.

We have tested on a few users and they were not required to manually reprovision when they opened 18.10 app it worked as expected.

Here's to hoping the rest work out that way.

 

[Chris Fella]

Just to clarify, it's quite simple. If you do not keep the apps up to date, as in from updates 3 to 4, and the app was not updated when the 3cx system was updated to update 4, in other words, the update of the desktop app was skipped, then 3cx system updated to update 5 there will be no update as this would cause a 401 error, when the desktop app is opened, simply because the version of the app is still the version for update 3, it will not work with update 5, and the desktop app will need to be uninstalled and the new version installed.

That does not appear to be true in my case. My users never had the webclient installed at all. They were on v18 update 4.

 

[Charles_3CX]

Yes, I understand that. The problem is when you have thousands of users and hundreds of locations to manage they don't all update every time. And this type of situation generates unnecessary support and dissatisfied users.

There can be legitimate reasons to skip an update, or the user may say No. Either way, the app should check for this situation and handle it programmatically, rather than require an uninstall, reinstall and reprovision - especially for minor point

That does not appear to be true in my case. My users never had the webclient installed at all. They were on v18 update 4.

releases.

From update 4 to 5 when desktop apps where updated or installed when on update 4 you would not have an issue.