Finally, GPO software installation policies do not have a mechanism to test for up-to-date existing installations, outdated older existing installations, or missing installations of Cisco Jabber, and can therefore not provide different actions based on individual scenarios.Wrapping the CiscoJabberSetup.msi execution into msiexec.exe (instead of the crude 'double-click' installation method) provides yet more command-line options for the installation or upgrade.

CiscoJabberSetup.msi actually has a lot of extremely useful ones, so using another mechanism would expand the available installation features greatly.

Speaking of no command-line switches when using the GPO software installation preference.

Since no command-line switch can be supplied via the GPO software installation, it must be run through an Orca transformation to eliminate all but the desired language code (for us that's '1033' for US English) to match the local settings.

The CiscoJabberSetup.msi file is multi-language.

The usually recommended solution to apply software installation settings via a Group Policy Object (GPO) poses additional challenges: This challenge has remained unchanged for many years, so it stands to reason that Cisco is not inclined to improve this installation/update approach.

Cisco jabber for windows admin