ProGet Documentation

ProGet Manual Installation Guide

  • Last Modified: 2020-11-16

Table of Contents

ProGet Software Components

On Windows, ProGet consists of 3 distinct deployable application components required to run the software:

  • Website - an ASP.NET 4.5 web application which serves as the primary interface to ProGet via a web UI and feed API implementations
  • Service - a Windows Service that performs indexing and other background tasks
  • Database - a SQL Server database which contains all of the persistent data including feeds, packages, privileges, and internal settings


Pre-Installation Check List

These are the same as the ProGet Installation Guide.

Get the Manual Installation Package

The manual installation package is a .zip file that contains all the files and scripts necessary to create or upgrade the deployable components listed above.

To download the package, select "Manual Install" link for the desired version from the following URL: If you are unsure which version to select, use the latest version.

The manual installation package contains the following:

  • Extensions directory - contains the default extensions shipped with the selected version of ProGet
  • Service directory - contains the files and binaries required to run the ProGet Windows Service
  • SqlScripts directory - contains the SQL scripts required to generate the SQL Server database, or update an existing one to the schema required for the downloaded version
  • Website directory - contains the files and binaries required to run the Website application

Note that, in earlier versions of ProGet, the directory names may be different or may be .zip files instead of directories. Regardless of the structure, the process has remained the same since ProGet v4.

Installation Directories

By default, the ProGet installer allows configuration of its root installation directory, and will configure temporary directories and package storage paths for you. During a manual installation, these directories must be provisioned prior to installation.

Before configuring the necessary paths, you should decide where the following base directories will reside:

DirectoryDescriptionInstaller Default
Root installation directorythe root disk path for the Website and Service binaries, and extensionsC:\Program Files\ProGet
Program data directorythe root disk path for package storage, temporary directories, and the configuration fileC:\ProgramData\ProGet

Though not strictly required until later, you may also want to ensure the existence of the following directories if you would like to use the installer defaults:

  • C:\ProgramData\ProGet\Extensions
  • C:\ProgramData\ProGet\ExtensionsTemp\Service
  • C:\ProgramData\ProGet\ExtensionsTemp\Web
  • C:\ProgramData\ProGet\Packages
  • C:\ProgramData\Inedo\SharedConfig
  • C:\Program Files\ProGet\Extensions

If you plan to use other paths (i.e. UNC shares) for certain storage paths like "packages root path", you may proceed without creating the directories before they are configured in the software.

Database Installation (SQL Server)

ProGet is compatible with existing supported SQL Server installations, local or remote, and also with SQL Azure. Examples here will use osql as the tool to execute sample queries (since it is installed with SQL Server), but you can also use sqlcmd or SQL Server Management Studio directly.

SQL Server Recommendations:

  • Use the latest version of SQL Server available (but it must be at least 2012 SP4)
  • ProGet does support SQL Server Express, but we recommend using an existing SQL Server Standard Edition (or higher) if you are licensed for it
  • If you've installed a new SQL Server instance, note whether a named or default instance is used, as it will be required for the connection string information (e.g. Server=dbserver01\SQLEXPRESS; ... vs. Server=dbserver01; ...). SQL Server Express defaults to SQLEXPRESS as the instance name
  • For single-server installations (i.e. non-HA/LB), you may have the database server running on the same server that ProGet is installed on (i.e. the connection string would be Server=localhost; ... or Server=localhost\SQLEXPRESS; ...)
  • For manual upgrades from a previous version installed via the ProGet installer, the instance name might be INEDO, and older versions (v3 and earlier) would have used the instance name PROGET


ProGet requires an existing SQL Server database server, so if you don't already have a database server, you'll need to create one. We recommend installing and configuring the latest version of SQL Server Express for this purpose:

This should mostly be a guided process, but consider:

  • Integrated Windows Authentication is the recommended authentication mechanism (i.e. using a domain account as opposed to supplying a username/password in the connection string)
  • Make sure to add your account (or a group that will represent ProGet database administrators) when prompted to "Specify SQL Server Administrators" during "Database Engine Configuration" step so that no additional steps are required to create/manage the ProGet database
  • Be aware of the SQL Server instance name as it is part of the Server value in the connection string

