Webex App | Installation and automatic upgrade

You can use the MSI file on Windows to install Webex App, or you can use the DMG file on Mac to do so. If you are an administrator, you can do either. To provide a better experience for users, you can incorporate command line parameters. The Webex App will, at regular intervals, search for newer versions in order to perform an automatic upgrade of the app. See Webex for Government software installation instead if your organization makes use of Webex for Government.

System requirements

• The requirements that are mentioned here may be subject to change as a result of our ongoing analysis of the bare minimum needed to run Webex App.
• We do not provide assistance for the use of the Webex App with any pre-release or early release programs, including the Apple Beta Software, the Windows Insider Program, and any other programs that are functionally equivalent.
• The performance of the Webex App may be affected by variables other than the operating system, such as the connectivity of the user‘s network or the presence of other applications on the user’s device.

Windows desktop minimum requirements

• Intel Dual-Core CPU 2.XX GHz or AMD processor.

• Minimum 4 GB RAM

• Windows 10 or later OS.

• Check to see that all of your drivers have the most recent versions. Please see the following for additional information on the most recent drivers for various graphic products:

• • How to find the latest compatible for an AMD graphics product
  • NVIDIA driver downloads
  • Intel downloads for graphics drivers

 

• Microsoft Edge WebView2 component.

Because of this, the amount of bandwidth required for program updates is significantly reduced. Offers the opportunity to enhance the possibilities of the memory.

• Download either the Evergreen Bootstrapper or the Evergreen Standalone Installer.

Mac desktop minimum requirements

• MacOS 10.13 and later.

• M1 chip or Intel CPU-based

• Minimum 4 GB RAM

Download the installer

Windows

If you are an administrator and want to access a particular edition of the application, you can do so by clicking on one of the following links:

• Localized versions:

  • 32-bit version https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex_x86.msi

  • 64-bit version https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex.msi

• Non-localized versions:

  • 32-bit version https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex_x86_en.msi

  • 64-bit version https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex_en.msi

Mac

The DMG file is available for distribution by clicking on the following link:

• Macs with Intel chips: https://binaries.webex.com/WebexTeamsDesktop-MACOS-Gold/Webex.dmg

• Macs with M1 chips: https://binaries.webex.com/WebexDesktop-MACOS-Apple-Silicon-Gold/Webex.dmg

Install Webex

Installing the desktop version of Webex App on either a Mac or a Windows computer is the topic of this tutorial. For Linux,

• Windows

Every time Webex App is updated to a new version, the installation takes place in the same folder on your device.

• To determine which version of the Webex App is currently installed on your device, go to Find your App version.

• By launching the Messaging App Version Report, administrators are able to determine what version of the app their users have installed on their devices.see Reports for your Cloud Collaboration portfolio.

Manual install

Installing the Webex App can be done either on a per-computer or per-user basis. Installing it is possible either through the users or through an IT administrator.

By default, the Webex App will install to the following folder: %LocalAppData%Programs.Spark from Cisco.

Users can download the installer file, which they can then execute. (msi). They do not require credentials that grant them access to the administrator account on their computer.

The appropriate version of Webex App is downloaded after the browser has determined whether the user’s operating system is 32 or 64 bits in size and acted accordingly.

Administrators are granted additional capabilities when running the installer and have the ability to select a per-computer installation as well as the installation directory.

Which MSI install package should I use?

The following is a comparison of the two different packages:

• Localized or non-localized package:Users who want Webex App to install in the language that is native to their operating system have the option of selecting a customized package.

  You are required to use a non-localized package if you are an administrator who is performing a bulk installation using a third-party distribution technique. Users are still able to access the Webex App in their language of choice. (if Webex supports that language).

  • When you try to uninstall Webex App after performing a mass installation using a localized package, you might run into some problems.
• 32-bit or 64-bit package: Select the product that corresponds to the architecture of the Windows operating systems that you intend to use.
• App only package:This is a choice that is available to you in the vast majority of scenarios. The only application that will be installed is Webex. When it’s essential, Webex App will download the components of the desktop meeting app.

  There are some circumstances in which you might require the package rather than the individual components.

• Bundle package: Both the Webex software and the desktop meetings software will be installed once you purchase and run this package. Make exclusive use of the bundle product in the following circumstances:
  • You are installing in a safe setting, which prevents other people’s computers from downloading software. People may experience usability issues when attending meetings with the Webex App if it is unable to download the necessary components for meetings.

     

  • Because you have not yet completed the transition to Webex App, your customers must continue to use the standalone desktopMeetings application.

Table 1. Webex App install packages for Windows

