Downloadable Version of new Windows Store App

[pace-IT]

Hello everyone,

will there also be a "downloadable" version of the new store app (e.g. MSI or EXE)? On the Remote Desktop Servers (Windows Server 2019 and 2022) of our customers there is no Microsoft App Store available and therefore the users unfortunately cannot use the new 3CX Windows Store app.

Kind regards
Tan

 

[rhbadmin]

rightfully or wrongfully my research in to this also:

"go to MS Store and copy the link of the app you want to install https://apps.microsoft.com/store/apps
Copy the link of the app and paste in this website, search in RP mode https://store.rg-adguard.net
In the result, find the .appx file of the app you need and right click and save as, your browser might detect it as a harmful app, you can ignore and keep the file
Make sure you also download all the dependencies and save them as well
Once you download all the dependencies and the application, start by installing dependencies first, and then the main app
To install, go to the downloads location, right click on each and click Install
Optional: you can also install via powershell Add-AppxPackage -Path "<PATH>".appx"


Powershell.exe Add-AppProvisionedPackage -online -packagepath "C:\PATH\Microsoft.WindowsAppRuntime.1.4_4000.1136.2333.0_x64__8wekyb3d8bbwe.Msix" -skiplicense
Powershell.exe Add-AppProvisionedPackage -online -packagepath "C:\PATH\3CXDMCC.3CX_20.0.410.0_x64__bhm4yemhnd70e.Msix" -skiplicense

Hello! This works fine! We are deploying 3CX with PDQ.

Is there a way to include the server link (3CX URL) or edit the package with the MSIX Packaging Tool to insert the server link?

Thank you for your help!

 

[toniSanta]

The MSIX Package is not supported on Windows 2016 (only Windows 2019 and newer).
Any chance to get a MSI Package?

 

[etiCloud]

I have recently returned to 3CX and the lack of MSI is going to stop me deploying to SME customers, we are now in June and there doesn't seem to be any movement on this, can we please have an update?

 

[etiCloud]

You can download the MSIX from here https://www.3cx.com/blog/press-releases/softphone-beta-csta/ under the section titled "Install and Update Yourself? Deploy as MSIX"

I missed this previous post, however having tested it does only work on 2019 and above.

 

[toniSanta]

I understand that MSIX works only on Windows 2019 and above, therefore I asked for a MSI Package. Windows 2016 has EOL in more than 2½ years, so we can not force our customers to change to Windows 2022 only for 3CX.

 

[etiCloud]

Thanks toniSanta,, we do have a small number of users who have ESU applied to 2016 servers which runs to 2027, this was more for information purposes, it would be interesting to know what is going to be the msix enterprise distribution method going forward though.

 

[toniSanta]

as of here https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2016 the "normal" end of life for Windows 2016 is 12 Jan 2027, so I do not think that at the moment there is an offer for ESU from Microsoft for this product.

 

[etiCloud]

apologies you are correct, we have it sat on 2012 R2 still, we made the decision to go to 2019 from 2012, so are fortunate.

 

[hozi]

But for bigger installs there are cases they don't want to rely on the microsoft store so we are working a way to deploy network wide - including tracking and updating. The mechanism we had in place previously can no longer be used because its no longer an MSI but an MSIX and it works somewhat differently. The electron app had its own updater.

@Nick Galea : Any update on the availabilty of an MSI package? Timeline?
Thank you!

 

[integrated30]

+1 same here.

 

[ITGuy65468]

Why? Why? Why? Do vendors insist on pulling the rug out from Sys Admins?!

Of course we need an MSI, did you consider asking your customer base? At this point I'm surprised the new version doesn't have "AI" in the title.

 

[ITGuy65468]

I have to agree with Kano90 on this one. For the first time since finding 3CX as a solution I'm seriously thinking about looking at alternatives. V20 seems like it was thrown together in a hurry, not tested, and released WAY before it was ready. So many features are missing that its a waste of time upgrading any existing installs as there WILL be missing functionality.

