Description of Update 2 for Windows Azure Pack

Download information

This update can be downloaded from the Microsoft Update Catalog.

Installation instructions

These installation instructions are for the following Windows Azure Pack components:

• Tenant site

• Tenant API

• Tenant Public API

• Administration site

• Administration API

• Authentication

• Windows Authentication

• Usage

• Monitoring

• Microsoft SQL

• MySQL

• Web Application Gallery

• Configuration site

• Best Practices Analyzer

• PowerShell API

To install the update .msi files for each Windows Azure Pack (WAP) component, follow these steps:

1. If the system is currently operational (that is, if it is handling customer traffic), schedule downtime for the WAP systems. WAP currently does not support rolling upgrades.

2. Stop customer traffic, or redirect customer traffic to sites that you consider sufficient.

3. Create backups of the computers.
   
   Notes
   

   • This update does not include database changes. Therefore, backing up and restoring databases is not necessary. We recommend that you keep current database backups.

   • If you are using Virtual Machines (VMs), take snapshots of their current state. Otherwise, go to the next step.

   • If you are not using VMs, take a backup of each MgmtSvc-* folder in the inetpub directory on each computer that has a WAP component installed.

   • Also, collect information and files that are related to your certificates, host headers, or any port changes.

4. Important Make sure that you create a backup of the Windows Azure Pack Usage Extension Site and Application Pool settings before you perform the update. To this, follow these steps:

   1. On the computer that contains the Usage Collector, create a backup of the Usage Collector Site and Application Pool settings by running the following two appcmd commands:
      
      

      %systemroot%\system32\inetsrv\appcmd.exe set site MgmtSvc-UsageCollector /name:MgmtSvc-UsageCollector.backup
      
      %systemroot%\system32\inetsrv\appcmd.exe set config /section:applicationPools /[name='MgmtSvc-UsageCollector'].name:MgmtSvc-UsageCollector.backup
      

   2. The Update .msi process will use these backups to restore the settings for this site. This manual step is required because the corresponding site .msi for the release version and Update 1 releases did not include this step. After you install Update 2, the .msi file includes this step. Therefore, the next update will not require this manual step.

5. Perform the update by using Microsoft Update either directly on each node or through the Windows Server Update Services (WSUS) server.

6. For each node under Load Balancing, run the updates for components in the following order:

   1. Update Resource Provider (RP) services (SQL Server, My SQL, SPF/VMM, Web Sites) as needed. Make sure that the RP sites are running.

   2. Update the Tenant API site, Public Tenant API, and Admin API nodes.

   3. Update the Admin and Tenant sites.

7. If everything is updated and functioning as expected, you can open the traffic to your updated nodes. Otherwise, see the "Update rollback instructions" section.

Update rollback instructions

1. If an issue occurs and you decide that a rollback is necessary, follow these steps:

   1. If a snapshot is available from step 3a, apply snapshots. If there are no snapshots, go to the next step.

   2. Uninstall the update from Microsoft Update or Uninstall programs.

   3. Reinstall the release version bits from Web PI, and do not run the Config wizard. Reinstall the Update 1 bits from Windows Update if you have them to start with.

   4. Replace the following items from the backup folders to release version bits:
      
      

      • Content folder

      • Manifest folder

      • Web.Config file

   5. Apply any changes that are associated with your certificates, host headers, and port changes

2. Do not leave the system in a partly updated state. Perform rollback operations on all servers that have WAP installed, even if the update failed on one node.

3. Recommended Run the Windows Azure Pack Best Practice Analyzer on each WAP node to make sure that configuration items are correct.

4. You can now open the traffic to your updated nodes.