*************************************************************** Voynex Media Guard Readme File March 20, 2009 Version 2.3 *************************************************************** (c) Copyright Voynex LLC, 2004-2009. All rights reserved. This file contains information that supplements Voynex Media Guard plug-in documentation. *************************************************************** Contents *************************************************************** 1. Overview 2. Installation 3. Monitoring 4. Requirements 5. Troubleshooting *************************************************************** 1. Overview *************************************************************** Voynex Media Guard system consist of the two counterparts: Windows Media Services plug-in and gateway. Plug-in is a DLL (dynamic link library), which works together with the media services. Plug-in "tells" media services when grant or deny access to the media content for connected user. Gateway is a remote HTTP server, where all accounting, billing and authorization logic is implemented. Plug-in communicates with external data storage(s) - receives authorization parameters and send statistics to the gateway. Also plug-in controls access to the media content. Gateway manages payment operations and actually performs users authorization. Media Guard plug-in interconnects with the gateway using application level protocol based on HTTP. Communication process is defined in protocol specification document shipped whith the installation. *************************************************************** 2. Installation *************************************************************** Voynex Media Guard plug-in must be installed on the computer running Windows Server Family OS with Windows Media Services installed. Gateway scripts must be istalled on the computer where the web server software is running. Physically both servers can be configured to work on the same computer. However, except for small-scale video deployments, it is not recommended. High demand for video streams will reduce the delivery speed of web server, and high demand for web pages will hurt video stream quality. This is especially true if both services are trying to push their output through the same network interface card (NIC). It is recommended that media server and getaway server should be in a one LAN for better performance and security. To install Media Guard software execute setup application (exe file). It will register plug-in dll, create registry keys and copy files to the installation folder. After the installation will be complete go to the WMS management console and enable the Voynex Media Guard Plugin. Read the "Monitoring" section on how to open WMS management console. If the enabling of the plug-in was completed in Error, then read the "Troubleshooting" section. *************************************************************** 3. Monitoring *************************************************************** After plug-in is installed and Windows Media Services are launched, Voynex Media Guard creates log file named mguard.log located at "%sysdrv%:\wmpub\wmiislog\" where %sysdrv% is the system disk (usually disk "C"). Each message in a log file begins with a new line and contains information about plug-in events. Each line contains time and date of the event, log level and description. Log level indicates the message type. There are six available log levels: "None", "Error", "Warning", "Info", "Trace", "All". Values are ordered by so called 'log level' value. "None" has the lowes log level value. When installing Media Guard user can specify log level. Messages with the lower log level are not added to the log file. If you want to display all messages use "All" value for log level. If you will notice any plug-in faults, please send us Media Guard log file. To use Media Guard windows media services have be started. To manage Windows Media Services 9 Series use corresponding MMC console. This console can be accessed from "Start Menu" -> "Administrative Tools" -> "Windows Media Services" menu or type the following in the command line ("Start Menu"-> "Run"): "%winsysdir%\windows media\server\admin\mmc\wmsadmin.msc", where %winsysdir% is the windows system directory (usually C:\Windows\System32) *************************************************************** 4. Requirements *************************************************************** Web interface * Operating System required: Microsoft Windows or Linux family OS * Software required Web server, PHP 4+, MySQL Media Services plug-in * Operating System required (one of the following OS): Microsoft Windows Server 2003 Enterprise/Datacenter Edition Microsoft Windows Server 2003 Enterprise/Datacenter Edition, x64 Edition Microsoft Windows Server 2003 R2 Enterprise/Datacenter Edition Microsoft Windows Server 2003 R2 Enterprise/Datacenter Edition, x64 Edition Microsoft Windows Server 2008 Web/Standard/Enterprise Edition Microsoft Windows Server 2008 Web/Standard/Enterprise Edition, x64 Edition Microsoft Windows Server 2008 R2 Beta Web/Standard/Enterprise Edition * Memory required: Minimum 512 MB RAM Recommended 2 GB RAM * Disk Space required: 1 MB * Software required Microsoft Windows Media Services 9 Series Notes ~~~~~ Microsoft Windows Media Services are shipped together with the Windows Server family OSes but they are not installed by default. Important ~~~~~~~~~ In WMS 9 Series (5.x), for each Publishing Point, there is a Microsoft FastCache Plugin under General category. When it is enabled, it notifies window media players that content can be cached to user's local disk. If you disable Fast Cache plug-in, your content will not be cached to disk by the Windows Media Player. You must disable this plug-in to protect your content from being saved by users. *************************************************************** 5. Troubleshooting *************************************************************** If there will be any problems with streaming look up for Windows Media Services errors log. Bllow is the explanations of the errors generated by Windows Media Services and related to authorization plug-ins. Also the following errors may occur when you will try to enable the Media Guard plug-in: 1. Server Error (0x8007007e) - The specified module could not be found. Cause: The Plug-in DLL or the dependent DLL files could not be found. This error appears when you try to enable the Plug-in. Action: Make sure the Plug-in DLL is installed on your system and was not moved after installation. 2. Server Error (0x80070005) - Access is denied. Cause: If the user who starts Windows Media Services does not have access privileges to access the Plug-in DLL or the dependent DLL files, this error appears when you try to enable the Plug-in. Action: Add the user account to the group or user names that have the permission to access the directory that contains the plug-in DLL or the dependent DLL files. Or grant "Read & Execute" permission on the Plug-in DLL or the dependent DLL files to the "Users" group. 3. Cannot stream media from the publishing point configured with Voynex Media Guard plug-in. Cause: If a fatal error occurrs, Windows Media Server will automatically disable the Plug-in. Action: Check the Server Properties tab to see if the Plug-in is enabled. If the Plug-in is disabled, fix the problem based on the error message shown in server Troubleshooting pane. Enable the Plug-in before the streaming is restarted.