1. Create a database named ProGet on the desired SQL Server instance

Technically speaking, the database doesn't need to be named ProGet, but for simplicity of both upgrades and configuration, we recommend ProGet as the database name. The database collation however must be SQL_Latin1_General_CP1_CI_AS to ensure case-insensitivity in default text comparisons.

osql -E -S <db-server> -Q "CREATE DATABASE [ProGet] COLLATE SQL_Latin1_General_CP1_CI_AS"

2. Create a database server login

Since most installations will use Integrated Authentication, a database server login for the ProGet user identity is required. If it doesn't exist, one can be created using this script:

osql -E -S <db-server> -Q "CREATE LOGIN [domain\ProGetServiceUser] FROM WINDOWS"

Note that built-in accounts may be used, such as NT AUTHORITY\NETWORK SERVICE or NT AUTHORITY\LOCAL SYSTEM, though an actual domain account is recommended.

For more information on creating database logins, see:

3. Run inedosql to update the database

What is inedosql?

inedosql is a open-source command-line tool developed by Inedo in order to execute SQL (.sql) scripts against a SQL Server database. Scripts with AH:ScriptId headers specify a globally unique GUID to a specific script that is added to an implementation-defined metadata table (typically named similar to __InedoDb_DbSchemaChanges) when the script is run so it only gets run once no matter how many times the update command is run. SQL scripts without this header are executed every time the command is run. All scripts are run in the order they are defined on disk, i.e. lexicographically. See the inedosql GitHub page for more information.

Database Update Process

  1. Copy the SqlScripts directory into a temporary directory.

  2. Run command line and change current directory to the SqlScripts folder which contains inedosql.exe file.

  3. Run the following command in that directory, replacing the connection string as needed:

.\inedosql.exe update . --connection-string=<connection-string>

For example:

cd C:\ProGetSetup5..14_Manual\
.\inedosql.exe update . --connection-string="Server=dbserver01\SQLEXPRESS; Database=ProGet; Integrated Security=true;"

This command will both update the schema of the target database, and recreate all objects (views, functions, stored procedures).

On new installations, be sure to note the connection string that was used for this command, as it be a required value in the configuration file that instructs ProGet which database to connect to.

ProGet 5.2 and earlier

In ProGet 5.2 and earlier, dbupdater.exe is used to update the database. Use these instructions for updating the database:

  1. Copy the SqlScripts directory into a temporary directory.

  2. Run command line and change current directory to the SqlScripts folder which contains dbupdater.exe file.

  3. Unpack required scripts from Scripts.gz with the following command:

.\dbupdater.exe unpack .\Scripts.gz .
  1. After the required folders/files are extracted, stay in the same directory and run the following command in that directory, replacing the connection string as needed:
.\dbupdater.exe update . <connection-string>

For example:

cd C:\ProGetSetup5.2.14_Manual\
.\dbupdater.exe unpack .\Scripts.gz .
.\dbupdater.exe update . "Server=dbserver01\SQLEXPRESS; Database=ProGet; Integrated Security=true;"

4. Create a database user and grant access to ProGet database role

In order for the database server login to access the database with the permissions required by ProGet, a database user must be created:

osql -E -S <db-server> -d ProGet -Q "CREATE USER [domain\ProGetServiceUser] FOR LOGIN [domain\ProGetServiceUser]"

Then the user must be granted access to the ProGet user role (which was added during the "run dbupdater.exe" step):

osql -E -S <db-server> -d ProGet -Q "ALTER ROLE [ProGetUser_Role] ADD MEMBER [domain\ProGetServiceUser]"

Website Installation (IIS)


Before installing ProGet in IIS, the following roles/features must be enabled in Windows:

