Centrally deploy 3CX Desktop App

[MH_INDUS]

Hello 3CX Team,

I am struggling to get the new Desktop App deployed with our deployment tool.

If I use the default parameters supplied by the MSI it will open once but not show as installed and cannot be provisioned.

If I use the parameters most other MSI files use (/qn /L* c:\MSISetup.log /norestart ALLUSERS=2) I get error 1603.

What are the proper parameters to deploy the App via msiexec?

 

[NickD_3CX]

While I have never tried this myself, another user posted something a while back:
https://www.3cx.com/community/threads/deploy-desktop-client-via-pdq.86018/post-405051

 

[MH_INDUS]

Hello @NickD_3CX, I looked through that thread before I opened this one.

At least with App Version 18.7.10 the commands from bradomski do not work.

Even with the INSTALLDIR parameter the App gets installed in the AppData folder of the installation user, which in the case of deployment tools is either a service user or the local system.

In its current state the Desktop App is not fit for enterprise deployments.

There are many other questions, threads and feature requests for the ability to centrally deploy and provision 3CX software. Please get your developers on this.

You cant serously demand from a simple user to sign in to the webclient, install the Desktop App, then provision it, Then install the Outlook plugin, then install the ClicktoCall extension and configure that. Those are way too many steps, none of which can be automated.

 

[NickD_3CX]

At least with App Version 18.7.10 the commands from bradomski do not work.

Even with the INSTALLDIR parameter the App gets installed in the AppData folder of the installation user, which in the case of deployment tools is either a service user or the local system.

I'm sorry it didn't work for you, I thought I should send the link anyway even if we didn't test it.

ou cant serously demand from a simple user to sign in to the webclient, install the Desktop App, then provision it, Then install the Outlook plugin, then install the ClicktoCall extension and configure that.

Currently that is the concept, along with simple instructions that can be customized in the Welcome Email.
To be fair, the steps aren't that difficult, but I suppose that is a matter of perspective.

In its current state the Desktop App is not fit for enterprise deployments.

For large deployments this is the recommendation:
https://www.3cx.com/docs/desktop-app-windows-terminal-server/

The provisioning via the WebClient just requires a few more clicks.