The performance of the Webex app may also be influenced by other factors, for example: network connectivity or other applications on your devices.


Keep in mind that we don't support using Webex with pre-release or early release programs, such as the Apple Beta Software, Windows Insider Program, or any other similar programs.

Windows

Windows PCs Recommended Minimum System Requirements


These requirements are continuously reviewed and may be revised.

Mac

Mac Recommended Minimum System Requirements


These requirements are continuously reviewed and may be revised.

  • MacOS 10.12 and later.

  • M1 chip or Intel CPU-based (4 GB of RAM minimum recommended).

The Webex app installs to the same system folder every time it's updated to a new version.


To view what version of the Webex app is installed, see Find Your App Version.

Installing

To install the Webex app, users don't need to have administrator access privileges on their machine.

Webex can be installed either per machine or per user and can be installed by users or IT administrators. When users install Webex they can download the app and then open the Webex.msi file to install it. The browser automatically detects if the users operating system is 32-bit or 64-bit and downloads the correct version of theWebex app. By default, the app is installed in the following folder %LocalAppData%\Programs\Cisco Spark.

Administrators, can run the installer with additional privileges and then they can choose per machine installation and the installation directory.

As an administrator, if you want to access a specific version of the app, use the following options:

For bulk installations, you can use the MSI file with a third-party distribution mechanism to bulk install Webex to select users or computers.

When you install Webex with the MSI file, you can add the following command line parameters. When you use the ALLUSERS=1 property to specify a per machine installation, you must have administration access privileges.

  • Silent installation

    You can include /quiet and there is no user interaction. For example: msiexec /i c:\work\Webex.msi /quiet.

  • ACCEPT_EULA

    You can choose to accept the end user licence agreement for users and users won't get a prompt to accept the end user licence agreement. For example: msiexec /i c:\work\Webex.msi ACCEPT_EULA=TRUE ALLUSERS=1.


    The end user license agreement is not displayed if either of the following registry entries are set to eula-disabled

    • HKEY_LOCAL_MACHINE\Software\CiscoCollabHost\Eula Setting

    • HKEY_LOCAL_MACHINE\Software\WOW6432Node\CiscoCollabHost\Eula Setting

  • EMAIL

    You can specify an email for a user and Webex uses the email to sign that user in to the Webex app. When your organization uses an authentication method, for example Kerberos, the user is automatically signed into Webex. For example: msiexec /i c:\work\Webex.msi EMAIL=acassidy@example.com ALLUSERS=1.

  • INSTALL_ROOT

    Choose a different folder to install the app using a command line parameter. For example: msiexec /i c:\work\Webex.msi INSTALL_ROOT="C:\Program Files" ALLUSERS=1.

  • DELETEUSERDATA

    By default, when you run the installer to update the Webex app, any user database or log files are retained. If you want to remove these files you can include the command line parameter: DELETEUSERDATA=1. For example, msiexec /i c:\work\Webex.msi DELETEUSERDATA=1 ALLUSERS=1.

  • AUTOSTART_WITH_WINDOWS

    When installing Webex, if you have administration access privileges, you can specify that Webex will automatically start with Windows using the AUTOSTART_WITH_WINDOWS=true property. If you don't specify the property option, the default value is set as true.

    • Specify Webex will automatically start with Windows. For example: msiexec /i c:\work\Webex.msi AUTOSTART_WITH_WINDOWS=true ALLUSERS=1.


      The checkbox in Settings will be grayed out for all users, you must have administration access privileges to change this option.

    • Specify Webex won't automatically start with Windows. For example: msiexec /i c:\work\Webex.msi AUTOSTART_WITH_WINDOWS=false ALLUSERS=1.

      Users can select or deselect the checkbox in Settings themselves.

  • ENABLEOUTLOOKINTEGRATION

    When installing Webex, if you have administration access privileges, you can specify that Webex will register with Microsoft Outlook for presence integration with Windows using the ENABLEOUTLOOKINTEGRATION=1 property. If you don't specify the property option, the default value is set as false.

    • Specify that Webex will register with Microsoft Outlook for presence integration on Windows. For example: msiexec /i c:\work\Webex.msi ENABLEOUTLOOKINTEGRATION=1 ALLUSERS=1.

      Users can select or deselect the checkbox in Settings themselves.

    • Specify that Webex won't register with Microsoft Outlook for presence integration on Windows. For example: msiexec /i c:\work\Webex.msi ENABLEOUTLOOKINTEGRATION=0 ALLUSERS=1.

      The checkbox in Settings will be grayed out for all users, you must have administration access privileges to change this option.

