Mediasite EX server deployment guide

Transcription

1 Mediasite EX server deployment guide

2 2008 Sonic Foundry, Inc. All rights reserved. No part of this document may be copied and/or redistributed without the consent of Sonic Foundry, Inc. Additional copies may be obtained by contacting Sonic Foundry. Sonic Foundry, the Sonic Foundry logo, Mediasite, and the Mediasite logo are registered trademarks of Sonic Foundry, Inc. All other trademarks are the property of their respective owners. Sonic Foundry, Inc. 222 W. Washington Avenue Madison WI toll free from the US and Canada Sonic Foundry. Since For more information or to provide feedback on Mediasite documentation, please contact Version: 5.0.1, November

3 Table of contents Getting started... 7 Core Mediasite components... 7 Minimum system requirements... 8 EX Server system requirements... 8 Windows Media Server system requirements... 9 Windows Media Server considerations... 9 System Manager system requirements Database server requirements EX Server deployment options Standard installation...11 High-availability installation Multiple EX Server installations on a single server Additional installation and configuration considerations Migration from 4.x to EX Server 5.0 upgrade Mediasite security Secure communication Security for resources on the EX Server Security for content on the Windows Media Server Deploying Mediasite Server Preparing the Mediasite database Preparing the EX Server s data locations Preparing the Windows Media Server

4 Table of contents Information to know before you begin installing Installing Microsoft ADAM (AD LDS) Configuring the Mediasite Directory Installing the Media Server Control Service (MSCS) Installing the Scheduler (optional) Installing EX Server in a standard installation Installing EX Server in a high-availability environment Install EX Server on the primary server Install EX Server on secondary servers Installing multiple EX Servers on a single server Testing the EX Server settings Configuring the Windows Media Server (optional) Enable Mac playback and push distribution Enable and configure the Mediasite plug-ins Installing and configuring the System Manager Install the System Manager Add a site for the EX Server Synchronize clocks on the servers and the Recorder Connecting the EX Server to an external directory (optional) Migrating to Mediasite Server Catalog mappings Using the Migration Wizard Using the Media Upgrade Tool Uninstalling 4.x software Renaming the virtual directory (optional) Upgrading Recorder 4.x...46 Upgrading Editor 4.x

5 Updating the Mediasite Server settings Updating the Mediasite Root URL Updating the import settings on a secondary server Using the secure socket layer for the Mediasite Directory connection Installing and configuring the Podcast Generator Create PodcastUser Installing the Podcast Generator Registering the EX Server with the Podcast Generator Enabling Podcast management in the Portal Configuring the MSCS multicast settings Index

6

7 Getting started This book describes how to install and configure Mediasite EX Server as well as how to migrate to EX Server from an EX or LX Server 4.x. You will also find descriptions of core Mediasite components, system requirements, deployment options, and Mediasite security. Once the EX Server is successfully deployed, you can connect Mediasite Recorders to it and begin preparing, recording, and publishing presentations. For more information on recording, preparing, and publishing presentations, see the Mediasite Recorder Software Guide and the Mediasite Server Guide. The ideal audience for this guide is someone with a solid background in: Microsoft Windows Server 2003, Windows Server 2008, or Windows XP Microsoft Internet Information Services: FTP and HTTP Microsoft Windows Media Services MySQL or Microsoft SQL Server databases Microsoft.NET Without this background, we strongly advise you to find a more qualified IT professional to install EX Server You can download the online version of this guide, which may contain more current information, from the SmartServe Portal at 1 Core Mediasite components All EX Server deployments include the following core components: Mediasite EX Server (a collection of web applications and services): manages and distributes rich media presentations in an enterprise environment Mediasite database (either MySQL or Microsoft SQL Server): stores all information about the deployed system such as presentation, streaming, and security settings Microsoft Active Directory Application Mode (ADAM): When configured as the Mediasite Directory stores user credentials and groups for the EX Server Mediasite System Manager: secures and manages the EX Server 7

8 Getting started Microsoft Windows Media Services: streams video in rich media presentations Mediasite Recorder: records presentations and can be used with an EX Server ADAM is called Active Directory Lightweight Directory Services (AD LDS) on Windows Server Microsoft ADAM (AD LDS), MySQL, Microsoft SQL Server, and Windows Media Server are not included with the EX Server software. All other software components are available with an EX Server installation. Minimum system requirements Before installation, ensure all machines, including the Windows Media Server, meet the following requirements. The Mediasite system supports Windows Server 2003 SP1 and Windows Server EX Server system requirements Microsoft Windows Server 2003 SP1 CPU:2 x Dual Core Intel Xeon 5130 processor (2GHz, 1333MHz FSB) RAM: 2 GB, 667 MHz Storage: Operating system plus.5mb storage per minute of content (presentation data and supporting content) Microsoft Internet Information Services (IIS) 6.0 Microsoft FTP Services or a third-party SFTP server* Microsoft.NET Framework 3.5 Microsoft Active Directory or LDAPcompatible directory (if using in addition to ADAM directory) RAID storage configuration and redundant power supplies (recommended) * Sonic Foundry does not provide thirdparty SFTP server software. Microsoft Windows Server 2008 CPU:2 x Dual Core Intel Xeon 5130 processor (2GHz, 1333MHz FSB) RAM: 2 GB, 667 MHz Storage: Operating system plus.5mb storage per minute of content (presentation data and supporting content) Microsoft Internet Information Services (IIS) 7.0 Microsoft FTP Services or a third-party SFTP server* Microsoft.NET Framework 3.5 Microsoft Active Directory or LDAPcompatible directory (if using in addition to AD LDS directory) RAID storage configuration and redundant power supplies (recommended) 8

9 Getting started On Windows Server 2008, IIS, AD LDS, and Application Server (.NET 3.0) are available as server roles so you must add them using Windows Server Manager (Server Manager > Roles > Add Roles). Once you have added these server roles, you will add the Application Server > Web Server (IIS) Support role service while accepting the default role services for the remaining server roles and then download and install Microsoft.NET Framework 3.5. For more information, see the documentation included with Windows Server Windows Media Server system requirements Microsoft Windows Server 2003 SP1 CPU:2 x Dual Core Intel Xeon 5130 processor (2GHz, 1333MHz FSB) RAM: 2 GB, 667 MHz Storage: Operating system plus 2MB storage per minute of video content Microsoft Windows Media Services 9 Series Microsoft.NET Framework 3.5 Microsoft FTP Services or a third-party SFTP server RAID storage configuration and redundant power supplies (recommended) Microsoft Windows Server 2008 CPU:2 x Dual Core Intel Xeon 5130 processor (2GHz, 1333MHz FSB) RAM: 2 GB, 667 MHz Storage: Operating system plus 2MB storage per minute of video content Microsoft Windows Media Services 9 Series Microsoft.NET Framework 3.5 Microsoft FTP Services or a third-party SFTP server RAID storage configuration and redundant power supplies (recommended) Windows Media Server considerations When you are choosing a machine for your Windows Media Server, there are additional hardware requirements and limitations that you must take into account: Windows Media Services is not installed initially on the Windows Server 2008 so you must first download and install it before the Streaming Media Services server role is available. You will then add the Streaming Media Services server role using Windows Server Manager (Server Manager > Roles > Add Roles). Multicast requires the Enterprise or Datacenter Editions of Windows Server 2003 SP1 and Windows Server

10 Getting started Windows Media Services is not supported on Windows Server 2008 for Itaniumbased systems. You can install Mediasite software on 64-bit versions of Windows Server 2003 SP1 (Enterprise and Datacenter editions) and Windows Server However, you will not be able to use the reporting and logging features on a 64-bit version of Windows Server 2003 SP1 because Microsoft does not support plug-ins on these machines. You cannot install Mediasite Server Control Service (MSCS) software on a 64-bit machine where Mediasite Editor or Podcast software is already installed because the MSCS software cannot co-exist with them. For more information, contact our technical support experts using the SmartServe Portal at To play presentations on Mac computers and use push distribution for live presentations, you must enable HTTP streaming in Windows Media Services. HTTP streaming is required for Silverlight playback. If you install EX Server on the same machine as the Windows Media Server, there are additional system requirements to ensure that IIS and Windows Media Services coexist. For more information, see Enable Mac playback and push distribution on page 34 and How To Set Up Windows Media Services 9 Series to Use HTTP Streaming on Port 80 with IIS 6.0 Installed on the Microsoft website. System Manager system requirements The machine where the System Manager is installed must meet the following requirements: Microsoft Windows XP, Windows Server 2003 SP1, or Windows Server 2008 Microsoft.NET Framework 3.5 Microsoft MDAC 2.7 or later Typically, the System Manager is installed on the same machine as the EX Server software, but it can also be installed on a desktop computer. 10

11 Getting started Database server requirements Use MySQL 5.0 or later, Microsoft SQL Server 2000, or Microsoft SQL Server 2005 for the Mediasite database. EX Server deployment options There are several deployment options for Mediasite installations all with their own requirements, benefits, and pre-installation routines so it is very important to plan your EX Server installation. This section describes these deployment scenarios and gives you enough information so you can avoid confusion when deploying Mediasite. The following software is required for all deployment options: The database server Windows Media Server Mediasite EX Server ADAM (AD LDS) To help you plan your installation, we provide technical planners that describe how to integrate Mediasite into your network. These documents should be read and understood before you install any software. Mediasite for the Enterprise: explains how to plan a Mediasite deployment on your network for different scenarios and list best practices when deploying a Mediasite Server. Network Setup and Firewall Consideration: explores issues most commonly encountered when installing and running Mediasite in an existing network. Mediasite Access Control: provides an overview of access control in Mediasite and the manner in which an external directory can be set up to work with Mediasite in an enterprise. These documents are available on the SmartServe Portal at Standard installation The simplest EX Server deployment is the standard installation in which the EX Server software is installed on one machine. You may install EX Server software on the same machine as other system components. However, to accommodate anything beyond the smallest installations, we recommend using separate machines for the EX Server, the Windows Media Server, and the database server. 11

