The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Configure an Email server to enable your system to send meeting invitations and other communications to users.
It is important that the Email server is always operational. Email is the primary method of communication with your users including recording notifications, meeting information changes, account status, and many other important announcements. (See also Adding Users.)
Users are identified to the system by Email address. If a user Email address is changed and the user remains active, the Email address on CWMS must also be changed or that user will not receive notifications.
Note | Turning on Maintenance Mode is not required to change these properties. |
Step 1 | Sign in to the
Administration site.
In a Multi-data Center system, the DNS determines which data center Dashboard appears. All data centers can be managed from this Dashboard. | ||
Step 2 | Select System and select View More in the Servers section. | ||
Step 3 | Turn on Maintenance Mode. See
Turning Maintenance Mode On or Off for Version 2.5 and Later.
Unless you are expanding a system, we recommend that you take a snapshot of each virtual machine. (See Taking a Snapshot by using VMware vCenter.) Turning on Maintenance Mode on all active data centers shuts down conferencing activity and prevents users from signing in to the WebEx site, scheduling meetings, joining meetings, or playing meeting recordings. If this data center is part of a Multi-data Center (MDC) system and another data center is active, in-progress meetings will fail over to the active data center. This might cause a brief interruption in active meetings. See About Maintenance Mode for information about which system tasks require Maintenance Mode to be turned on. | ||
Step 4 | In the SMTP Server section, select Edit. | ||
Step 5 | Enter the fully qualified domain name (FQDN) of a mail server that the system will use to send emails. | ||
Step 6 | (Optional)Select TLS enabled to enable Transport Layer Security (TLS). (Basic authentication is enabled by default.) | ||
Step 7 | (Optional)Edit the
Port field to change the default value.
The SMTP default port numbers are 25 or 465 (secure SMTP port).
| ||
Step 8 | (Optional)Enable mail server
authentication, select
Server
authentication enabled. If you enable authentication, enter the
Username and
Password credentials necessary for the system to
access the corporate mail server.
Emails from the system are sent by admin@<WebEx-site-URL>. Ensure that the mail server can recognize this user. For micro, small, or medium systems, email notifications come from the administration virtual machines (either the primary or high-availability system). For large systems, email notifications come from the web virtual machines (either on the primary or high-availability system). In a large system, there are three web virtual machines on the primary system and one web virtual machine on the high-availability system. | ||
Step 9 | Select Save. |
See Activating or Deactivating Users and Administrators from the Users Page, Adding Users, and Editing Users.
If you are running Windows 7 and have your Cisco WebEx site open in an Internet Explorer 10 browser, you may want to select the document Internet Explorer 10 standards to make sure all the buttons in the application work properly.
The system creates a First Administrator account. This administrator must sign into the system, create a password, and add other administrators. Until then, no other administrator can have access to the system. As part of the process, the First Administrator can create an Auditor account, separating the administrator and auditor. This can be done as part of the deployment process or the First Administrator can create an Auditor (Adding an Auditor Role.) ). (See
A mail server for the system to use to send emails to administrators must be configured. See Configuring an Email (SMTP) Server for instructions.
The First Administrator has the Auditor role by default, and is the only one who can activate the Auditor role for another user. When doing so, the Auditor privileges are taken away from the First Administrator. If an Auditor is also a System Administrator, that person has a System Auditing role.
The Auditor role separates administrative actions from system monitoring as follows:
If the Administrator and Auditor roles are not separated, only Administrator and Hosts roles exist; administrators have all the authority.
If the Administrator and Auditor roles are separated when the system is deployed, a First Administrator role is created (described as the emergency account). After system deployment, only the First Administrator emergency account can create an Auditor, taking the Auditor privileges away from administrators. The First Administrator can create as many auditors as desired after the system has been deployed.
Auditor parameters (such as the name) can be modified, but once created the Auditor role cannot be deactivated or reassigned to another user ID.
An Auditor cannot modify user parameters.
An Auditor does not have Host privileges and cannot schedule meetings by using the Auditor account. An Auditor can attend meetings as a participant.
Most of the system test are accomplished by using the CWMS system, for example by Using the Meetings Test and Using the System Resource Test.
When testing an upgraded system, you can keep the original system until you have finished testing the upgraded system (but because they share some parameters, such as IP addresses, you cannot power on both systems at the same time). Once you are satisfied with the results of the upgraded system tests, you can remove (forever) the original system. Be sure your upgraded system is running when removing the original system. This prevents accidental removal of the base virtual machine disk (VMDK) file that must be accessed by the upgraded system.
Some of the recommended tests to run on the system are.
Add, edit, activate, and deactivate users. (See Managing Users.)
Schedule and hold a meeting.
Reschedule an existing meeting.
Delete a series of scheduled meetings.
Add and open a meeting attachment from the meeting invitation.
Record a meeting and play back the recording.
The system can also be tested by: