Polycom RealPresence Media Manager Software Edition

Transcription

1 INSTALLATION GUIDE Software August Rev A Polycom RealPresence Media Manager Software Edition Polycom, Inc. 1

2 Copyright 2013, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc America Center Drive San Jose, CA USA Trademarks Polycom, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc. and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or transmitted in any form or by any means, for any purpose other than the recipient's personal use, without the express written permission of Polycom. End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this product. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. Open Source Software Used in this Product This product may contain open source software. You may receive the open source software from Polycom up to three (3) years after the distribution date of the applicable product or software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive software information, as well as the open source software code used in this product, contact Polycom by at OpenSourceVideo@polycom.com. Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document, Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document. Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose. Information is provided as is without warranty of any kind and is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss of business information), even if Polycom has been advised of the possibility of such damages. Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. your opinions and comments to DocumentationFeedback@polycom.com. Visit the Polycom Support Center for End User License Agreements, software downloads, product documents, product licenses, troubleshooting tips, service requests, and more. Polycom, Inc. 2

3 Contents About This Guide... 6 Conventions Used in this Guide... 6 Information Elements... 6 Typographic Conventions... 7 Part I: Installation Prerequisites : RealPresence Media Manager Software and Server Prerequisites... 9 Getting Started... 9 Required Software... 9 RealPresence Media Manager 6.5 Software Edition Hardware Requirements Virtual Machines Preparing Your Environment for Your RealPresence Media Manager Installation Part II: Setting Up Web, SQL, and Media Servers : Configuring Microsoft Windows Server 2012 for Polycom RealPresence Media Manger Software Installation Installing Server Roles in Windows Server Installing IIS Media Services Disabling the Default IIS Website : Configuring Microsoft SQL Server 2012 for RealPresence Media Manager Software Installation SQL Server 2012 Requirements Preparing to Set Up SQL Server Setting Up SQL Server : Setting Up Microsoft Windows Media Services (WMS) and Internet Information Services (IIS) Requirements for Windows Media Services and IIS Smooth Streaming Using External and Third-party Streaming Servers Windows Media Services (WMS) Enabling Roles in Windows Media Services Configuring the Windows Media Server s HTTP Streaming Port Creating Publishing Points in Windows Media Services Setting Authorization Rights for Publishing Points Internet Information Services (IIS) Media Services (Smooth Streaming) Polycom, Inc. 3

4 5: Setting Up Microsoft Expression Encoder 4 Pro Expression Encoder 4 Pro Requirements Enabling the Desktop Experience Feature Installing Expression Encoder 4 Pro Part III: Installing Polycom RealPresence Media Manager Software : Installing RealPresence Media Manager Software Running the RealPresence Media Manager Installer Setting the IP Address, Port, Host Header, and Credentials : Installing and Launching the RealPresence Media Manager Admin Tool Installing and Launching the Admin Tool Activating the Product License Key Activating a Product License Key on a New Installation of RealPresence Media Manager Software Activating a Product License Key on a RealPresence Media Manager Appliance Setting Initial Admin Tool Media Manager Preferences Encrypting Database Strings : Installing in RealPresence Media Manager Software Installing the Outgoing Service Stopping the Service on the Application Server Purging Old Database Records Configuring in RealPresence Media Manager Configuring SMTP Restarting the Service on the Application Server Testing Your Installation : Configuring Reports Configuring SQL Server Reporting Services and Reports Connecting SSRS in SQL Server 2012 or SQL Server 2008 R2 to RealPresence Media Manager Software Selecting an Account and Creating a Report Server Creating a Report Server Database Configuring Anonymous SSRS Access Installing Media Manager Reports using the Reports Uploader : Upgrading a Previous Version of RealPresence Media Manager Software to Version Preparing Your Environment for Upgrading to Version Upgrading to RealPresence Media Manager 6.5 Software Polycom, Inc. 4

5 11: Getting Help The Polycom Community : Troubleshooting : References Moving the SQL Database Performing a Factory Restore on the RealPresence Media Manager Appliance Edition A: Appendix Acceptance Criteria Polycom, Inc. 5

6 About This Guide This installation guide uses a number of conventions that help you to understand information and perform tasks. Conventions Used in this Guide This installation guide contains terms, graphical elements, and a few typographic conventions. Familiarizing yourself with these terms, elements, and conventions will help you successfully perform tasks. Information Elements This guide may include any of the following icons to alert you to important information. Icons Used in this Guide Name Icon Description Note The Note icon highlights information of interest or important information needed to be successful in accomplishing a procedure or to understand a concept. Administrator Tip The Administrator Tip icon highlights techniques, shortcuts, or productivity related tips. Caution Warning Web Info The Caution icon highlights information you need to know to avoid a hazard that could potentially impact device performance, application functionality, or successful feature configuration. The Warning icon highlights an action you must perform (or avoid) to prevent issues that may cause you to lose information or your configuration setup, and/or affect phone or network performance. The Web Info icon highlights supplementary information available online such as documents or downloads on support.polycom.com or other locations. Timesaver The Timesaver icon highlights a faster or alternative method for accomplishing a method or operation. Power Tip The Power Tip icon highlights faster, alternative procedures for advanced administrators already familiar with the techniques being discussed. Troubleshooting The Troubleshooting icon highlights information that may help you solve a relevant problem or to refer you to other relevant troubleshooting resources. Polycom, Inc. 6

7 Name Icon Description Settings The Settings icon highlights settings you may need to choose for a specific behavior, to enable a specific feature, or to access customization options. Typographic Conventions A few typographic conventions, listed next, are used in this guide to distinguish types of in-text information. Typographic Conventions Convention Bold Italics Blue Text Courier Description Highlights interface items such as menus, soft keys, file names, and directories. Also used to represent menu selections and text entry to the phone. Used to emphasize text, to show example values or inputs, and to show titles of reference documents available from the Polycom Support Web site and other reference sites. Used for cross references to other sections within this document and for hyperlinks to external sites and documents. Used for code fragments and parameter names. Polycom, Inc. 7

8 Part I: Installation Prerequisites Part 1 describes the hardware and software requirements, and prerequisite conditions you need to install Polycom RealPresence Media Manager 6.5 software. This part also provides you with the necessary background information for preparing your server environment for your RealPresence Media Manager software implementation, including lists of prerequisites for installing RealPresence Media Manager with the following Microsoft servers and applications: Windows Server 2012 and Windows Server 2008 R2 Windows SQL Server 2012 and 2008 R2 Windows Media Services Internet Information Services 7.5 (IIS) for Windows Server 2008 R2 installations Internet Information Services 8 (IIS) for Windows Server 2012 installations Polycom, Inc. 8

9 1: RealPresence Media Manager Software and Server Prerequisites This chapter shows you the prerequisites you need to install RealPresence Media Manager software. Getting Started You need to have the following before starting your RealPresence Media Manager installation: IP addresses of all servers, including: Host name or IP address of your SQL Server 2012 or SQL Server 2008 R2 Your SQL Server instance name, if applicable. For example, default instances might be MyServerName or an IP address such as Examples of named instances might be MSSQLINSTANCENAME, MyServerName\MSSQLINSTANCENAME, or \MSSQLINSTANCENAME Admin user names and passwords for all servers, including application servers, media servers, and database servers: SQL Server login with rights to add or edit databases, create logins, and create jobs Your chosen username and password for the default administrator account in RealPresence Media Manager software Your chosen usernames for the primary and reporting databases IP address, port, and host header for the RealPresence Media Manager portal Usernames, if not the default usernames, and passwords for the following SQL database users, that you create during installation: Portal Admin service Reports Outgoing service Firewall rules that you may have created in advance LDAP information if you are using LDAP authentication Required Software You need the following software to complete the installation described in this guide: Polycom RealPresence Media Manager Software Edition, or Hosted Edition, version 6.5 Microsoft Windows Server 2012 (Windows Server 2008 R2 Standard Edition and Enterprise Edition are supported) Microsoft SQL Server 2012 or SQL Server 2008 R2 Polycom, Inc. 9

