Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4
Installing Web Conferencing
Downloads: This chapterpdf (PDF - 201.0KB) The complete bookPDF (PDF - 1.85MB) | Feedback

Installing Web Conferencing

Table Of Contents

Installing Web Conferencing

About the Web Conferencing Installation

About SQL Server Integration

MSDE Database Size

MSDE Database Scalability

About SQL Server Installation Options

About Sun Java Runtime Environment

Preinstallation Tasks: Web Conferencing

Installing Cisco Unified MeetingPlace Audio Server

Installing SQL Server on a Remote Server

Creating a Least Privileged SQL Account

Assigning Installation and Ongoing Rights

Assigning Server and Database Roles

Gathering Web Conferencing Installation Values

Installation Tasks: Web Conferencing

Installing the Operating System on the Cisco MCS Server

Installing Web Conferencing

Testing the Web Conferencing Installation

Defining the Web Conferencing Server

Testing the Web Server Over an HTTP Connection

Testing the Web Server Over an HTTPS Connection

Testing the Meeting Console Connection


Installing Web Conferencing


This chapter describes how to complete a new installation of Cisco Unified MeetingPlace Web Conferencing. It does not describe upgrades. (For information about upgrading, see the "Upgrading to Web Conferencing Release 5.4" chapter.)

This chapter contains the following sections:

About the Web Conferencing Installation

Preinstallation Tasks: Web Conferencing

Installation Tasks: Web Conferencing

Testing the Web Conferencing Installation


Note Before reviewing this chapter, please read System Requirements for Cisco Unified MeetingPlace Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html. New installations of Release 5.4 require a Cisco MCS.


About the Web Conferencing Installation

Before you begin installing Cisco Unified MeetingPlace Web Conferencing, make sure that you understand the following concepts:

About SQL Server Integration

About SQL Server Installation Options

About Sun Java Runtime Environment

About SQL Server Integration

Cisco Unified MeetingPlace Web Conferencing is closely integrated with Microsoft SQL Server. It uses Microsoft SQL Server for its databases: MPWEB and MPWEB-Slave-######.

All new servers being deployed must be either Cisco MCS or, for Cisco Unified MeetingPlace customers with a legacy system, Cisco MCS-equivalent servers.

Cisco Unified MeetingPlace Web Conferencing comes with a distributable version of SQL Server called MSDE 2000. Although MSDE 2000 and SQL Server 2000 are based on the same technology, MSDE 2000 does not scale as well as SQL Server 2000. Because of this by-design limitation, Cisco Unified MeetingPlace Web Conferencing customers running MSDE 2000 can encounter performance and scalability-related problems when their usage of Cisco Unified MeetingPlace Web Conferencing grows.

The following sections provide information about how to anticipate and diagnose performance and scalability limitations related to MSDE:

MSDE Database Size

MSDE Database Scalability

MSDE Database Size

MSDE limits the database size to 2 GB. If either the MPWEB or the MPWEB-Slave database reaches 2 GB, the Cisco Unified MeetingPlace Web Conferencing application can fail. Therefore, you must monitor the growth of the MPWEB databases and take one of the following actions before either database reaches 2 GB:

Set a more aggressive value for the Purge Meetings Held Before (Days) parameter in MeetingNotes.

Upgrade to a full version of SQL Server with a per processor license, as this does not have a database size limitation.

MSDE Database Scalability

MSDE implements a concurrent workload throttle mechanism to limit scalability under heavy load. Currently, this mechanism activates when more than eight SQL queries execute concurrently. However, there is no direct mapping between the number of active web-conferencing users and the exceeding of this limit.

Rather, the exceeding of this limit depends on the following:

Number of active users.

Features that are used at any given time and how these features interact with the database.

Current size of the database.

Power of the server (for example, CPU and disks).

Although Microsoft does not give information about the specific algorithm that is used to implement this concurrent workload throttle mechanism, our tests show that the slowdown is based on the number of SQL queries that exceed the limit of eight queries. For example, if 10 concurrent queries execute, the slowdown is minimal. If 20 concurrent queries execute, the slowdown is more noticeable. If 40 or more concurrent queries execute, the slowdown can become so significant that users find Cisco Unified MeetingPlace Web Conferencing as unresponsive or non-functional.

