Description of Update Rollup 5 for Windows Azure Pack

Introduction

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

Issues that are fixed in this update rollup

The following issues are fixed in Windows Azure Pack UR5:

  • Adds support for SQL Governor in the SQL Server Resource Provider.

    Symptom Administrators cannot optimize their SQL Server resource offerings. The SQL Server Resource Governor features are not supported in the SQL Server Resource Provider.

    Resolution Admnistrators now have access to this functionality in SQL Server 2014 through the Windows Azure Pack Resource Provider for SQL Server. It is provided through the Admin and Tenant Portal extensions as well as the corresponding PowerShell Cmdlets. Notice that Windows Azure Pack does not support this feature in versions before SQL Server 2014. Also, WAP does not use this feature for its own management databases, it is meant to be used by the tenants in these databases.

    Important This feature requires you run the PowerShell script in step 7 of the installation instructions below. If you do not do so, it will not affect the existing functionality or update process of your WAP deployment. SQL Resource Governor will not be available or configurable.

  • Adds administrator support for disabling native Network RP to allow for third-party network provider.

    Symptom Administrators don't have an option to associate Network Resource Providers other than the one provided through the Service Provider Foundation or Virtual Machine Manager Resource Provider.

    Resolution Administrators can now create plans to configure or disable the native Network Resource Provider and allow for third-parties to plug in their Network Resources.

  • Provides detail on Virtual Machine Memory type, Memory Startup and Maximum values in the Tenant Portal.

    Symptom Tenants cannot see details about the kind of memory allocated to their virtual machines and corresponding Startup and Maximum values.

    Resolution Tenants can now see information in the "quick glace" panel about what kind of memory (dynamic or static) their virtual machines have and the corresponding Memory Startup and Maximum values.

  • Fix to the Get-MgmtSvcRelyingPartySettings PowerShell cmdlet.

    Symptom When you run this cmdlet by using a particular namespace in the parameter, it does not return the correct set of setting. Instead, it returns the settings for a different namespace, not the one provided.

    Resolution The Get-MgmtSvcRelyingPartySettings cmdlet no longer returns the settings of the wrong namespace.

  • Fix to the issue of failing to establish Remote Desktop Connection to virtual machines put behind a Network Address Translation (NAT) device.

    Symptom Tenants who have virtual machines located behind a NAT cannot access their virtual machines through Remote Desktop Connections.

    Resolution The Tenant Portal Service Provider Foundation Resource Provider UI makes sure that the correct external IP address is used to establish the Remote Desktop connection.

  • Fix to the Attached Network dialog box where the network entries in the list were disabled.

    Symptom When the tenant is attaching a network to a computer, the corresponding dialog box does not let them choose an already attached network. Instead, the entries are displayed as disabled.

    Resolution The dialog box now lets the user select from the available networks.

  • New support for the Turkish language.


How to obtain and install Update Rollup 5 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 Operational Manager component 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.

Manual download of the update packages

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

Download Download the Windows Azure Pack update package now.

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:

  1. If the system is currently operational (handling customer traffic), schedule downtime for the Azure servers. The Windows Azure Pack does currently not support rolling upgrades.

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

  3. Create backups of the computers and databases:

    1. This update does contain database changes (see step 7); we strongly recommend that you keep backups of your databases current before installation.

    2. If you are using virtual machines, take snapshots of their current state. Otherwise, go to the next step.

    3. If you are not using VMs, take a backup of the computer to be used for restoring in case you have to roll back your update installation.


  4. If you are using your own theme for the Windows Azure Pack Tenant site, make sure that you preserve your theme customizations before you perform the update.

  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. If you are using the original self-signed certificates installed by WAP, the update operation will replace them. You have to export the new certificate and imported to the other nodes under Load Balancing. These certs have the CN=MgmtSvc-* (Self-Signed) naming pattern.

    2. Update Resource Provider (RP) services (SQL Server, My SQL, SPF/VMM, websites) as needed. And 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. This step is required in order to enable new support for SQL Server Resource Governor:

    1. Download and open with a text editor (or Windows PowerShell ISE) the following PowerShell script. This script will change the Azure Pack Databases.

    2. Change the connection string line, as follows:

      $wapConnectionString = "server=yourservername;uid=sa;pwd=yourpassword;database=master;"

    3. Run this script as an administrator on the computers that contain the Mgmt-Svc-PowerShellAPI module. These are the computers that are running the following:

      • Usage Extension

      • Web App Gallery Extension

      • SQL Server Extension

      • MySQL Extension


  8. If all components are updated and functioning as expected, you can start to open traffic to your updated nodes. Otherwise, see the "Rollback instructions" section.


In case an issue occurs and you verify that a rollback is necessary, follow these steps:

  1. If snapshots are available from step 3B in the "Installation instructions" section, apply the snapshots. If there are no snapshots, go to the next step.

  2. Use the backup that was taken in steps 3A and 3C in the "Installation instructions" section to restore your databases and computers.

    Do not leave the system in a partly updated state. Perform rollback operations on all machines where Windows Azure Pack was installed, even if 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 changed

File size

Version

MgmtSvc-AdminAPI.msi

4284KB

3.22.8196.48

MgmtSvc-AdminSite.msi

17108KB

3.22.8196.48

MgmtSvc-AuthSite.msi

12372KB

3.22.8196.48

MgmtSvc-ConfigSite.msi

7813KB

3.22.8196.48

MgmtSvc-Monitoring.msi

4448KB

3.22.8196.48

MgmtSvc-MySQL.msi

3780KB

3.22.8196.48

MgmtSvc-PowerShellAPI.msi

3780KB

3.22.8196.48

MgmtSvc-SQLServer.msi

4036KB

3.22.8196.48

MgmtSvc-TenantAPI.msi

4276KB

3.22.8196.48

MgmtSvc-TenantPublicAPI.msi

4316KB

3.22.8196.48

MgmtSvc-TenantSite.msi

18404KB

3.22.8196.48

MgmtSvc-Usage.msi

4384KB

3.22.8196.48

MgmtSvc-WebAppGallery.msi

4012KB

3.22.8196.48

MgmtSvc-Bpa.msi

896KB

3.22.8196.48

MgmtSvc-WindowsAuthSite.msi

4212KB

3.22.8196.48



Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×