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.
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.
Turning on Maintenance Mode
is not required to change these properties.
Sign in to the
System and select
More in the Servers section.
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. See
About Maintenance Mode for information about which system
tasks require Maintenance Mode to be turned on.
Enter the fully qualified
domain name (FQDN) of a mail server that the system will use to send emails.
enabled to enable Transport Layer Security (TLS). (Basic
authentication is enabled by default.)
Port field to change the default value.
The SMTP default
port numbers are 25 or 465 (secure SMTP port).
The Web node and Admin node send SMTP requests to the configured
Email server. If there is a firewall between the internal Web and Admin virtual
machines and the Email server, the SMTP traffic might be blocked. To ensure
Email server configuration and Email notification work properly, port 25 or 465
(secure SMTP port number) must be open between the Email server and the Web and
the Admin virtual machines.
(Optional)Enable mail server
authentication enabled. If you enable authentication, enter the
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
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.
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.
Tools > Developer
At the top of the Developer
Tools window, select
Document Mode: IE7
Standards > Internet Explorer 10 Standards.
From the Administration web site, navigate to Settings > Company Info
Select the local
Time Zone for this system from the drop-down list.
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.
Enter the first
and last names of the administrator.
complete administrator email address and confirm it by entering it again.
Next to create the initial password.
Enter a password
and confirm it by entering it again.
Submit to sign in to the WebEx Administration site.
Sign into the
system and add administrators and users. Upon creation of each new account, the
system sends an email to that person, welcoming them and asking that user to
sign in and change the initial password.
sign in, each administrator is offered a tutorial of the system. The
administrators can view the tutorial immediately or view it on demand.
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.