About SQL Server Installation Options

To ease installation, Cisco Unified MeetingPlace Web Conferencing is bundled with both Microsoft SQL Server and Microsoft SQL Desktop Engine (MSDE). You can choose to install SQL Server on either the same machine as Cisco Unified MeetingPlace Web Conferencing or, for better performance, on a separate machine.

If you choose to install SQL Server on the same machine as Cisco Unified MeetingPlace Web Conferencing, choose Local as your SQL Server database location during your installation. If the installer fails to detect a version of SQL Server 2000 on your local system, it installs both SQL Server 2000 and the appropriate service pack for you automatically. No additional steps are required.


Note Check System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html for the required service pack.


If you choose to install SQL Server on a separate machine, install both SQL Server 2000 and the appropriate service pack before installing Cisco Unified MeetingPlace Web Conferencing, then on the MCS, install Cisco Unified MeetingPlace Web Conferencing. During installation, choose Existing Remote as your SQL Server database location and enter the appropriate SQL access information.

Table 2-1 describes conditions that must be met for Cisco Unified MeetingPlace Web Conferencing to automatically install either SQL Server or MSDE.

Table 2-1 Conditions for Automatic SQL Server Installation 

If These Conditions Are Met...
Cisco Unified MeetingPlace Web Conferencing Will...

You install Cisco Unified MeetingPlace Web Conferencing on a Cisco MCS server or a Cisco MCS-equivalent server that accepts the installation of the Cisco MCS server OS image.

During installation, you specify the SQL Server location as Local.

The installer does not detect an existing installation of SQL Server on the local server.

Install a full version of SQL Server 2000.

You install Cisco Unified MeetingPlace Web Conferencing on a non-Cisco MCS server.

You specify the SQL Server installation location as Local during the Cisco Unified MeetingPlace Web Conferencing installation.

The installer does not detect an existing installation of SQL Server on the local server.

Install MSDE.

During installation, you specify the SQL Server installation location as Remote. (This option requires that you install either full SQL or MSDE on the remote server before you install Cisco Unified MeetingPlace Web Conferencing.)

OR

You specify the SQL Server installation location as Local, but the Cisco Unified MeetingPlace Web Conferencing installer detects that SQL or MSDE is already installed on the local server.

Not install SQL Server or MSDE.

You install Cisco Unified MeetingPlace Web Conferencing on a Cisco MCS server.

You install a full version of SQL Server on the same Cisco MCS server, or it already exists locally.

Install the SQL Server service pack.

Note If the SQL Server service pack is not installed automatically, download the appropriate service pack from the Microsoft website and do a manual install.


About Sun Java Runtime Environment

Cisco Unified MeetingPlace Web Conferencing requires a particular version of Sun Java Runtime Environment (JRE) (refer to System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html). If you currently have Sun JRE installed on the machine where you are installing Cisco Unified MeetingPlace Web Conferencing, make sure that it is a supported version. Otherwise, the installer will stop and prompt you to uninstall Sun JRE before attempting your Cisco Unified MeetingPlace Web Conferencing install again.

If you do not have Sun JRE installed, the installer loads it for you automatically. No additional steps are required.

Preinstallation Tasks: Web Conferencing

Before attempting to install Cisco Unified MeetingPlace Web Conferencing, refer to System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html for updated system requirements. When reviewing the requirements, note the following considerations:

If you are installing Web Conferencing in a segmented meeting access configuration, that is, allowing external access, also see the "Installing Web Conferencing for a Segmented Meeting Access Configuration" chapter in this guide.

If you are installing Web Conferencing in a load balancing configuration, also see the "Installing Web Conferencing in a Load Balancing Configuration" chapter in this guide.

After reviewing system requirements, complete the following preinstallation tasks:

1. Installing Cisco Unified MeetingPlace Audio Server

2. (Optional) Installing SQL Server on a Remote Server

3. Creating a Least Privileged SQL Account

4. Gathering Web Conferencing Installation Values

Installing Cisco Unified MeetingPlace Audio Server