10 Microsoft Internet Information Services 7.5 for Windows Server 2008 R2 or Microsoft Internet Information Services 8 for Windows Server 2012 Windows Media Services Microsoft.NET Framework v4.5 Microsoft Expression Encoder 4 Pro SP2 Note: 32-bit Operating Systems RealPresence Media Manager 6.5 software does not support 32-bit operating systems. RealPresence Media Manager 6.5 Software Edition Hardware Requirements The RealPresence Media Manager software application must meet the following minimum hardware requirements for successful installation of RealPresence Media Manager Software Edition and associated services: Table 1: RealPresence Media Manager - Software Edition Hardware Requirements Minimum Hardware Processor Memory Local Storage Network Recommended Hardware Processor Memory Local Storage Shared Storage Specification Intel Xeon 4-core or comparable 4GB 40GB RAID 1 Partition (OS) 40GB RAID 1 Partition (Apps) 1GB Specification Intel Xeon 8-core or comparable 8GB 40GB RAID 5 Partition (OS) 20GB RAID 5 Partition (Apps) 40GB iscsi/fc SAN (OS) 20GB iscsi/fc SAN (Apps) Polycom, Inc. 10

11 Note: Storage Area Network Protocols Servers can be deployed over Internet Small Computer System Interface (iscsi) or Fibre Channel (FC) Storage Area Networks (SAN). For RealPresence Media Manger Software Edition deployments, the database and storage servers must meet the following minimum hardware requirements: Table 2: Database and Storage Server Hardware Requirements Minimum Hardware Database/Reporting Services Storage/Repository Processor Intel Xeon 4-core or comparable Intel Xeon 2-core or comparable Memory 4GB 4GB Local Storage 40GB RAID 5 Partition (OS) 50GB RAID 5 Partition (Apps, Data) 40GB RAID 10 Partition (OS) 1TB RAID 5 Partition (Apps, Data) Network 1GB 1GB Recommended Hardware Database/Reporting Services Storage/Repository Processor Intel Xeon 8-core or comparable Intel Xeon 6-core or comparable Memory 8GB 8GB Local Storage Shared Storage 40GB RAID 10 Partition (OS) 500GB RAID 10 Partition (Apps, Data) 40GB iscsi /FC SAN (OS) 100GB iscsi /FC SAN (Apps) 40GB RAID 10 Partition (OS) 2TB RAID 10 Partition (Apps, Data) Dedicated iscsi or FC SAN shared repository for WMS/Smooth Streaming/Wowza/Web Content For RealPresence Media Manger Software Edition deployments, the server roles must meet the following minimum hardware requirements: Table 3: Server Role Hardware Requirements Minimum Hardware Windows Media Services Smooth Streaming Processor Intel Xeon 2-core or comparable Intel Xeon 4-core or comparable Memory 4GB 4GB Local Storage 40GB RAID 1 Partition (OS) 250GB RAID 1 Partition (Data) 40GB RAID 1 Partition (OS) 250GB RAID 1 Partition (Data) Polycom, Inc. 11

12 Minimum Hardware Windows Media Services Smooth Streaming Network 1GB 1GB Recommended Hardware Windows Media Services Smooth Streaming Processor Intel Xeon 4-core or comparable Intel Xeon 4-core or comparable Memory 8GB 8GB Local Storage Shared Storage 40GB RAID 5 Partition (OS) 1TB RAID 5 Partition (Data) 40GB iscsi /FC SAN (OS) 2TB shared repository (Data) 40GB RAID 5 Partition (OS) 1TB RAID 5 Partition (Data) 40GB iscsi /FC SAN (OS) 2TB shared repository (Data) Table 4: Database and Storage Server Hardware Requirements Minimum Hardware Web Content Polycom Media Services Agent (MSA) for Thumbnailing and Transcoding Processor Intel Xeon 2-core or comparable Intel Xeon 4-core or comparable Memory 4GB 8GB Local Storage 40GB RAID 1 Partition (OS) 250GB RAID 1 Partition (Data) 40GB RAID 1 Partition (OS) 40GB RAID 1 Partition (Apps, Data) Network 1GB 1GB Recommended Hardware Web Content Polycom Media Services Agent (MSA) for Thumbnailing and Transcoding Processor Intel Xeon 4-core or comparable Intel Xeon 8-core or comparable Memory 8GB 16GB Local Storage Shared Storage 40GB RAID 5 Partition (OS) 1TB RAID 5 Partition (Data) 40GB iscsi /FC SAN (OS) 2TB shared repository (Data) 40GB RAID 5 Partition (OS) 250GB RAID 5 Partition (Apps, Data) 40GB iscsi /FC SAN (OS) 2TB shared repository (Data) Polycom, Inc. 12

13 Virtual Machines RealPresence Media Manager can be installed on virtual machines (VM) to simplify maintenance, disaster recovery, and expansion. Virtual machine environments can over-share resources across VM instances, affecting the responsiveness of CPU-, RAM- and disk-intensive applications like RealPresence Media Manager. The following Virtualization platforms are compatible, but because performance is influenced by actual deployment configurations, each environment must be reviewed and certified by Professional Services after installation. You need an existing support contract with a virtualization provider and or the ability to resolve issues that are unique to virtualized environments. Polycom recommends using management systems to govern and report against virtual hosts. Open Source virtualization platforms and non-affiliated internet-based third-party cloud providers are not supported without validation and written authorization from Polycom Global Support Services. Table 5: Supported Virtualizations VMware Supported Versions Management Product Reference Performance Best Practices Memory Management Network I/O Latency Reference vsphere v4.x and 5.x Standard or above vcenter Microsoft Supported Versions Management Product Reference Hyper V 2008R2 SP1 Microsoft System Center 2012 VMM Citrix Supported Versions Xen Server v5.5, v5.6, and v6.0 Management Product Reference XenCenter ID= Polycom, Inc. 13

14 Preparing Your Environment for Your RealPresence Media Manager Installation Caution: Install RealPresence Media Manager software only after all Microsoft Servers are Installed If RealPresence Media Manager software will be installed on a single server along with the Application server and/or Media Servers, it is absolutely necessary that all Microsoft server roles are fully installed and functional before installing the Polycom RealPresence Media Manager software. This is the order detailed in this guide. Before installing RealPresence Media Manager software, ensure the following prerequisite conditions are met: All servers and virtual machines must be running Windows Server 2012 or 2008 R2 All servers and virtual machines are running on the same version number of operating system and same level of service pack or hot fix Microsoft SQL Server and IIS are installed and fully functional Microsoft Expression Encoder 4 Pro installed on any transcoding or thumbnailing servers IIS 7.5 (for Windows Server 2008 R2) or IIS 8 (for Windows Server 2012) installed on the application server Windows Server 2012 are installed on the application server before installing RealPresence Media Manager software The Microsoft SQL Server database server and the Media Manager Portal Server are in constant communication and must be on the same LAN, or LAN-Latency equivalent WAN. This guide describes installation of RealPresence Media Manager software and SQL Server 2012 on the same server. Media servers, such as Windows Media Services for Server 2008 R2 installations, are installed and prepared. You can configure media servers after installing Media Manager, but you can more easily verify that the media servers are operational if they are installed at the same time as Media Manager. The Polycom RealPresence Media Manager server must have Internet connectivity to activate the license. If you do not have an Internet connection, or HTTPS access is blocked, you can follow the manual license key activation procedure. This process can take several hours as the key is generated by a support technician. Note: Server Requirements Server requirements may vary depending on planned workload and deployment. The recommendations and procedures described in this guide are general. You may need to customize the configurations to suit the needs of your individual installation. Polycom, Inc. 14

15 Part II: Setting Up Web, SQL, and Media Servers Part II guides you through installing and preparing your server environment for your RealPresence Media Manager software installation. Polycom, Inc. 15