12 Getting started 12 High-availability installation In a high-availability installation two or more EX Servers work redundantly to improve reliability, fault-tolerance, or performance. In a high-availability installation, you install each EX Server on a machine that works with a network load balancer and manage the primary and secondary EX Servers as a single system. All EX Servers in the installation point to common data sources and access them across the network. You will set-up machines with network load-balancing to support a high- availability installation before installing the EX Server software on those machines. The network load balancer s IP address or FQDN is required during installation. The number of servers required in a high-availability installation depends on your usage requirements and how you choose to configure your system. During a presentation, the load on the EX Server is directly proportional to the number of viewers so it is important to estimate the maximum number of viewers there will be at any given time, how many presentations you will have on your EX Server, and whether your presentations will be largely on-demand presentations or live broadcasts. Also, you must take into account your network configuration and its current bandwidth usage and requirements from everyday traffic. When planning the number of servers needed for a high-availability installation, you must also consider how the machines will host the software: 1. Will the Mediasite and presentation data be stored on a dedicated machine, such as a NAS or SAN, or on one of the EX Servers? Take into consideration that the amount of data stored increases as the number of presentations on the EX Server increases. 2. Will the Microsoft ADAM or AD LDS software, which will be configured to run the Mediasite Directory that stores user credentials and groups, be installed on a dedicated machine? 3. Will the database server, which stores all information about the deployed system, be installed on a dedicated machine or will you use a database server already on your network? 4. Will the Media Server, which serves video to the audience during a presentation, be installed on a dedicated machine? How you answer the questions above will depend on your network configuration and available resources as well as your expected average server load. For example, if you will have a large number of on-demand presentations, you may choose to have two EX Servers with the primary EX Server hosting the Mediasite Directory, a dedicated machine for storing Mediasite and presentation data, a dedicated machine for your database server, and another machine for the Media Server.

13 Getting started In a high-availability installation, each machine must meet the minimum EX Server system requirements listed on page 8. Each additional EX Server requires a high-availability license. To purchase Mediasite EX Server high-availability licenses contact your Sonic Foundry account representative or reseller. Multiple EX Server installations on a single server You can install multiple instances of EX Server software (up to a maximum of 20) on a single machine, which results in centralized operations and reduced server hardware costs. Each EX Server exists independently of the other servers on the machine, must have its own database and Mediasite Directory, and can be installed as a standard or high-availability installation. The number of machines required when installing multiple EX Servers on a single machine depends on how you configure each one. Also, for each EX Server you may use a different Windows Media Server or the same Windows Media Server with different on-demand publishing points and FTP directories for each EX Server. Each additional installation of EX Server software on the same machine requires a multiserver install license. To purchase Mediasite EX Server multi-server install licenses, contact your Sonic Foundry account representative or reseller. Additional installation and configuration considerations Whether you are doing a standard, high-availability, or multiple EX Server installation, there are other things to consider when installing and configuring your system if you are using Secure FTP (SFTP), secure socket layer (SSL) or Mediasite Podcasting. Sonic Foundry does not provide SFTP software or SSL certificates. Secure FTP If you plan to use secure FTP on the Mediasite Server, you must install and configure third-party SFTP software and then configure the virtual directories required for the Mediasite Server in the SFTP software. If your SFTP server uses FTP over SSH or FTP with SSL, the FTP Data URLs will use sftp:// or ftps://, respectively. For example: sftp://mysecureftpserver.mycompany.net or ftps://mysecureftpserver.mycompany.net 13

14 Getting started For more information on secure FTP, see the documentation included with your SFTP Server software. For more information on using secure FTP with the Mediasite Server, see Secure communication on page 16 and Preparing the EX Server s data locations on page 20. Also see KB Article available on the SmartServe Portal at Secure Socket Layer If you plan to use secure socket layer with the Mediasite Server or an external directory, you must purchase SSL certificates and install them before you begin installing and configuring Mediasite software. When using SSL on the Mediasite Server, instead of applying SSL to the root of the website, enable it only on the LoginForm virtual directory, which maps to the Mediasite Login form. The Login Form is the only web page that passes usernames and password in clear text. Once you have applied SSL to the LoginForm virtual directory, you must update the Login Form URL, so that it uses instead of For example: When using SSL with an external directory, you must configure SSL on the server where the directory is installed. Also, you must ensure the appropriate port is open between the server and the Mediasite Server. The default port number for SSL is 636. When SSL is not used, the default port number is 389. Using IIS Manager, you will update the Login Form URL as one of the properties for the Mediasite installation s root virtual directory. On Windows Server 2003, you will update the URL on the virtual directory s ASP.NET > Edit Configuration > Authentication properties page. On Windows Server 2008, you will go to the IIS > Authentication > Forms Authentication properties page. For more information, refer to the documentation included with IIS. Mediasite Podcast also sends user credentials to EDAS in plain text so if you will use podcasting you may want to also apply SSL to the ExternalDataAccess virtual directory. Mediasite Podcasting The Mediasite Podcast Generator (add-on sold separately) converts on-demand Mediasite presentations to podcasts. To use Mediasite podcasting, install the Podcast Generator on the same machine as the Mediasite Server or on a separate machine (recommended). If installed on the Mediasite Server, make sure to set the update time to the middle of the night when the server isn't 14

15 Getting started being used. Also, the installation machine must have a Pentium 4 processor or better, preferably the Pentium D or Core processor. For more information on Mediasite Podcasting, see Installing and configuring the Podcast Generator on page 51 and the Mediasite Podcasting User Guide available on the SmartServe Portal at Migration from 4.x to The sequence for installing and configuring software when migrating from EX or LX Server 4.x to EX Server differs from that of a new deployment because you must also migrate, or move, data between the servers. Both systems must be operational to move data between them. Also, Mediasite 4.x and Mediasite can co-exist on the same hardware so that you can run Mediasite 4.x in production while testing Mediasite When planning your migration to EX Server 5.0.1, you must consider the following: Migration of data from the Mediasite 4.x installation to the Mediasite installation. Additional storage space. You will need twice the amount of storage space if you will run both Mediasite 4.x and Mediasite after migrating the data from the 4.x system. Bringing the Mediasite into production. You will bring down the Mediasite 4.x site and rename Mediasite such that the external links to presentations and catalogs are maintained or you will set up redirectors on the Mediasite 4.x site. Using redirectors will involve manual work because when Mediasite 4.x is uninstalled using the EX Server 4.x installer, the virtual directories are removed. You can migrate from 4.1 and later versions of the Mediasite Server. However, we recommend first upgrading to 4.3 and then migrating to For more information and migration instructions, see Migrating to Mediasite Server "on page 41. We strongly recommend that you plan your EX Server installation and migration. See Mediasite for the Enterprise available on the SmartServe Portal at 15

16 Getting started EX Server 5.0 upgrade The EX Server installers detect 5.0 software and automatically perform upgrades. Run the appropriate installers to upgrade the Scheduler, EX Server, Media Server Control Service (MSCS), and System Manager software. For more information, see the Mediasite EX Server Release Notes available on the SmartServe Portal at Mediasite security Mediasite security is comprised of secure communication among the Mediasite applications and services, security for resources (applications, presentations, and system components) on the EX Server, and security for content on the Windows Media Server. EX Server security must be managed by someone with a solid background in role-based security and how it is implemented in your network, especially if an external directory is used with the EX Server. Secure communication The EX Server, the Recorder, and the MSCS all use Windows Communication Foundation (WCF) to ensure secure communication among Mediasite applications and services. The Mediasite installers generate and install certificates in the Local Machine Store of machines running EX Server, MSCS, or Mediasite Podcast software as well as the Mediasite Recorder. Certificates are used, for example, when you connect a Recorder to the EX Server or add a site to the System Manager. EX Server also includes a secure FTP (SFTP) client that allows you to use a third-party SFTP server to transmit presentation data securely between the Recorder and the EX Server. To use SFTP with the EX Server, you must install and configure your SFTP server software and create virtual directories before you install and configure Mediasite software. For more information on the virtual directories required for the EX Server when using SFTP, see Preparing the EX Server s data locations on page Security for resources on the EX Server Resources on the EX Server are secured using Windows forms authentication, directories connected to the EX Server, and roles. Roles are database objects associated with an implicit set of permissions that map to users and groups in directories connected to the EX Server. Before others can use resources on the Mediasite Server, you must give them

17 Getting started access by adding roles, groups and users (if using the Mediasite Directory), and assigning permissions. You assign permissions to resources on a role-by-role basis to give users varying levels of access to the web applications and presentations. Users must log in to use the web applications and to play back, record, or edit presentations on the EX Server and are authenticated by the system using credentials stored in the directory. They are granted or denied access to a resource based on the permissions assigned to their corresponding roles. The Mediasite Directory, which is based on Microsoft's ADAM (AD LDS on Server 2008), stores users and groups and includes built-in users, groups, and roles. EX Server requires a connection to the Mediasite Directory to function because of the built-in roles in the directory. However, you can also connect the EX Server to an external Active Directory or an LDAP-based directory and add roles to the Mediasite system for users and groups in the external directory. You will assign these roles permissions to Mediasite resources in the same manner as roles added from the Mediasite Directory. EX Server is secure by default, meaning you can lock yourself out if you do not write down the credentials of the built-in user, MediasiteAdmin and the Mediasite Root URL. Initially, only the MediasiteAdmin user s credentials can be used to add a site for an EX Server to the System Manager, log into the web applications, and playback, record, or edit presentations on the EX Server. The MediasiteAdmin user has full permissions to all features and operations. Before others can use resources on the EX Server, you must log into the Management Portal or the System Manager as the MediasiteAdmin user and give them access by assigning permissions. For more information, see Configuring the Mediasite Directory on page 22, Add a site for the EX Server on page 37, Connecting the EX Server to an external directory (optional) on page 38, and the Mediasite Server Guide. Security for content on the Windows Media Server To secure publishing points on the Windows Media Server and minimize the risk of video content being passed to unauthorized users, the MSCS includes the Mediasite Authorization plug-in. You will enable and configure the Mediasite Authorization plugin to secure the publishing points. When security is enabled on a Broadcast Server, the Mediasite Authorization plug-in automatically secures content on any unicast publishing point created by the MSCS. For more information on securing content on live and on-demand publishing points, see Enable and configure the Mediasite plug-ins on page 35 and Add a Unicast Pull Broadcast Server in the Mediasite Server Guide. 17

