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

Installing Web Conferencing for a Segmented Meeting Access Configuration

Table Of Contents

Installing Web Conferencing for a Segmented Meeting Access Configuration

About Segmented Meeting Access

About the SMA-1S Configuration

About the SMA-2S Configuration

About the SMA-2S Configuration with SSL and Segmented DNS

Installing Web Conferencing in an SMA-1S Configuration

Gathering Basic Information About the Web Server

Installing Web Conferencing in an SMA-1S Configuration

Installing Web Conferencing in an SMA-2S Configuration

Gathering Basic Information About the Internal and External Web Servers

Installing Web Conferencing on an Internal Server

Copying GUIDS from the Internal Web Server to the External Web Server

Installing Web Conferencing on an External Server


Installing Web Conferencing for a Segmented Meeting Access Configuration


Cisco Unified MeetingPlace Web Conferencing supports two segmented meeting access configurations that allow you to provide external access to your users while maintaining network security. Although you can provide external access to Cisco Unified MeetingPlace web conferences by simply opening ports in your firewall, we do not recommend this option because it lacks security.

This chapter contains the following sections:

About Segmented Meeting Access

Installing Web Conferencing in an SMA-1S Configuration

Installing Web Conferencing in an SMA-2S Configuration


Note Before reviewing this chapter, 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.


About Segmented Meeting Access

While external participation is possible by controlling port access through a firewall, we highly recommend that you consider a segmented meeting access (SMA) configuration instead. SMA configurations isolate some meetings on the private corporate network while exposing others, designated as external, to the Internet. Users designate their meetings as internal or external during the scheduling process by setting the Allow Internet Access parameter on the New Meeting scheduling page.

Typically, a Cisco MCS is placed in the demilitarized zone, or DMZ, a network segment created between the private corporate network and the Internet to host meetings for external access.

Cisco Unified MeetingPlace Web Conferencing supports two SMA configurations, which you can decide upon during the Web Conferencing installation. For more information, see Table 2-2 on page 2-7, "Installation Values for Cisco Unified MeetingPlace Web Conferencing."

The following sections describe the supported SMA configurations:

About the SMA-1S Configuration

About the SMA-2S Configuration

About the SMA-2S Configuration with SSL and Segmented DNS

About the SMA-1S Configuration


Note For requirements, see the "Segmented Meeting Access Requirements" sections of System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/us/products/sw/ps5664/ps5669/prod_installation_guides_list.html. New installations of Cisco Unified MeetingPlace Web Conferencing Release 5.4 require a Cisco MCS.


In a Segmented Meeting Access-1 Server (SMA-1S) configuration, a single web server is placed in a network segment, such as a demilitarized zone (DMZ), and two websites provide access to Cisco Unified MeetingPlace Web Conferencing. One of the sites is accessible only from behind the firewall. The other is accessible from inside or outside the firewall.

While internal users have access to the full-access Web Conferencing user interface, external users have limited access to an attend-only web page that allows attendance only to external meetings.

The benefits of this configuration are cost effectiveness—because only one web server is required—and a moderate level of security. However, this configuration is more complex to deploy than the Segmented Meeting Access-2 Servers (SMA-2S) configuration and involves setting up virtual websites. It also requires a segmented DNS for a single click-to-attend notification link. If you want to maintain a single click-to-attend link, more DNS work is required.

Figure 3-1 Segmented Meeting Access - 1 Server Configuration

1

Cisco Unified MeetingPlace Audio Server system

2

Internal DNS server

3

Cisco Unified MeetingPlace web server

Note The web server must have two IP addresses.

4

Internal user

Internal users enter internal meetings through the internal website.

Internal users entering an external meeting are redirected to their meeting from the internal website.

5

External user

External users access external meetings through the external website.

External users do not have access to internal meetings.

   

About the SMA-2S Configuration


Note For requirements, refer to the "Segmented Meeting Access Requirements" sections of System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/us/products/sw/ps5664/ps5669/prod_installation_guides_list.html. New installations of Cisco Unified MeetingPlace Web Conferencing Release 5.4 require a Cisco MCS.


In the Segmented Meeting Access-2 Servers (SMA-2S) configuration, Cisco Unified MeetingPlace Web Conferencing is deployed on two separate web servers or two separate clusters of web servers. One is on the internal network, behind the firewall; the other is on another network segment, such as a DMZ. The internal server or cluster is accessible only from behind the firewall, while the external server or cluster is accessible from inside or outside the firewall.

While internal users have access to the full-access Web Conferencing user interface, external users have access to an attend-only web page that allows attendance only to external meetings.

The SMA-2S configuration is the preferred and most secure deployment model if you want to provide external access to Cisco Unified MeetingPlace web conferences.

We highly recommend that you configure external web servers to use Secure Sockets Layer (SSL). This provides optimum security and resolves proxy server issues that can prevent users from joining a web conference. (For more information, refer to the "Configuring External Access to Cisco Unified MeetingPlace Web Conferencing" chapter of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.)