16 2: Configuring Microsoft Windows Server 2012 for Polycom RealPresence Media Manger Software Installation This chapter shows you how to set up Windows Server 2012 for your RealPresence Media Manager installation. To complete this configuration, first install the following software on the machine you plan to install RealPresence Media Manager software on: Microsoft Windows Server 2012 Microsoft IIS Media Services 4.1 Microsoft Expression Encoder 4 Pro Polycom recommends installing the operating system and application files to the C:/ drive and saving any data to the D:/ drive. Install any hotfixes after installing the operating system. Caution: Install RealPresence Media Manager software only after all Microsoft servers are installed If RealPresence Media Manager will be installed on a single server along with the Application server and/or Media Servers, it is absolutely necessary that all Microsoft server roles are fully installed and functional before installing the Polycom RealPresence Media Manager software. This is the order detailed in this guide. Installing Server Roles in Windows Server 2012 First, you need to add server roles for the IIS web server and features such as.net framework in Windows Server The following procedure describes adding roles in a role-based installation using the Add Roles and Features Wizard. To add server roles in Windows Server 2012: 1 In Windows Server 2012, open Server Manager. Polycom, Inc. 16

17 2 In the Server Manager Dashboard, click Add roles and features to open the Add Roles and Features Wizard. 3 In the Add Roles and Features Wizard, on the Before you begin page, verify that your destination server is correct and that you have met the listed prerequisites. Click the Next button. Polycom, Inc. 17

18 4 Select Role-based or feature-based installation. Click the Next button. 5 On the Select destination server page, select a destination server from the server pool. Click the Next button. The destination server displays in the top right corner on all Add Roles and Features Wizard pages. 6 On the Server Roles page, select Web Server (IIS). Polycom, Inc. 18

19 A new dialog box will open, prompting you to add required features. Select the Include management tools checkbox and click the Add Features button. 7 On the Features page, select the.net Framework 3.5 Features,.NET Framework 4.5 Features, and ASP.NET 4.5 checkboxes. Select other features that apply to your installation. Click the Next button. Polycom, Inc. 19

20 8 On the Web Server Role (IIS) page, read the note and click the Next button. On the Role Services page, select the Role services from the following list. Click the Next button when finished. Web Server Common HTTP Features Default Document Directory Browsing HTTP Errors Static Content HTTP Redirection Health and Diagnostics HTTP Logging Performance Static Content Compression Security Request Filtering Basic Authentication Windows Authentication Management Tools IIS Management Console Polycom, Inc. 20

21 9 On the Confirmation page, review your configuration settings. Click Export configuration settings to save your settings in an XML file. Click the Install button to install the server roles and features. 10 On the Results page, you can monitor the installation progress. You can close the Add Roles and Features Wizard without affecting the installation in progress by clicking the Close button. Admin Tip: Finishing the Roles Installation You will need to restart the destination server in the Windows Server Manager Dashboard to finish the installation. Installing IIS Media Services 4.1 You may need to install Microsoft IIS Media Services 4.1 before installing RealPresence Media Manager software. IIS Media Services includes the Smooth Streaming extension, which enables adaptive streaming of media to Microsoft Silverlight and other clients over HTTP. To install IIS Media Services: 1 Download IIS Media Services 4.1 here. 2 Browse to the downloaded file, Media Services.exe. Right-click the file and select Run as administrator. Polycom, Inc. 21

22 3 In the Web Platform Installer 4.5 window, click the Install button. 4 Accept the license terms by clicking the I Accept button. Polycom, Inc. 22

23 5 After IIS Media Services 4.1 has successfully installed, click the Finish button. 6 Unless you want to add additional products, you can close the Web Platform Installer 4.5 window by clicking the Exit button. Disabling the Default IIS Website Disable the default IIS website before installing RealPresence Media Manager software. If you attempt to install RealPresence Media Manager software without disabling the default website, the installation will fail. To disable the default IIS website: 1 Open IIS Manager. In Server Manager, right-click the IIS server and select Internet Information Services Manager (IIS). \ 2 In the Connections panel, select Default Web Site. Polycom, Inc. 23

24 3 In the Manage Website panel, click Stop. Polycom, Inc. 24

25 3: Configuring Microsoft SQL Server 2012 for RealPresence Media Manager Software Installation A compatible Microsoft SQL Server is required for the Polycom RealPresence Media Manager software s database server. This chapter guides you through setting up Microsoft SQL Server 2012 in Windows Server 2012 for your RealPresence Media Manager software installation. SQL Server 2012 Requirements You need to meet the following requirements to configure SQL Server 2012 for RealPresence Media Manager software installation: Windows Server 2008 R2 or Windows Server 2012 SQL Server 2008 R2, SQL Server 2012, or SQL Server 2012 Express is required for the Polycom RealPresence Media Manager software s database server. While Microsoft SQL Server Express is supported for small deployments such as labs or small departments, Polycom recommends production environments be deployed using Microsoft SQL Server Standard or better. SQL Server login credentials with rights to add or edit databases, create logins, and create jobs Mixed Mode authentication must be enabled on the SQL Server Full Text Search must be enabled on the SQL Server Preparing to Set Up SQL Server 2012 Before you begin setting up SQL Server 2012 for your RealPresence Media Manager software installation, you need to test setup support rules and resolve any failures. To prepare Microsoft SQL Server: 1 Open SQL Server Manager. 2 Click Installation to open the SQL Server Installation Center. Polycom, Inc. 25

26 3 Select New SQL Server stand-alone installation or add features to an existing installation to launch the setup wizard. 4 On the Setup Support Rules page, click the Run button to scan your system for possible error sources. The page will display the rules and statuses as either Passed or Warning. All failures must be corrected before you proceed with setting up SQL Server. Click the Re-run button to re-run the test. Once the rules have all passed, click the Next button and proceed with setup. Polycom, Inc. 26

27 Setting Up SQL Server 2012 To set up SQL Server 2012: 1 In the SQL Server 2012 Setup dialog box, on the Feature Selection page, select the Instance Features and Shared Features you wish to install. Feature descriptions and prerequisites are displayed on the right side of the Feature Selection page. Check the Shared feature directory path and change it if necessary. Click the Next button. 2 On the Instance Configuration page, select Default instance or enter a Named instance, Instance ID, and select the Instance root directory for the instance of SQL Server 2012 you are setting up. You need to select Named instance if you have more than one instance of SQL Server installed on the same machine. Polycom, Inc. 27

28 Click the Next button. 3 On the Server Configuration page, on the Service Accounts tab, set the Startup Type for each service that will run in this instance of SQL Server The options are: Automatic Manual Disabled Click the Next button. 4 On the Database Engine Configuration page, on the Server Configuration tab, select Mixed Mode. Polycom, Inc. 28

29 Admin Tip: Windows Authentication Mode or Mixed Mode If you select Windows Authentication mode, local users added in the SQL Server 2012 Setup wizard will not be able to log in using the password you enter on the Database Engine Configuration page. Select Mixed Mode to allow local users you add on this page to log in to the server, or access SQL Server 2012 services. Enter the SQL Server 2012 system administrator password. You can add and remove users by clicking the Add Current User, Add, and Remove buttons. Click the Next button. Polycom, Inc. 29

30 5 On the Reporting Services Configuration page, select Install only. Click the Next button. Click through the Error Reporting and Installation Configuration pages, and then click the Install button. 6 You can configure Reporting Services in a later step. For more information about configuring Reporting Services, see Configuring SQL Server Reporting Services and Reports. Note: Compatibility Level When configuring Microsoft SQL Server 2012, you must set the compatibility level to 90. For more information about how to set the compatibility level in SQL Server 2012, and compatibility level best practices, visit the SQL Server Compatibility Level page in Microsoft s TechNet Library. Polycom, Inc. 30

31 4: Setting Up Microsoft Windows Media Services (WMS) and Internet Information Services (IIS) Depending on your deployment, you may need to install and configure Windows Media Services and IIS Smooth Streaming; however, they are not compatible with all media servers. Windows Media Services is not supported in Windows Server To support mobile devices with a RealPresence Capture Station Pro, RealPresence Capture Station Portable Pro, or Polycom RSS 4000 appliance and RealPresence Media Manager 6.5 software, you need at least one Microsoft IIS Smooth Streaming Server. This chapter provides a quick outline for configuring Windows Media Services and IIS Smooth Streaming on a single application server in a small production or lab environment. In many larger deployments, the media servers are individual servers. For more information about Windows Media Services and IIS Smooth Streaming, visit Microsoft s support website. Requirements for Windows Media Services and IIS Smooth Streaming You need to meet the following minimum requirements to use Windows Media Services and IIS Smooth Streaming: Windows Server 2008 R2 or Windows Server 2012 (IIS Smooth Streaming only) Windows Media Services is required to support Windows Media Streaming. Windows Server 2008R2 or Windows Server 2012 is required to support Microsoft IIS Smooth Streaming. If you will be using this Windows server with a Media Services Agent (MSA), ensure that Microsoft.NET Framework 4.5 (.NET 4 and 3.5 are supported) is installed. Note: Windows Media Services is not supported in Windows Server 2012 Polycom, Inc. 31