18 Getting started Microsoft does not support plug-ins on the 64-bit version of Windows Server 2003 SP1. 18

19 Deploying Mediasite Server Mediasite offers several different deployment options but all include the same core components. Thus, the installation and configuration process is fundamentally the same for all EX Server deployments. To deploy the Mediasite system, you will: 1. Prepare the Mediasite database, EX Server s data locations, and the Windows Media Server, see pages Install Microsoft ADAM SP1, see page Configure the Mediasite Directory, see page Install the Media Server Control Service, see page Install the Scheduler on machines where the EX Server software will be installed (optional), see page Install EX Server software on one or more servers, see pages Test the EX Server settings, see page Configure the Windows Media Server (optional), see page Install and configure the System Manager, see page Synchronize the clocks on the servers and your Recorders, see page Connect the EX Server to an external directory (optional), see page Attached to the front cover in this guide is the Mediasite EX Server Installation Checklist. Use this checklist to track vital information during installation. More advanced users can use the checklist to install or migrate to Mediasite EX Server Preparing the Mediasite database The Mediasite database is a core component of any EX Server deployment. EX Server supports either MySQL or Microsoft SQL Server as its database server. For all installations, you must prepare the database before you install the EX Server software. To prepare the Mediasite database: 1. Create an empty database on the database server. When you install multiple EX Servers on the same machine, each EX Server requires its own database. 19

20 Deploying Mediasite Server 2. Create a database user with owner-level permissions for the empty database. The EX Server installer uses these credentials, specified during the installation process, to create the tables in the Mediasite database and populate them with values. 3. When using MySQL 5.0 or later, enable the old password encryption method on the database server. For more information on configuring your database server, see the documentation included with the software. If you are using MySQL, you should ensure that you are using a properly licensed installation. Also, we do not recommend using the MySQL database server when installing multiple EX Servers on a single server. Doing so may infringe upon MySQL license terms. You can find complete licensing information at Preparing the EX Server s data locations The EX Server s data locations are where Mediasite data (configuration files, Viewer and presenter image files, temporary files required for multicast, etc.) and presentation data (image and SAMI files associated with presentations) are stored. Data is uploaded to the data locations using FTP or secure FTP (SFTP) if you are using an SFTP server. Mediasite and presentation data can be stored locally on the machine where the EX Server software is installed or on a network share on a different machine. When data is stored locally, it is referred to as a local data location. When data is stored on a separate machine, this is referred to as a remote data location. Remote data locations are required when deploying EX Server in a high-availability environment because all servers point to a common data source. For all installations, you must specify the values the installer needs to create the data locations. What items you need to create depends on how you have chosen to configure your data location. To prepare your EX Server s data locations, do the steps that apply: 1. If you will store Mediasite and presentation data locally, create a local user on the machine where the EX Server software will be installed. Once installation is complete, assign this user write permission to the Mediasite data and presentation data folders created by the installer. 2. If you are using a remote data location to store the Mediasite and presentation data, create a network share on the machine and give a network user write permissions for the share. Write down the path of the network share. 20

21 Deploying Mediasite Server 3. If you want to create the virtual directories manually or are using secure FTP, create FTP virtual directories for the Mediasite and presentation data folders on the machine where the FTP or SFTP server is installed. Write down the URLs for the virtual directories. 4. If you are using IIS FTP user isolation, give a user on the network write permissions for the FTP server. Write down the URL of the FTP server. It is helpful to use names for the items above that will help you to remember their purpose. For example, MediasiteNetworkUser as the name of the network user when using a remote data location. Preparing the Windows Media Server The Windows Media Server streams video when a presentation is played back by a viewer. For all deployments, when installing EX Server software, you must specify the names of the Window Media Server s publishing point and FTP virtual directory. You also need the credentials of a FTP user. These items are not created by the installer and must be created before you begin installing EX Server software. To prepare the Windows Media Server: 1. Ensure the Windows Media Server meets the system requirements. 2. Create an FTP virtual directory that points to the location to which media files will upload when you publish presentations to the EX Server. 3. Create a local user on the Windows Media Server and give the user write permission for the source folder to which the FTP virtual directory points. This user s credentials are used to upload video files to the Windows Media Server using FTP. 4. Create an on-demand publishing point on the Windows Media Server that points to the same source folder as the FTP directory. It is helpful to use names for the items above that will help you to remember their purpose. For example, MediasiteUser as the name of a user or MediasiteVideo as the name of the FTP virtual directory or source folder. Information to know before you begin installing When you install EX Server, you need the values of the items created in Preparing the Mediasite database, Preparing the EX Server s data locations, and Preparing the Windows Media Server as well as the following additional information: 21

22 Deploying Mediasite Server The encryption key you want to use to encrypt and decrypt data sent between the EX Server and the MSCS. The fully-qualified domain name (FQDN) or IP address of the machine where you are installing the EX Server software. The Windows Media Server s FQDN or IP address. Mediasite database information: server s FQDN or IP address, database type, database name, port number, username, and password. Mediasite Directory information: the server path of the Mediasite Directory, which includes the FQDN or IP address of the server where the directory is installed and the port number, and the passwords for the MediasiteAdmin and MEDIASITESYSTEM users. The load-balancer s FQDN or IP address if you are doing a high-availability installation. server information: the FQDN or IP address of an server and the address that will be used by the EX Server and the Scheduler to send about presentations, and the address for the person responsible for managing the EX Server. Installing Microsoft ADAM (AD LDS) The Mediasite Directory is based on Active Directory Application Mode (ADAM), or Active Directory Lightweight Directory Services (AD LDS) as it is called on Windows Server On Windows Server 2003 you must install Microsoft ADAM SP1, which is available for X86-based and X64-based machines, before you configure the Mediasite Directory. To install Microsoft ADAM SP1, run the appropriate installer available at and follow the prompts to install the software. AD LDS is available as a server role in the Windows Server 2008 OS. You will add the role using Windows Server Manager (Server Manager > Roles > Add Roles). The Mediasite Directory Configuration Wizard starts the required AD LDS services. Configuring the Mediasite Directory The Mediasite Directory stores user credentials and groups of users. Included in the directory are built-in Mediasite users and groups such as the required MediasiteAdmin user and the MediasiteAdministrators group. You will connect the EX Server to the 22

23 Deploying Mediasite Server Mediasite Directory by specifying the directory s server path, including the FQDN or IP address, when you install the EX Server software. To configure the Mediasite Directory: 1. Put the Mediasite EX Server software CD into your CD drive. From the Autorun screen, select Configure Mediasite Directory to launch the configuration wizard. If Autorun is disabled, double-click MediasiteDirectory.exe and follow the prompts to configure the Mediasite Directory. 2. On the Ports page, specify the LDAP and SSL ports. The default LDAP port is 389 and the default SSL port number is On the Select ADAM Instance Name and Folders page, specify the ADAM instance name and folders. If you do not want to use either of the default folder locations, click Browse to find another folder location or to make a new folder. 4. On the Set Password page, enter the password that will be used for the built-in Mediasite administrator account, MediasiteAdmin. 5. On the Set Mediasite System Password page, enter the password for the built-in Mediasite system user, MEDIASITESYSTEM. The Mediasite system runs under the context of this user. 6. On the Confirm Installation page, click Next to install the software. Once the installation has successfully completed, click Finish to exit the Wizard. 7. If you are installing multiple EX Servers on a single machine, install a Mediasite Directory for each one. Each directory must use unique values for the ports (any available port in the range: ), ADAM instance name, and folder names. At this point you have configured the Mediasite Directory. Now you install and configure the Media Server Control Service. If you are installing the EX Server in a high-availability environment, we recommend replicating the Mediasite Directory on another server to ensure that if it fails on one machine, another one is available. For instructions on replicating the Mediasite Directory (ADAM or AD LDS) on another server, see KBA available on the SmartServe Portal at Installing the Media Server Control Service (MSCS) MSCS creates publishing points on the Media Server just before a live presentation begins when Unicast Pull or Multicast Pull distribution is used. Unicast Pull distribution is used for the default Broadcast Server, which is created using values specified when the EX Server software is installed. 23

24 Deploying Mediasite Server You cannot install MSCS software on a 64-bit machine where Mediasite Editor or Podcast software is already installed because the software cannot co-exist. The MSCS installer also installs the Mediasite plug-ins, which are bundled with the MSCS software. For more information, see Enable and configure the Mediasite plugins on page 35. A multicast license is required to use Multicast Pull with Mediasite. To purchase multicast licenses, contact your Sonic Foundry account representative or reseller. Also, multicast must be supported on your Windows Media Server and network hardware. The MSCS software is installed on the Windows Media Server: 1. From the Autorun screen select Install Mediasite Media Server Control Service to launch the installation wizard. If Autorun is disabled, double-click MediaServerControlService.exe. 2. Follow the prompts to install the software. On the Media Server Distribution Settings page, specify the Media Server Control Service settings: Application URL: Enter a URL that includes the FQDN or IP address of the Windows Media Server and the port that the MSCS will use to communicate with the Mediasite Server. The default URL includes the domain name of the machine and port For example: Encryption Key/Confirm Encryption Key: The key needed to encrypt and decrypt data sent back and forth between the EX Server and the MSCS. 3. On the Ready to Configure page, click Next to install and configure the software. Once the installation has successfully completed, click Finish to exit the Wizard. Installing the Scheduler (optional) The Scheduler creates recurring presentations and allows you to automate all or part of the recording process. Installing the Scheduler is optional. You will install the Scheduler, which runs as a Windows service, on the same machine as the EX Server software. Mediasite applications communicate with the Scheduler using a web service. When you install the EX Server software, the installer registers the new EX Server with the Scheduler. In a high-availability installation, you will install the Scheduler on each machine in the installation. The installer registers each EX server with the Scheduler installed on its respective machine. When multiple EX Servers are installed on a single machine, each EX Server is registered and communicates with the Scheduler independently. 24