You must install and configure Audio Server software on a Cisco Unified MeetingPlace 8100 series server before you begin the Web Conferencing installation. (Refer to the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.)

Installing SQL Server on a Remote Server

Cisco Unified MeetingPlace Web Conferencing requires SQL Server. You can choose to install SQL Server (or MSDE) on either the same machine as Web Conferencing or on a separate machine.

If you choose to install SQL Server on a separate machine, install both SQL Server 2000 and the appropriate service pack on a separate Windows machine before installing Web Conferencing. This can be a Cisco MCS or legacy non-Cisco MCS.


Note While we support Microsoft SQL Server Database Engine (MSDE), we strongly recommend that all Cisco Unified MeetingPlace systems, particularly production systems, use a fully licensed SQL Server.


Creating a Least Privileged SQL Account

By default, Cisco Unified MeetingPlace Web Conferencing uses the SQL and MSDE built-in sa administrator account to connect to its database. Depending on your server hardware and the options that you choose during installation, Web Conferencing may install SQL or MSDE for you. For more information about SQL and MSDE installation, see the "About SQL Server Integration" section.

During the SQL or MSDE installation, you will be asked to set a password for the sa account. Be sure to set a strong password, without spaces. Often, a strong password is sufficiently secure to protect your system from unauthorized access. However, if you do not want to use a SQL account that has full administration rights, you can create a least-privileged SQL account for use by Web Conferencing.


Caution If you choose to create a SQL account that is dedicated to Web Conferencing use, ensure that it meets all the specified requirements in this procedure. Failure to do so can cause a database connection failure between Web Conferencing and the SQL Server and result in a total outage or broken features.


Note If Cisco TAC determines that your SQL account does not meet requirements, you will be asked to reconfigure your SQL account and to delete any existing Cisco Unified MeetingPlace Web Conferencing database so that a new database can be created once the account problem is remedied.


The Web Conferencing installer does not verify the existence of the SQL account or the validity of its user name and password combination. As such, you must confirm that the SQL Server account that you plan to use exists and that it conforms to the required access rights before you install Web Conferencing. Therefore, to create a SQL account that you can use to access the Cisco Unified MeetingPlace database with authentication, do the procedures in the following:

Assigning Installation and Ongoing Rights

Assigning Server and Database Roles

Assigning Installation and Ongoing Rights

During the installation of Cisco Unified MeetingPlace Web Conferencing, you are prompted to enter a SQL Server user name and password. This SQL Server user must have the right to log in to the SQL Server instance that you specify during the installation. To assign and verify rights, do the following procedure.

To Assign Installation and Ongoing Rights


Step 1 Assign the following additional rights to the SQL Server user:

Create Database

Create Table

Create Default

Step 2 (Optional) After the installation is complete, remove the Create Database right from this SQL Server user.

Step 3 Confirm that the SQL Server user has the following rights for all tables in the MPWEB database:

Select

Insert

Update

Delete


Note This user must be able to alter the MPWEB database.


Step 4 Continue with the next section, "Assigning Server and Database Roles."


Assigning Server and Database Roles

SQL Server provides some built-in roles that simplify the process of granting and denying rights.

Note that you cannot assign database roles until after the database is created. Therefore, wait until Cisco Unified MeetingPlace Web Conferencing completes installation before you assign roles.

To Assign Server and Database Roles


Step 1 To create a user with the proper rights for Cisco Unified MeetingPlace Web Conferencing, use the SQL Server Enterprise Manager to create a user and assign the following server role:

dbcreator

Step 2 Assign the following database roles for the MPWEB database:

public

db_datareader

db_datawriter

db_ddladmin

db_owner


Troubleshooting Tips

If you receive the error below, change the owner of the MPWEB database by entering the following command: exec sp_changedbowner 'sa'. This launches a procedure that is stored in the MPWEB database.

Error 21776: [SQL-DMO] The name 'dbo' was not found in the Users collection.
If the name is a qualified name, use [] to separate various parts of the name,
and try again.

For more information about this error, see Microsoft Knowledge Base Article 305711, BUG: DBO User Does Not Display in Enterprise Manager.