32 Using External and Third-party Streaming Servers RealPresence Media Manager 6.5 software supports the following external streaming servers for live streaming and on-demand: Windows Media Services 9 IIS Media Services Wowza Media Server 3.5 Configuration of third-party servers is not covered in this guide and is the customer s responsibility. Windows Media Services (WMS) WMS is not supported in Windows Server 2012 To support the Windows Media format, you will need a Windows 2008 R2 server configured for Windows Media (Enterprise is required for multicast). This server should have the Polycom version 6.5 Media Services Agent installed to enable automation using the RealPresence Media Manager Admin Tool In Windows Server 2008 R2, WMS is installed using a separate role installer which must be downloaded from Microsoft at the following URL: Enabling Roles in Windows Media Services Once you download and install the Windows Media Role package, you must enable the role. To add and enable roles: 1 In the Windows Server Manager dialog box, click Add Roles. 2 In the Add Roles wizard, click Server Roles. Polycom, Inc. 32

33 3 Select Streaming Media Services and click the Next button. 4 On the Select Data Transfer Protocols page, select the Real Time Streaming Protocol (RTSP) checkbox. 5 Click the Install button. Polycom, Inc. 33

34 Configuring the Windows Media Server s HTTP Streaming Port If Internet Information Services (IIS) is using port 80, then you must configure Windows Media Services for a different port, such as port 81. You need to configure the HTTP streaming port setting in the RealPresence Media Manager software s Admin Tool to match the port you configure for in Windows Media Services. Caution: Configuring Ports for IIS and Windows Media Services If the Windows Media Service is to be installed on the same server as the Web Content or Media Manager Portal Server, you must configure an alternative port for Windows Media streaming over HTTP since IIS will bind to port 80 by default. In this case, Polycom recommends using port 81 for HTTP streaming in Windows Media Services. The RealPresence Media Manager default servers are configured to use port 81 for http streaming during installation. To configure the Windows Media Server s HTTP streaming port: 1 In the Windows Media Services management tool, select your server. 2 Click the properties tab. 3 Select the desired control protocol category. 4 Right-click WMS HTTP Server Control Protocol and select Properties. 5 Select Use other port ( ), and enter 81 in the field. Polycom, Inc. 34

35 6 Click OK. 7 Right-click WMS HTTP Server Control Protocol again, and select the Enable checkbox. Creating Publishing Points in Windows Media Services You need to create Publishing Points on the Windows Media Server for one or both types of content you will publish using Media Manager. You can create either On-demand publishing points for content that users will view on demand, or Broadcast publishing points for content that will be published as a live stream. To create Publishing Points in Windows Media Services: 1 Open the Windows Media Admin snap-in, right-click Publishing Points, and select Add Publishing Point (Advanced). 2 Select the type of publishing point, either On-demand or Broadcast. 3 Do one of the following: If you select On-Demand, browse to and select the directory where your video files will be stored. This directory might be configured as mapped, shared drive, or configured as an FTP directory. Admin Tip: Setting Read Permissions If you link an on-demand publish point to a directory, the directory must have read permissions set for the WMUS_ServerName user. If you select Broadcast (live), choose Push or Pull. Push means that the encoder starts the connection. Pull means that the server starts the connection. If your encoder is behind a firewall and your server is outside the firewall, you need to choose Push for the encoder to initiate the connection. Admin Tip: Recovering from a Loss of Connectivity Pull publish points can recover from a loss of network connectivity between the encoder and server, while Push publish points require a manual encoder restart. This makes Pull a better choice when available. 4 In the Add Publishing Point dialog box, enter a Publishing point name. 5 In the Location of Content field, enter a push or pull location: For a Push publishing point, enter the content location as Push:* Polycom, Inc. 35

36 For a Pull publishing point, enter the content location as DNS_or_IP_address_of_encoder:encoder_port Setting Authorization Rights for Publishing Points You may wish to set up authorization rights for your publishing points in the Windows Media Services management tool in the following scenarios: You are using a standalone WMS server and want to support live streaming from a Polycom RSS This WMS server has a Media Services Agent (MSA) installed on it to support automated, wide distribution of content using the RealPresence Media Manager software. The MSA requires permissions for publishing points. You are publishing to the WMS server using a RealPresence Capture Station Pro appliance, and wish to use the hypothetical user account PRCS105 to publish from the encoder settings on the RealPresence Capture Station Pro appliance. User PRCS105 requires write permissions for publishing points on the WMS server. To set up authorization rights for your publishing points in the Windows Media Services management tool: 1 Select your server, and click the Properties tab. 2 Select the authorization category. Polycom, Inc. 36

37 3 Right-click WMS NTFS ACL Authorization and clear the Disable checkbox. 4 Right-click WMS Publish Points ACL Authorization and click Properties. 5 Select the permissions level you wish to assign to users. 6 There are three levels: Read enables you to view content being served from a publishing point. Assign this permission to the everyone user group. Write enables you to publish content to an existing publish point. Assign this permission to the user account or accounts you wish to have applications, such as RealPresence Capture Station Encoder or RealPresence Media ManagerScheduler Service, use to write content to the publishing points. Create enables you to create publishing points. Assign this permission to the user accounts you wish to have applications, such as RealPresence Media ManagerScheduler Service, or URL Import service for RSS-4000 streaming, or Media Services Agent for MSA distribution, use to create publishing points. Admin Tip: Setting Read Permissions If you link an on-demand publish point to a directory, the directory must have read permissions set for the WMUS_ServerName user. Internet Information Services (IIS) Media Services (Smooth Streaming) To deliver live and on-demand streaming video through RealPresence Media Manager software, you need to install the Media Services (Smooth Streaming) role in Microsoft IIS. Before installing or configuring IIS Media Services, you need to install and configure IIS 7 for Windows Server 2008R2 or IIS 8 for Windows Server For more information about IIS, visit the Official Microsoft IIS Site. To Enable IIS Media to deliver on-demand Smooth Streams from a RealPresence Capture Station Pro appliance or other device: 1 Create one or more virtual directories from which to serve the IIS Smooth stream. 2 Give this directory read, read and execute, and list folder contents permissions for the IIS_IUSRS group. For streaming from a RealPresence Capture Station appliance, you need to configure the RealPresence Capture Station software with the correct permissions for transferring files. You can also share the folder or folders using Windows or set up the folders as FTP destinations to enable RealPresence Capture Station appliances to upload Smooth Streaming on-demand files. Polycom, Inc. 37

38 To enable IIS Media to deliver live Smooth Streams from RealPresence Capture Station appliances or other device: 1 Set up a Smooth Streaming publish point for each RealPresence Capture Station appliance with the ios/smooth option. 2 Open IIS Manager and browse to the website you will serve Smooth Streams from. 3 In the Configuration Options screen, in the Media Services section, double-click Live Smooth Streaming Publishing Points. A message displays in the top right corner of IIS manager, stating that the application pools must be updated to support smooth streaming publishing points. Click the message. 4 You may be required to restart the site in IIS Manager. To restart, right-click the site and select Managing>Restart. Wait for the process to complete. 5 Click Add to add a new publishing point. 6 Provide a unique name for the publishing point, such as CapStation_01_Live. 7 Select properties for the new publishing point and configure it as follows: Archive Media: Select checkbox Allow client connections: Select checkbox Enable DVR for recent content: Select checkbox DVR Window Length: 1 Allow server connections: Select checkbox Start publishing point automatically upon first client request: Select checkbox Polycom, Inc. 38

