Solved Improved client/extension registration/mass deployment

[JSlow]

Maybe this exist and I just couldn't find anything but I figured I'd post anyway.

Since the Windows app got updated to a new fancy client that appears to be mostly just a bunch of UI changes...it would be really cool if there was a better way for users to actually setup the app. For computer competent people it isn't a hassle really, but there are some minor annoying issues that I think could be solved if the registration was done via sign-in rather than a provisioning file.

Problems with current system:

• A welcome email is required.
  • Normally not an issue. But if a user uses a different computer (Either due to upgrades or user desire), they will be required to find the welcome email from the PBX and drop the provision file to the client. I can almost guarantee you no end user is going to keep that welcome email so it would require the PBX admin to go back into the console and resend the email.
• Some users don't understand how to do it themselves.
  • Pretty self-explanatory. Yes it's a simple drag n' drop but in my experience even this may be to complicated for some people.

My suggestion is to use a sign-in method instead of the provisioning file. From an admin standpoint, all we would need to do is publish the MSI with some additional arguments so the client knows where to look for the pbx. For instance:

3cxapp.msi -q -addr fqdn.goes.here [-SSO]

• -q is quietly install the client
• -addr is the fqdn of the PBX
  • If -SSO is not supplied, the user would be greeted with a sign-in page as if they were going to use the webclient.
• -SSO is to use SSO sign-in. This would grab the credentials from Windows and use them to authenticate upon launch of the application...no interaction from the user required. I believe this is possible as other programs are capable of this.

That's all really. It would make it so much easier to deploy and to make people actually use the app instead of using their desk phones.

 

[NickD_3CX]

Hi!

The new Desktop App no longer requires the Welcome Email to be provisioned.
All you need to do is log into your WebClient from any PC and from there, download and provision the App:
https://www.3cx.com/user-manual/web-client/#h.d3b3lf2mdzdr

About needing the email to find the credentials to log in, while you have a point, in V18 SSO is possible for users!
So, they can log into their WebClient using the Gmail or MS365 login details.
Instructions for Google can be found in the Management Console --> Settings --> Google, while for instructions for MS365 you can check here:
https://www.3cx.com/docs/microsoft-365-integration/

 

[JSlow]

Hi!

The new Desktop App no longer requires the Welcome Email to be provisioned.
All you need to do is log into your WebClient from any PC and from there, download and provision the App:
https://www.3cx.com/user-manual/web-client/#h.d3b3lf2mdzdr

About needing the email to find the credentials to log in, while you have a point, in V18 SSO is possible for users!
So, they can log into their WebClient using the Gmail or MS365 login details.
Instructions for Google can be found in the Management Console --> Settings --> Google, while for instructions for MS365 you can check here:
https://www.3cx.com/docs/microsoft-365-integration/

Neat. However, that is only a partial solution. I know it may seem small but some people really don't like doing ANY setup themselves...this includes going to a website (even if it's only once) and clicking more buttons then they care to click for (Typically 2 or more clicks).

It would just be a small/large QOL for the end user if it setup as minimal/automated as possible.

 

[NickD_3CX]

Neat. However, that is only a partial solution. I know it may seem small but some people really don't like doing ANY setup themselves...this includes going to a website (even if it's only once) and clicking more buttons then they care to click for (Typically 2 or more clicks).

It would just be a small/large QOL for the end user if it setup as minimal/automated as possible.

I have worked with users enough to know that some are like that.
If the users of said customer don't like too many clicks, why not only have them use the WebClient? They would literally need only 1 click on the SSO button if they already logged in to their Google/MS365 account.

 

[JSlow]

I have worked with users enough to know that some are like that.
If the users of said customer don't like too many clicks, why not only have them use the WebClient? They would literally need only 1 click on the SSO button if they already logged in to their Google/MS365 account.

I could do that. I might of just imaged it but I thought the web client was going to go through some kind of change/retirement in favor of the desktop client.

 

[NickD_3CX]

...but I thought the web client was going to go through some kind of change/retirement in favor of the desktop client.

There are no current plans to retire the WebClient, so you don't need to worry about that.

 

[JSlow]

There are no current plans to retire the WebClient, so you don't need to worry about that.

So I just imaged it. Cool. Alright, I can live with deploying a webapp/shortcut the web client for use. Thank you!

 

[NickD_3CX]

You are most Welcome!