Mediasite EX server deployment guide

Mediasite EX server deployment guide

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 53703 877-783-7987 toll free from the US and Canada 608-443-1600 Sonic Foundry. Since 1991. For more information or to provide feedback on Mediasite documentation, please contact mediasite@sonicfoundry.com. Version: 5.0.1, November 2008 2

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... 10 Database server requirements... 11 EX Server deployment options... 11 Standard installation...11 High-availability installation... 12 Multiple EX Server installations on a single server... 13 Additional installation and configuration considerations... 13 Migration from 4.x to 5.0.1...15 EX Server 5.0 upgrade... 16 Mediasite security... 16 Secure communication... 16 Security for resources on the EX Server... 16 Security for content on the Windows Media Server... 17 Deploying Mediasite Server... 19 Preparing the Mediasite database... 19 Preparing the EX Server s data locations... 20 Preparing the Windows Media Server... 21 3

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

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

Getting started This book describes how to install and configure Mediasite EX Server 5.0.1 as well as how to migrate to EX Server 5.0.1 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 5.0.1. You can download the online version of this guide, which may contain more current information, from the SmartServe Portal at www.sonicfoundry.com/support. 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

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

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

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 2008. 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 www.sonicfoundry.com/support. 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

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 www.sonicfoundry.com/support. 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

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.

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

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 10455 available on the SmartServe Portal at www.sonicfoundry.com/support. 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 https:// instead of http://. For example: https://mymediasiteserver.mycompany.net/mediasite/loginform/login.aspx 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

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 www.sonicfoundry.com/support. Migration from 4.x to 5.0.1 The sequence for installing and configuring 5.0.1 software when migrating from EX or LX Server 4.x to EX Server 5.0.1 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 5.0.1 can co-exist on the same hardware so that you can run Mediasite 4.x in production while testing Mediasite 5.0.1. 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 5.0.1 Mediasite installation. Additional storage space. You will need twice the amount of storage space if you will run both Mediasite 4.x and Mediasite 5.0.1 after migrating the data from the 4.x system. Bringing the Mediasite 5.0.1 into production. You will bring down the Mediasite 4.x site and rename Mediasite 5.0.1 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 5.0.1. For more information and migration instructions, see Migrating to Mediasite Server "on page 41. We strongly recommend that you plan your EX Server 5.0.1 installation and migration. See Mediasite for the Enterprise available on the SmartServe Portal at www.sonicfoundry.com/support. 15

Getting started EX Server 5.0 upgrade The EX Server 5.0.1 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 www.sonicfoundry.com/support. 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 20. 16 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

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

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

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 19-21. 2. Install Microsoft ADAM SP1, see page 22. 3. Configure the Mediasite Directory, see page 22. 4. Install the Media Server Control Service, see page 23. 5. Install the Scheduler on machines where the EX Server software will be installed (optional), see page 24. 6. Install EX Server software on one or more servers, see pages 25-32. 7. Test the EX Server settings, see page 33. 8. Configure the Windows Media Server (optional), see page 34. 9. Install and configure the System Manager, see page 36. 10. Synchronize the clocks on the servers and your Recorders, see page 37. 11. Connect the EX Server to an external directory (optional), see page 38. 2 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 5.0.1. 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

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 www.mysql.com. 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

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

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. E-mail server information: the FQDN or IP address of an e-mail server and the e-mail address that will be used by the EX Server and the Scheduler to send e-mail about presentations, and the e-mail 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 2008. 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 http://www.microsoft.com/downloads 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

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 636. 3. 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: 1025-65535), 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 10557 available on the SmartServe Portal at www.sonicfoundry.com/support. 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

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 8092. For example: http://mymediaserver:8092/ 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

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

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

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

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

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