Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 6.x
Installing Web Conferencing
Downloads: This chapterpdf (PDF - 335.0KB) The complete bookPDF (PDF - 1.82MB) | Feedback

Installing Web Conferencing

Table Of Contents

Installing Web Conferencing

Preinstallation Tasks: Web Conferencing

Installing Cisco Unified MeetingPlace Audio Server

Planning Web Conferencing License Usage

Installing SQL Server on a Remote Server

Gathering Web Conferencing Installation Values

Installation Tasks: Web Conferencing

Installing the Operating System on the Cisco MCS Server

Configuring Network Settings on the Cisco MCS Server

Installing Web Conferencing

Postinstallation Tasks: Web Conferencing

Defining the Web Conferencing Server Hostname Information

Testing the Web Conferencing Installation

Testing the Web Server Home Page Connection

Testing the Meeting Console Connection

Installing the Cisco Security Agent for Cisco Unified MeetingPlace Web Conferencing

Creating and Using a Least-Privileged SQL Account for Web Conferencing

Creating a Least-Privileged SQL Account for Web Conferencing

Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility

Configuring SSL


Installing Web Conferencing


This chapter describes how to complete a new installation of Cisco Unified MeetingPlace Web Conferencing. It does not describe upgrades.

This chapter contains the following sections:

Preinstallation Tasks: Web Conferencing

Installation Tasks: Web Conferencing

Postinstallation Tasks: Web Conferencing


Note Before reviewing this chapter, please read System Requirements for Cisco Unified MeetingPlace Release 6.x at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html. All installations of Release 6.x require a Cisco MCS and a supported version of MCS OS 2003 software.


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. Planning Web Conferencing License Usage

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

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.)

Planning Web Conferencing License Usage

Cisco Unified MeetingPlace Release 6.0 introduced a new license usage model for Web Conferencing. In this model, users joining a Cisco Unified MeetingPlace meeting from the web see one of two meeting console formats, with different license requirements:

Full meeting room

Includes tools for sharing and collaboration, in-session controls, and other features such as chat and polling.

Requires an available web conferencing license for each participant.

Participant list only

Includes only the list of meeting participants and associated audio and video controls (such as mute audio and pause video).

No web conferencing license is required to use this meeting console; it is included in the license for an audio port.


The meeting console format that participants see in a meeting depends on the Host Meetings With setting in the profile of the meeting scheduler. When planning for web conferencing license usage, consider the licensing capacity of your Web Conferencing server and determine which groups or individuals should have the capability to schedule meetings that utilize the full meeting room.

Files for license keys that you may add or upgrade are made available to you when you purchase a new Cisco Unified MeetingPlace system or upgrade to the current release. These files are loaded into your Cisco Unified MeetingPlace 8100 series server when it is purchased. To add additional web conferencing licenses to the Audio Server, refer to the "About Loading Cisco Unified MeetingPlace License Keys" section in the "Managing and Maintaining Cisco Unified MeetingPlace" chapter of the applicable Administration Guide for Cisco Unified MeetingPlace Audio Server at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_maintenance_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 on either the same machine as Web Conferencing or on a separate machine. If you choose to install SQL Server on the same machine as Cisco Unified MeetingPlace Web Conferencing, the installer will handle the installation of SQL Server 2000 and the appropriate service pack on your local system automatically; in this case, no pre-installation steps are required.

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 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.


Gathering Web Conferencing Installation Values

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

Table 2-1 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.

(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

After installing the operating system on the web server, you will enable two IP interfaces for the server on the same subnet. During installation of the Web Conferencing software, you will enter the information for the primary IP interface. List either the primary IP address of the web server or the hostname associated with this IP address.

Web server primary hostname:

Web server primary IP address:

Notes:

Location of SQL Server 2000 database

If you are installing SQL Server 2000 on the web server, 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.


Caution The Web Conferencing installer does not create or verify the existence of the SQL account or check the validity of its user name and password combination. If the Web Conferencing installer will be installing SQL Server locally on the Web Conferencing server, you must use sa as the user name. To ensure that the Web Conferencing server functions correctly after installation, we strongly recommend that you use sa as the user name during the installation even if you have preinstalled SQL Server on a remote server. After the installation, you can configure a least-privileged SQL account and configure Web Conferencing to use this account instead.

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 three parts:

1. Installing the Operating System on the Cisco MCS Server

2. Configuring Network Settings on the Cisco MCS Server

3. 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 server.

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

Follow the installation procedure in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later), which is included with the operating system software. Although the document refers to Cisco Unified CallManager and other applications, it also applies to Cisco Unified MeetingPlace integration applications.


Note Return to this document before performing the Post-Installation Tasks in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later).


Step 3 Continue with the next section, "Configuring Network Settings on the Cisco MCS Server".


Configuring Network Settings on the Cisco MCS Server