25 Deploying Mediasite Server To install the Scheduler: 1. From the Autorun screen, select Install Mediasite Scheduler to launch the installation wizard. If Autorun is disabled, double-click Scheduler.exe. 2. Follow the prompts to install the software. 3. On the Schedule Service Install Type page, specify the service settings: Scheduler Service Install Type: Select the New Schedule Service radio button. Port: The port the scheduling service will use to communicate with the Mediasite EX Server. The default port number is Service ID: This number identifies the scheduling service. When Mediasite scheduling is used in a high-availability installation, each physical server where the software is installed has a scheduling service with a unique service ID. This value is set to 1 for a new schedule service installation and cannot be modified. 4. On the Ready to Configure the Mediasite Scheduler page, click Configure. Once the configuration has successfully completed, click Finish to exit the Wizard. 5. If you are using the Scheduler in a high-availability installation, install the Scheduler software on every machine as described above, however, on the Scheduler Service Install Type page, select the Additional Scheduler Service radio button as the install type and enter a value for the service ID. The Service ID for each additional server in a high-availability installation must be unique and greater than 1. In the unlikely event that the installer does not register the EX Server with the Scheduler, you can register it from the Configuration Editor by going to Modules > Scheduler Configuration, entering the credentials of any user with administrative privileges, and clicking Create Site Registration. By default, the MediasiteAdmin user is used for scheduling. However, we recommend setting up another user with administrative privileges and using it for scheduling. Installing EX Server in a standard installation To install EX Server for a standard installation: 1. From the Autorun screen, select Install Mediasite EX Server to launch the installation wizard. If Autorun is disabled, double-click EX_Server.exe. 2. On the Choose New or Existing Server page, select the Enter a new Mediasite radio button and enter the Mediasite name. Follow the prompts to install the software. 3. On the Mediasite Server Location page, click Change to specify a location other than the default one. The default location is C:\Program Files\Sonic Foundry\Mediasite 25

26 Deploying Mediasite Server EX Server (<Mediasite_name>). Make sure to choose a location that has a large amount of disk space particularly if you will use a local Mediasite data location. By default, the Mediasite and presentation data folders are located here. 4. On the Mediasite Server Install Type page, select the New Mediasite Installation radio button. 5. On the Mediasite Data Location Type page, select the data location type settings: Mediasite Data Location Type: Select the Local radio button to have the Mediasite data and presentation data folders installed on the server. Select the Remote radio button to install these folders on a network share on a different server. Create FTP Virtual Directory (IIS only): By default, the installer will create FTP virtual directories in Internet Information Services (IIS) that point to the Mediasite data and presentation data folders. Clear this check box if you want to create the FTP virtual directories manually. Do not use FTP Virtual Directories: Select this check box if you want to use directories instead of virtual directories on the FTP Server to access the Mediasite data and presentation data folders. If you are using secure FTP (SFTP), you must create the virtual directories manually because IIS does not support secure FTP. If you are using FTP User isolation in IIS, select the Do not use FTP virtual directories check box. 6. On the Mediasite Data Location page, specify where you want to install the Mediasite and presentation data folders. The settings displayed on this page depend on the data location type selected on the Mediasite Data Location Type page. If you are using a local Mediasite data location, click Change to browse to an existing folder on the server or create a new one. The default location is the Mediasite Server Location. Write down the path. You will need this path later when you assign the FTP user permissions to the Mediasite and presentation data folders. If you are using a remote Mediasite data location, specify the network share and the credentials of a network user: Network Location: The path for the network share. The path should include the FQDN or IP address of the server and the name of the network share. If the network share is inaccessible across the network, the installer will not continue. Username: The username for a network account with read and write permissions to the network share. Password/Re-enter Password: The password. 26

27 Deploying Mediasite Server 7. On the Web Site Details page, specify the following web server settings: Website: Choose a web site for the web server from the drop-down list. Virtual Directory: The installer creates this virtual directory on the server. This virtual directory points to the Mediasite web applications and services. The default value is the Mediasite name. HTTP Server URL: The URL of the web server. The URL should include the FQDN or the IP address of the server. The default value is a URL that uses the FQDN detected by the installer. The HTTP Server URL and the Virtual Directory make up the Mediasite Root URL, which determines the URLs for the Mediasite web applications and services. 8. On the FTP Site Details page, specify the FTP settings that will be used to upload data to the EX Server. The settings displayed on this page depend on the FTP virtual directory option selected on the Mediasite Data Location Type page. If you used the default setting with the Create FTP Virtual Directory check box selected, the installer will automatically create the FTP virtual directories in IIS using the following settings: FTP Site: Choose an FTP site for the FTP server from the drop-down list. Mediasite Data Virtual Directory: Enter a name for the FTP virtual directory that will point to the Mediasite data folder. The installer creates this virtual directory on the EX Server. The default value is <Mediasite_name>Data. Slide Image Virtual Directory: Enter a name for the FTP virtual directory that will point to the presentation data folder, which is the default location for storing slide images for a presentation. The installer creates this virtual directory on the EX Server. The default value is <Mediasite_name>PresentationData. FTP Server URL: The URL of the FTP server. The URL should include the FQDN or the IP address of the server. The default value is a URL that uses the FQDN detected by the installer. Username: The username for a local user on the server. These credentials are used to access the Mediasite and presentation data folders using FTP. Password/Confirm Password: The password. If you are manually creating your FTP virtual directories, you must first create the directories first and specify the following settings in the installer: 27

28 Deploying Mediasite Server Mediasite Data FTP URL: The URL of the Mediasite data FTP location. The URL must include the FQDN or the IP address of the FTP server and the name of the folder. Presentation Data FTP URL: The URL of the presentation data FTP location. The URL must include the FQDN or the IP address of the FTP server and the name of the folder. Username: The username of a local user on the FTP server. Password/Confirm Password: The password. If you are using secure FTP, the URLs will have one of the following formats: sftp://myserver.yourcompany.net/mediasitedata (FTP over SSH) ftps://myserver.yourcompany.net/mediasitedata (FTP with SSL) If you are using directories instead of virtual directories to access your data folders on the FTP server, the installer will create the directories using the following settings: FTP Server URL: The URL of the FTP Server. The URL must include the FQDN or the IP address of the FTP server and the name of the folder. Username: The name of a network user. Password/Confirm Password: The password. 9. On the Media Server Distribution Settings page, specify the Media Server Control Service and Windows Media Server s on-demand distribution settings: Domain Name/IP Address: The FQDN or IP address of the Windows Media Server where the MSCS is installed. This media server will broadcast live presentations. Port: The port the EX Server will use to communicate with the Media Server Control Service. The default value is The installer will automatically register the Mediasite Server with the MSCS using the domain name or IP address and port specified. Encryption Key/Confirm Encryption Key: The key needed to encrypt and decrypt data sent back and forth between the EX Server and the MSCS. Domain Name/IP Address: The FQDN or IP address of the Windows Media Server that will distribute media files for on-demand presentations. On-Demand Publishing Point: The name of an on-demand publishing point on the Windows Media Server. Leave this field blank to use the default on-demand 28

29 Deploying Mediasite Server publishing point. This publishing point will store on-demand content for the EX Server. 10. On the Media Server Upload Settings page, specify the following FTP settings for the On-Demand Media Server: FTP Server URL: The URL for uploading media files to the Windows Media Server using FTP. The default value is based on the FQDN or IP address entered for the Windows Media Server on the Media Server Distribution Settings page. If you are using secure FTP, the URL will have one the following formats: sftp://mediaserver.yourcompany.net/mediasitevideo (FTP over SSH) ftps://mediaserver.yourcompany.net/mediasitevideo (FTP with SSL) FTP Directory: The FTP directory on the Windows Media Server where the video for on-demand presentations will be uploaded when a presentation is published to the EX Server. FTP Username: The username for the FTP user on the Windows Media Server. These credentials are used to upload video for on-demand presentations to the Media Server using FTP. Password/Confirm Password: The password. 11. On the Mediasite Database Settings page, specify the database settings: Server Name: The name of the server where the empty database is installed. Database Name: The name of the Mediasite database. Database Type: Choose the type of database server you are using, MySQL or SQL Server. Server Port: The port the database uses to communicate with the EX Server. The default value is 3306 for MySQL, and 1433 for Microsoft SQL Server. Use Windows Integrated Security: Select this check box to use the credentials of a user on your Windows network. This option is available only with Microsoft SQL Server. Username: The username needed to connect to the database. Password/Confirm Password: The database password. 12. On the Directory Connections page, specify the Mediasite Directory settings: Server Path: The server path for the Mediasite Directory. The path must include the FQDN or IP address of the server where the directory is installed and the port 29

30 Deploying Mediasite Server number. The default server path uses the FQDN detected by the installer and port 389. Password: The password for the built-in Mediasite administrator user, MediasiteAdmin. Mediasite System User Password: The password for the built-in system user, MEDIASITESYSTEM. 13. On the Settings page, optionally, specify the server settings needed for use with the Scheduler. If you use the default values, the EX Server installer will use the default client on the local machine: Server Address: The IP address or FQDN of the server that will send automatic s when a new presentation is created or recorded. The default value is Server Port: The port the scheduling service will use to communicate with the server. The default port number is 25. Default Address: The address that will be used to send alerts when presentations are created by the Scheduler and invitations. The default value is user@localhost. Mediasite Administrator s Address: The address of the person to whom will be sent automatically when there is a problem scheduling a presentation on a Recorder. The default value is admin@localhost. 14. If you have installed the Scheduler software, the EX Server installer will detect it and will display a message asking if you want to register this Mediasite Server with the Scheduler. Click Yes to have the installer register the EX Server with the Scheduler automatically. Click No if you want to register the EX Server with the Scheduler later using the Configuration Editor. 15. On the Ready to Configure the Mediasite Server page, click Configure. When the configuration is complete, click Finish to exit the Wizard and view the configuration status log file. After installing the EX Server software, test the server s settings. See Testing the EX Server settings on page 33 for instructions. Installing EX Server in a high-availability environment Installing EX Server in a high-availability environment is a two-part process you will first install the EX Server software on the primary server then install the software on one 30

