Article: How to Run FrameFlow on IIS 7.0 (Server 2008/Vista/Windows 7) with HTTPS/SSL

Summary

This article explains how to run FrameFlow on IIS 7.0 (Windows Server 2012/2008/Vista/Windows 7) with HTTPS/SSL.

By default the user interface is accessed through a web server that is integrated right in FrameFlow and FrameFlow MSP. The integrated web server makes for quick and easy deployment without the need to install and configure IIS. However, there are certain times when you may prefer to access the FrameFlow user interface through IIS and this is fully supported. Reasons to switch to IIS may include corporate policy or the need to use HTTPS/SSL to protect access to the console.

1. Stopping the FrameFlow Service

  1. Press Win + R to open the Run dialog
  2. In the "Open:" drop down, type: services.msc
  3. Press Enter or click OK to open the services window
  4. Right click on the "FrameFlow Service" or "FrameFlow MSP Service" service and choose "Stop"

2. Disable the Integrated Web Server

Open the "config.ini" file which is found at "C:\Program Files (x86)\FrameFlow Multi-Site Monitor\config.ini"
using Notepad and look for the section called [WebServer] followed by and entry called "Enabled=1" and change it to "Enabled=0"

3. Starting the FrameFlow Service

  1. Press Win + R to open the Run dialog
  2. In the "Open:" drop down, type: services.msc
  3. Press Enter or click OK to open the services window
  4. Right click on the "FrameFlow Service" or "FrameFlow MSP Service" service and choose "Start"

4. Install IIS

  1. Use the Server Manager to add the "Application Server" role.
  2. In the "Role Services" section enable "Web Server (IIS) Support".
  3. In the role services for IIS enable "ASP" and "Server Side Includes".

5. Install a Self-Signed Certificate

  1. Select the top level item which has the same name as the local system.
  2. On the righthand side double-click on the item called "Server Certificates".
  3. In the Actions menu on the very righthand side select "Create Self-Signed Certificate".
  4. Enter a name for the certificate and press OK.
  5. Navigate to the "Default Web Site" item in the IIS Manager.
  6. Right-click on "Default Web Site" and select "Edit Bindings".
  7. Use the Add button to add an HTTPS binding on port 443 with your newly created certificate.
  8. Use the Remove button to remove the http binding on port 80 so that HTTPS/SSL is required to access the site.

6. Add the Application

  1. In the IIS Manager right click on "Default Web Site" and select "Add Application".
  2. For the alias specify "frameflow".
  3. For the physical path enter "C:\Program Files (x86)\FrameFlow Multi-Site Monitor\Html".

7. Configure Application Pool (64-bit Windows Only)

  1. If running on a 64-bit version of Windows, select Application Pools.
  2. Right-click on "DefaultAppPool" and choose "Advanced Settings".
  3. Set "Enable 32-bit Applications" to "True" and press OK.

8. Register Required Components

  1. Use "Run as Administrator" to open a command line window.
  2. Use "cd" to navigate to your FrameFlow installation folder.
  3. Run: regsvr32 frameflowtokenexpander.dll

9. Configure IIS Handlers

  1. Use "Run as Administrator" to open a command line window.
  2. Run: %windir%\system32\inetsrv\appcmd unlock config -section:system.webServer/handlers

10. Verify HTTPS/SSL Access

  1. Verify that you can access the user interface through HTTPS/SSL by visiting "https://servername/frameflow"
  2. Your web browser may warn about the self-signed certificate before allowing you to proceed.

11. Update Remote Node Configurations (FrameFlow MSP Only)

  1. On each remote node, edit the file "config.ini" in the "C:\Program Files (x86)\FrameFlow Multi-Site Monitor" folder.
  2. Edit the "MasterNode" value to start with "https://".