Update Rollup 9 for Windows Azure Pack

Introduction
This article describes the issues that are fixed in Update Rollup 9 for Windows Azure Pack. Additionally, this article contains the installation instructions for Update Rollup 9 for Windows Azure Pack.

Issues that are fixed in this update rollup

  • Issue 1: WAP administrators cannot change the tenant administrator of a subscription

    Symptom Tenants cannot be disassociated from their subscriptions that they have created and no longer need.

    Resolution WAP administrators can now assign any subscription to any other tenant making the target tenant the new owner (or tenant admin) of a subscription. You can do this by using a new Windows PowerShell cmdlet. Example:

    Update-MgmtSvcSubscriptionOwner-SubscriptionId fcd7a855-7aa4-495e-a41b-135ec3f2ca14 -NewOwner $newOwner -AdminUri $AdminSiteURL -Token $token -Verbose

    Note Calling this cmdlet triggers subscription update events. These events are sent to all registered Resource Providers and Billing adapters to let them to process the change as necessary.

  • Issue 2: WAP administrators cannot hide specific VHDs from the Tenant UI during VM Creation

    This behavior make sure that any VHD used by the WAP administrator for system administration or any other deployments outside the scope of WAP are seen by tenant users and can be selected by users when they are provisioning their virtual machines (VMs).

    Symptom Tenants can see and select VHDs that are not meant to be used to create tenant VMS. This always results in VM failure and bad user experiences.

    Resolution Administrators can tag specific VHDs in Microsoft Virtual Machine manager (VMM) by using the “WAPHIDDEN” tag. This causes the VHDs not to be listed in the tenant portal UI. This does not hide the VHDs from any other interface, such as PowerShell cmdlets and REST APIs.

  • Issue 3: Failure to send VM Role deletion event when a cloud service is deleted

    Symptom When the administrator deletes a cloud service, all the associated VM Roles are also deleted. However, the associated VM Role deletion event is not sent to listening runbooks.

    Resolution The VM Role deletion event is now sent as expected.

  • Issue 4: Several of the list controls that are displayed in the WAP Tenant Portal extension for VMs are out of order

    Symptom This problem is especially noticeable when you create VM roles. The user experience degrades when the number of items in these lists increases because the users can no longer locate and select items quickly.

    Resolution The following list controls are changed to sort the data items:

    • VM Role list and other dropdown lists when you provision a VM Role from the Gallery. (This includes Data Disks and Logical Network lists.)
    • When you attach a DVD device to a VM.

  • Issue 5: The Russian Time Zone updates is not applied to the WAP administrator and tenant portals

    Symptom Azure Pack portal displays the older time zones for Russia.

    Resolution The Russian time zones are updated to reflect the latest standard.

  • Issue 6: The Admin Portal Web Sites extension, the UI control to enter the memory limit for the website does not support an amount great enough to support x64 websites

    Symptom When you enter a memory amount, the limits are from 1 to 1,024 Megabytes.

    Resolution This field now accepts large values that address the needs of x64 websites.

  • Issue 7: Usage Configuration items are overwritten by update rollups

    Symptom The Usage Configuration items are being overwritten by update rollups. That is, the configuration values in the Usage configuration table are not preserved by the updates.

    Resolution Values are now preserved.
How to obtain and install Update Rollup 9 for Windows Azure Pack

Download information

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

Windows Update

To obtain and install an update package from Windows Update, follow these steps on a computer that has Microsoft Systems Center 2012 R2 Operations Manager installed:

  1. Click Start and then click Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, click Check Online for updates from Microsoft Update.
  4. Click Important updates are available.
  5. Select the update rollup package, and then click OK.
  6. Click Install updates to install the update package.

Microsoft Update Catalog

The update packages are available for manual download and installation 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 (handling customer traffic), schedule downtime for the Azure servers. The Windows Azure Pack does not currently support rolling upgrades. 
  2. Stop or redirect customer traffic to sites that you consider satisfactory.
  3. Create backups of the computers.

    Notes

    • This update includes database changes. Therefore, you should back up your databases. In general, we recommend that you keep current database backups.
    • If you're using VMs, take snapshots of their current state.
    • If you're not using VM’s, back up each MgmtSvc-* folder that's inside the inetpub folder on each computer that has a WAP component installed.
    • Collect information and files that are related to your certificates, host headers, and any port changes.
  4. 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.
  5. 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 "MgmtSvc-AdminAPI" site in Internet Information Services (IIS).
  6. 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 will replace them. You have to export the new certificate and import it on the other nodes that are 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. Also, 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.
  7. Update the database to include a new stored procedure by using the provided script. You can find scripts to obtain database versions and update databases that are installed by the MgmtSvc-PowerShellAPI.msi in the following location:

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

Rollback instructions

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

  1. If snapshots are available from step 3 in the "Installation instructions" section, apply the snapshots. If there are no snapshots, go to the next step.
  2. To restore your databases and computers, use the backup that was made in step 3 of the installation instructions section.

    Note Do not leave the system in a partly updated state. Perform rollback operations on all computers on which Windows Azure Pack was installed, even if an 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.
  3. Open the traffic to your restored nodes.

Files that are updated in this update rollup


File nameVersion
MgmtSvc-SQLServer.msi3.31.8196.4
MgmtSvc-TenantAPI.msi3.31.8196.4
MgmtSvc-TenantPublicAPI.msi3.31.8196.4
MgmtSvc-TenantSite.msi3.31.8196.4
MgmtSvc-Usage.msi3.31.8196.4
MgmtSvc-WebAppGallery.msi3.31.8196.4
MgmtSvc-WindowsAuthSite.msi3.31.8196.4
MgmtSvc-AdminAPI.msi3.31.8196.4
MgmtSvc-AdminSite.msi3.31.8196.4
MgmtSvc-AuthSite.msi3.31.8196.4
MgmtSvc-Bpa.msi3.31.8196.4
MgmtSvc-ConfigSite.msi3.31.8196.4
MgmtSvc-Monitoring.msi3.31.8196.4
MgmtSvc-MySQL.msi3.31.8196.4
MgmtSvc-PowerShellAPI.msi3.31.8196.4

Properties

Article ID: 3129786 - Last Review: 01/28/2016 21:44:00 - Revision: 2.0

Microsoft System Center 2012 R2, Windows Azure Pack

  • kbqfe kbsurveynew kbfix kbexpertiseinter atdownload KB3129786
Feedback