Server Roles

  • Web Server (IIS) > Web Server > Security > Windows Authentication (if planning to configure Integrated Windows Authentication in the future)
  • Web Server (IIS) > Web Server > Application Development > .NET Extensibility 4.6 (or greater)
  • Web Server (IIS) > Web Server > Application Development > ASP.NET 4.6 (or greater)
  • Web Server (IIS) > Web Server > Common HTTP Features > Static Content
  • Web Server (IIS) > Management Tools > IIS Management Console


  • .NET Framework 4.6 Features > .NET Framework 4.6
  • .NET Framework 4.6 Features > ASP.NET 4.6

1. Copy Website files

Copy the contents of Web directory from the installation package to a subdirectory of the root installation directory identified earlier. For reference, the installer defaults this to: C:\Program Files\ProGet\Web

2. Create an application pool in IIS

While you could use an existing application pool if desired, we recommend creating a new one. The minimum requirements for the application pool are:

  • .NET CLR Version - 4.0
  • Managed Pipeline Mode - Integrated is recommended, but Classic will also work

Example PowerShell command to create an app pool:

&"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>

You may adjust other application pool settings as desired.

3. Create a site in IIS

The minimum requirements for the IIS web site are:

  • Physical Path - the path on disk where the ProGet Website files were copied to in step 1
  • Application Pool - the application pool to use, created in step 2
  • Binding - the combination of IP address(es) and port(s) used to access ProGet over the network

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 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.

Service (Windows Service)

1. Copy service files

Copy the contents of Service directory from the installation package to a subdirectory of the root installation directory identified earlier. For reference, the installer defaults this to: C:\Program Files\ProGet\Service

2. Install the service

The copied service files will contain the service executable ProGet.Service.exe; run this program from an elevated command prompt or PowerShell window to install the Windows Service (INEDOPROGETSVC):

PS C:\Program Files\ProGet\Service> .\ProGet.Service.exe install --user="ProGetServiceUser@domain" --password="<account-password>"

Note: at this time, it is not permitted to change the service name from INEDOPROGETSVC.

3. Start the service

The service can be started from the Windows Service Controller, or using the following PowerShell command:


First Run

Once the Website and Service are started, ProGet should be accessible via the binding specified in IIS site step 3. The first time you access ProGet via the Website, some additional settings must be configured.

1. Ensure the ProGet configuration file exists with valid values

Once the Website, Service, and Database are configured, the final step is to create or update the ProGet Configuration File to supply the database connection string noted earlier in step 3 of the database configuration, and ensure WebServer Enabled="false".

Once values in this file are changed, any IIS application pool or ProGet Windows Service that reference it must be restarted to see the new values.

2. Ensure the proper Advanced Configuration settings are set

Once you log-in to ProGet for the first time, you can visit the Administration > Advanced Settings page to finalize the configuration stored in the database.

The following settings within the product that must be configured, their corresponding directories, and their installer defaults are listed below:

SettingDescriptionInstaller Default
Extensions.BuiltInExtensionsPathpath containing extensions included with the installation packageC:\Program Files\ProGet\Extensions
Extensions.ExtensionsPaththe disk path where downloaded extensions are stored and loaded from by ProGetC:\ProgramData\ProGet\Extensions
Extensions.UseNewExtensionLoaderwhen set, uses CommonCachePath instead of ServiceTempPath and WebTempPath for Extensionstrue (checked)
Extensions.CommonCachePathused only when UseNewExtensionLoader is true, a temp path where extensions loaded from ExtensionsPath are extracted to and loaded by the ProGet serviceC:\ProgramData\ProGet\ExtensionsCache
Extensions.ServiceTempPathused only when UseNewExtensionLoader is false, a temp path where extensions loaded from the extensions path are extracted to and loaded by the ProGet serviceC:\ProgramData\ProGet\ExtensionsTemp\Service
Extensions.WebTempPathused only when UseNewExtensionLoader is false, a temp path where extensions loaded from the extensions path are extracted to and loaded by the ProGet WebsiteC:\ProgramData\ProGet\ExtensionsTemp\Web
Extensions.UpdateFeedUrlthe extensions feed URL, required to browse extensions in the software
Storage.PackagesRootPathbase path on disk for ProGet's default package storeC:\ProgramData\ProGet\Packages (more info)

