eM Client 11 windows unattended install

looks like the software packaging has changed with v11 release

what is the process that i can use to push out unattended/quiet installs/upgrades for our existing fleet

the download page seems serve up “emclient.appinstaller” download (no version in the filename)

Hi @dcvcnoc,
With eM Client 11, we switched the packaging to MSIX. This lets us offer native 64-bit and ARM versions while keeping the installer small.
Our blog post has more details: eM Client 11 has been released | eM Client

We’ve also set up a Windows download page that includes (the last) MSI installer: Download eM Client 11 for Windows | eM Client.
Please note that this MSI doesn’t contain the app itself - it keeps your existing file associations and then installs version 11 through the .appinstaller.

How you push it out depends on your deployment tool. Are you using Intune, or Active Directory / Group Policy? Or something else?
Generally, you can download the .msixbundle from the .appinstaller link and deploy that. Some tools can also work with the .appinstaller file directly.

We don’t have any guide on the topic yet, but if you let me know which tool you’re using, we’ll try to help with the details.

1 Like

i’m personally using PDQ Connect, but the same need exists with Intune, GPO or other similar managed deployment mechanisms

i need a reliable quiet/unattended installation/upgrade mechanism that i can fire via a command line “one-liner” that performs the install without any user intervention or UI popups/prompts/etc

in the 10.x era you had an annoying thank you web page that i would love to suppress, but my key issue here is that the 11.x installer (even the alternate .msi version) doesnt seem to work with the previous guidance…below command fails with a 1603 error

e.g.

msiexec.exe /i “emclient-11.0.1054.msi” ALLUSERS=1 /qn /norestart /log output.log MAILCLIENT_ASSOCIATE=0 MAILCLIENT_RUNATSTART=0 MAILCLIENT_LAUNCH=0

couple other installer related data points

  1. winget doesn’t seem to correctly report versions older than 11.x any longer

e.g. on a system with 10.4.5674 installed it reports “< 11.0.1054” which is pretty unusual

  1. “winget update --id=eMClient.eMClient” does not perform a silent install
    <i’ll have to post screenshot separately>

the upgrade from 10.4.5674 to 11.0.1054 via winget does appear to work, but the 2 resulting software registry entries seem to be an odd mix of winget and MSIX entries and the GUI installed apps fails to report a version for “eM Client” while it does report one for the “eM Client (Updater)”

with two packages it then begs the question of how an uninstall happens, i suspect it means the uninstall is a two step process to remove each component independently

sure enough trying
“winget uninstall --id=eMClient.eMClient”

  • only seems to uninstall the “eM Client (Updater)” portion

Please note that the WinGet package isn’t maintained by us.

When you use the MSI updater, it actually still installs version 11 through .appinstaller (MSIX) but keeps your existing file associations from the previous (MSI) versions. The MSI doesn’t contain the app itself. That’s why you see two entries, “eM Client” and “eM Client (Updater).”

If you uninstall the MSI entry, only the updater is removed. To remove eM Client itself, you need to uninstall the “eM Client” entry separately.

We don’t recommend the MSI for new installations, because it’s meant only for upgrading existing ones. So if you make new installs (not upgrade from v10 or older) use the .appinstaller file.

1 Like

if its not maintained by you, who is it maintained by?

it sure looks like its published by y’all and it downloads from your site

i think i’m starting to understand this two package thing is a transitionary step only for the v10 to v11

i notice after the v11 second update to 11.0.1201 that the “eM Client (Updater)” is still stuck at 11.0.1054

i subsequently removed that “eM Client (Updater)” package

looks like its an automated tool that generated that winget manifest

reference: New version: eMClient.eMClient version 11.0.1054 by UnownBot · Pull Request #448894 · microsoft/winget-pkgs · GitHub
reference: GitHub - UnownPlain/anthelion: Automatically update packages in the Windows Package Manager Community Repository · GitHub

msi transition and winget issues aside, the core question remains going forward

→ how can i automate a silent/unattended install for emclient 11.x?