Agreed. Did not expect this from 3CX.

 

[in.windows]

Everything you should know about today's available 3cx.msix version:

Installed components on Windows server 2022 in powershell as folowing:
Add-AppxPackage -Path .\Microsoft.WindowsAppRuntime.1.5.msix
Add-AppxPackage -Path .\Microsoft.VCLibs.x64.14.00.Desktop.appx
Add-AppxPackage -Path .\Microsoft.UI.Xaml.2.8.appx
Add-AppxPackage -Path .\3CX.msix

Launched 3cx app, logged into account, few clicks in the app and app crashed:

Application: 3CXSoftphone.exe
CoreCLR Version: 8.0.624.26715
.NET Version: 8.0.6
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0434e49, exception address 00007FFBEA0DF17C

Faulting application name: 3CXSoftphone.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xe0434e49
Fault offset: 0x00007ffbea0df17c
Faulting process id: 0x33e4
Faulting application start time: 0x01dac303d8be61be
Faulting application path: C:\Program Files\WindowsApps\3CXDMCC.3CX_20.0.491.0_x64__97f1hnz6y6tba\3CXSoftphone.exe
Faulting module path: unknown
Report Id: 548788d9-7698-438f-aae4-0b66ca21fb70
Faulting package full name: 3CXDMCC.3CX_20.0.491.0_x64__97f1hnz6y6tba
Faulting package-relative application ID: App


release:
Get-AppxPackage | Where-Object {$_.name -Like "*3cx*"}


Name : 3CXDMCC.3CX
Publisher : CN=3CX Ltd, O=3CX Ltd, L=Egkomi, C=CY
Architecture : X64
ResourceId :
Version : 20.0.491.0
PackageFullName : 3CXDMCC.3CX_20.0.491.0_x64__97f1hnz6y6tba
InstallLocation : C:\Program Files\WindowsApps\3CXDMCC.3CX_20.0.491.0_x64__97f1hnz6y6tba
IsFramework : False
PackageFamilyName : 3CXDMCC.3CX_97f1hnz6y6tba
PublisherId : 97f1hnz6y6tba
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : False
Dependencies : {Microsoft.WindowsAppRuntime.1.5_5001.119.156.0_x64__8wekyb3d8bbwe}
IsPartiallyStaged : False
SignatureKind : Developer
Status : Ok

 

[454ss]

Another vote here to PLEASE get us a .exe or msi installer or SOMETHING. I am currently having issues with downloads from the Microsoft Store, and its an unpleasant experience for IT staff anyway. I am currently needing to install the 3CX client software on a machine and the MS Store is buggy and doesnt work.

 

[sfernandes]

+1. MSI please.

 

[ThomB_3CX]

@sfernandes msix is available from the partner portal in Downloads section

 

[sfernandes]

@sfernandes msix is available from the partner portal in Downloads section

Thank you @ThomB_3CX !

 

[454ss]

@ThomB_3CX Thank you very much!

 

[hozi]

Currently, deploying Microsoft Store apps is not feasible on Microsoft Terminal Server, and using MSIX packages also presents challenges in these environments.
I found a workaround in the German 3CX forum (https://www.3cx.de/forum/threads/v20-client-auf-windows-server-2022.119922/post-430344), but it requires manual updates and isn't ideal!

1. Download the Windows App SDK v1.5 Runtime (https://learn.microsoft.com/de-de/windows/apps/windows-app-sdk/downloads).
2. Download the 3CX MSIX package.
3. Install the runtime on the Terminal Server.
4. Open PowerShell and run the following command: Add-AppProvisionedPackage -online -packagepath "<local_path>\3CX_v20.0.546.msix" -skiplicense

With this method, you need to manually update the client app each time a new version is released.

Is this the intended approach for deploying the 3CX Client App? I have my doubts...

 

[jeffry van meer]

but is i understand .MSIX is only for windows LTSC. we need to deploy it on a couple of windows 2019 RDS-servers. Is there any solution for this?