31 Deploying Mediasite Server or more secondary servers. Before you begin installing the software, ensure all servers can connect across the network to each other, the network share, the Windows Media Server, the database server, and the Mediasite Directory. Install EX Server on the primary server Install the EX Server software on the primary server using the steps described in Installing EX Server on a single server making sure to use a remote Mediasite data location and to specify the load-balancer s IP address or FQDN for the URLs on the Web Site Details and FTP Site Details pages. Install EX Server on secondary servers The EX Server installer configures additional servers using the primary server s configuration settings so you must ensure these servers can communicate with the primary server. You will modify the hosts file on each additional server so that the Mediasite installation s FQDN is tied to the primary server's IP address. If the installer cannot connect to the primary server, it will allow you to configure each additional server manually. Once all additional servers are installed, you will then modify the hosts file on all servers so that the Mediasite installation s FQDN points to the local loopback address. If the ASP.NET worker process is being run as an identity, the user profile on the machines (primary and additional) must be created before installation, that is, the identity needs to log into both machines at least once. This needs to be done because certificates are stored in the identity s certificate store. To install the EX Server software on a secondary server: 1. From the Autorun screen, select Install Mediasite EX Server to launch the installation wizard. If Autorun is disabled, double-click EX_Server.exe. 2. On the Choose New or Existing Server page, select Enter a new Mediasite and enter the Mediasite name. Use a name that will help you to identify this as a secondary server, for example <Mediasite_name>_server2. 3. Follow the prompts in the Wizard to configure the secondary server. 4. On the Mediasite Server Install Type page, select the Additional Server in an existing Mediasite Installation radio button. 5. On the Mediasite Data Location Type page, select the Remote radio button. By default FTP virtual directories that point to the Mediasite and presentation data folders will be created on this server to provide load-balancing for the FTP virtual directories on the primary server. Clear the Create FTP Virtual Directories check box if you don t want to create these directories on the secondary server. 31

32 Deploying Mediasite Server 6. On the Mediasite Data Location page, enter the same network share and security credentials specified on the primary server. 7. On the Web and FTP Sites page, select the same Web and FTP sites selected on the primary server. These sites must use the same ports as the ones specified on the primary server. The FTP drop-down list is not shown if the Create FTP Virtual Directions check box was not selected. 8. On the Primary Mediasite Server Settings page, enter the following information about the primary server: Primary Mediasite Server URL: The primary server s Mediasite Root URL including the FQDN or IP address of the primary server and the Mediasite name, for example: The primary server s Mediasite Root URL is not the installation s Mediasite Root URL. The installation s Mediasite Root URL uses the load-balancer s FQDN or IP address. Mediasite System User/Password: The same Mediasite system user password specified on the primary server. 9. On the Ready to Configure the Mediasite Server page, Click Configure to configure the secondary server using the selected settings. When the configuration is complete, click Finish to exit the Wizard. After installing the EX Server software on the primary and secondary servers, test the settings on each server. See Testing the EX Server settings on page 33 for instructions. Installing multiple EX Servers on a single server 32 You can install multiple instances of the EX Server software (up to 20) on a single machine, which results in centralized operations and reduced server hardware costs. Each EX Server has its own database and Mediasite Directory, exists independently of the other servers, and can be installed as a single server or as a high-availability server. The number of machines required when installing multiple EX Servers on a single machine depends on how you configure each EX Server. You may use a different Windows Media Server or the same Media Server with different on-demand publishing points and FTP directories for each EX Server. When naming the Mediasite for an EX Server, use a name that will help you to distinguish it from the others. To install an EX Server as a single server, follow the steps in, Installing EX Server in a standard installation on page 25.

33 Deploying Mediasite Server To install an EX Server in a high-availability environment, follow the steps in Installing EX Server in a high-availability environment on page 30. After installing the EX Servers, test the settings for each server. See Testing the EX Server settings on page 33 below for instructions. Testing the EX Server settings You can test the EX Server s settings using the Configuration Editor web application. The server settings in the Configuration Editor are pre-configured using values set when you installed the EX Server software. To test the EX Server settings: 1. Launch the Configuration Editor by entering the URL in the web browser on the server on which the EX Server software is installed. For security reasons, the Configuration Editor can only be launched from this server. The Configuration Editor s URL has the following form: name>/configurationeditor The Configuration Editor runs using Windows integrated authentication. This means that to use it, you need to authenticate yourself using administrator credentials on the machine. These credentials are usually cached, but the first time you use the Configuration Editor you may be prompted to re-enter your credentials. Also, when the System Manager is installed on the same machine as the EX Server software, you can use it to launch the Configuration Editor instead of entering the URL into the web browser. 2. Click one of the following tabs in the Configuration Editor to test or verify the settings on that page: Database Connection: Click Test Connection to test the connection to the Mediasite database. Security: Click the Mediasite Directory link and click Test Connection to test the connection to the Mediasite Directory using the credentials of the MediasiteAdmin. Site Info: Click Test Services to test the Mediasite web services. Settings: Verify the server connection settings match the ones specified during the EX Server installation 33

34 Deploying Mediasite Server 34 Modules: You will go here to test or update the settings for modules being used with EX Mediasite Server such as the Podcast Generator. You will also come to this tab to register or unregister the EX Server with the Scheduler. For more information on the Scheduler, see Installing the Scheduler (optional) on page 24. For more information on Mediasite Podcasting, see the Mediasite Podcasting User Guide, found on the SmartServe Portal at Import: If you are using EX Server in a high-availability environment, launch the Configuration Editor on each of the secondary servers and verify the Mediasite Root URL displayed in the import settings. The Mediasite Root URL displayed here should use the FQDN or IP address of the primary server and not the load-balancer s FQDN or IP address. If the value is incorrect, enter the correct value and click Import. You will also use the Configuration Editor to connect the Mediasite Server to an external directory. For more information, see Connecting the EX Server to an external directory (optional) on page 38. Also, take note of the Mediasite Root URL on the Site Info page since you will use it to connect the System Manager or a Recorder to the EX Server. See Add a site for the EX Server on page 37 and the Mediasite Recorder Software Guide for more information. If any test does fail, verify the settings are correct. If the problem persists, contact Sonic Foundry s technical support experts on the SmartServe Portal at Caution: You can update most settings in the Configuration Editor. However, you must be very careful because the EX Server will not work if any of these settings are incorrect. Configuring the Windows Media Server (optional) Configuring the Windows Media Server includes enabling Mac playback and push distribution as well as enabling and configuring the Mediasite plug-ins. Configuring the Windows Media Server is optional. Enable Mac playback and push distribution To play presentations on Mac computers and use push distribution for live presentations, you must enable HTTP streaming in Windows Media Services. Push distribution is available in Microsoft Windows Media Services 9 (WMS) on both Windows Server 2003 SP1 and Windows Server 2008.

35 Deploying Mediasite Server To enable Mac playback and push distribution: 1. Enable HTTP streaming. If you will not use push distribution, you do not need to do the remaining steps. 2. Enable the WMS Publishing Points ACL Authorization plug-in. 3. Assign the FTP user on the Media Server permission to read, write, and create publishing points. 4. Give the Network Services user Modify, Read & Execute, List Folder Contents, Read, and Write permissions for the System Temp folder. For instructions on enabling HTTP streaming, see the documentation for your Windows Media Server. Enable and configure the Mediasite plug-ins The Mediasite plug-ins, Mediasite Media Authorization and Mediasite Media Logging, are installed along with the MSCS software on the Windows Media Server. The Media Authorization plug-in secures the publishing points on the Windows Media Server and minimizes the risk of presentation content being passed to unauthorized users. The Media Logging plug-in collects on-demand presentation playback data from the Windows Media Server for EX Server usage reporting, such as duration of presentation viewed. You will enable and configure the plug-ins for the Windows Media Server and each publishing point on which you want to secure content or collect playback data. Microsoft does not support plug-ins on the 64-bit version of Windows Server 2003 SP1. To enable and configure the plug-ins: 1. Select the server s name (root node) or the publishing point in Windows Media Services and click the Properties tab. 2. Click the Authorization category, right-click Mediasite Media Authorization Plug-in, and select Enable. 3. Right-click Mediasite Media Authorization Plug-in, select Properties, and select an EX Server from the Installed Mediasite Servers drop-down list. Only EX Servers registered with the MSCS are available in the drop-down list. The EX Server installer automatically registers the Mediasite Server with the MSCS using the domain name or IP address and port specified during installation. 35

36 Deploying Mediasite Server If you do not see the EX Server you want listed, use the Management Portal to verify the settings for the EX Server s default Broadcast Server are correct and to test the connection to the MSCS. If the test is successful, the EX Server is automatically registered with the MSCS. For more information, see Adding content servers in the Mediasite Server Guide. 4. Click Test Connection and click OK when the confirmation message appears. Click OK to apply your changes and exit the dialog. 5. Click the Logging category, right-click Mediasite Media Logging Plug-in, and select Enable. 6. Right-click Mediasite Media Logging Plug-in, select Properties, and select an EX Server from the Installed Mediasite Servers drop-down list. 7. Click Test Connection and click OK when the confirmation message appears. Click OK. Live broadcast publishing points are created dynamically by the MSCS so to secure them when using Unicast Pull distribution you must also enable security on the Broadcast Server. For more information, see the Mediasite Server Guide. See the documentation for your Windows Media Server for more information on the WMS settings. A secured on-demand publishing point cannot be shared between multiple EX Servers. Each EX Server must have a unique secured publishing point because the publishing point s URL points back to the EX Server. Installing and configuring the System Manager The System Manager is used to manage one or more sites. A site is an EX Server installation and can be either a single-server or high-availability deployment. Add a site for an EX Server to the System Manager, by connecting to it, to secure and manage the EX Server. By default, the System Manager is secure. Only the built-in Mediasite role, MediasiteAdmin specified during the Mediasite Directory installation, has permissions to add a site to System Manager. All other users must be assigned permissions. For more information, see Securing Mediasite Server in the Mediasite Server Guide. Install the System Manager The System Manager is installed on the EX Server or a desktop computer. 36