Running the App

Webex has its own automatic update solution that is independent from the Windows operating system. The app can automatically update without the knowledge of the Windows operating system, so the installed version of the app may be different from the version the user sees while using the app.

Installing

To install the Webex app, users don't need to have administrator access privileges on their machines.

Users double-click the Webex.dmg file to install it. By default, the Webex app is installed in the Applications folder, however users can drag and drop the Webex app to any other directory.


To view what version of the Webex app is installed, see Find Your App Version.

Running the App

The app has its own auto-update solution, independent from the operating system's installation mechanism. The app is only installed once using the operating system mechanism. After that, the app automatically updates without the knowledge of the operating system. Therefore, the installed version of the app might be a different version than the one you see while using the app.

As an administrator you can download a single installer that includes the Webex app and the Webex Meetings app.

Install

When you install Webex app and the Webex Meetings app with the EXE file, you can add the following command line parameters. When you use the ALLUSERS=1 property to specify a per machine installation, you must have administration access privileges.

  • ACCEPT_EULA

    You can choose to accept the end user licence agreement for users and users won't get a prompt to accept the end user licence agreement. For example: c:\work\WebexBundle.exe ACCEPT_EULA=TRUE ALLUSERS=1.


    The end user license agreement is not displayed if either of the following registry entries are set to eula-disabled

    • HKEY_LOCAL_MACHINE\Software\CiscoCollabHost\Eula Setting

    • HKEY_LOCAL_MACHINE\Software\WOW6432Node\CiscoCollabHost\Eula Setting

  • EMAIL

    You can specify an email for a user and the Webex app and the Webex Meetings app uses the email to sign that user in to the apps. When your organization uses an authentication method, for example Kerberos, the user is automatically signed into Webex. For example: c:\work\WebexBundle.exe EMAIL=acassidy@example.com ALLUSERS=1.

  • INSTALL_ROOT

    Choose a different folder to install the app using a command line parameter. For example: c:\work\WebexBundle.exe INSTALL_ROOT="C:\Program Files" ALLUSERS=1.

  • AUTOSTART_WITH_WINDOWS

    If you have administration access privileges, you can specify that Webex will automatically start with Windows using the AUTOSTART_WITH_WINDOWS=true property. If you don't specify the property option, the default value is set as true.

    • Specify that Webex will automatically start with Windows. For example: c:\work\WebexBundle.exe AUTOSTART_WITH_WINDOWS=true ALLUSERS=1.


      The checkbox in Settings will be grayed out for all users, you must have administration access privileges to change this option.

    • Specify that Webex won't automatically start with Windows. For example: C:\work\WebexBundle.exe AUTOSTART_WITH_WINDOWS=false ALLUSERS=1.

      Users can select or deselect the checkbox in Settings themselves.

When a release is made generally available, it can take 7 days for it to roll out to all users. During those 7 days, users can update the version of the app by either restarting the app or clicking .

If you have the Pro Pack for Control Hub add-on service, you can check what version of the app your users are on. See the Messaging App Version Report in Analytics for your cloud collaboration portfolio.

After the 7 day rollout window, the update is automatically applied.

When Webex is running, it periodically checks to see if there is a newer version of the app available. When a newer version becomes available, the app automatically downloads the new version and stores it on the local computer:

  • On Windows, it is the following folders in the user's profile:

    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, it is a folder in the user's Application support folder: ~/Library/Application Support/Cisco Spark

Updated copies of the application are stored in this folder, including the current version. This way, if an upgrade fails, the app can fall back to a previous version.

For any patches done for a release, there is a 3 day rollout window before all organizations are updated.

You can choose to set the frequency for Webex updates for users in your organization.


These controls are not yet available for Webex for Government.

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

To uninstall Webex, go to the Applications folder and drag Webex to the trash.

As an administrator you can secure the Webex app on your user's mobile devices. The solutions we support include MDM/MAM with Microsoft Intune, MDM/MAM with AppConfig, app wrapping using the iOS IPA files and the Android AAB files, and admin controls for mobile management

For more information, see Secure Mobile Devices.