39 Enable output to Apple mobile digital devices: Select checkbox to publish to ios or Android mobile devices. 8 You need to start each new publishing point after you create it. To start, right-click the publishing point and select Start Publishing Point. To enable the publishing point to automatically restart for each new presentation (optional): 1 Right-click the IIS website and select Explore. Polycom, Inc. 39

40 2 Browse to the publishing point config file (in this example, it is named CapStation_01_Live.isml) and open it with notepad.exe. 3 Add the following to the config file: <meta name="restartonencoderreconnect" content="true" /> 4 Reboot the server. Record the following Media Server settings for future reference: Media Server URL HTTP Streaming Port IIS Media Services Publishing Points IIS Media Services Website Location Windows Media Services Live Publishing Points and Type Windows Media Services On Demand Publishing Points and file locations Windows Media Services users with create permissions Windows Media Services users with write permissions Polycom, Inc. 40

41 5: Setting Up Microsoft Expression Encoder 4 Pro Install Microsoft Expression Encoder 4 Pro before installing RealPresence Media Manager software. The license key is included in your RealPresence Media Manager software package. Admin Tip: Installing Expression Encoder 4 Pro Install Expression Encoder 4 Pro on a dedicated, stand-alone server with Server 2008 R2 or Server 2012 to maximize transcoding and thumbnailing efficiency. Transcoding and thumbnailing are CPUintensive operations and may degrade the performance of RealPresence Media Manager software in single-server installations. Expression Encoder 4 Pro Requirements You need the following: Windows Server 2008 R2 or Windows Server 2012 Download the Expression Encoder 4 Pro SP2 installer to the server from The activation key for Expression Encoder 4 Pro SP2 (provided with your RealPresence Media Manager software license key) Enabling the Desktop Experience Feature If you are installing Expression Encoder, you need to enable the Desktop Experience feature. The Desktop Experience feature enables you to configure and control the Expression Encoder Pro software. To enable the Desktop Experience feature: 1 On the server, in Windows Server Manager, select Add Features. 2 Click Desktop Experience. Admin Tip: Installing Ink and Handwriting You will be required to install the Ink and Handwriting features included in the Expression Encoder Pro Desktop Experience package. 3 Restart the server. The Server Manager will automatically launch and complete the installation of the Desktop Experience feature. Polycom, Inc. 41

42 4 Close Windows Server Manager. Installing Expression Encoder 4 Pro To install Expression Encoder 4 Pro: 1 Browse to the Expression Encoder Pro installer, Encoder_En.exe. 2 Right-click Encoder_En.exe and select Run as administrator. 3 Follow the default installation prompts. 4 Enter the activation key, which was provided with your RealPresence Media Manager software license key. Timesaver: You do not need to reboot the servers. When the Expression Encoder Pro 4 installation is complete, you do not need to reboot the server to continue. Polycom, Inc. 42

43 Part III: Installing Polycom RealPresence Media Manager Software Part III shows you the steps for installing the RealPresence Media Manager software on the target application server. Before installing RealPresence Media Manager software, ensure you meet the following prerequisites: Application server with Microsoft Windows Server 2012 or Windows Server 2008 R2 Database server with Microsoft SQL Server 2012 or SQL Server 2008 R2 Microsoft Internet Information Services (IIS) 7.5 installed on the target application server Microsoft Expression Encoder Pro 4 installed on the target application server Microsoft.NET Framework 4.5 installed on the target application server Polycom, Inc. 43

44 6: Installing RealPresence Media Manager Software Install the RealPresence Media Manager software on your application server using the new Polycom RealPresence Media Manger InstallShield Wizard. The wizard guides you through the installation, offering default settings, or the option to change to custom installation settings, for each step. The installation process is as follows: Stop the Internet Information Services (IIS) default website in Windows Server 2012 Run setup.exe Activate the license Install the program files Install the primary and reporting database Select the IP address and port Set credentials Start the installation Caution: Install RealPresence Media Manager Software only after all Microsoft Servers are installed. If RealPresence Media Manager will be installed on a single server along with the application server or media servers, it is necessary that all Microsoft server roles are fully installed and functional before installing the Polycom RealPresence Media Manager software. This is the order detailed in this guide. Running the RealPresence Media Manager Installer The following procedure describes the basic steps to follow in the RealPresence Media Manager InstallShield Wizard. Polycom, Inc. 44

45 To start installation: 1 On the application server, in Windows Explorer, navigate to the PRMMx64 folder included with your zipped installer package. Polycom, Inc. 45

46 2 Open the folder, right-click setup.exe and select Run as administrator. 3 When the Polycom RealPresence Media Manager InstallShield Wizard opens, accept the End User License Agreement (EULA) and click the Next button. 4 Enter your Customer Information, including: User Name Organization 5 Accept the default destination folders by clicking the Next button, or select new destination folders for the program files, by clicking the Change button. If you click the Change button, you can change the locations of some features, including: Databases Polycom, Inc. 46

47 Portal Scheduler Windows Service Windows Service The default location for application files and web files is C:\. You can also install the RealPresence Media Manager software s application files to C:\ and the web files to a different local drive partition, such as D:\. Click the Next button. Caution: Installing Reporting on the Primary Database RealPresence Media Manager will run reports from the Primary Database by default. For large scale implementations, it is recommended to install reporting to an external database server. 6 Next, accept the default features to install to the default locations, or select Custom Setup to select which features you want to install. The options include: Databases Portal Scheduler Windows Service Windows Service To change an install location from the default for a feature, select the feature in the list, and then click the Change button. Browse to the new location. For most installations, select all the features. In the following exceptions, deselect the Database feature: For upgrade installations from earlier versions of RealPresence Media Manager software, deselect Databases. Polycom, Inc. 47

48 For secondary failover or load-balancing installations of RealPresence Media Manager software instances, deselect Databases. After installation configure Outgoing and Scheduler Services for manual startup. If you are using custom scripts to create databases in SQL Server, deselect Databases. When you have selected all the features to install, click the Next button. Admin Tip: Use the Appropriate Credentials Use the correct credentials for installation of RealPresence Media Manager software on the dedicated server, which may be different from credentials needed for configuration. Polycom, Inc. 48

49 7 Select the Primary Database you are installing to by browsing to it. Select Windows Authentication, to use the Windows credentials you are currently using, or the Server authentication, and enter the system administrator credentials in the Login ID and Password fields. Admin Tip: Global and Default Admin User Account Settings Remember your Global Username, Default Admin and password. You will use these credentials to log in to the RealPresence Media Manager software s Admin Tool and portals. The global admin user may be used to log into the admin tool should the RealPresence Media Manager ever be misconfigured so normal users cannot log in. Record these credentials in a secure location. 8 Enter the Global and Default Admin User Account Settings in the corresponding fields. Click the Next button. 9 If you are installing the RealPresence Media Manager software on a server with Windows Server 2012, the message Windows Media Services Not Detected displays. Windows Media Services is not supported in Server Continue to the next installation step. Polycom, Inc. 49

50 10 Select the reporting database server you are installing to by browsing to it. Select Windows authentication to use your current Windows credentials, or select Server authentication and enter the system administrator credentials in the Login ID and Password fields. Troubleshooting: Reporting Database Failure If the reporting database fails after selecting the reporting database server, the credentials you entered for the database server may be incorrect. Click the Back button twice to go back two steps and then re-enter the credentials for both the Primary Database and the Reporting Database. Click the Next button. 11 Select a Recovery Model: Simple Select the Simple recovery model to keep space requirements small, such as in smaller installations where a dedicated database administrator will not always be available to monitor the SQL Server. The Simple recovery automatically reclaims log space and does not back up logs. If you select this recovery model, remember that you can only recover changes made before your last backup. If the simple recovery method is chosen, a maintenance job will be installed that will create a backup, update statistics and defragment indexes on a nightly basis. The schedule may be changed in the SQL Server Agent after installation. Full Select the Full recovery model for more robust recovery options. This model requires additional maintenance specific to the usage and environment of a particular deployment. For this reason, the maintenance job will not be installed if either of these models is chosen. It is recommended that these models only be used if there will be an on-site or contracted database administrator present to monitor the SQL Server. The Full recovery model enables recover to an arbitrary point in time and requires log backups. Polycom, Inc. 50

