Previous Topic

Next Topic

Specifying upgrade management settings

The Upgrade Management screen enables you to specify how upgrades to the Cisco WebEx Connect application and Cisco Jabber application should be rolled out to users in your organization. You can roll out upgrades using the following upgrade modes:

  • Default: where all users are automatically upgraded to the latest version of Cisco WebEx Connect and Cisco Jabber. This is the default upgrade mode.
  • Custom: where you can manually configure how you want to roll out the upgrades to users. In this case, you need to select a baseline version and create an upgrade task, which defines how the upgrades are rolled out.

You can switch between the two upgrade modes at any point time but this has an impact on how upgrades are rolled out. For example, if you select a specific version (using the Custom mode) to roll out to users, and then change the mode to Default and users will be upgraded to whatever is the default version of the client at that time, except if they were on a version that was later than the default version.

You can set a baseline version if you want all your users on the same version of the application. This requires all users that are on older versions to upgrade but users on newer application versions than the baseline are not required to downgrade.

Setting a baseline version



Note: Setting the baseline version is OPTIONAL. We recommend that the baseline version is set to the version of application you require all your current and future users to be running as the minimum version.

Setting a baseline version ensures that any new users you provision will download the version of the client that you have set as your baseline.

You can upgrade one or more of your users to a version of the application higher than the baseline by creating an Upgrade Task. However, the upgrade management service prevents users from running any earlier version of the application. Any user on a version earlier than the baseline are immediately asked to upgrade to the baseline version at login. Setting a baseline version ensures that all your current and new users will at least be running that version of the application.

If you decide not to set a baseline version, any new user you provision is directed to download the current default version of the application.

To set a baseline version:

  1. In the Upgrade Mode section, select Change to view the available upgrade modes.



  2. Select the baseline as applicable.



  3. Select the version to deploy and select OK.



    Note: If you do not select a baseline, the following message is displayed:

    You have not set baseline versions.

    The URL in the Welcome email to download the Cisco WebEx Connect client will be directed to the latest versions of Cisco WebEx Connect for both platforms.



  4. Select Yes to view the selected version on the Upgrade Management screen listed under Baseline Versions. If you have selected an older version (than the latest version) in step 6, all newer versions are displayed above Baseline Versions.




  5. Select Download next to the applicable version to download the application. This step is OPTIONAL.
  6. Select Release Notes next to the release notes for that version.



    Note: The version listed under Baseline Versions is the version that is deployed to your organization.


Creating an upgrade task



To create an upgrade task:

  1. Select the Configuration tab to display the Organization Information screen.
  2. Under Connect Client, select Upgrade Management
  3. Select Create Upgrade Task to open the Create Upgrade Task for Windows in the Upgrade Management work area.



  4. From the Target Version drop down list, select the applicable version to deploy.


    Note: You need to select a version higher than the previously set baseline as the target version.

  5. Select Provide Customized URL to specify a custom link from where the Cisco WebEx Messenger Setup Program can be downloaded. This field is optional.
  6. In the Optional Upgrade box, select a date and time on which the upgrade will be optionally deployed. Or select Skip to skip applying the optional upgrade.
  7. In the Mandatory Upgrade box, select a date and time on which the upgrade is deployed. Or select Skip to skip applying the mandatory upgrade.
  8. From the Time Zone drop down list, select the time zone based on which the upgrade is deployed. The date and time that you select for optional and mandatory upgrades are calculated according to this time zone.
  9. Under Target User, select:
    • All users: to deploy the upgrade to all the users in your organization.
    • Specific Upgrade Sites: to deploy the upgrade to the selected upgrade sites. In this case, the upgrade will be deployed to all users within those sites. If no upgrade sites are listed, you will need to create them. For more information, see Creating upgrade sites.
  10. Select Save to save the upgrade task. The upgrade is displayed on the Upgrade Management page.



To edit or cancel an upgrade task:

  1. Select Edit to edit the details of the upgrade task.
  2. Select Close Upgrade Task to display (and cancel the deployment) as shown in the following graphic.



  3. Select Yes to delete the upgrade task.

Top of Page   Print