Gathering Web Conferencing Installation Values

Gather and record the information in Table 2-2 to prepare for your installation of Cisco Unified MeetingPlace Web Conferencing.

Table 2-2 Installation Values for Cisco Unified MeetingPlace Web Conferencing 

Parameter
Description and Value

Hostname of MeetingPlace Server

This parameter refers to the Cisco Unified MeetingPlace Audio Server system hostname. If you are installing multiple web servers that share a database and point to the same Audio Server system, make sure that the Audio Server hostname on all of these web servers match.

Note If a connection exists between the web server and the Audio Server system—that is, if there is no firewall between them, port 5003 is not blocked, and the Audio Server system is up and running—then you can use an IP address instead of a hostname. However, using an IP address prevents you from taking advantage of the Audio Server system's reverse connection feature, which allows the Audio Server system to initiate a connection to the web server when port 5003 is blocked inbound.

Hostname:

IP address:

Notes:

Location of web server

Internal (Full Access)—Cisco Unified MeetingPlace Web Conferencing is installed with all features enabled, and this server is placed inside your corporate network. In Segmented Meeting Access-2 Server (SMA-2S) deployments, this server functions as the internal web server.

External (Limited Access)—Cisco Unified MeetingPlace Web Conferencing is installed with attend-only capability. In SMA-2S deployments, this server is placed outside your corporate firewall in an Internet-accessible network, such as a DMZ, and functions as the external web server.

Both—Depending on the release of Cisco Unified MeetingPlace Web Conferencing, you may see this option referred to as Both (Full Access) or Both (SMA-1S).

Web Conferencing is installed on a single machine but configured to host two websites. One website provides a full-access user interface to internal users, and the second website provides attend-only access to Internet users. This server is placed in the DMZ and is the definition of a Segmented Meeting Access-1 Server (SMA-1S) deployment.

Note While the Both configuration has some security benefits, we strongly recommend the SMA-2S deployment for maximum security.

(For more information on SMA configurations, see the "Installing Web Conferencing for a Segmented Meeting Access Configuration" chapter.)

Web server location:

Notes:

Hostname or static IP address of web server

Segmented meeting access (SMA) configurations require two hostnames or IP addresses: one for the internal web server or site, and one for the external web server or site.

Internal web server hostname:

Internal web server IP address:

(Optional) External web server hostname:

(Optional) External web server IP address:

Notes:

Location of SQL Server 2000 database

If you are installing SQL Server 2000 on this machine, enter Local Server.

If you are pointing the web server to a version of SQL Server previously installed on a separate machine, enter Existing Remote Server.

If you are connecting to a remote SQL Server, also enter its hostname or IP address.

SQL Server location:

(Optional) Remote SQL Server hostname:

(Optional) Remote SQL Server IP address:

Notes:

Your SQL Server 2000 user name and password

If you are completing a new installation of Cisco Unified MeetingPlace Web Conferencing with a local install of the SQL Server, use sa as your user name.

Note You must enter a password. Web Conferencing does not support a blank password. The password you enter during this installation will override any blank or previously entered SQL Server password.

User name:

Password:

Notes:


Installation Tasks: Web Conferencing

The Cisco Unified MeetingPlace Web Conferencing installation is completed in two parts:

1. Installing the Operating System on the Cisco MCS Server

2. Installing Web Conferencing

Installing the Operating System on the Cisco MCS Server

Before you begin, confirm that your system meets the network and system requirements. (Refer to System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.)

To Install the Operating System on the Cisco MCS Server


Step 1 Dedicate a networked Cisco MCS on which to install Cisco Unified MeetingPlace Web Conferencing.

Step 2 Install the required Cisco MCS operating system on the Cisco MCS Unified CallManager Appliance. When the installer prompts you for the product key, enter BTOO VQES CCJU IEBI.

The operating system CD was shipped with your Cisco Unified MeetingPlace application software.

(For additional information about MCS OS installation, refer to the "About the Cisco MCS Unified CallManager Appliance" section in the Installation Planning Guide for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.)

Step 3 Confirm the following:

Microsoft IIS 5.0 is installed.

