Update Rollup 7.1 for Windows Azure Pack

View products that this article applies to.

Introduction

This article describes the issues that are fixed in Update Rollup 7.1 for Windows Azure Pack. It also contains the installation instructions for Update Rollup 7.1 for Windows Azure Pack.

↑ Back to the top

Issues that are fixed in this update rollup

Windows Azure Pack

Issue 1

If you download the Guardian Key to create virtual machine shielding data, the downloaded content will be invalid.

Note The shielding data feature is applicable only when you use it together with Windows Server Technical Preview.

Issue 2

When you change the Scale control for a website from Small to Large, the Admin or the Tenant portal can successfully run more requests without generating errors. But after you refresh the website, the scale reverts to its original setting of Small.

Issue 3

When you update any setting on the Websites configuration tab in the Admin Portal, this enables the disabled configuration sections.

↑ Back to the top

How to get and install Update Rollup 7.1 for Windows Azure Pack

Download information

Update packages for Windows Azure Pack are available from Microsoft Update or by manual download.

Microsoft Update

To get and install an update package from Microsoft Update, follow these steps on a computer that has a Windows Azure Pack component installed:

Click Start, and then click Control Panel.
In Control Panel, double-click Windows Update.
In the Windows Update window, click Check Online for updates from Microsoft Update.
Click Important updates are available.
Select the Update Rollup package, and then select OK.
Click Install updates to install the update package.

Microsoft Update Catalog

Go to the following website to manually download the update packages from the Microsoft Update Catalog:

Download the Windows Azure Pack update package now.

↑ Back to the top

Installation instructions

The installation instructions in this update rollup are for the following Windows Azure Pack components:

Tenant site
Tenant API
Tenant Public API
Administrator site
Administrator 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:

If the system is currently operational (handling customer traffic), schedule downtime for the Azure Pack servers. The Windows Azure Pack currently doesn't support rolling upgrades.
Stop or redirect customer traffic to sites that you consider satisfactory.
Create backup images of the web servers and the SQL Server databases.

Notes
- If you're using virtual machines, take snapshots of their current state.
- If you're not using VMs, take a backup of each MgmtSvc-* folder in the Inetpub directory on each machine that has a WAP component installed.
- Collect information and files that are related to your certificates, host headers, and any port changes.
If you're using your own theme for the Windows Azure Pack Tenant site, follow these instructions to preserve your theme changes before you perform the update.
Perform the update by running each .msi file on the computer on which the corresponding component is running. For example, run the MgmtSvc-AdminAPI.msi on the computer that's running "MgmtSvc-AdminAPI" site in Internet Information Services (IIS).
For each node under Load Balancing, run the updates for components in the following order:
1. If you're using the original self-signed certificates that are installed by WAP, the update operation replaces them. You have to export the new certificate and import to the other nodes under Load Balancing. These certificates have a CN=MgmtSvc-* (Self-Signed) naming pattern.
2. Update Resource Provider (RP) services (SQL Server, My SQL, SPF/VMM, websites) as necessary. Make sure that the RP sites are running.
3. Update the Tenant API site, Public Tenant API, Administrator API nodes, and Administrator and Tenant authentication sites.
4. Update the Administrator and Tenant sites.
Scripts to get database versions and update databases installed by the MgmtSvc-PowerShellAPI.msi are stored in the following location:

C:\Program Files\Management Service\MgmtSvc-PowerShellAPI\Samples\Database
If all components are updated and functioning as expected, you can open the traffic to your updated nodes. Otherwise, see the "Rollback instructions" section.

Note If you're updating from an update rollup that's equal to or older than Update Rollup 5 for Windows Azure Pack, follow these instructions to update the WAP database.

↑ Back to the top

Files included in this update rollup

File name	Size	Version
MgmtSvc-AdminAPI.msi	4,366,336	3.27.8196.3
MgmtSvc-AdminSite.msi	17,825,792	3.27.8196.3
MgmtSvc-AuthSite.msi	12,181,504	3.27.8196.3
MgmtSvc-Bpa.msi	921,600	3.27.8196.3
MgmtSvc-ConfigSite.msi	8,044,544	3.27.8196.3
MgmtSvc-Monitoring.msi	4,521,984	3.27.8196.3
MgmtSvc-MySQL.msi	3,997,696	3.27.8196.3
MgmtSvc-PowerShellAPI.msi	3,883,008	3.27.8196.3
MgmtSvc-SQLServer.msi	4,321,280	3.27.8196.3
MgmtSvc-TenantAPI.msi	4,345,856	3.27.8196.3
MgmtSvc-TenantPublicAPI.msi	4,419,584	3.27.8196.3
MgmtSvc-TenantSite.msi	19,283,968	3.27.8196.3
MgmtSvc-Usage.msi	4,431,872	3.27.8196.3
MgmtSvc-WebAppGallery.msi	4,100,096	3.27.8196.3
MgmtSvc-WindowsAuthSite.msi	4,317,184	3.27.8196.3