Follow the steps in this section to define installation roles and features on each server that runs an instance of MEDIAL.
To define roles and features for MEDIAL:
1. Open Server Manager by clicking the icon next to the Windows logo on the taskbar.
If this button is not present:
a. Click the Windows icon:
b. Click Administrative Tools.
c. Double-click Server Manager.
2. On the welcome screen, click Add roles and features.
3. At the Before you begin screen, click Next.
4. At the next screen, leave the radio button for Role-based or feature-based installation set as-is and click Next.
5. Leave the current server selected and click Next.
6. From the list of Roles, check the Web Server (IIS) role.
7. In the window that appears, ensure that the box for Include management tools is checked and click Add Features.
8. On the Select Features screen, check the box to add .NET Framework 3.5 features.
10. Click Add Features in the window that appears.
11. Back on the Select Features screen, click Next.
12. Click Next on the Web Server Role (IIS) screen.
13. At the Select role services screen, scroll down and check the Application Development box. Expand the lists and check all of the roles within it, agreeing to any sub-roles when prompted. Click Next.
14. The server will require a restart. Check the Restart the destination server automatically if required box to do this automatically after the roles and features have been installed. Then click Install.
On the MEDIAL machine, the additional IP addresses required by MEDIAL need to be added to the network card.
To add network addresses:
2. Type network and sharing center.
3. Click Network and Sharing Center.
4. Click Change adapter settings.
6. Click Internet Protocol Version 4 and select Properties.
7. Click Advanced.
10. Close all windows by clicking OK.
By default, Internet Information Services listens on all available IP Addresses. To avoid port conflict with Wowza Media Server, the IP address that will be used for the MEDIAL websites (front-end and back-end) need to be bound to IIS. The IP address used by Wowza Media Server also needs to be bound to IIS.
1. Open a command prompt with administrative privileges. Run the following commands in the order they appear. Here the first and second addresses are for the front-end and back-end MEDIAL sites. The third address is for Wowza. With Windows Server 2012, the local loopback address (127.0.0.1) must also be bound to IIS.
Netsh http add iplisten ipaddress=x.x.x.1 Netsh http add iplisten ipaddress=x.x.x.2 Netsh http add iplisten ipaddress=x.x.x.3 Netsh http add iplisten ipaddress-127.0.0.1
Note: The preceding example assumes that MEDIAL and Wowza are installed on the same machine. If they are installed on separate machines, bind the two MEDIAL addresses and the loopback address on the MEDIAL machine. Bind the Wowza address and the loopback address on the Wowza machine.
2. Restart IIS by issuing the following commands:
net stop http /y
net start http
net start w3svc
Perform the MEDIAL Installation
After you have carried out all of the necessary preparation steps, you can install MEDIAL and its related software according to the instructions in the Installation section, beginning with the topic Codec Support.