Upgrade Azure DevOps Server Express
TFS 2015
Upgrading Azure DevOps Server Express is fairly simple, because Express installations are limited in size and to a single machine, and can't be configured for additional integrations such as reporting.
You can upgrade your express installation to a later version of Azure DevOps Server Express, or upgrade to a full Azure DevOps Server installation.
Prepare your environment
As with any upgrade, first check the system requirements to ensure that your current configuration is supported. For an Express deployment, check the OS. The upgrade process will attempt to upgrade SQL Express to the latest version, which typically requires the latest service pack of the currently installed version. The upgrade process itself tells you if any required component is missing.
Expect the best, prepare for the worst
For Azure DevOps Express installations, a pre-production upgrade isn't typically necessary, as these installations are used by only a small number of people. Even so, before starting the upgrade, you should take backups. The upgrade wizard provides access to a database backup tool which can do this for you if needed.
Upgrade to a newer Express version
To upgrade to a newer version, download and install that Azure DevOps Server Express version from the Download page. Install the software where you have the existing version installed. You will only need to make a couple of basic decisions. The installation remembers the settings from your previous installation.
As with all Azure DevOps configuration wizards, readiness checks will run to validate that your system is ready to configure. When you choose Configure your databases, your database will be upgraded.
Upgrade to a full Azure DevOps Server version
Upgrading an express installation to a full Azure DevOps Server version requires that you also upgrade from SQL Express to a SQL Server Standard or Enterprise edition.
The basic steps are:
Upgrade from SQL Express to SQL Server
Note
Make sure that you (1) enable the SQL Server Agent service in Windows Service Control Manager, and (2) provision the SQL Server Agent service account by using SQL Server Configuration Manager.