Figure 3-2 Segmented Meeting Access-2 Server Configuration

1

Internal Cisco Unified MeetingPlace web server

This web server sits inside the private corporate network.

2

External Cisco Unified MeetingPlace web server

This web server sits in a network segment, such as a DMZ.

3

Internal user

Internal users enter internal meetings through the internal web server.

Internal users enter external meetings through the external web server.

4

External user

External users can enter external meetings only.

Users enter these meetings through the external web server.


About the SMA-2S Configuration with SSL and Segmented DNS

If your Cisco Unified MeetingPlace Web Conferencing system has SSL configured on the external web server and a segmented DNS, the segmented DNS name cannot be the same as the SSL certificate name on the external or internal machine. See the following example for configuration guidelines.

Example

You have an SMA-2S configuration in which SSL is required for external users but is not required for internal users who are accessing the internal or external machine.

The segmented DNS name is meetingplace.company.com.

The SSL certificate name for the external machine is meetingplace1.

The hostname for the external machine from the internal machine is meetingplace1.

All URLs and click-to-attend links are in the form of http://meetingplace.company.com.

When users access http://meetingplace.company.com from the external network, the external machine will automatically redirect them to HTTPS plus whatever hostname is configured in the database—in this case, meetingplace1.


Note If you force SSL on all users, both internal and external users will be forced to use SSL when they access the external web server.


Installing Web Conferencing in an SMA-1S Configuration

This section contains information on the following tasks:

1. Gathering Basic Information About the Web Server

2. Installing Web Conferencing in an SMA-1S Configuration

Gathering Basic Information About the Web Server

Gather and record the information in Table 3-1 to prepare for the SMA-1S deployment.

Table 3-1 Information Values for the SMA-1S Deployment 

Information
Value

NetBios (computer) name of web server

NetBios name:

Notes:

IP address or hostname of web server

IP address:

Hostname:

Notes:

IP address to which web server resolves internally

IP address:

Notes:

IP address to which web server resolves externally

IP address:

Notes:


Installing Web Conferencing in an SMA-1S Configuration

Before You Begin

Read the "Installing Web Conferencing" chapter and have it available to assist you during the installation.

Restrictions

Your system must satisfy all the requirements as described in System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

You must be deploying this Cisco MCS in a network segment, such as a DMZ.

To Install Web Conferencing in an SMA-1S Configuration


Step 1 Close 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.

Step 3 When prompted for your Server Location, choose Both (SMA-1S).

The Both option automatically configures your web server as an external web server. The external web server displays a modified attend-only interface for users who want to attend Cisco Unified MeetingPlace web conferences from outside the private corporate network.

Step 4 Continue following the instructions in the installer windows by using information from the "Gathering Web Conferencing Installation Values" section on page 2-7.

Step 5 When you reach the final installer window, choose to reboot your computer now, then click Finish.

You must reboot your machine for changes to take effect.


What to Do Next

Configure the web server for an SMA-1S deployment. Refer to the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html. Start with the "How to Configure IIS" section.

Installing Web Conferencing in an SMA-2S Configuration

This section contains information on the following tasks:

1. Gathering Basic Information About the Internal and External Web Servers

2. Installing Web Conferencing on an Internal Server

3. Copying GUIDS from the Internal Web Server to the External Web Server

4. Installing Web Conferencing on an External Server

Gathering Basic Information About the Internal and External Web Servers

Gather and record the information in Table 3-2 to prepare for the SMA-2S deployment.

Table 3-2 Information Values for the SMA-2S Deployment 

Information
Value

NetBios (computer) name
of internal web server

NetBios name:

Notes:

Hostname or fully qualified domain name of internal web server that is resolvable from internal network

Hostname:

FQDN:

Notes:

IP address of internal web server that is resolvable from internal network

IP address:

Notes:

SQL Server that internal web server will be using

Note SQL Server can be on web server or on separate remote server. (See the "About SQL Server Integration" section on page 2-1.)

IP address:

Hostname:

Notes:

IP address or hostname of external web server that is resolvable from internal web server

IP address:

Hostname:

Notes:

NetBios (computer) name of external web server

NetBios name:

Notes:

Hostname or fully qualified domain name of external web server that is resolvable from Internet

Hostname:

FQDN:

Notes:

IP address of external web server that is resolvable from Internet

IP address:

Notes:

SQL Server that external web server will be using

Note SQL Server can be on web server or on separate remote server. Each internal Cisco Unified MeetingPlace web server and external Cisco Unified MeetingPlace web server must have its own SQL Server. (See the "About SQL Server Integration" section on page 2-1.)

IP address:

Hostname:

Notes:


Installing Web Conferencing on an Internal Server

Before You Begin

See the "Installing Web Conferencing" chapter for assistance with the installation.

Restrictions

Your system must satisfy all the requirements as described in System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

