Introduction
This article describes the issues that are fixed in Update Rollup 11 for Windows Azure Pack (WAP). This article also contains the installation instructions for this update rollup.
Issues that are fixed in this update rollup
-
Issue 1When you create virtual machines (VMs), tenants can select a Virtual Network to associate to the VMs but then can't associate the VMs to a subnet available in the Virtual Network. With this update and Update Rollup 11 for System Center 2012 R2 Orchestrator - Service Provider Foundation installed, tenants can select the combination of Virtual Network and associated subnets.
-
Issue 2Tenants can't add Domain Groups to the Co-administrators dialog box if the name contains a space. The dialog box for "ADD CO-ADMINISTRATOR" doesn't let the user enter a name that includes a space. With this update, tenants can enter a Domain Group Name that includes spaces.
-
Issue 3Tenants can't see the virtual machine creation time through the Tenant Portal. This update provides that information in the VM's Quick Glance section and as a new column in the main VM list.
-
Issue 4Tenants can't use administrator names that contain a period (.) character when they create an SQL database. This update resolves that issue.
-
Issue 5Tenants can't sign up in Spanish or other languages through the default .NET Membership Authentication site. This update resolves that issue.
How to obtain and install Update Rollup 11 for Windows Azure Pack
Download information
Update packages for Windows Azure Pack are available from Microsoft Update or by manual download.
Microsoft Update
To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an applicable component installed:
-
Click the Start button, 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 Optionalupdates are available.
-
Select the Update Rollup package, and then click OK.
-
Click Install updates to install the update package.
Manual download of the update packages
Go to the following website to manually download the update packages from the Microsoft Update Catalog:
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 component, follow these steps:
-
If the system is currently operational (handling customer traffic), schedule downtime for the Azure servers. The Windows Azure Pack doesn't currently support rolling upgrades.
-
Stop or redirect customer traffic to alternative sites that you consider satisfactory.
-
Create backups of the computers.Notes
-
If you're using virtual machines, take snapshots of their current state.
-
If you're not using virtual machines, take a backup of each MgmtSvc-* folder inside the Inetpub directory on each machine that has a WAP component installed.
-
Collect information and files related to your certificates, host headers, and any port changes.
-
-
If you're using your own theme for the Windows Azure Pack Tenant site, see How to Persist a Windows Azure Pack Theme after Microsoft Upgrade 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 MgmtSvc-AdminAPI.msi on the computer that is running the "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 installed by WAP, the update operation will replace them. You have to export the new certificate and import it 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 needed. And 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 obtain 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\DatabaseIf all components are updated and functioning as expected, you can open the traffic to your updated nodes. Otherwise, see the "Rollback instructions" section, below.Note If you're updating from an update rollup that is the same as or earlier than Update Rollup 5 for Windows Azure Pack, follow these instructions to update the WAP database.
-
If a problem occurs and you determine that a rollback is necessary, follow these steps:
-
If snapshots are available as described in the second note in step 3 of the "Installation instructions" section, above, apply the snapshots. If there are no snapshots, go to the next step.
-
Use the backup that was taken as described in the first and third notes in step 3 on 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 where Windows Azure Pack was installed, even if the update failed on only one node.We recommend that you 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.