Description	Is localized?	OS architecture	Install package download link
Webex App only	Localized	32 bit	https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex_x86.msi
Webex App only	Non-localized (EN)	32 bit	https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex_x86_en.msi
Webex App only	Localized	64 bit	https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex.msi
Webex App only	Non-localized (EN)	64 bit	https://binaries.webex.com/WebexTeamsDesktop-Windows-Gold/Webex_en.msi
Webex App and desktop meetings bundle	Localized	64 bit	https://binaries.webex.com/Webex-Desktop-Windows-x64-Combined-Gold/WebexBundle.msi
Webex App and desktop meetings bundle	Non-localized (EN)	64 bit	https://binaries.webex.com/Webex-Desktop-Windows-x64-Combined-Gold/WebexBundle_en.msi

Bulk install

The examples in this article make use of Microsoft’s msiexec application. t. See https://docs.microsoft.com/en-us/windows/win32/msi/using-windows-installer for more details.

These are the specifications that can be used on the command line when installing a Webex App using an MSI package:

Installation context

In order to designate a per-computer installation with the ALLUSERS=1 setting, you need to have access privileges that allow you to administer the system. See https://docs.microsoft.com/en-us/windows/win32/msi/allusers for more details.

Silent installation

You can install without requiring any involvement from the user by including the /qn switch. As an illustration, you could type msiexec /i c:workWebex.msi /qn.

ACCEPT_EULA

If you want to approve the end-user license agreement on behalf of your users, set this property to TRUE. Users are not prompted in any way to approve the end-user license agreement when the installer is run.

For example: msiexec /i c:\work\Webex.msi ACCEPT_EULA=TRUE ALLUSERS=1.

If you change either of the following registry entries to eula-disabled, the end-user license agreement will no longer be displayed on your computer:

• • • HKEY_LOCAL_MACHINE\Software\CiscoCollabHost\Eula Setting

    • HKEY_LOCAL_MACHINE\Software\WOW6432Node\CiscoCollabHost\Eula Setting

AUTOSTART_WITH_WINDOWS

Determines whether or not the Webex App launches automatically whenever Windows begins up.

The number that is used by default is true. To make those kinds of changes, you need administrative responsibilities.

Examples:

• • • msiexec /i c:\work\Webex.msi AUTOSTART_WITH_WINDOWS=true ALLUSERS=1

When Windows boots up, the Webex Application will automatically launch. (default). Because of this setting, the Start Webex when my computer begins control will always be enabled but will be grayed out, preventing the user from changing it.

• • • msiexec /i c:\work\Webex.msi AUTOSTART_WITH_WINDOWS=false ALLUSERS=1

The Webex App does not immediately launch whenever Windows is started. Users have the ability to modify Start Webex when my computer starts within the settings of the Webex App.

DEFAULT_THEME

Identifies the motif that is applied to the Webex App.

The default setting is Dark. To make those kinds of changes, you need administrative responsibilities.

Within the settings of Webex, users have the ability to modify the theme.

Examples:

• • • msiexec /i c:\work\Webex.msi DEFAULT_THEME="Light" ALLUSERS=1

      Specifies the light theme for Webex App.

    • msiexec /i c:\work\Webex.msi DEFAULT_THEME="Dark" ALLUSERS=1

      Specifies the dark theme for Webex App.

DELETEUSERDATA

Indicates whether or not the user information and log files should be deleted or kept.

The default number is 0, which means that both the database and the logs will be kept during the installation process.

Examples:

• • • msiexec /i c:\work\Webex.msi DELETEUSERDATA=1 ALLUSERS=1

      Removes user database and logs during install.

EMAIL

You can make the process of signing users into the Webex App more streamlined by specifying their email address or a pattern that demonstrates how to derive the email address. This parameter gives you this ability.

For instance, msiexec /i c:work would get the job done.The e-mail address cassidy@example.com will be prefilled in the Webex sign-in sequence if you install the Webex.msi file with the EMAIL=acassidy@example.com parameter.

The following are some examples of valid numbers to use for the EMAIL parameter:

• • • Email address of the user (for instance, acassidy@example.com) — This field requires a real email address so that the sign-up procedure can be prepopulated with it. It only represents one email account, so you shouldn’t use it with the ALLUSERS=1 parameter. This is not recommended for use on devices that support more than one person at a time.

For example: msiexec /i Webex.msi EMAIL=$acassidy@example.com

• • • Instructs Webex to retrieve the user’s User Principal Name (UPN) from Windows at the moment of sign in when $userPrincipalName is used. You are able to use this for machines that have more than one user.

For example: msiexec /i Webex.msi EMAIL=$userPrincipalName ALLUSERS=1

• • • $mail tells Webex to retrieve the user’s email address from LDAP or Active Directory when they check in, if that information is stored in either of those directories. You are able to use this for machines that have more than one user.

For example: msiexec /i Webex.msi EMAIL=$mail ALLUSERS=1

• • • At the moment of sign in, $SAMAccountName instructs Webex to retrieve the user’s SAMAccountName from Windows. In most cases, this is utilized for outdated environments. You are able to use this for machines that have more than one user.

