Upgrading Windows Cells

This topic describes how to upgrade the PCF Runtime for Windows tile and update the Windows stemcell.

Upgrade PCF Runtime for Windows

The latest versions of your existing products appear in the Ops Manager Installation Dashboard. Upgrade your product to the latest version by following these instructions.

  1. Navigate to the Ops Manager Installation Dashboard.

  2. Click on the green download icon on the left-hand side of the screen to locate and download the product version to which you want to upgrade.

  3. When the download completes, click Apply Changes.

  4. If necessary, configure the product. For more information about configuring PCF Runtime for Windows, see the Deploying PCF Runtime for Windows topic.

  5. Locate the Pending Changes section on the right-hand side of the screen and click Apply Changes.

Upgrade the Windows Stemcell

  1. Navigate to the Ops Manager Installation Dashboard.

  2. Retrieve the stemcell by following the steps below for your IaaS:

  3. Click the PCF Runtime for Windows tile.

  4. Within the Settings tab, click Stemcell on the left-hand navigation.

  5. Click Import Stemcell.

  6. Select the previously acquired stemcell and click Open.

  7. Click Installation Dashboard to navigate back to the Ops Manager Installation Dashboard.

  8. Click Apply Changes.

Upgrade Windows Apps

Consult the following list of scenarios for instructions about upgrading your apps.

  • If your .NET app was previously pushed with the binary_buildback and you are relying on the WebAppServer.exe you must push with the hwc_buildpack:

    $ cf push APP-NAME -s windows2012R2 -b hwc_buildpack

    By passing windows2012R2 with the -s flag, you instruct PCF to run the app in the Windows cell. If you are not pushing your app from its directory, add the -p flag to specify the path to the directory that contains the app.

    An app with the hwc_buildpack should not be pushed with the -c flag.

    If you try to cf restage, your app will fail to restage because you cannot switch to the hwc_buildpack using cf restage.

  • If you have a binary app you must push with the -c flag:

    $ cf push APP-NAME -s windows2012R2 -b binary_buildpack -c PATH-TO-BINARY
    
  • If your app needs a custom start command and requires the WebAppServer.exe, you must update the start command to reflect the path to hwc.exe, which is provided by the HWC buildpack.

Create a pull request or raise an issue on the source for this page in GitHub