51 Bulk-logged Select the Bulk Logged recovery model if you want to reduce log space for most bulk operations that need minimal logging. You can recover to the end of any backup, but not at an arbitrary point in time. The Bulk-logged recovery model requires the same database maintenance considerations as the Full recovery model. Enter the paths where the RealPresence Media Manager database files will be located on the target Microsoft SQL Server or Servers. Admin Tip: Using Non-default Database Paths If you use non-default database paths, the paths must exist on the target database servers before you install the RealPresence Media Manager software. All paths must also end in a back-slash (\). Click the Next button. Troubleshooting: SQL Script Installer Error If you receive an error message while the RealPresence Media Manager software installer is running the SQL scripts, one or more of the database file paths may be incorrect. Go back and check that the database file paths are correct and end in back-slashes (\). If a back-slash is missing, you need to restart the RealPresence Media Manager installation from the beginning. Polycom, Inc. 51

52 Setting the IP Address, Port, Host Header, and Credentials The next step is to enter the settings for the website that IIS Manager creates for your RealPresence Media Manager portal. Admin Tip: Multiple Websites on the IIS Server Polycom recommends hosting only the RealPresence Media Manager portal website on the IIS server. To complete the installation: 1 Enter a unique IP address or host header for the RealPresence Media Manager software s portal to use on the server, or leave the IP address and Host Header fields blank except in the following scenarios: The server is hosting multiple websites The server has a separate website for the Web Content Server role Click the Next button. 2 Set the Media Manager Primary Database Portal credentials. This creates matching login credentials for the server and the Web.Config file of the portal. Polycom, Inc. 52

53 3 Set the Media Manager Primary Database Admin credentials. These credentials are used by the RealPresence Media Manager software s Admin (WCF) Web Services and Scheduler Windows Service. Click the Next button. 4 Set the Login ID and Password for Media Manager Reporting Database credentials. These credentials are used by the Admin Web Services and SQL Server Reporting Services to generate reports. Click the Next button. Polycom, Inc. 53

54 5 Set the Login ID and Password for Media Manager Primary Database Outgoing Service Credentials. Click the Next button. Admin Tip: Use Unique Credentials for Each Database Service Use four different login IDs and passwords for the database services credentials. Do not repeat the database catalog name or login ID if you are using the primary database for reporting. Allow the installer to create both databases and follow the instructions for SQL Server Reporting Services (SSRS) setup to re-use the primary database for reporting purposes. 6 On the Ready to Install page, click the Next button to install the RealPresence Media Manager software s program files, database, services and web site on the selected server. Polycom, Inc. 54

55 7 On the InstallShield Wizard Completed page, select the Show the Windows Installer Log checkbox. Click the Finish button. If you are installing RealPresence Media Manager software on Windows Server 2012, you will get a WMS error. This error occurs because Windows Server 2012 does not support the Windows Media Services (WMS) role and the Polycom Media Services Agent is installed on the application server automatically. Click the OK button to continue installing RealPresence Media Manager software. The InstallShield Wizard will install the RealPresence Media Manager software files. The process takes between 20 and 30 minutes. Polycom, Inc. 55

56 7: Installing and Launching the RealPresence Media Manager Admin Tool After installing the RealPresence Media Manager software s program files on the application server and setting up global authentication, you need to launch the RealPresence Media Manager software s Admin Tool. The Admin Tool enables you to configure user permissions, portal settings, and manage content without the need to use Windows server management tools. Installing and Launching the Admin Tool To configure and administer RealPresence Media Manager software, you need to install the Admin Tool. If you are logging in to the Admin Tool for the first time, you will be prompted to enter an Activation product key. To install, launch, and log in to the Admin Tool: 1 In your browser s address bar, enter the URL for your RealPresence Media Manager software portal and add /admin/ to load the Admin Tool launch page. For example, enter in the browser s address bar. 2 On the Launch page, click the Launch Application button to launch the Windows Installer and install the RealPresence Media Manager Admin Tool. Once it has finished installing, you can launch the Admin Tool from the Launch page. 3 To launch the Admin Tool from the Launch page, click the Launch Application button to open the Media Manager Login dialog box. Polycom, Inc. 56

57 4 In the Media Manager Login dialog box, in the Portal URL field, enter the URL of your Media Manager portal. Click the Refresh button. 5 Enter your valid, administrator address and password. 6 Click the Log In button to launch the Media Manager Admin Tool application. Activating the Product License Key To activate the RealPresence Media Manager license, you ll need the following items: RealPresence Media Manager appliance serial number A RealPresence Media Manager appliance serial number is an auto-generated number that is connected to a particular appliance. The serial number cannot be transferred to other RealPresence Media Manager software installations on other appliances. You access the RealPresence Media Manager appliance serial number from the sticker on the appliance. You ll need the serial number to obtain an activation key from Polycom Support. Polycom Software License code You received a Polycom Software License code when you purchased your RealPresence Media Manager appliance and/or software license. Refer to your software license for the code. You ll need the code to obtain an activation key from Polycom Support. Activation key An activation key is generated by Polycom Support. To obtain the activation key, you need to enter your RealPresence Media Manager appliance serial number and Polycom Software License code through the Polycom Support portal. Then, you can enter the activation key into the RealPresence Media Manager software s Admin Tool, which will activate the license. Note: Store the serial number, license code, and activation key for future reference. Store the RealPresence Media Manager appliance serial number, Polycom Software License code, and Activation key in a safe location for future reference. You may need to provide the information to Polycom Support if you experience issues with the RealPresence Media Manager software. Polycom, Inc. 57

58 To obtain the product license key: 1 Using an Internet browser, visit Polycom Support at 2 In the Licensing & Product Registration menu, select Activation/Upgrade. 3 Log in to your Polycom online account. 4 On the License and Product Activation page, select SITE & Single Activation/Upgrade. 5 Enter the RealPresence Media Manager appliance serial number (that you obtained in step 1) in the Serial Number box, and click Next. The system validates the serial number and identifies the type of product the number belongs to. 6 On the Activation page, enter the Polycom Software License code you received when you purchased the RealPresence Media Manager software license, and click Activate. The system produces an activation key. Copy the activation key to a text file so you can enter it into the RealPresence Media Manager Admin Tool in a later step. When you launch the RealPresence Media Manager Admin Tool for the first time, the Manage License dialog box opens and prompts you to enter the Product Activation Key. To activate the license in the RealPresence Media Manager Admin Tool: 1 Check that you are connected to the Internet. 2 Enter the Product Key in the field. 3 Click the Activate via Internet button. The RealPresence Media Manager software connects to the Polycom Activation Server on port 443 and verifies your license key. Polycom, Inc. 58

59 Activating a Product License Key on a New Installation of RealPresence Media Manager Software Follow these steps to activate a new installation of RealPresence Media Manager software. To activate the license: 1 Launch the Admin Tool from the Launch page by clicking the Launch Application button. 2 In the Media Manager Login dialog box, click the Refresh button. 3 In the license field, enter your product license key. 4 Click the Activate via Internet button. Activating a Product License Key on a RealPresence Media Manager Appliance When you first start up your RealPresence Media Manager appliance, it uses the 90-day trial license by default. You need to remember to retrieve your product license key and activate the RealPresence Media Manager software license before the 90-day trial expires. To activate a new product license key on a RealPresence Media Manager appliance: 1 Launch the RealPresence Media Manager software Admin Tool and log in using your administrator address and password. 2 Right-click the Media Manager Root and select Properties. 3 Click the Manage License tab. Polycom, Inc. 59

60 4 In the Activation section, enter the new product key, or click the Import License File button. 5 Browse to the product license key and select it. 6 Click the Activate via Internet button. Polycom, Inc. 60

