Update Rollup 7.1 for Windows Azure Pack
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.
Issues that are fixed in this update rollup
Windows Azure Pack
Issue 1If 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 2When 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 3When you update any setting on the Websites configuration tab in the Admin Portal, this enables the disabled configuration sections.
How to get and install Update Rollup 7.1 for Windows Azure Pack
Download informationUpdate packages for Windows Azure Pack are available from Microsoft Update or by manual download.
Microsoft UpdateTo 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 CatalogGo to the following website to manually download the update packages from the Microsoft Update Catalog:
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
- Windows Authentication
- Microsoft SQL
- Web Application Gallery
- Configuration site
- Best Practices Analyzer
- PowerShell API
- 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.
- 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:
- 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.
- Update Resource Provider (RP) services (SQL Server, My SQL, SPF/VMM, websites) as necessary. Make sure that the RP sites are running.
- Update the Tenant API site, Public Tenant API, Administrator API nodes, and Administrator and Tenant authentication sites.
- 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.
If an issue occurs and you verify that a rollback is necessary, follow these steps:
- If snapshots are available from the second note in step 3 in the "Installation instructions" section, apply the snapshots. If there are no snapshots, go to the next step.
- Use the backup that was taken in the first and third note in step 3 in the "Installation instructions" section to restore your databases and computers.
Note Don't leave the system in a partly updated state. Perform rollback operations on all computers on which Windows Azure Pack was installed, even if the update failed on one node.
Recommended Run the Windows Azure Pack Best Practice Analyzer on each Windows Azure Pack node to make sure that configuration items are correct.
- Open the traffic to your restored nodes.
Files included in this update rollup
Article ID: 3091399 - Last Review: 09/15/2015 00:29:00 - Revision: 2.0
Windows Azure Pack
- kbqfe kbsurveynew kbfix atdownload kbexpertiseadvanced KB3091399