37 Deploying Mediasite Server To install the System Manager: 1. From the Autorun screen select Install System Manager to launch the installation wizard. If Autorun is disabled, double-click System_Manager.exe. 2. Follow the prompts to install the software. Once the installation has successfully completed, click Finish to exit the Wizard. A shortcut to System Manager appears on the desktop. Add a site for the EX Server You can add sites for multiple EX Servers to the System Manager. To add a new site: 1. Launch the System Manager using the shortcut on the desktop. Once System Manager opens, the Site Connection Properties dialog appears. If not, click Add New Site to display it. 2. Enter the site connection details for the EX Server: URL: The Mediasite Root URL for the EX Server. If you are adding a site for an EX Server in a high-availability environment, use the installation s Mediasite Root URL in which the load-balancer s IP address or FQDN is used. Username/Password: The credentials specified for the MediasiteAdmin user during installation. Test: Click this button to test the connection. If the connection fails, verify the information you entered is correct by comparing it against the data in the Configuration Editor and try again. 3. Click OK to add the new site. The System Manager is secure by default so initially only the built-in Mediasite user, MediasiteAdmin has permissions to add a site using System Manager. Once you secure your Mediasite system, you can assign permissions to use System Manager to others. For more information, see the Mediasite Server Guide. Synchronize clocks on the servers and the Recorder The clocks on the EX Server, the Media Server, and the Recorders must be synchronized to ensure all components work together correctly. Adjust the clocks manually or find software that will do this for you. Once the clocks are synchronized, reboot the computers so the software will detect the changes. 37

38 Deploying Mediasite Server Now that your EX Server is successfully deployed, you can optionally connect the EX Server to an external directory. Connecting the EX Server to an external directory (optional) Use the Configuration Editor to connect the EX Server to an external directory that stores the credentials of users and groups on your network. This allows you to manage internal Mediasite users separately from external Mediasite users. For example, external users would be stored in the Mediasite Directory while internal users for example students or employees would be stored in the external directory. The EX Server supports connections to the following directories: Microsoft Active Directory (AD) or a global catalog. A global catalog is an index of the Active Directory database that contains a partial copy of its contents. Lightweight Directory Access Protocol (LDAP) including ADAM directories other than the Mediasite ADAM directory installed as part of the Mediasite installation. Once connected to an external directory, you can add roles for groups and users in the directory to the EX Server to secure your Mediasite system. For more information, see the Mediasite Server Guide. The fields available to you on the directory connection pages depend on what directory you are using with your Mediasite Server. To connect the Mediasite Server to an external directory: 1. In the Configuration Editor, go to Security > Add New Provider and specify the settings needed to connect to the directory: Name: Enter the name of the provider. Provider Type: Choose LDAP Directory or Active Directory. Server Path: Enter the path of the directory. The path should include the FQDN or IP address of the server where the directory is located and the port. The default port is 389. The server path will have the following formats: LDAP://servername.company.net:389 or GC: //servername.company.net:389 (global catalog) SSL: Select this check box if you already have Secure Socket Layer configured on your system. When SSL is used, the SSL port should be used in the Directory Server Path. The default value for the SSL port is

39 Deploying Mediasite Server Base DN: Enter the distinguished name for the top level of the directory. Username/Password: Enter the credentials needed to connect to the directory. Use Anonymous authentication: This option is available only when connecting to a LDAP-based directory. Select this check box to connect to a LDAP directory that does not require user credentials. 2. Click Advanced Settings and specify the settings for accessing user and group information in the directory: Access group membership via the user directory entry: Select this radio button to determine group membership by inspecting the group membership property of the user directory entry. Access group membership via a group search: Select this radio button to determine group membership by searching the group member property of group directory entries. Users DN: The distinguished name for the user directory. Users ID Property Name: The attribute used to identify a User ID in the directory. User Display Name Property Name: The attribute used when displaying users. User Property Name: The attribute used to identify the primary address for the user. Group Membership Property Name: The attribute used to identify a user s group memberships. User LDAP Search Filter: The filter to use when searching the directory for users. Groups DN: The distinguished name for the group directory. Group ID Property Name: The attribute used to identify a group in the directory. Group Display Name Property Name: The attribute used when displaying groups. Group Member Property Name: The attribute used to identify a group member in the directory. Group LDAP Search Filter: The search filter to use when searching the directory for groups. Perform a nested group search: This check box is selected by default for LDAP. When selected, each sub-group within a group is searched for users as part of a group search. Clear this check box if you don t want to search subgroups for users. 39

40 Deploying Mediasite Server Determine group membership using security groups: This check box is not available for LDAP and is selected by default for Active Directory. When selected, security groups are searched including nested ones. Distribution lists are not searched. Return unlimited search results: This radio button is selected by default. This check box should be selected only if your directory supports paged searching. Return server limited search results: This radio button should be selected if your directory does not support paged searching. 3. Click Save. Click Test Connection to verify the directory connection using the settings above. Now that your EX Server is successfully deployed, you can connect Recorders to it and begin preparing, publishing, and organizing your presentations using the management applications. For more information on preparing, publishing, and recording presentations, see the Mediasite Server Guide and the Mediasite Recorder Software Guide. 40

41 Migrating to Mediasite Server This chapter explains how to migrate, or move data, from an EX or LX Server 4.x to an EX Server You will also find information to help you plan your migration and update the Recorder and Editor Software. You can migrate Mediasite data from version 4.1, 4.1.1, 4.2 and 4.3 versions of the EX or LX Server. However, we recommend upgrading to 4.3 software before you migrate data to If you are running version 4.0 of the EX Server, you must upgrade to the 4.3 version of EX Server before migrating Mediasite data to For instructions on updating an earlier version of EX or LX Server to 4.3 software, see Mediasite 4.3 LX Server Release Notes or Mediasite 4.3 EX Server Release Notes available on the SmartServe Portal at For purposes of documentation, we will be referring to migration from 4.x to 5.0.1, even though you cannot migrate EX Server 4.0 to EX Server For brevity, we will sometimes use 4.x Server to refer to a 4.x version of EX or LX Server and EX to refer to a version of EX Server. The sequence for installing and configuring software when going from EX or LX 4.x to EX differs from a new deployment because you must migrate data from the 4.x database to the database. Both systems must be operational when you begin migrating data using the Migration Wizard and each Mediasite Server should have its own copies of all media and image files. Also, we highly recommend that you test your EX before transitioning fully from a 4.x Server. To migrate from a 4.3 Server to an EX Server 5.0.1, you will: 1. Prepare the Mediasite database for the installation in the same manner described for a new deployment. 2. Copy the folders containing 4.3 media and image files to new locations. Each folder containing media or image files on the 4.3 Server maps to an on-demand server or image server, respectively, on the 4.3 Server. Similarly, the new locations will map to on-demand and image servers on the EX You will need these locations when you use the Migration Wizard so write them down. 3. Assign the same write permissions to the new locations that were assigned to the original ones. 3 41

42 Migrating to Mediasite Server Create FTP (or SFTP) virtual directories and on-demand publishing points that map to the locations where the media files have been copied. 5. Create FTP (or SFTP) virtual directories that point to the locations where the image files have been copied. 6. Install all Mediasite software, except for the Mediasite Directory in the same manner described for a new deployment. You will reuse the 4.x Mediasite Directory with the EX The Migration Wizard uses RoleIDs to set up mappings between roles defined on the two Mediasite Servers. To ensure the Migration Wizard maps roles, ownership, and permissions correctly, you must connect the EX to the same directories used with 4.x. You will then do the following additional steps that apply: 1. Connect the EX to the same external directory to which the EX 4.x is connected using the Configuration Editor. 2. Use the Management Portal to add broadcast media (live), on-demand, and slide (image) servers to the EX that map directly to those on the 4.x Server. The settings for the 5. 0 image and on-demand servers must map to the locations where the media and image files were copied. The EX installer will create the default servers using the data you specify during installation but the remaining servers must be created manually. 3. Use the Mediasite Migration Wizard, which is packaged in the Mediasite Migration Toolkit as well as bundled with the EX software, to move content in the 4.x database to the database. 4. Run the Media Upgrade Tool, which is packaged in the Mediasite Migration Toolkit, in the new media file locations. Upgraded media files will not work with the 4.x system in some cases, such as when using Silverlight to playback presentations. 5. Enable logging and authorization on the on-demand publishing points using the Mediasite plug-ins. 6. After you transition to the EX 5.0.1, uninstall the 4.x versions of EX or LX Server, the System Manager, and MSCS software. 7. Optionally, rename the virtual directory to reuse the 4.x URLs. For instructions on doing the steps above, see Deploying Mediasite Server on pages 19-38, Using the Migration Wizard on page 43, Uninstalling 4.x software on page 45, and Renaming the virtual directory (optional) on page 46. Also, see Adding content servers in the Mediasite Server Guide. 42

43 Migrating to Mediasite Server Catalog mappings In the release, you can add multiple catalogs to each EX Server in addition to the default catalog. You can add catalogs containing presentations from any folder on the Mediasite Server, and you can add linked catalogs that map directly to folders on the Mediasite Server. Each catalog and catalog folder has a unique URL that includes its name. In the 4.x releases, a single Presentation Catalog was associated with each Mediasite Server. Folders were included in the Catalog as categories and were associated with a specific layout. In 4.x, there was also an option to hide folders from the catalog since all folders were included by default. Because of the differences in the and 4.x catalogs, when you migrate 4.x catalogs to EX each category layout in 4.x is mapped to a catalog. All 4.x folders (categories) using a particular layout in 4.x will be included in the corresponding catalog as linked folders. All folders that were hidden from the Catalog in 4.x will appear only as folders in They will not be included in any catalog. All catalog URLs from a 4.x Server will work with the EX Server. For more information on catalogs see Working with catalogs in the Mediasite Server Guide. In the Migration Wizard, migrating 4.x catalogs is optional. Because your folders and presentations are moved over to the EX intact, you can easily use them to create new catalogs. Using the Migration Wizard Use the Migration Wizard to move data from your 4.x database to the database. When complete, presentations and system components (server groups, Players, presenters, encoding profiles, and so forth) are available on the EX Server and have the appropriate ownership and permissions assigned to them. To migrate data to the EX database: 1. Double-click the MigrationTool.exe file, which is located in the Mediasite Migration Toolkit. Follow the prompts to migrate the data. 2. On the Migration Type Selection Page, select Migrate from Mediasite 4.1, 4.2 or 4.3 to Mediasite