For example: msiexec /i Webex.msi EMAIL=$SAMAccountName ALLUSERS=1 ALLUSERS=1 ALLUSERS=1

Users are able to sign in automatically by combining the EMAIL parameter with an authentication technique like Kerberos or mTLS. Both of these methods are examples.

Users are unable to modify the Webex identity that they use to sign in when the EMAIL parameter is being used.

ENABLEOUTLOOKINTEGRATION

Indicates whether or not the Webex App will register with Microsoft Outlook in order to integrate presence. To make those kinds of changes, you need administrative responsibilities.

The default value is 0.

Examples:

• • • msiexec /i c:\work\Webex.msi ENABLEOUTLOOKINTEGRATION=1 ALLUSERS=1

The Webex App integrates presence functionality with Microsoft Outlook on Windows by registering with it.

Within the Webex settings, users have the ability to modify the Connect Webex to Microsoft Outlook setting.

• • • msiexec /i c:\work\Webex.msi ENABLEOUTLOOKINTEGRATION=0 ALLUSERS=1

On Windows, the Webex App does not register with Microsoft Outlook, which prevents presence interaction. (default).

By default, this configuration causes the Connect Webex to Microsoft Outlook feature to be disabled across the board for all users. To modify this setting, you will need to have access credentials for the administration section.

FORCELOCKDOWN

Only applies to the bundle install products in this case. If the current version of the meetings desktop software is compatible with the meeting site, the app will be locked. To make those kinds of changes, you need administrative responsibilities.

Example: msiexec /i WebexBundle.msi FORCELOCKDOWN=LockWhenCompatible

INSTALL_ROOT

Identifies the location in which the Webex App will be installed.

Example: msiexec /i c:\work\Webex.msi INSTALL_ROOT="C:\Program Files" ALLUSERS=1

INSTALLWV2

When you install Webex App, it will also install the WebView2 integrated browser developed by Microsoft.

This built-in browser is necessary for the Webex App.

Example: msiexec /i c:\work\Webex.msi INSTALLWV2=1

Running the app

Webex App comes with its own built-in automatic update system, which is not contingent on the Windows operating system in any way. Because the application has the ability to update itself automatically without the awareness of the Windows operating system, the version of the application that is installed on the user’s device may differ from the version that the user sees while using the application.

• Mac

Installing

Users are exempt from the requirement that they have administrator access capabilities on their computers in order to install the Webex App.

Users will install it by launching the Webex.dmg file and clicking it twice. Users are able to drag and drop Webex App to any other directory of their choosing; however, the typical installation location for Webex App is the Applications folder.

To determine which version of Webex App is currently installed on your device,

By executing the Messaging App Version Report, administrators are able to determine which version of the app their users have installed on their devices.

Bulk install

You have the ability to prepopulate Webex App with the user’s email if you are an administrator and you use the Mac defaults command along with the LoginHint parameter.

defaults write Cisco-Systems.Spark LoginHint -string "<user-email@example.com>"

To disable the prepopulating, use the following command:

defaults delete Cisco-Systems.Spark LoginHint

Running the app

The application possesses its very own autoupdate system, which operates independently from the installation procedure of the operating system. Using the technology provided by the operating system, the application is only ever installed once. After that, the program will perform subsequent updates automatically, oblivious to the presence of the operating system. Because of this, the version of the app that is installed on your device may differ from the version that is displayed while you are actually using the app.

Update process

It typically takes a week for a new version to become available to everyone. Users have the ability to check for changes at any time during those seven days. Users are able to view Update the app to the latest release.

After the rollout timeframe of seven days has passed, the update will be applied automatically.

If you have the Pro Pack for Control Hub, you will have the ability to verify the app version that each of your users is using. Check out the Version Report for the Messaging App in Analytics for your cloud collaboration portfolio.

When you have the Webex App running, it will check for updates on a regular basis to see if there is a more recent version of the app accessible. When a later version is released, the application will automatically download the updated version and save it to the local computer:

• On Windows:

  C:\Users\<username>\AppData\Local\CiscoSparkLauncher

  C:\Users\<username>\AppData\Local\CiscoSpark

  C:\Users\<username>\AppData\LocalLow\WebEx

  C:\Users\<username>\AppData\Local\WebEx

• On MacOS:

  ~/Library/Application Support/Cisco Spark

These directories contain both the application’s current version and its upcoming version; this allows the application to revert to the previous version in the event that the upgrade is unsuccessful.

In the event that we issue a patch for a release, we will send out the update to all organizations within a rollout window of three days.

Administrator controls to manage releases

You have the ability to customize the refresh interval for the Webex App with the Product update controls.

Uninstall the Webex App

• Windows

To uninstall the app use msiexec /x Webex.msi.