You must be deploying this Cisco MCS inside your private corporate network.

To Install Web Conferencing on an Internal Server


Step 1 Close any open applications.

Step 2 Install Web Conferencing:

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

b. When prompted for your Server Location, choose Internal (Full Access).

c. When prompted for your SQL Server location, choose Local Server.

If your web server is running Cisco MCS OS and you choose the Local Server option, a full version of Microsoft SQL Server is automatically installed. For any other installations, such as non-MCS servers or the Remote Server option, you must first manually install SQL Server before you install Web Conferencing. (For more information about SQL Server installation, see the "About SQL Server Integration" section on page 2-1.)

d. Continue following the instructions in the installer windows using information from the "Gathering Web Conferencing Installation Values" section on page 2-7.

e. When you reach the final installer window, choose to reboot your computer now, then click Finish.

You must reboot the machine for changes to take effect.

If you are using a Cisco MCS server and chose Local Server as your SQL Server location, upon server reboot, the installer continues to install SQL Server and the SQL Server service pack. This process can take some time and requires two automatic reboots. Status updates appear from the Cisco Unified MeetingPlace icon in the system tray.

While your system reboots, do not terminate any processes or reboot or shut down the server.


What to Do Next

1. Define the internal web server. See the "Defining the Web Conferencing Server" section on page 2-12.

2. Continue with the "Copying GUIDS from the Internal Web Server to the External Web Server" section.

Copying GUIDS from the Internal Web Server to the External Web Server

The GUIDS entries for site and system must match between the internal and external web servers. Make sure that you run the GUIDS.reg file on each external web server before installing Cisco Unified MeetingPlace Web Conferencing.


Caution You must complete this step before running the Cisco Unified MeetingPlace Web Conferencing installer on the external web server. If this step is skipped or completed incorrectly, Presentation mode will not work for internal users in external meetings. Recovering from this problem requires that you rebuild the SQL Server database.

Before You Begin

Install Cisco Unified MeetingPlace Web Conferencing on the internal web server. See "Installing Web Conferencing on an Internal Server" section.

To Copy GUIDS from the Internal Web Server to the External Web Server


Step 1 Copy the GUIDS.reg file from the internal web server (located in the Program Files\Cisco Systems\MPWeb directory).

Step 2 Paste the GUIDS.reg file to the Temp directory on the external web server.

Step 3 On the external web server, double-click the GUIDS.reg file to install it.

Step 4 When prompted to add the information from the GUIDS.reg file to the registry, click OK.

Step 5 Continue with the "Installing Web Conferencing on an External Server" section.


Installing Web Conferencing on an External Server

Before You Begin

See the "Installing Web Conferencing" chapter for assistance with the installation.

Restrictions

You must be installing Web Conferencing on a Cisco MCS with the required Cisco MCS OS installed and running. Refer to System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

You must be deploying this Cisco MCS in a network segment, such as a DMZ.

To Install Web Conferencing on an External Server


Step 1 Close any open applications.

Step 2 Confirm that you have synchronized the GUIDSystemID and GUIDSiteID between the internal web server and the external web server.

(See the "Copying GUIDS from the Internal Web Server to the External Web Server" section.)

Step 3 Install Web Conferencing:

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

b. When prompted for your Server Location, choose External (Limited Access).

c. When prompted for your SQLServer location, choose either Local Server or Remote Server.

If you choose the Local Server option and the web server is running Cisco MCS OS, a full version of Microsoft SQL Server is automatically installed. For any other configuration, such as non-MCS servers or the Remote Server option, you must first manually install SQL Server before you install Web Conferencing. (See the "About SQL Server Integration" section on page 2-1.)

d. Continue following the instructions in the installer windows by using information in the "Gathering Web Conferencing Installation Values" section on page 2-7.

e. When you reach the final installer window, choose to reboot your computer later, then click Finish.

Note that you also must reboot your server again in Step 5 for the installation to complete.

If you are using a Cisco MCS server and you chose Local Server as your SQL Server location, upon server reboot, the installer continues and installs SQL Server and the SQL Server service pack. This process can take some time and requires two automatic reboots. Status updates appear from the MeetingPlace icon in the system tray.

While the server is installing SQL Server or the SQL Server service pack, do not terminate any processes or reboot or shut down the server.

Step 4 Copy and paste the GUIDS.reg file:

a. Navigate to the Temp directory.

b. Copy the GUIDS.reg file and paste it to the Program Files\Cisco Systems\MPWeb directory.

This replaces the GUIDS.reg file that the installer created.

Step 5 Reboot the machine for changes to take effect.

Step 6 Define the external web server. See the "Defining the Web Conferencing Server" section on page 2-12.


What to Do Next

Configure the SMA-2S deployment. Refer to the "Configuring External Access to Cisco Unified MeetingPlace Web Conferencing" chapter of the Configuration Guide for Cisco Unified MeetingPlace Web Conferencing at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.