Static resources are cached to enhance the performance of web pages; however, the data cached can be incorrect. Therefore, we recommend that you clear your browser cache.
|| Go to the
license manager on the original system and generate a license request by
manager opens in a new tab.
appears with the license request text. Copy the text and save the license
request in a convenient location as it might be necessary to use the manual
re-host procedure to reclaim your licenses. This information can also help
Cisco to find your licenses. (See
Fulfilling Licenses by Using the License Manager.)
vSphere client, deploy the Admin virtual machine (by using the temporary IP
address) for the upgraded system by selecting the
configuration with the
suffix, for example
Admin Auto-upgrade. Use the same host as the original system Admin
||Verify that the
Upgrade Administration virtual machine can reach the original system disks.
Administration virtual machines are on the same ESXi host and have access to
the same data stores, therefore they should be able to view both sets of disks.
The datastore used by the Administration virtual machine datastore (vmdk) files
should be visible through the vCenter (by using the same vCenter credentials
that the automatic upgrade process uses).
||Power on the
Administration virtual machine for the upgraded system and write down the
deployment URL displayed on the virtual machine console.
deployment URL into a web browser URL field.
Administration and vCenter URLs and credentials, so we can deploy the virtual
machines for you. (See
Providing VMware vCenter Credentials.)
||To deploy any
additional virtual machines, select
Until you begin
the setup of the upgraded system and the original system is placed in
maintenance mode, users can hold meetings, but administrators should not modify
the original system virtual machines.
||Note the names
of the automatically-created virtual machines listed in vCenter.
The format for
virtual machine names is
When the upgrade
is complete, the virtual machines do not display. To find the virtual machines
that were created as part of the CWMS upgrade, you can search based on this
The progress of
the upgrade is displayed on the deployment URL of the upgraded system and on
the VMware console connected to the primary system Admin virtual machine. The
VMware console provides the deployment URL to use in case the browser window
inadvertently closes during the upgrade process.
put the system in maintenance mode and begin the setup of the upgraded system,
message displays when Maintenance Mode is enabled, which might take up to 30
||To launch the
upgraded Cisco WebEx Administration site, select
Sign In to
Administration Site and sign in.
||Wait for the
system to come to a good state, then turn off maintenance mode on the upgraded
system and select
It can take a few minutes for the meeting service to become available. Your system is ready for users to start meetings when all the virtual machines listed on the System Properties page display a status of Good (green). See Turning Maintenance Mode On or Off.
upgraded system. (See
About System Testing.)
upgraded system is running satisfactorily, you can delete your original system
to free the original system resources. Keep the upgraded system running while
deleting the original system to prevent the accidental removal of the Hard disk
4 base VMDK file that might be accessed by the upgraded system.
If the upgrade
is unsuccessful, power off the upgraded system, power on the original system,
and contact Cisco TAC.
update the license version as appropriate for the upgraded system. (See
About Host Licenses
Re-hosting Licenses after a Major System Modification).
previously deployed Cisco WebEx Meetings Application or Productivity Tools are
different versions or build numbers from a newly deployed version of the
application and the upgrade is not blocked, you are notified by an upgrade
warning dialog box. It might be necessary to push the Cisco WebEx Meetings
Application or Productivity Tools to the users.
Meetings Application and Productivity Tools Compatibility Matrix section
of the Cisco WebEx Meetings Server Planning Guide, found at
180 days or less the license-free grace period shall expire. If the original
system had valid licenses, those licenses must be re-hosted in 180 days or
less. If the original system was operating in the license-free grace period,
the remaining unexpired days are transferred to the upgraded system.