IIS Administration Service and World Wide Web Publishing Service are running.

A default website is configured in the IIS.

You have Administrator privileges on the Cisco MCS.

Step 4 (Optional) If a release of Sun JRE is installed, confirm that it is a supported version (refer to System Requirements for Cisco Unified MeetingPlace). If it is not, uninstall Sun JRE.

Web Conferencing installs the required release of Sun JRE during the installation. (For more information, see the "About the Web Conferencing Installation" section.)

Step 5 Continue with the next section, "Installing Web Conferencing."


Installing Web Conferencing

The Cisco Unified MeetingPlace Web Conferencing executable takes 35 to 45 minutes to install the following components:

Cisco Unified MeetingPlace Gateway SIM.

Cisco Unified MeetingPlace Web Conferencing software.

.NET framework.

(If the local server option is chosen) SQL Server 2000. This requires an automatic reboot.

(If the local server option is chosen) The appropriate release of the SQL Server 2000 service pack. This requires an automatic reboot.


Note Check System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html for the required SQL Server 2000 service pack.


Before You Begin

Confirm that your installation drive has sufficient disk space to allow for the storage of applications, attachments, recordings, and meeting and profile database information, which will grow over time. (Refer to System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.)

If antivirus software is running on a Cisco MCS, disable it.

Confirm that the Cisco Unified MeetingPlace 8100 series server has Cisco Unified MeetingPlace Audio Server Release 5.4 or later installed.

Have the information that you gathered in the "Gathering Web Conferencing Installation Values" section available.

Complete the "Installing the Operating System on the Cisco MCS Server" section.

Restriction

We do not support installing or upgrading to Web Conferencing Release 5.4 by using Terminal Services.


Caution Do not interrupt the server during program installation or during automatic system shutdown or reboot.

To Install Cisco Unified MeetingPlace Web Conferencing


Step 1 Exit any open applications.

Step 2 Insert the Cisco Unified MeetingPlace Web Conferencing CD into the CD or DVD-ROM drive and double-click the .exe file to begin installation.


Note If a Missing Server Version error message appears, confirm that Audio Server Release 5.4 or later is installed on the Cisco Unified MeetingPlace 8100 series server. If the correct version is installed, proceed with the Web Conferencing installation. If not, upgrade the Audio Server software to version 5.4 or later before proceeding.


Step 3 After the install files are extracted, click Next and follow the instructions in the installer windows using the information you gathered in the "Gathering Web Conferencing Installation Values" section. Note the following considerations:

If you enter an IP address instead of a hostname for the Audio Server system, a warning message appears regarding reverse connection.

If this machine is in a network segment, such as a DMZ, and you are interested in reverse connection, enter a hostname instead of an IP address, then proceed with the installation.

If this machine has a connection to the Audio Server system—that is, if they are in the same network segment, port 5003 is open, and the Audio Server system is running—and you are not interested in reverse connection, then use the IP address and proceed with the installation.

Step 4 The installer installs the Gateway SIM first. When the InstallShield Wizard Complete window appears, click Finish. The Gateway SIM is installed.

Step 5 When the installer prompts you for the Installation Key, note the following considerations:

If you are installing Web Conferencing on a machine that is already configured on the Audio Server system, enter this machine's ethernet address in the Installation Key Entry window, then click Next.

If this is a new installation of Web Conferencing, this machine is probably not configured on the Audio Server system. In this instance, leave this field blank and click Next.

Step 6 Continue following the instructions in the installer windows using information from the "Gathering Web Conferencing Installation Values" section.

Step 7 At the final installer window, choose to reboot your computer now, then click Finish. You must reboot the machine for changes to take effect.

During installation, remember the following information:

If you chose Local Server as your SQL Server location, after the first reboot, the installer begins installing SQL Server. Status updates appear from the Cisco Unified MeetingPlace icon in the system tray, and when SQL Server installation is complete, the server reboots automatically.

If the installer detects a local SQL Server installation, after the second reboot, the installer begins installing the SQL Server service pack. Status updates appear from the Cisco Unified MeetingPlace icon in the system tray. When the service pack installation is complete, the server reboots automatically.

