Upgrade System Center Service Provider Foundation

You must have System Center - Service Provider Foundation 1801 installed to apply the 2019 update.

Upgrade to System Center 2019 - Service Provider Foundation

The following sections describe the procedures required to upgrade from SPF 2016/1801/1807 to SPF 2019.

Prerequisites

  • SPF:
  • VMM:
  • Windows Azure Pack - Install update rollup 12, or later.
  • VMM management console - The machine running the VMM 2016/1801/1807 management console should have the latest VMM updates installed.

Assumptions

The upgrade instructions in this article assume the following scenario:

  • SPF and VMM are running on System Center 2016/1801/1807
  • 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 2019 upgrade has already been completed, and that the necessary backups of the current Windows Azure Pack environment have been performed.

Upgrade order

Here's the recommended upgrade order for the above scenario:

  1. Update the VMM console to 2019. If required, update the VMM server to 2019.
  2. Update SPF to 2019.

Before you start

  1. Make sure Windows Azure Pack, SPF, and VMM are all running the required updates.
  2. We recommend that you shut down VMM and Windows Azure Pack servers, removing all database activity.
  3. Verify SPF system requirements. Note that SPF must run on Windows Server 2016/2019 - Core or Desktop experience.
  4. Verify VMM console requirements.

Run the SPF upgrade

Prepare the SPF 2019 computer on which you want to run the upgrade.

  1. Create a new server running Windows Server 2019, on which you want to install SPF 2019. You can also use a Virtual Machine (VM).
  2. In our example, we'll create a machine call SERVER-SPF-UPGRADE.
  3. 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.
  4. Install the latest Windows updates on the VM.
  5. Restart the VM to make sure there are no pending reboots.

    Note

    Don't join the VM to a domain.

Remove SPF 2016/1801/1807

  1. Uninstall the VMM admin console on the SPF machine.
  2. Uninstall the SPF Web Component on the SPF machine.
  3. Rename the machine. For example, from SERVER-SPF-01 to SERVER-SPF-OLD.

Set up the SPF 2019 computer

  1. Rename the VM you set up. Use the original name of the SPF computer. So change the VM name from SERVER-SPF-UPGRADE to SERVER-SPF-01.
  2. Join the VM to the domain.
  3. 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.
  4. Install SPF 2019, using the existing SQL Server database name during setup.

Post-upgrade tasks

  1. 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.
  2. 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:

  1. Start VMM 2019.
  2. 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.
  3. 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.

You must have System Center - Service Provider Foundation 1801 installed to apply the 1807 update.

This article provides the upgrade information for System Center 1801 - Service Provider Foundation (SPF).

Upgrade to System Center 1801 - Service Provider Foundation

The following sections describe the procedures required to upgrade from System Center 2012 R2 SPF or System Center 2016 SPF to SPF 1801.

Prerequisites

  • SPF:
    • On System Center 2012 R2 install update rollup 12 or later, in order to upgrade to 1801.
    • On System Center 2016 install update rollup 2 or later, in order to upgrade to 1801.
  • VMM:
    • On System Center 2012 R2 install update rollup 12 or later, in order to upgrade to 1801.
    • On System Center 2016 install update rollup 2 or later, in order to upgrade to 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.

Assumptions

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.

Upgrade order

Here's the recommended upgrade order for the above scenario:

  1. Update the VMM console to 1801. If required, update the VMM server to 1801.
  2. Update SPF to 1801.

Before you start

  1. Make sure Windows Azure Pack, SPF, and VMM are all running the required updates.
  2. We recommend that you shut down VMM and Windows Azure Pack servers, removing all database activity.
  3. Verify SPF system requirements. Note that SPF must run on Windows Server 2016 - Core or Desktop experience.
  4. Verify VMM console requirements.

Run the SPF upgrade

Prepare the SPF 1801 machine

  1. 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.
  2. 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.
  3. Install the latest Windows updates on the VM.
  4. Restart the VM to make sure there are no pending reboots.
  5. Don't join the VM to a domain.

Remove SPF 2012 R2/2016

  1. Uninstall the VMM admin console on the SPF machine.
  2. Uninstall the SPF Web Component on the SPF machine.
  3. Rename the machine. For example, from SERVER-SPF-01 to SERVER-SPF-OLD.

Set up the SPF 1801 machine

  1. Rename the VM you set up to the original name of the SPF machine, so from SERVER-SPF-UPGRADE to SERVER-SPF-01.
  2. Join the VM to the domain.
  3. 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.
  4. Install SPF 2016, using the existing SQL Server database name during setup.

Post-upgrade tasks

  1. 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.
  2. 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:

  1. Start VMM 1801.
  2. 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.
  3. 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.

This article provides the upgrade information for System Center 2016 - Service Provider Foundation (SPF).

Upgrade to System Center 2016 - Service Provider Foundation

The following sections provide information about how to upgrade from System Center 2012 R2 SPF to SPF 2016.

Prerequisites

  • SPF 2016 requires Windows Server 2016.
  • SPF should be running update rollup 9 or later, in order to upgrade to 2016.
  • The VMM server should be running update rollup 9 or later, in order to upgrade to 2016.
  • The VMM console machine should be running update rollup 9 or later, in order to upgrade to 2016.
  • Windows Azure Pack should be running on Windows Server 2012 R2 with at least update rollup 10.

Assumptions

The upgrade instructions in this article assume the following scenario:

  • SPF and VMM are running on System Center 2012 R2.
  • 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 2016 upgrade has already been completed, and that the necessary backups of the current Windows Azure Pack environment have been performed.

Upgrade order

Here's the recommended upgrade order for the above scenario

  1. Update the VMM console to 2016. We're presuming you've already updated the VMM server to 2016. Read this article if you haven't.
  2. Update SPF to 2016.

Before you start

  1. Make sure Windows Azure Pack, SPF, and VMM are all running the required updates.
  2. We recommend that you shut down VMM and Windows Azure Pack servers, removing all database activity.
  3. Verify SPF system requirements. Note that SPF must run on Windows Server 2016 - Core or Desktop experience.
  4. Verify VMM console requirements.

Run the SPF upgrade

Prepare the SPF 2016 machine

  1. Create a new server running Windows Server 2016, on which to install SPF 2016. You can use a VM. In our example, we'll create a machine call SERVER-SPF-UPGRADE.
  2. 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.
  3. Install the latest Windows updates on the VM.
  4. Restart the VM to make sure there are no pending reboots.
  5. Don't join the VM to a domain.

Remove SPF 2012 R2

  1. Uninstall the VMM admin console on the SPF 2012 R2 machine.
  2. Uninstall the SPF Web Component on the SPF 2012 R2 machine.
  3. Rename the machine. For example, from SERVER-SPF-01 to SERVER-SPF-OLD.

Set up the SPF 2016 machine

  1. Rename the VM you set up to the original name of the SPF 2012 R2 machine, so from SERVER-SPF-UPGRADE to SERVER-SPF-01.
  2. Join the VM to the domain.
  3. 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.
  4. Install SPF 2016, using the existing SQL Server database name during setup.

Post-upgrade tasks

  1. On the SPF machine, install the latest update: update rollup 2 for SPF 2016
  2. 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:

  1. Start VMM 2016.
  2. In the Windows Azure Pack 2012 R2 Admin portal, check in this order: 1) VMs; 2) Gallery items; 3) Templates; 4) SPF configuration settings. Make sure everything's working as expected.
  3. In the Windows Azure Pack 2012 R2 Tenant portal, check in this order: 1) Deployment settings; 2) VMs; 3) Plans; 4) Deployment options. Make sure everything's working as expected.

Next steps

Manage SPF