Once the operating system is installed, you must configure the network interfaces. Cisco Unified MeetingPlace Web Conferencing has the following networking requirements:

Two separate IP addresses are required.

The IP addresses must be on the same network segment. (Both must be connected to the same Layer 3 subnet and the same Layer 2 Ethernet broadcast domain.)

The two IP interfaces cannot share the same hostname or be aliased to each other in DNS. (Hostnames are only required if the server will be configured for Secure Sockets Layer.)

Cisco Unified MeetingPlace Web Conferencing supports assigning the two required IP addresses by using the following Network Interface Card (NIC) configurations:

One NIC enabled and configured with two IP addresses; second NIC is disabled

Only utilizes one of the two NICs on the system.

The NIC is a single point of failure.

This configuration is available for both HP and IBM MCS server models

To configure this option, perform the "To Configure a Single NIC with Both IP Addresses on the Cisco MCS Server" procedure.

Both NICs enabled, one IP address per NIC

Each NIC on the system is used, although one NIC may be more heavily used than the other.

Each NIC is a single point of failure. If either NIC fails, Web Conferencing will be unavailable.

If the Web Conferencing server is connected to a 100 MB/sec. network, the NIC capacity may be exceeded in large meetings with heavy application sharing.

This configuration is available for both HP and IBM MCS server models.

To configure this option, perform the "To Configure One IP Address per NIC on the Cisco MCS Server" procedure.

Both NICs enabled, teamed, configured in Transmit Load Balancing (TLB) mode

The two NICs act together to handle traffic for both IP addresses; one NIC receives inbound traffic, both NICs send outbound traffic.

If either NIC fails, the other NIC can take over.

We strongly recommend this configuration if the Web Conferencing server is connected to a 100 MB/sec. network.

This configuration is available only for HP MCS server models.

To configure this option, perform the "To Configure NIC Teaming on the Cisco MCS Server (HP Models Only)" procedure

Both NICs enabled, teamed, configured in Network Fault Tolerance (NFT) mode

One NIC is active, handling traffic for both IP addresses.

The other NIC is passive and takes over if the primary NIC fails.

This configuration is available only for HP MCS server models.

To configure this option, perform the "To Configure NIC Teaming on the Cisco MCS Server (HP Models Only)" procedure


To Configure a Single NIC with Both IP Addresses on the Cisco MCS Server


Step 1 Follow the procedure for "Configuring Network Settings" in the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later). In this procedure, configure the primary NIC on the system with a static IP address and with DNS, WINS, or the LMHosts file for hostname resolution.

Step 2 Add the secondary IP address to the primary NIC:

a. On the Start menu, click Settings > Network Connections.

b. Right-click Local Area Connection, then click Properties.

c. Double-click Internet Protocol (TCP/IP).

d. Click Advanced.

e. On the IP Settings tab, in the IP Addresses area, click Add.

f. Enter the secondary IP address and subnet mask and click Add.

g. Click OK three times to close the Local Area Connection Properties window.

Step 3 (Optional) Continue performing the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later).


Note We highly recommend that you configure the duplex of your network adapters for Full Duplex (either 100/Full or 1000/Full, as applicable). Autonegotiation may impact Web Conferencing traffic flow.


Step 4 Proceed to the "Installing Web Conferencing" section.


To Configure One IP Address per NIC on the Cisco MCS Server


Step 1 Follow the procedure for "Configuring Network Settings" in the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later). In this procedure, configure the primary NIC on the system with a static IP address and with DNS, WINS, or the LMHosts file for hostname resolution.

Step 2 Repeat Step 1 for the secondary NIC on the system, using a different IP address on the same subnet, with the same subnet mask and default gateway. If you receive a warning about using the same default gateway, click OK to accept the warning and continue.

Step 3 Enable the secondary NIC:

a. On the Start menu, click Settings > Network Connections.

b. Right click Local Area Connection 2 and click Enable.

Step 4 (Optional) Continue performing the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later).


Note We highly recommend that you configure the duplex of your network adapters for Full Duplex (either 100/Full or 1000/Full, as applicable). Autonegotiation may impact Web Conferencing traffic flow.


Step 5 Proceed to the "Installing Web Conferencing" section.


To Configure NIC Teaming on the Cisco MCS Server (HP Models Only)


Step 1 Follow the procedure for "Configuring Network Settings" in the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later). In this procedure, configure the primary NIC on the system with a static IP address and with DNS, WINS, or the LMHosts file for hostname resolution.


Note If you are using the LMHosts file for hostname resolution, add an entry for both the primary and secondary IP addresses and hostnames.


Step 2 Enable the secondary NIC:

a. On the Start menu, click Settings > Network Connections.

b. Right click Local Area Connection 2 and click Enable.

Step 3 Configure network teaming by using the HP Network Configuration Utility, available by choosing Start > Settings > Control Panel > HP Network. Refer to the HP Network Configuration Utility online help for instructions.