61 Setting Initial Admin Tool Media Manager Preferences When the Media Manager Admin Tool launches for the first time, the Edit Preferences tab opens in the Work Area. To edit your preferences: 1 Enter an address. 2 If you want to change your password, select the Change Password checkbox and enter your old password and a new password in the corresponding fields. 3 Select a Time Zone, Locale, and Language from the lists. 4 Click the Save button. Encrypting Database Strings If security is a concern for this installation, follow best practice methods and you can encrypt the Media Manager config files. This is an optional step. You need to encrypt the config files manually using aspnet_regiis.exe. To encrypt the config files, follow these examples: Encrypt c:\windows\ Microsoft.NET\Framework\v \aspnet_regiis.exe pef connectionstrings c:\inetpub\wwwroot\polycom\realpresence Media Manager\Portal Decrypt c:\windows\ Microsoft.NET\Framework\v \aspnet_regiis.exe pdf connectionstrings c:\inetpub\wwwroot\polycom\realpresence Media Manager\Portal Admin Tip: Encrypting Windows Services For the windows services you have to rename the.exe.config to web.config, run the process, and then rename it back when the encryption is complete. If you ve already encrypted and you want to descript, use -pdf instead of pef. Polycom, Inc. 61

62 8: Installing in RealPresence Media Manager Software You can configure RealPresence Media Manager software to send messages to alert you of the following conditions: When users register for events When new users self-register System alerts Pending tasks Installing the Outgoing Service The RealPresence Media Manager software s feature uses Simple Mail Transfer Protocol (SMTP). To install the service, you need to complete the following steps: Stop the service on the application server that RealPresence Media Manager software is installed on if you are upgrading from a previous version of RealPresence Media Manager software Purge old database records if you are upgrading from a previous version of RealPresence Media Manager software Configure the service in the RealPresence Media Manager software Admin Tool Configure SMTP by editing the Outgoing .exe.config file Restart the service on the application server Stopping the Service on the Application Server Before proceeding with configuration of outgoing settings, you need to stop the service running in Windows Server To stop the service running on the application server: 1 In Windows Server 2012, open the Run dialog box and run services.msc. 2 In the Services dialog box, select Polycom RealPresence Media Manager Outgoing Services. Polycom, Inc. 62

63 3 Click Stop the service. Purging Old Database Records To purge old database records: 1 Using SQL Server Management Studio, log in to the database. 2 Select Databases AccordentAmms. 3 Click New Query. 4 Enter the following commands: DELETE FROM AMMS.Outgoing Attachments DELETE FROM AMMS.Outgoing s Go 5 Execute the query. The message Query executed successfully displays at the bottom of the window. 6 Close SQL Server management studio. Configuring in RealPresence Media Manager To configure the outgoing settings in RealPresence Media Manager: 1 Launch the RealPresence Media Manager Admin Tool and log in. 2 In the Portal Administration panel, right-click the Media Manager Root and click Properties. 3 In the System Settings tab, in the Settings section, enter a From Address and a From Name in the fields. System level messages, such as alerts and notices, will be sent from this address and name. Polycom, Inc. 63

64 4 Click the Save button. 5 Right-click your portal and click Properties. 6 In the Details tab, in the Settings section, enter a From Address and a From Name in the fields. Portal level messages, such as registrations, will be sent from this address and name. 7 Click the Save button. Configuring SMTP The next step is to configure the SMTP settings by editing the Outgoing .exe.config file. To configure SMTP by editing the config file: 1 Using Windows Notepad, or another XML editor, open and edit this file: C:\Program Files (x86)\polycom\realpresence Media Manager\ Service\Outgoing .exe.config Polycom, Inc. 64

65 2 Locate the mailsettings tag. 3 Edit the network string to contain the following values: Host Your organization s SMTP server, for example smtp.majoru.edu username Enter a username if required password Enter a password if required enablessl Change this value to True if SSL is required 4 Save the file. Restarting the Service on the Application Server After configuring outgoing in RealPresence Media Manager and editing the SMTP config file, you can restart the outgoing service in Windows Server Polycom, Inc. 65

66 To stop the service running on the application server: 1 In Windows Server 2012, open the Run dialog box and run services.msc. 2 In the Services dialog box, select Polycom RealPresence Media Manager Outgoing Services. 3 Click Start the service. Testing Your Installation After installing and configuring the outgoing service in RealPresence Media Manager software, you can test the configuration by sending an from the system. To send a test notification using the outgoing service: 1 Launch the RealPresence Media Manager Admin Tool and log in. 2 In the Scheduling panel, click the New button to open the new event tab in the Work Area. Polycom, Inc. 66

67 3 Select Notification from the Event Type list. 4 Enter text in the Subject and Body fields. 5 To select a recipient address, in the Send to additional users section, click the Resource Control button, select users or groups from the list in the Users & Groups panel, and click the Add button. Send the test to a known address so you can see the results immediately. Polycom, Inc. 67

68 6 To associate the notification with an Upcoming Event, click the Resource Control button next to the Upcoming Event field, expand the portal node, select an Upcoming Event from the list, and then click the Add button. Polycom, Inc. 68

69 9: Configuring Reports To generate reports in RealPresence Media Manager software, you need to install and configure SQL Server Reporting Services (SSRS) on a server that will be accessible to all clients using the RealPresence Media Manager Admin Tool. Polycom recommends installing SSRS on the RealPresence Media Manager portal server. This chapter shows you the steps for installing and configuring SSRS. Configuring SQL Server Reporting Services and Reports To generate reports using the RealPresence Media Manager Admin Tool, install Microsoft SQL Server Reporting Services (SSRS). SSRS can be installed on a singular admin services web service, on each web server of an admin services web farm, on a separate database server, or on the primary RealPresence Media Manager database server. Admin Tip: Selecting an Account You can use the System or Network Service account for the service. If there is an existing instance of the SQL Server, you can use the same account. In some domains you will find that authentication fails if running as Network Service due to GPO. In these cases, try the Local System account for better results. Polycom, Inc. 69

70 Connecting SSRS in SQL Server 2012 or SQL Server 2008 R2 to RealPresence Media Manager Software To connect SSRS in SQL Server 2012 or SQL Server 2008 R2 to RealPresence Media Manager software: 1 On the database server you have installed SSRS on, open Reporting Services Configuration Manager. The Reporting Services Configuration dialog box opens. 2 In the Reporting Services Configuration Connection dialog box, enter the reporting server name, which is the RealPresence Media Manager server, in the Server Name field and click the Find button. 3 Select the Report Server Instance from the menu in the Report Server Instance field. Click the Connect button. Polycom, Inc. 70

71 4 The Report Server Status page opens. If the Report Service Status displays as Stopped, click the Start button. Selecting an Account and Creating a Report Server To select an account and create a Report Server URL: 1 With SSRS connected to the RealPresence Media Manager software server, in Reporting Services Configuration Manager, in the navigation pane, click Service Account. 2 Select either Use built-in account and select the account from the list, or Use another account and complete the Account and Password fields. 3 Click Apply. 4 In the navigation pane, click Web Service URL. 5 Complete the fields that are relevant to your RealPresence Media Manager software installation. Polycom, Inc. 71

72 6 Click Apply. You need to click Apply even if you did not change any of the settings on the Web Service URL page. Creating a Report Server Database Once you have generated the Report Server URL, you can create or change the Report Server Database. To create a Report Server database: 1 In the navigation pane, click Database. 2 Click Change Database. Polycom, Inc. 72

73 3 Select Create a new report server database and click the Next button. 4 Complete the fields with information specific to your RealPresence Media Manager software installation and click the Next button. Polycom, Inc. 73

74 5 Enter a name for the database you are creating, for example ReportServer, or select an existing database from the list. Select Native Mode and click the Next button. 6 Select an authentication type from the list and enter credentials for the account running Reporting Services. Click the Next button. Polycom, Inc. 74

75 7 Read the summary and verify that the information is correct and click the Next button. 8 Click the Finish button. To configure the remaining settings for SSRS: 1 In Reporting Services Configuration Manager, in the navigation pane, click Report Manager URL. Polycom, Inc. 75

76 2 If there are any custom settings for the RealPresence Media Manager website, such as host headers or non-standard port numbers, click the Advanced button and complete the fields. 3 Click the Apply button. 4 If you are deploying SSRS on multiple servers in addition to the RealPresence Media Manager web server, you need to add the servers. In the navigation pane, click Scale-out Deployment. 5 Click the Add Server button to add SSRS servers to your existing SSRS deployment. Click the Apply button. Polycom, Inc. 76

