This article describes how to upgrade from System Center 2012 R2 – Service Provider Foundation (SPF) or System Center 2016 SPF, to SPF 1801.
- Windows Azure Pack – Install update rollup 12, or later.
- VMM management console – The machine running the VMM 2012 R2 or 2016 management console should have the latest VMM updates installed.
The upgrade instructions in this article assume the following scenario:
- SPF and VMM are running on System Center 2016
- We highly recommend that you reuse the current SPF server name to simplify the seamless integration into your existing Windows Azure Pack deployment.
- The VMM console is installed on a separate computer.
- The upgrade uses the existing SPF server name.
- These upgrade instructions assume that the VMM 1810 upgrade has already been completed, and that the necessary backups of the current Windows Azure Pack environment have been performed.
Here’s the recommended upgrade order for the above scenario:
- Update the VMM console to 1801. If required, update the VMM server to 1801.
- Update SPF to 1801.
Before you start
- Make sure Windows Azure Pack, SPF, and VMM are all running the required updates.
- We recommend that you shut down VMM and Windows Azure Pack servers, removing all database activity.
- Verify SPF system requirements. Note that SPF must run on Windows Server 2016 – Core or Desktop experience.
- Verify VMM console requirements.
Run the SPF upgrade
Prepare the SPF 1801 machine
- Create a new server running Windows Server 2016, on which to install SPF 1801. You can use a VM. In our example, we’ll create a machine call SERVER-SPF-UPGRADE.
- Install the prerequisites on the new VM, as follows:
- Install SQL ODBC Drivers.
- Install SQL Native Client
- Install SQL Server command line utilities.
- Install SQL Server CLR types.
- Install IIS with the following features: PowerShell: Install-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Http-Tracing, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Basic-Auth, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Scripting-Tools, NET-Framework-45-ASPNET, NET-WCF-HTTP-Activation45, ManagementOdata, WAS, WAS-Process-Model, WAS-Config-APIs.
- Install WCF Data Services 5.0 for OData V3.
- Install ASP.NET MVC 4.
- Install the latest Windows updates on the VM.
- Restart the VM to make sure there are no pending reboots.
- Don’t join the VM to a domain.
Remove SPF 2012 R2/2016
- Uninstall the VMM admin console on the SPF machine.
- Uninstall the SPF Web Component on the SPF machine.
- Rename the machine. For example, from SERVER-SPF-01 to SERVER-SPF-OLD.
Set up the SPF 1801 machine
- Rename the VM you set up to the original name of the SPF machine, so from SERVER-SPF-UPGRADE to SERVER-SPF-01.
- Join the VM to the domain.
- Install the VMM console.For a core installation you can install from the command line, or set up from the user interface and change to Core later.
- Install SPF 2016, using the existing SQL Server database name during setup.
- SPF needs a server certificate for website binding. You can use the self-signed certificate generated during setup, but we don’t recommend this for a production environment.
- If you do use a self-signed certificate:
- It should be used only for testing purposes.
- The FQDN should be specified for the certification path instead of “localhost”.
- It should be located in the personal or webhosting store.
Test Windows Azure Pack
Test everything’s working as follows:
- Start VMM 1801.
- In the Windows Azure Pack Admin portal, check in this order: 1) VMs; 2) Gallery items; 3) Templates; 4) SPF configuration settings. Make sure everything’s working as expected.
- In the Windows Azure Pack Tenant portal, check in this order: 1) Deployment settings; 2) VMs; 3) Plans; 4) Deployment options. Make sure everything’s working as expected.