Upgrade from the Preview version of Windows Azure Pack

 

Applies To: Windows Azure Pack

Note

This topic is not applicable to most customers as the preview version is no longer available.

If you want to upgrade your express or distributed deployment from the preview version to the new version, follow these steps:

To upgrade from preview to Windows Server version of Windows Azure Pack

  1. On each machine running a Windows Azure Pack component, stop all sites and IIS services.

  2. To enable rollback in case of problems during the upgrade, back up all sites, virtual machines, and databases. The upgrade process does not automatically back up the current running versions of Windows Azure Pack components.

  3. If you have created a custom theme for your tenant portal, follow these steps:

    1. Create a new folder named app_CustomTheme on the tenant machine:

      C:\inetpub\MgmtSvc-TenantSite\app_CustomTheme

    2. On the tenant machine, copy the content folder from the custom theming kit to C:\inetpub\MgmtSvc-TenantSite\app_CustomTheme

  4. Locate and record the connection string information for the existing preview databases along with the current passphrase. Without this information, the upgrade will install a new installation instead of upgrading the previous version.

  5. Using Windows Platform Installer, install the latest version of Windows Azure Pack components.

    If you are upgrading an express deployment, you can install the upgrade on the machine hosting your express deployment as explained in Install an express deployment of Windows Azure Pack. During configuration, be sure to use the existing preview database and current passphrase.

    If you are upgrading a distributed deployment, you must install the appropriate components on each machine in your deployment. Follow the instructions in Install a distributed deployment of Windows Azure Pack. During configuration, be sure to use the existing preview database and current passphrase.

  6. The upgrade will automatically update your deployment to the new version, keeping your user, plan, and account data intact, with the following exceptions.

    • All tenant passwords must be reset.

    • The upgrade process resets IIS settings (including custom ports and host headers) of the portal and API machines to their default values. If you want to use non-default values you must manually reset them.

    • The upgrade process resets firewalls to default settings. If you want to use non-default firewall rules you must manually add them for tenant and API endpoints.

Next steps