77 Configuring Anonymous SSRS Access If public access to SSRS is required or if Media Manager is not installed in an Active Directory Domain, you need to configure anonymous SSRS access. To configure anonymous SSRS access: 1 On the RealPresence Media Manager software application server, using Windows Explorer, browse to the SSRS folder. The path is: PRMM v6.5.x.x x64\prerequisites\ssrs 2 Right-click Accordent.ReportingServices.AnonymousSecurity.dll and select Copy. 3 In Windows Explorer, browse to the SSRS installation s ReportServer\bin directory in the SQL server folders. Right-click the bin directory and select Paste. 4 Browse to the SSRS installation s Reporting Services\ReportServer folder. 5 Right-click the web.config file and select Edit. 6 Edit the web.config file to match the following XML (the changed values are indicated in bold): <?xml version="1.0" encoding="utf-8"?> <configuration> <system.web> <pages validaterequest="false"> <controls> <add tagprefix="asp" namespace="system.web.ui" assembly="system.web.extensions, Version= , Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> </controls> </pages> <authentication mode="none" /> <identity impersonate="false" /> <compilation defaultlanguage="c#" debug="false" tempdirectory="c:\program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\RSTempFiles\"> <assemblies> <clear /> <add assembly="reportingserviceswebserver" /> <add assembly="system.xml, Version= , Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <add assembly="system.web.services, Version= , Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </assemblies>] Save the changes. 7 Right-click the rsreportserver.config file and select Edit. Edit the rsreportserver.config file to match the following XML (the changed values are indicated in bold): Polycom, Inc. 77

78 </URLReservations> <Authentication> <AuthenticationTypes> <Custom/> </AuthenticationTypes> <RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel> <RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionSc enario> <EnableAuthPersistence>true</EnableAuthPersistence> </Authentication> <Service> Add the section in bold: <Security> <Extension Name="Windows" Type="Microsoft.ReportingServices.Authorization.WindowsAuthorization, Microsoft.ReportingServices.Authorization"/> </Security> <Authentication> <Extension Name="Windows" Type="Microsoft.ReportingServices.Authentication.WindowsAuthentication, Microsoft.ReportingServices.Authorization"/> </Authentication> <Security> <Extension Name="None" Type="Accordent.ReportingServices.AnonymousSecurity.Authorization, Accordent.ReportingServices.AnonymousSecurity"/> </Security> <Authentication> <Extension Name="None" Type="Accordent.ReportingServices.AnonymousSecurity.AuthenticationExtension, Accordent.ReportingServices.AnonymousSecurity"/> </Authentication> <EventProcessing> Save the changes. 8 Right-click the rssrvpolicy.config file and select Edit. Edit the rsreportserver.config file to match the following XML (the changed values are indicated in bold): </CodeGroup> </CodeGroup> <CodeGroup class="unioncodegroup" version="1" Polycom, Inc. 78

79 PermissionSetName="FullTrust" Name="Private_assembly" Description="This code group grants custom code full trust."> <IMembershipCondition class="urlmembershipcondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin\Polycom.ReportingServices.AnonymousSecurity.dll" /> </CodeGroup> </PolicyLevel> </policy> </security> </mscorlib> </configuration> Save the changes. 9 Restart the SSRS service. Installing Media Manager Reports using the Reports Uploader To upload the RealPresence Media Manager reports to your SSRS instance, install the RealPresence Media Manager software s Reports Uploader application. To install the Reports Uploader: 1 On the RealPresence Media Manager software application server, using Windows Explorer, browse to the ReportsUploader directory. The path is PRMM v6.5.x.x.64\reportsuploader. 2 Run Accordent.Amms.Reports.Uploader.exe. 3 Enter the Reporting Services Web Service URL, and complete the fields for the primary database and reporting database subfolders. You created these databases when you installed the RealPresence Media Manager software. If you set a Target Reports Folder, which places reports in a subfolder rather than the root folder of SSRS, you need to use this folder in the Admin Services Reports.config rdlpath. 4 Click the Upload Files button to install Media Manager Reports. When the Reports Uploader is installed, the message Processing Complete displays. The reports will be located on the SSRS instance in the Primary and Reporting folders. Polycom, Inc. 79

80 You can verify your SSRS installation by browsing to the Reports folder on the configured RealPresence Media Manager Web Server. 5 Set the reportingservicespath and rdlpath in your Admin Services Reports.config if nonstandard, or located on a different server from the RealPresence Media Manager software. Polycom, Inc. 80

81 10: Upgrading a Previous Version of RealPresence Media Manager Software to Version 6.5 This chapter shows you how to upgrade an older version of RealPresence Media Manager software to version 6.5. Note: Minimum Upgradeable Version of RealPresence Media Manager Software RealPresence Media Manager versions starting with 4.5 can be upgraded to version 6.5. Preparing Your Environment for Upgrading to Version 6.5 Before upgrading to version 6.5, your existing hardware needs to meet the following specifications: Table 6: RealPresence Media Manager - Software Edition Minimum Hardware Requirements Minimum Hardware Processor Memory Local Storage Network Interface Recommended Hardware Processor Memory Local Storage Shared Storage Specification Intel Xeon 4-core or comparable 4GB (8GB or more is recommended) 40GB RAID 1 Partition (OS) 40GB RAID 1 Partition (Apps) 100 Mb/s, 1GB is recommended Specification Intel Xeon 8-core or comparable 8GB 40GB RAID 5 Partition (OS) 20GB RAID 5 Partition (Apps) 40GB iscsi/fc SAN (OS) 20GB iscsi/fc SAN (Apps) Polycom, Inc. 81

82 Upgrading to RealPresence Media Manager 6.5 Software After you have prepared your environment, you can upgrade the RealPresence Media Manager software. To upgrade to version 6.5: 1 On the application server, in Windows Explorer, navigate to the PRMMx64 folder included with your zipped version 6.5 installer package. 2 Open the folder, right-click setup.exe and select Run as administrator. 3 You will see a message warning that you are about to upgrade from version X to version When the Polycom RealPresence Media Manager InstallShield Wizard opens, accept the End User License Agreement (EULA). Polycom, Inc. 82

83 5 On the Upgrade Verification screen, check that your current RealPresence Media Manager software version is correct and verify the values from the config files. 6 Click the Install button to start the upgrade to RealPresence Media Manager 6.5 software. Polycom, Inc. 83

84 The RealPresence Media Manager InstallShield Wizard upgrades to the version 6.5. Polycom, Inc. 84

85 11: Getting Help For more information about installing, configuring, and administering Polycom products, refer to Documents and Downloads at Polycom Support. To find all Polycom partner solutions, see Polycom Global Strategic Partner Solutions. The Polycom Community The Polycom Community gives you access to the latest developer and support information. Participate in discussion forums to share ideas and solve problems with your colleagues. To register with the Polycom Community, simply create a Polycom online account. When logged in, you can access Polycom support personnel and participate in developer and support forums to find the latest information on hardware, software, and partner solutions topics. Polycom, Inc. 85

86 12: Troubleshooting Use the following list as a guide to resolving issues, problems, or common difficulties you may encounter while deploying RealPresence Media Manager software. You have installed the RealPresence Media Manager software, but using to open the RealPresence Media Manager portal does not work. You need to open and enter the Product Key. For more details, see Activating the Product License Key in Chapter 7. You have installed the RealPresence Media Manager software, but when you launch the RealPresence Media Manager Admin Tool, the error message, Server Error in Application DEFAULT WEB SITE displays. The Default IIS website is still running on the IIS web server. You need to stop the Default Website in IIS Server Manager, and then start the RealPresence Media Manager portal website. For more details see Disabling the Default IIS Website in Chapter 2. After installation, you cannot log in to your RealPresence Media Manager portal or Admin Tool using the credentials you set. Set the SQL Server to mixed mode authentication and retry your login to the RealPresence Media Manager portal or Admin Tool. For more details, see Setting Up SQL Server 2012 in Chapter 3. Are notifications being produced by the RealPresence Media Manager software? s appear in the database if they are being produced. Polycom, Inc. 86