Step 4 Add the primary IP address to the NIC team:

a. On the Start menu, click Settings > Network Connections.

b. Right-click Local Area Connection 3, then click Properties.

c. Double-click Internet Protocol (TCP/IP).

d. Click Use the following IP address; in the appropriate fields, enter the server primary IP address, subnet mask, and default gateway that you used in Step 1.

e. If you configured DNS or WINS for the primary NIC by using the procedure in Step 1, repeat the procedure for the team. If you configured the LMHosts file, skip to Step 5 substep d.

Step 5 Add the secondary IP address to the NIC team:

a. On the Start menu, click Settings > Network Connections.

b. Right-click Local Area Connection 3, then click Properties.

c. Double-click Internet Protocol (TCP/IP).

d. Click Advanced.

e. On the IP Settings tab, in the IP Addresses area, click Add.

f. Enter the secondary IP address and subnet mask and click Add.

g. Click OK three times to close the Local Area Connection Properties window.

Step 6 Verify that the team is configured correctly:

a. On the Start menu, click Run.

b. Type cmd and press Enter. The command window opens.

c. Type ipconfig /all and press Enter. The connection information displays in the command window. The Local Area Connection 3 (for the network team) should show two IP addresses.

Step 7 (Optional) Continue performing the post-installation tasks in Installing the Operating System on the Cisco Unified Communications Server (version 2003.1.1 or later).


Note We highly recommend that you configure the duplex of your network adapters for Full Duplex (either 100/Full or 1000/Full, as applicable). Autonegotiation may impact Web Conferencing traffic flow.


Step 8 Proceed to the "Installing Web Conferencing" section.


Installing Web Conferencing

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

Cisco Unified MeetingPlace Gateway SIM.

Cisco Unified MeetingPlace Web Conferencing software. This requires an automatic reboot.

(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.

Cisco Unified MeetingPlace Web Conferencing engine. This requires an automatic reboot.

Note that there are a total of four automatic reboots if you are installing SQL Server 2000 locally, or two if you are using a remote SQL server.


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.



Note The installation executable disables antivirus software for the duration of the installation.


Before You Begin

Confirm that the Cisco MCS server is configured with the correct time zone and daylight savings time settings. The installation may fail if you do not configure the system to automatically observe daylight savings time in a time zone that requires it.

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.)

Confirm that the Cisco Unified MeetingPlace 8100 series server has Cisco Unified MeetingPlace Audio Server Release 6.0 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 6.x 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 DVD into the DVD-ROM drive and double-click the CiscoUnifiedMeetingPlaceWebConferencing.exe file to begin installation.


Note The Cisco Unified MeetingPlace Web Conferencing CD contains multiple executable files. Verify that you are double-clicking the correct executable file.


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.


Note If a Missing Server Version error message appears, confirm that Audio Server Release 6.0 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, click Cancel and upgrade the Audio Server software to version 6.0 or later before proceeding.


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


Note If you chose Local Server as your SQL Server location, after the first reboot, you must log in to the system as an administrator in order for the installer to begin installing SQL Server. When SQL Server installation is complete, the server reboots automatically.


During installation, remember the following information:

If the installer detects a local SQL Server installation, after the second reboot, the installer begins installing the SQL Server service pack. 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. Status updates appear from the Cisco Unified MeetingPlace icon in the system tray during the installation.

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.

After creating the database and installing the Web Conferencing engine, the server reboots automatically.

Step 6 After the final automatic reboot (the fourth reboot if you are installing SQL Server 2000 locally, or the second if you are using a remote SQL server), open the Gateway SIM event log to monitor Web Conferencing application activities.

While the system is coming up, you should see the event text, "Waiting for Connect."

When the Web Conferencing engine is ready, you should see response text similar to the following:

MPConnect (0x14B0) Debug: Response: <?xml version="1.0" encoding="utf-8"?>  
<results><status code="ok"/></results>

Step 7 Continue with the next section, "Postinstallation Tasks: Web Conferencing."


Postinstallation Tasks: Web Conferencing

We recommend that you complete the following optional tasks as applicable after installing the web conferencing software:

Defining the Web Conferencing Server Hostname Information

Testing the Web Conferencing Installation

Installing the Cisco Security Agent for Cisco Unified MeetingPlace Web Conferencing

Creating and Using a Least-Privileged SQL Account for Web Conferencing

Configuring SSL

Defining the Web Conferencing Server Hostname Information

If you want users to be able to access the Web Conferencing server by using the fully qualified domain name (FQDN) of the server, or if you plan to configure SSL for this server, do the following procedure.


Note If the web server is not in a Domain Name Server (DNS), do not perform this procedure.