The directories referenced in the configuration values must exist prior to beginning use of ProGet as a package manager - ProGet does not create them for you. If they do not exist, several extensions-related errors will be logged in the Diagnostic Center, and/or packages may be stored on disk in an undefined manner. If the directories did not exist but ProGet was already started, both the IIS application pool and Windows Service must be restarted.

Each of these directories can assigned to a path on a local volume or UNC share provided that:

  • the user account specified as the "log on user" for the Windows Service has read/write/delete access to them
  • the user account specified as the "application pool identity" in IIS has read/write/delete access to them

We do not recommend using a mapped drive (e.g. X:\Packages) to reference directories for the reasons described here: Instead, use the full UNC path that the drive is mapped to, for example: \\file-sv01\$x\packages

If you do attempt to use a mapped drive (or you are installing on Azure using Azure Files as the backing store), you may need to configure the ProGet application pool to set the Load User Profile property to True.

Packages Root Path

The Storage.PackagesRootPath setting defines the base storage location on disk for packages managed by ProGet's default package store. Its value is stored in the database and assignable on the Advanced Settings page.

There are several other packages path settings (e.g. Storage.NpmPackagesLibrary, Storage.MavenArtifactLibrary) that by default are relative to the Storage.PackagesRootPath. If one of these settings is individually set, it will override the default behavior of being relative to the root path. To restore that behavior, save the desired field with an empty value.

Note: Older load-balanced installations may have stored the ProGetConfig.Storage.PackagesRootPath storage location in a web application configuration file. This source of configuration will be removed in a future version of ProGet, replaced solely by the database setting. If you see the ProGetConfig.Storage.PackagesRootPath setting in an existing Web_appSettings.config, its value should be migrated to the Storage.PackagesRootPath setting in Administration > Advanced Settings. The database setting already takes precedence if it exists, so if there is an existing value for this setting on the Advanced Settings page, it can be removed from the configuration file.

3. Set license key and activate

All editions of ProGet require a valid license to use. Once the ProGet Website is accessible, you must visit the Administration > Licensing & Activation page to apply a license key. If ProGet is able to access the internet, the key will be automatically activated.

If you have already obtained a license key but cannot automatically activate, visit the License Key Activation documentation for more information on manual activation.

If you do not have a license key yet (or do not know what yours is), you may view keys associated with your organization or request one from MyInedo.


While extensions are available in our own public ProGet instance, the ProGet installation ships with "frozen" or "locked" versions of the extensions at the time the installer was built.

Once the Extensions.BuiltInExtensionsPath setting is configured to a valid directory, copy the contents of Extensions/ directory from the installation package into that directory, then restart the application pool and ProGet Windows Service. Any extensions in this path are combined with the extensions managed within the ProGet software (i.e. downloaded from the Administration > Extensions page and stored in the Extensions.ExtensionsPath directory), and the "latest" SDK-compatible version (as per semantic versioning rules) is loaded.

Manual Extension Installation

For installations that are restricted from accessing the internet, or if you with to install a version other than the latest, extensions can also be installed manually:

  1. Download the desired version of the extension from the public ProGet feed
    Copy the extension file (e.g. Windows.upack) to the extensions path.
  2. Visit the Admin > Advanced Settings page within your ProGet instance to determine where extensions are stored by examining the Extensions.ExtensionsPath setting.
  3. Ensure the file is named <extension-name>.upack in the extensions directory, and that no other files with the same name exist in that directory, even with a different extension. For example, make sure to delete an existing <extension-name>.inedox file if you are installing <extension-name>.upack. The downloaded file may contain a version part, which should be removed (e.g. InedoCore-1.5.0.upack should be just InedoCore.upack)
  4. Restart the product's Windows service: Admin > Service > Stop then Start (e.g. INEDOBMSVC, INEDOPROGETSVC)
  5. Restart the product's Website application, either the IIS application pool: Admin > Service > Restart Web App
  6. Verify that the new extension has been loaded (Admin > Extensions)

