Hosting Through IIS Instead of the Integrated Web Server

KB#1013: Last Updated Feb 13, 2019

When you install any of our products using the installer, you’re presented with two application hosting options: Integrated Web Server or IIS Web Application.

The question of which to choose comes down to simplicity or robustness. The Integrated Web Server is easy to install (and obviously doesn’t require IIS installed), while an IIS Web Application offers a whole lot more advanced hosting features and configurations (but of course requires IIS).

If you’ve started with the Integrated Web Server and would like to upgrade your hosting to an IIS Web Application, all it takes is a few easy steps.

1. Change Configuration

The service looks in configuration to determine whether the integrated web server should be started.

BuildMaster & Otter

The integrated web server's configuration is stored in a configuration file.

  1. On the server, navigate to the Service root directory
    (by default, C:\BuildMaster\Service or C:\Otter\Service)
  2. Open App_appSettings.config in any text editor
  3. Change the value of the key named IntegratedWebServer.Enabled to False
  4. Save the file


In ProGet, the integrated web server's configuration is stored in the database.

  1. Sign in to ProGet with an account that has administrative privileges
  2. Click the Admin link (top right corner of the navigation
  3. Click on All Settings under the System Settings options
  4. Change the UseIntegratedWebServer key to False

2. Uninstall IWS Service

This step is only necessary for BuildMaster & Otter, skip to step 3 for ProGet.

  1. Open a Command Prompt with administrative privileges
  2. Navigate to the service directory
    (default C:\BuildMaster\Service or C:\Otter\Service)
  3. Stop the IWS Service by typing net stop inedobmwebsrv for BuildMaster & net stop inedootterwebsrv for Otter
  4. Uninstall the IWS Service by typing bmservice UninstallWebServer for BuildMaster & otterservice UninstallWebServer for Otter

3. Create IIS Web Application

  1. Open the IIS Manager
  2. Create a new Application Pool named BuildMasterAppPool, ProGetAppPool, or OtterAppPool with the following configuration:
    • Framework Version(IIS 7.x): v4.0
    • Management pipeline mode (IIS 7.x): Classic

    Instructions for creating pools can be found here:

  3. Create a new Website (virtual directories are not supported) named BuildMaster, ProGet, or Otterwith the following configuration:
    • Home Directory: C:\BuildMaster\WebApp (default), C:\Program Files\ProGet\WebApp (default), or C:\Program Files\Otter\WebApp (default)
    • Framework Version (IIS 6): v4.0

The installer relies on IIS naming conventions. If you don't follow the conventions (ProductName for site, ProductNameAppPool for application pool), then the installer will not be able to stop the application pool during upgrade (which will likely cause errors), nor will uninstallation remove these from IIS.

Your product will now be hosted through IIS. The products aren't very particular about how they are hosted, so virtually any of the settings within the IIS Application or Application Pool can be changed to suit your needs.