44 Migrating to Mediasite Server On the Mediasite Source Database Settings page, specify the source database s server name, database name, database type, server port, and the database owner s username and password. 4. On the Mediasite Destination Database Settings page, specify the source database s server name, database name, database type, server port, and the database owner s username and password. If both of the Mediasite Servers are on the same machine, the source and destination database settings will be pre-filled. 5. On the Server Mapping page, for each slide (image), broadcast media (live media), and on-demand media server on the 4.x Server, select a corresponding server of the same type from the drop-down list. The server on the 4.x Server will be mapped to the selected server on the EX If you have not added any servers to the EX only the default servers will be available in the drop-down lists. 6. On the Presentation Data Location page, for each slide (image) server select the presentation data location. The default location is the path you specified when you created the slide server and is the location where you copied your 4.x presentations. If the path is incorrect you will receive an error message warning you that the slide server may not work correctly once you migrate the data. If you receive an error message, enter the path where the 4.x presentations were copied and click Check Paths to verify the correct locations have been specified. If the test fails, exit the Wizard, go to the Management Portal and verify that paths for the slide servers point to the locations where the presentations were copied. You will then have to restart the Migration Wizard. Optionally, specify additional data to migrate: Migrate Reporting Data: Select this check box to migrate reporting data from the 4.x Server to the EX along with the other data being migrated. Migrate Catalogs: By default, 4.x catalogs are migrated to EX Clear this check box if you do not want to reuse your 4.x catalogs. You will have to create new catalogs on the EX manually. You can also migrate 4.x reporting data separately to the EX using the Migration Wizard by selecting Migrate Reporting Data from Mediasite 4.1, 4.2 or 4.3 to Mediasite on the Migration Type Selection page. 7. On the Ready to Migrate the Mediasite data page, click Migrate to begin the data migration using the selected settings. Once the migration has completed, click Finish to exit the Wizard. 44

45 Migrating to Mediasite Server Using the Media Upgrade Tool The Media Upgrade Tool takes the scripts out of the video and transcodes audio on presentations using the Windows Media Audio 9.x Voice codec. You must run the Media Upgrade Tool so your media files will work correctly with the EX. Caution: Upgraded media files will not work with the 4.x system in some cases, such as when using Silverlight to playback presentations, so only run the Media Upgrade tool against folders mapping to on-demand servers. To upgrade your media files using the Media Upgrade Tool: 1. Double-click the VoiceCodecConverter.exe file, which is located in the Mediasite Migration Toolkit. 2. Browse to the directory containing the media files. The publishing point on the Windows Media Server points to this location. 3. Clear the Keep Back-up Files check box to remove back-up files created by the Media Upgrade Tool. 4. Click Convert. The conversion may take several minutes if you have a large number of media files. 5. If you kept the back-up files, click Clean to remove them. When the confirmation message appears, click OK. Uninstalling 4.x software Once you are ready to transition to the EX Server 5.0.1, uninstall the 4.x versions of the System Manager, EX or LX Server, and MSCS software. Before you delete the 4.3 Server software and folders, you must first remove the 4.x configuration using the 4.x Server installer: 1. Double-click EX_Server.exe to launch the installation wizard. 2. On the Choose New or Existing Server page, select the Select an existing Mediasite radio button and choose your 4.x Server. Click Next. 3. On the Choose Wizard Action page select the Remove Configuration radio button. Click Next. 4. On the Ready to remove the Mediasite Server configuration page click Next. The installer begins removing the configuration. When the configuration is complete, click Finish to exit the Wizard. 5. Use the Windows Control Panel > Add or Remove Programs to remove the 4.x versions of the System Manager, EX or LX Server, and MSCS software. 45

46 Migrating to Mediasite Server Once the software is uninstalled, reboot the server and delete the 4.x software installation folders. Renaming the virtual directory (optional) Use the EX Server installer to rename the virtual directory if you want to reuse the URLs from 4.x. Renaming the virtual directories is optional. To rename the virtual directory: 1. Launch the EX installer, check Select an existing Mediasite, select the Mediasite you want to update, and click Next. 2. Select the Rename Root Virtual Directory radio button and click Next. The Mediasite EX Server Configuration Wizard is automatically launched. 3. Follow the prompts in the Wizard to configure the EX Server. 4. On the Web Site Details page, enter a new name for the virtual directory. 5. On the Ready to Configure the Mediasite Server page, click Configure. When the configuration is complete, click Finish to exit the Wizard. Upgrading Recorder 4.x The Recorder installer upgrades Recorder 4.x to Recorder includes the Mediasite Recorder Control Service 5.0, which listens on port The RL Recorders also include the Mediasite Serial Communications Service 5.0. The Recorder installer also bundles the Recorder 4.3 software. A switcher application is installed that you can use to switch between 4.x and software on your Recorders. Switching between the two versions allows a Recorder to connect to either a 4.x or EX Server. See the Mediasite Recorder Release Notes available from the SmartServe Portal at for instructions on upgrading to Recorder Recorder can connect only to 5.0 and EX Servers. Recorder 4.3 can connect to all 4.x EX or LX Servers. Also, note that the Recorder Control Service for 4.3 listens on port

47 Migrating to Mediasite Server Upgrading Editor 4.x When a Recorder 4.x is upgraded to 5.0.1, the Editor software is also installed. The Editor software does not replace the Editor 4.x software. Instead both versions of the Editor will be available on the Recorder. You will use the Editor installer to install Editor on a desktop computer. See the Mediasite Editor Release Notes available from the SmartServe Portal at for instructions on upgrading to Editor

48

49 Updating the Mediasite Server settings In this chapter you will find instructions on using the Configuration Editor to update the Mediasite Root URL, a secondary server s import settings, and the Mediasite Directory connection. Updating the Mediasite Root URL The Mediasite Root URL determines the URLs for the EX Server s web applications and services. You may need to update the Mediasite Root URL when you update the FQDN or IP address of the EX Server (or the load-balancer if installing in a high-availability environment). For example, the FQDN of the EX Server may change when the server is moved from a demonstration system to a production system. To update the Mediasite Root URL: 1. Go to Site Info, update the Mediasite Root URL and click Save. 2. Test the web services to verify they are working correctly. If the services pass, click Save to apply your changes. If not, verify that you are entering the correct information and try again. 4 Caution: Once you change the Mediasite Root URL on the EX Server, you must update it in every location where it has been entered to keep your system functioning correctly: the MSCS, the System Manager, Recorders connected to the EX Server, and the plug-ins. Also, existing links on external web pages will stop working once the RootURL is updated. Updating the import settings on a secondary server The import settings specify the details of the primary EX Server from which secondary servers in a high-availability installation will retrieve configuration data. When you update the Mediasite system user password, IP address, or FQDN on the primary EX Server, you must update the import settings on the secondary servers. Updating the import settings ensures the EX servers can continue to communicate with each other. 49

50 Updating the Mediasite Server settings To update the import settings on a secondary server, go to the Import tab, update the values as needed, and click Import. Using the secure socket layer for the Mediasite Directory connection The EX Server s connection to the Mediasite Directory is added using the values specified during the installation and by default does not use the secure socket layer (SSL). However, if SSL is enabled on the server where your Mediasite Directory is installed, you can update the connection so that it uses SSL. To use SSL for the Mediasite Directory connection: 1. Launch the Configuration Editor on the Mediasite Server and go to Security > Mediasite Directory. 2. Select the SSL check box and update the port in the path so that it uses the SSL port. The default SSL port number is Click Save. 50

51 Appendix A Installing and configuring the Podcast Generator The Mediasite Podcast Generator, a separately sold EX Server add-on, converts ondemand Mediasite presentations to podcasts. In Mediasite, podcasts are a collection of audio-only (.mp3) presentations distributed by RSS (Really Simple Syndication) feeds for playback on mobile devices and personal computers. If you have not purchased this addon and would like to use these features, contact your Sonic Foundry, Inc. sales representative. This appendix explains how to install and configure the Podcast Generator. You use the Configuration Editor to configure podcasting and then use the Management Portal to create and manage podcasts at a folder level. For instructions on creating new podcasts, preparing presentations that you want to add to podcasts, and making the podcasts available to your audience, see the Mediasite Podcasting User Guide available from the SmartServe Portal at The Podcast Generator is supported on 32-bit and 64-bit versions of Windows Server 2003 SP1 and Windows Server However, the Podcast Generator cannot be installed on a 64-bit machine where the MSCS software is installed. The installation will fail because the MSCS and Podcast software cannot co-exist. Create PodcastUser Before installing the Podcast Generator, you must use the Management Portal to create a user with administrator-level privileges, other than MediasiteAdmin, and give them podcast management privileges. This ensures that presentations in a podcast-enabled folder appear in the podcast without limits being placed on the MediasiteAdmin user s privileges. 1. Create a new user called PodcastUser in the Mediasite Directory and add a new role that maps to it. 2. Add PodcastUser to the MediasiteAdministrators group or any group with administrator-level permissions. The credentials of a user with administrator-level privileges are required to connect to Mediasite External Data Access Service (EDAS) when you register the EX Server with the Podcast Generator. 51

52 Installing and configuring the Podcast Generator 3. Assign the PodcastUser role read permissions to each folder that will be podcastenabled so the PodcastUser can control which presentations are available in a podcast. 4. Deny the PodcastRole permissions on any presentation in a podcast-enabled folder that will not be a part of the podcast. This must be done each time you add a new presentation to the podcast-enabled folder that will not added to the podcast. You will give the PodcastRole permissions to create podcasts and manage podcasts using System Manager. For more information, see Enabling Podcast management in the Portal on page 54 and Securing the Mediasite Server in the Mediasite Server Guide. Installing the Podcast Generator The Podcast Generator must be installed on a machine separate from the EX Server that meets the following requirements: Pentium 4 or better (Pentium D or Core processor recommended) 512MB RAM Microsoft Windows XP, Server 2003 SP1, or Server 2008 Microsoft Internet Information Services (IIS) 5.1, 6.0, or 7.0 Microsoft.NET 3.5 Windows Media Player 11 or Media Format 11 runtime 52 Before installing the Podcast Generator on Windows 2003 Server, SP1 or SP2, you must install the Microsoft hot fixes described in articles and , respectively. Both articles are available on the Microsoft website. When you install the Podcast Generator, a certificate is generated and stored in the local machine store for secure communication between the EX Server and the podcast web service. To install the Podcast Generator: 1. Double-click Podcast_Generator.exe and follow the prompts in the Mediasite Podcast Generator Installer to install the software. When you get to the Web Site Details page, specify the podcast web service settings: Web Site: Choose a web site for the web server from the drop-down list. Virtual Directory: The installer creates this virtual directory on the server. This virtual directory points to the podcast web service. The default value is PodcastService.