Note: the InedoCore extension must be installed to use Active Directory integration.

Upgrading an Existing ProGet Installation

Upgrading a ProGet installation from an existing installation can be performed by following this installation guide, except it should be much simpler and quicker than the initial installation since the infrastructure is already in place.

This guide may also be used to upgrade an instance that was installed by the installer, but once that has occurred, this manual process must be used going forward.

1. Backup the existing instance

To backup the instance, refer to the Backup and Restoring ProGet documentation.

2. Stop services

Before upgrading ProGet, the existing instance must be taken offline. Ensure that the application pool and Windows Service are both stopped.

Here is an example PowerShell script that performs these operations:

&"C:\Windows\System32\inetsrv\appcmd.exe" stop apppool ProGet

3. Copy installation package contents

For the most part, an upgrade is an "XCOPY deployment" of files from the manual installation package. Copy all of the contents of each of the following into the specified target directory while carefully analyzing the differences in configuration files as noted:

ContentsTargetInstaller DefaultNotes
ServiceService installation directoryC:\Program Files\ProGet\ServiceMay overwrite existing App_appSettings.config if empty
WebWebsite application home directoryC:\Program Files\ProGet\WebMay overwrite existing Web_appSettings.config if empty
ExtensionsExtensions.BuiltInExtensionPath directoryC:\Program Files\ProGet\ExtensionsOverwrite contents with install package contents

While v5.1.0 and later versions of ProGet should not store data in these configuration files, existing installations might contain relevant data such as connection strings that should ultimately be migrated to the ProGet Configuration File and removed from the *_appSettings.config file.

4. Update database schema

Because the tool used to update the database schema is aware of previous scripts that have run, this process is the same as the initial installation process. See Running dbupdater.exe above to perform this step using the existing connection string specified in the ProGet Configuration File. An additional benefit of being aware of previous scripts that have run is that the dbupdater.exe command can be applied to a database copy or backup to test the SQL upgrade before running it against a production database.

5. Start services

Once all files are copied and the database is updated, the services can be started to bring ProGet back online.

Here is an example PowerShell script that performs these operations:

&"C:\Windows\System32\inetsrv\appcmd.exe" start apppool ProGet


There are a lot of moving pieces involved in a manual installation (particularly ones that the installer would have handled for you). Here are the most common manual installation errors as we have noted from our various support channels.

Cannot connect to the database

Perhaps the most common problem is that the SQL Server database is inaccessible. Check the following:

  • the user account connecting (i.e. the application pool identity or Windows Service logon user) have a database login, an associated database user, and that user is granted the ProGetUser_Role
  • the user account is a domain account when accessing a database over the network (i.e. don't use NETWORK SERVICE and connect to a remote database)
  • the connection string exists in the ProGet configuration file and is valid (i.e. has the correct server name, database name, and includes the instance name e.g. SQLEXPRESS)

Windows Service will not start

Typically when the ProGet Windows Service does not start, it is database connection-related. Any errors logged by the ProGet Service can be found in the Windows Event Log under Windows Logs > Application.

Alternatively, you can run the service interactively (i.e. in a command window) to view live log output. Simply ensure the INEDOPROGETSVC service is stopped, then run the following command as an administrator:

PS C:\Program Files\ProGet\Service> .\ProGet.Service.exe run --mode=serviceonly

If there is a difference in behavior when run interactively vs. running the service, there may be a problem with the user account that the ProGet service is running as.

Can't control the service from within ProGet

Visit the Service Messenger documentation for enabling inter-process communication between the ProGet Website and ProGet Service.

Extensions failing to load

Extensions failing to load is commonly caused by:

  • missing/invalid extensions path setting (check Administration > Advanced Settings)
  • the service not being restarted after the extension path is changed

Load errors for extensions are logged in the Diagnostic Center.

Additional help & support

Inedo offers several support mechanisms if you have any other questions regarding a manual installation:

Is this documentation incorrect or incomplete? Help us by contributing!

This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.

Generated from commit ffb6a807 on master