Installations of SQL Server and the SQL Server service pack are slow, and depending on your server hardware, installations may take 40 minutes or more to complete.

The Cisco Unified MeetingPlace icon appears as an orange door .

If the SQL Server installation appears to be taking too long (over 35 minutes), check Task Manager to confirm that SQLInstall.exe is running.

After the server reboots, the installer invokes SQLInstall.exe to create the MPWEB SQL database. This process may take 5 to 10 minutes.

Step 8 Open the Gateway SIM event log to monitor Web Conferencing application activities.

Step 9 Continue with the next section, "Testing the Web Conferencing Installation."


Testing the Web Conferencing Installation

After you install Cisco Unified MeetingPlace Web Conferencing, test the installation by completing the following tasks:

1. Defining the Web Conferencing Server

2. Testing the Web Server Over an HTTP Connection

3. Testing the Web Server Over an HTTPS Connection

4. Testing the Meeting Console Connection

Defining the Web Conferencing Server

To Define theCisco Unified MeetingPlace Web Conferencing Server


Step 1 Open your web browser, and enter the URL of your web server.

For internal web servers, the default URL structure is http://<server>, where <server> is the name of your internal web server.

For external web servers, the default URL structure is http://<server>/mpweb/admin, where <server> is the name of your external web server.

Step 2 When the Web Conferencing home page appears, sign in by using your System Manager-level user ID and password, then click Sign In Now.

If you are on an internal web server, the Welcome page appears with your name displayed at the top. To access the administrative page, click Admin.

If you are on an external web server, the administrative page appears.

Step 3 From the Admin page, click Web Server.

Step 4 From the View section of the page, click the name of the web server that you want to configure.

Information about this web server populates the Edit section of the page.

Step 5 For Hostname, enter the fully qualified domain name (FQDN) of the web server. Note the following considerations:

If this field contains just the hostname of your web server, change it to the FQDN, that is, hostname.domain.com.

If the web server is not in a Domain Name Server (DNS), insert the IP address instead.

This hostname or IP address must be resolvable by its intended users. (For details, see the "Testing the Web Server Over an HTTP Connection" section.)

Step 6 For Web Conference Active, choose Yes or No.

The default is Yes. Choosing No means that this web server will not host meetings.

Step 7 Click Submit.


Testing the Web Server Over an HTTP Connection

Confirm that the web server can resolve itself using the hostname configured on the Web Server administrative page. This is the hostname that you configured in Step 5 of the preceding section, "Defining the Web Conferencing Server," and is also the hostname that end users use to connect to this web server.

To Test the Web Server Over an HTTP Connection


Step 1 From the web server, use a web browser to connect to http://hostname.domain.com, the Fully Qualified Domain Name, or FQDN, of the web server.

or

If the web server is not in a Domain Name Server (DNS), use a web browser to connect to an IP address from the web server.

Step 2 If the Cisco Unified MeetingPlace Web Conferencing home page appears, the connection is successful.

If an error message appears, see the "Server Connection Problems" section on page 6-2


Testing the Web Server Over an HTTPS Connection

To Test the Web Server Over an HTTPS Connection


Step 1 From the web server, use a web browser to connect to https://hostname.domain.com, the Fully Qualified Domain Name, or FQDN, of the web server.

or

If the web server is not in a Domain Name Server (DNS), use a web browser to connect to an IP address from the web server.

Step 2 If the Cisco Unified MeetingPlace Web Conferencing home page appears, the connection is successful.

If any security warning dialog boxes appear, see the "Server Connection Problems" section on page 6-2.


Testing the Meeting Console Connection

To Test the Meeting Console Connection


Step 1 From an end-user system, open a web browser and enter the Cisco Unified MeetingPlace Web Conferencing URL in the address field and click Enter.

Step 2 Sign in by using your System Manager-level user ID and password.

Step 3 From the Welcome page, click Schedule Meeting.

Step 4 From the New Meeting scheduling page, fill in your meeting details, then click Schedule.

Step 5 Return to the Welcome page and enter the meeting ID of the meeting you just scheduled, then click Attend Meeting.

Step 6 Confirm that the meeting console loads properly.