53 Installing and configuring the Podcast Generator Encryption Key: The value needed to encrypt and decrypt data sent back and forth between the Podcast Generator and the EX Server. 2. On the Ready to Configure page, click Configure. When the configuration is complete, click Finish to exit the Wizard. Registering the EX Server with the Podcast Generator Use the Configuration Editor to register an EX Server with the Podcast Generator. 1. Launch the Configuration Editor on the EX Server, go to Modules > Podcast Configuration and enter the connection settings: Podcast Service URL: The location of the podcast web service. The URL should include the FQDN or IP address of the server where the Podcast Generator is installed. The Podcast Web Service URL has the following format: Encryption Key: The value needed to encrypt and decrypt data sent back and forth between the Podcast Generator and the EX Server. 2. Click Test to verify the connection to the podcast web service. If the test fails verify that you have entered the correct values. If it passes, the following values are prefilled. Update these settings as needed: Certificate Serial #: The certificate the Podcast Service and EX Server will use to communicate securely. This value is read-only. Start Time: The time each day the Podcast Generator polls podcast-enabled folders on the EX Server for new presentations. The Podcast Generator will convert the new presentations to MP3 files and update the podcast and RSS feed. The default value is the time at which the software is installed. Podcast Update Interval (Hours/Minutes): The amount of time in hours and minutes after the initial start time that the Podcast Generator should wait before it polls podcast-enabled folders again. The default value is 12 hours and 0 minutes. External Data Access Login URL: The URL for EDAS on the EX Server. This value is read-only. 3. To connect to EDAS, enter the credentials of the PodcastUser created in Create PodcastUser on page 51 as the External Data Access Login credentials. Click Test to verify the connection using the specified credentials. 4. Click Podcast Publishing and Access and update the pre-filled settings as needed: 53

54 Installing and configuring the Podcast Generator Base Podcast URL: The URL that forms the base of the URLs users will use to subscribe to podcasts. The default value is the Mediasite data location, for example: FTP Server URL: The FTP location where the Podcast Generator uploads converted MP3 files. The default value is the EX Server s FTP data location, for example: ftp://<yourserver.yourcompany.net>/ Mediasite50Data/Presentations Publishing and Access Username/Password: The credentials of a user with full permissions to the location where the podcasts files are uploaded. The default credentials are those of the FTP user specified for the Mediasite data location. 5. Click Test Publishing to test the FTP server URL using the pre-filled or updated Podcast Publishing and Access settings. 6. Click Podcast Copyright and Filename and enter the default copyright information. 7. From the Podcast Filename drop-down list, choose how podcast files will be named: Presentation Title or Presentation ID. 8. Click Save. Enabling Podcast management in the Portal Use the System Manager to assign roles permission to view the Podcast tab as well as create and manage podcasts in the Portal. You must also assign these permissions to the role you created earlier, PodcastRole, which maps to the user, PodcastUser. By default, these permissions are unassigned so the Podcasting feature is unavailable to all users. To enable Podcast management in the Portal: 1. In the System Manager, click Portal Resource Permissions> Podcasting Management, assign roles read permissions, and click Apply. 2. Click Operation Permissions > Create Podcasts, assign roles execute permissions, and click Apply. 3. Click System Policies, select Podcast from the drop-down list, assign roles read and write permissions, and click Apply. These permissions will be the default permissions for every podcast created. However, these permissions can be updated. For more information on assigning permissions to resources and operations in the Portal as well as assigning system policies (default permissions), see the Mediasite Server Guide. Once you assign initial podcast-related permissions using the System Manager, these security features are available in the Management Portal. 54

55 Configuring the MSCS multicast settings Appendix B The Mediasite multicast add-on allows you to broadcast live Mediasite presentations using multicast if the Windows Media Server and network hardware supports multicast. When a presentation is broadcast live using IP-multicast distribution, only one stream is sent from the Windows Media Server to the network. Any number of viewers can join the multicast stream and the network routing and switching hardware will provide a copy of the video stream to the user without any additional load on the server. It may be necessary to update the multicast settings used by the MSCS. The default settings use an IP address range of and a port range of The Mediasite Module Services Manager is used to configure the multicast settings. To update the MSCS multicast settings: 1. On the Windows Media Server, go to C:\Program Files\Sonic Foundry\Module Services Manager\5_0\bin\ and double-click MediasiteModuleServicesManager.exe. 2. In the left pane, select Multicast Options. 3. Select the default address range and click Remove. Repeat for the default port ranges. 4. Enter the new multicast settings: Address ranges: Enter the start and end values for the multicast IP address range and click Add. The addresses should be within the following range: The MSCS will create broadcasting points in this address range when using multicast for a live presentation. The default address range is Port Ranges: Enter the start and end values for the port range and click Add. The MSCS will use these ports when using multicast for a live broadcast. The default port range is Time to Live (TTL): Enter the amount to time that the data will be transmitted before it is discarded. The default value is 64 seconds. 5. Click Save. A multicast license is required to use multicast with Mediasite. To purchase multicast licenses, contact your Sonic Foundry account representative or reseller. 55

56 Index A Active Directory, Microsoft, 38 ADAM SP1, install, 22 anonymous authentication, 39 audio correction tool, 42 B base DN, 39 C clocks, synchronize, 37 cluster Scheduler, install, 25 communication, secure, 16 components, Mediasite, 7 Configuration Editor add directory connection, 38 test server-level settings, 33 URL, 33 configure Mediasite directory, 22 multicast, 55 plug-ins, Mediasite, 35 Windows Media Server, 34 D data locations local, 20 prepare, 20 remote, 20 select type, 26 database prepare, 19 server requirements, 11 settings, 29 test connection, 33 Windows integrated security, 29 deploying EX Server, 19 deployment options, 11 destination folder, 25 directory connection settings, 29 external, 17 Mediasite, 17 Mediasite, use SSL, 50 secure socket layer, use, 38 test connection, 33 E server specify settings, 30 verify connection settings, 33 encryption key, update, 49 EX Server add site for, 37 deploy, 19 migrate to, register with Podcast Generator, 53 security, 16 test server-level setting, 33 update settings, 49 EX Server upgrade, 16 external directory, 17 add connection, 38 anonymous authentication, 39 base DN, 39 server path, 38 F FTP secure, 16 use directories, 26 virtual directory, create, 26 G getting started, 7 H high-availability installation, 12, 30 import settings, 34, 49 56

57 Index primary server, install, 31 Scheduler, install, 24 secondary server, install, 31 HTTP streaming, enable, 34 I import settings, 34 install type new installation, 26 installation additional considerations, 13 high-availability, 12, 30 information to know, 21 Media Server Control Service, 23 Microsoft ADAM SP1, 22 multiple EX Servers on a single server, 13, 32 options, 11 podcast, prepare for, Scheduler, 24 standard, 11, 25 System Manager, 36 integrated security, Windows, 29 L Lightweight Directory Access Protocol, 38 local data location, 26 M Mac playback, enable, 34 media upgrade tool, migration, 45 Mediasite components, 7 directory, 17 directory, configure, 22 directory, use SSL, 50 plug-ins, 17 plug-ins, configure, 35 Root URL, 17, 27 Scheduler, 24 security, 16 Microsoft Active Directory, 38 ADAM SP1, 22 migrate, migration, 15 audio correction tool, 42 Editor, upgrade, 47 Mac playback, 42 media upgrade tool, 45 Recorder, upgrade, 46 rename virtual directory, 46 uninstalling 4.x software, 45 using the wizard, 43 minimum hardware requirements, 8 modules install, 51 test settings, 34 MSCS register Mediasite Server, 34 multicast configure in MSCS, 55 multiple EX Servers on a single server, 13 P password MediasiteAdmin, 23, 30 system user, 23, 30 plug-ins, Mediasite, 17, 35 podcast create PodcastUser, 51 enable in portal, 54 install, 52 install and configure, register EX Server, 53 prepare data locations, 20 database, 19 Windows Media Server, 21 primary server EX Server, install, 31 import settings, 34 Mediasite Root URL, 34 publishing points collect data, 35 on-demand, 28 secure, 17 secure, 35 push distribution, enable, 34 57

58 Index R remote data location credentials, network user, 26 network share, 26 requirements database server, 11 hardware, 8 System Manager, 10 Root URL update, 49 Root URL, Mediasite, 17, 27 S Scheduler cluster, install, 25 high-availability installation, 24 install, 24 multiple EX Servers, install, 24 service ID, 25 service install type, additional, 25 service install type, new, 25 secondary server EX Server, install, 31 secure FTP client, 16 virtual directories, create, 26 security EX Server, 16 publishing points, 17 secure communication, 16 settings data location type, 26 data locations, 26 database, 29 directory connections, 29 server, 30 FTP Server, 27 import, 34 import settings, update, 49 media server distribution, 24, 28 media server upload, 29 Mediasite Root URL, update, 49 modules, test, 34 primary EX Server, 32 test server-level, 33 web server, 27 standard installation, 11, 25 streaming, HTTP, 34 synchronize clocks, 37 System Manager add site, 37 install, 36 system user set password, 23 test credentials, 33 T test database connection, 33 directory connection, 33 system user credentials, 33 tool, audio correction, 42 U uninstall 4,x software, 45 upgrade from 5.0, 16 upgrading Editor, 47 Recorders, 46 URL FTP Server, 27, 28 HTTP server, 27 V virtual directory Mediasite data, 27 rename, 46 slide images, 27 web server, 27 W web server setting, 27 Windows Media Server configure, 34 distribution settings, 24, 28 enable Mac playback, 34 enable push distribution, 34 FTP settings, 29 prepare, 21 58

59 Index publishing point, 28 register server with MSCS, 34 security, 17 upload settings, 29 wizard, migration, 43 59