To Define the Cisco Unified MeetingPlace Web Conferencing Server Hostname Information


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 [Home Page], enter the fully qualified domain name (FQDN) of the primary network interface on the web server, for example, hostname.domain.com. Note the following considerations:

To use SSL, you must enter the FQDN.

This hostname must be resolvable by its intended users. (For details, see the "Testing the Web Server Home Page Connection" section.)

Step 6 For Hostname [Web Conferencing], enter the FQDN of the secondary network interface on the web server, for example, hostnamewc.domain.com. Note the following considerations:

To use SSL, you must enter the FQDN.

This hostname must be resolvable by its intended users. (For details, see the "Testing the Meeting Console Connection" section.)

Step 7 Click Submit.


Testing the Web Conferencing Installation

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

1. Testing the Web Server Home Page Connection

2. Testing the Meeting Console Connection

Testing the Web Server Home Page 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 Hostname Information," and is also the hostname that end users use to connect to this web server.

To Test the Web Server Home Page 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 5-3


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.


Installing the Cisco Security Agent for Cisco Unified MeetingPlace Web Conferencing

For instructions on installing the Cisco Security Agent, refer to the applicable Release Notes for Cisco Security Agent for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.

Creating and Using a Least-Privileged SQL Account for Web Conferencing

By default, the Cisco Unified MeetingPlace Web Conferencing installer suggests using the SQL built-in sa administrator account as the SQL Server user name. Often, a strong password for the sa account is sufficiently secure to protect your system from unauthorized access. However, if you do not want to continue to use a SQL account that has full administration rights after the installation is complete, you can create a SQL account with minimal privileges that is dedicated to Web Conferencing use, and configure the Web Conferencing server to use this account.

To create and use a least-privileged SQL account, do the following tasks in the order presented:

1. Creating a Least-Privileged SQL Account for Web Conferencing

2. Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility

Creating a Least-Privileged SQL Account for 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 database role 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.


To Create a Least-Privileged SQL Account for Web Conferencing


Step 1 Open the SQL Server Enterprise Manager and create a new login:

a. On the Start menu, click Programs > SQL Server 2000 > Enterprise Manager.

b. Click a server group to expand it, then click the name of a server.

c. Click Security to expand it.

d. Click New Login. The SQL Server Login Properties window opens.

Step 2 On the General tab, enter a name for the login.

Step 3 Click SQL Server Authentication, then enter a password for the account.

Step 4 In the Database drop-down menu, click MPWEB to set the MPWEB database as the default database.

Step 5 Click the Database Access tab.

Step 6 Specify the database roles for the MPWEB database:

a. In the Databases table, click the check box for the MPWEB database.

b. In the Database Roles table, click the check boxes for the following roles:

db_datareader

db_datawriter

db_ddladmin

Step 7 Repeat Step 6 for each additional MPWEB slave database. The slave databases have names that begin with "MPWEB_". Depending on your deployment, your SQL Server will have either one or two slave databases.

Step 8 Click OK to complete the account configuration.


Updating SQL Account Access from the MeetingPlace Gateway Configurations Utility

The MeetingPlace Gateway Configurations utility allows you to update the web server with the least-privileged SQL login account that you created in the "To Create a Least-Privileged SQL Account for Web Conferencing" procedure. It does not create a SQL Server login for you.

To Update SQL Account Access from the MeetingPlace Gateway Configurations Utility


Step 1 Stop the Cisco Unified MeetingPlace Web Conferencing Service:

a. From the Windows Start menu, choose Settings > Control Panel > Administrative Tools > Services.

b. Right-click Cisco Unified MeetingPlace Web Conferencing and choose Stop.

c. (Optional) To stop other Cisco Unified MeetingPlace gateway services, including Gateway SIM, right-click the service and choose Stop.

d. If the IIS Admin Service is still running, right-click the service and choose Stop.

e. Close the Services control panel.

Step 2 Open the MeetingPlace Gateway Configurations utility:

a. From your system tray, right-click the Cisco Unified MeetingPlace icon.

b. Choose Properties.

Step 3 Click the Web Conferencing tab.

Step 4 For Server, enter the hostname or IP address of the SQL Server you want to update. For a local server, enter local.

Step 5 For Username and Password, enter the login account username and password you applied to the SQL Server in the "To Create a Least-Privileged SQL Account for Web Conferencing" procedure.

Step 6 Click OK.

Step 7 Restart the Cisco Unified MeetingPlace Web Conferencing Service:

a. From the Windows Start menu, choose Settings > Control Panel  > Administrative Tools > Services.

b. Right-click Cisco Unified MeetingPlace Web Conferencing and choose Start.

c. If you stopped any other gateway services, restart them by right-clicking the applicable service and choosing Start.

d. Close the Services control panel.


Configuring SSL

For instructions on configuring SSL, refer to the "Configuring External Access to Cisco Unified MeetingPlace Web Conferencing" chapter of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing, Release 6.x at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.