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, except for load-balanced or High Availability installations of ProGet which require IIS. 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.
The service looks in configuration to determine whether the integrated web server should be started.
Enabled
attribute to false
on the key WebServer
IntegratedWebServer.Enabled
to False
Enabled
attribute to false
on the key WebServer
IntegratedWebServer.Enabled
to False
Enabled
attribute to false
on the key WebServer
Before ProGet v5.1.0, the integrated web server's configuration was stored in the database.
UseIntegratedWebServer
key to False
You will need to uninstall the Integrated Web Server (IWS) for each product you are looking to migrate to IIS.
C:\Program Files\BuildMaster\Service
net stop inedobmwebsrv
bmservice UninstallWebServer
C:\Program Files\Otter\Service
net stop inedootterwebsrv
otter.service.exe UninstallWebServer
C:\Program Files\ProGet\Service
net stop inedoprogetwebsvc
proget.service.exe UninstallWebServer
You will need to setup a new Application Pool and WEb Site for each product in IIS.
To create a new Applicaiton Pool, you will need to perform the following steps.
BuildMaster
, ProGet
, or Otter
with the following minimum configuration:Example PowerShell command to create an app pool for ProGet:
&"C:\Windows\System32\inetsrv\appcmd.exe" add apppool /name:ProGet /managedRuntimeVersion:v4.0 /managedPipelineMode:Integrated /processModel.identityType:SpecificUser /processModel.userName:ProGetServiceUser@domain /processModel.password:<account-password>
Additional instructions for creating application pools can be found here: Create an Application Pool in IIS 7.x
To create a new Applicaiton Pool, you will need to create a new Website (virtual directories are not supported) named BuildMaster, ProGet, or Otter with the following minimum configuration:
C:\Program Files\[ProductName]\Web
)[ProductName]
)Note that any of these values can be edited once they are created, for example, to add SSL certificates, update the port that ProGet is listening on, etc.
Example PowerShell command to create a ProGet site:
&"C:\Windows\System32\inetsrv\appcmd.exe" add site /name:ProGet /physicalPath:"C:\Program Files\ProGet\Web" /bindings:"http/*:80:" /applicationDefaults.applicationPool:ProGet
You may adjust other IIS site settings as desired.
Your product will now be hosted through IIS. The products aren't very particular about how they are hosted as long as the prerequisite roles & features are installed, so virtually any of the settings within the IIS Application or Application Pool can be changed to suit your needs.
Is this documentation incorrect or incomplete? Help us by contributing!
This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.