Update Rollup 8 for Windows Azure Pack

This article describes the issues that are fixed in Update Rollup 8 for Windows Azure Pack. Additionally, this article contains the installation instructions for Update Rollup 8 for Windows Azure Pack (WAP).

Issues that are fixed in this update rollup

Windows Azure Pack

  • Issue 1

    Administrators cannot offer and tenants cannot use multiple external IP addresses through a Network Address Translation (NAT) connection.
    Even though Microsoft System Center Virtual Machine Manager (VMM) has functionality to allocate IP addresses for this purpose, the WAP administrator and tenant experiences do not provide such functionality. Administrators can now allocate a set of external IP addresses for tenants to use when you create NAT rules. The administrator can set up the IP address quota through the Administrator Portal virtual machine (VM) extension.

    Note For existing plans, the Administrator Portal shows the "External IP addressed" quota as "0" when in reality it should show "Unlimited," as it does for an existing plan. This UI issue will be addressed in a future release.
  • Issue 2

    Tenants can create only one checkpoint per virtual machine.
    Administrators can create plans that include quotas that let tenants create multiple VM checkpoints.
  • Issue 3

    An unexpected exception is generated by the PowerShell command "Get-MgmtSvcSqlDatabase."
    The command Get-MgmtSvcSqlDatabase does not retrieve SQL database information. The following examples return exception "Object reference not set to an instance of an object":
    • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId "someid" -DisableCertificateValidation
    • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId $hostserver.ServerId -Name "somename" -DisableCertificateValidation
    • Get-MgmtSvcSqlDatabase -AdminUri $AdminUri -Token $Token -HostingServerId " someserverid" -Name "datatest" -DisableCertificateValidation

    After you apply this update, the Get-MgmtSvcSqlDatabase command returns the database information in all expected cases.
  • Issue 4

    An unexpected exception is generated by the PowerShell command "Remove-MgmtSvcMySqlHostingServer." 
    This command fails with the exception "Index (zero-based) must be greater than or equal to zero and less than the size of the argument list" when you run statements such as the following:
    • Remove-MgmtSvcMySqlHostingServer -AdminUri $AdminUri -Token $Token -HostingServerId $HostServer[0].ServerId -DisableCertificateValidation
    • Remove-MgmtSvcMySqlHostingServer -AdminUri $AdminUri -Token $Token -HostingServerId "someserverid" -DisableCertificateValidation

    After you apply this update, the Remove-MgmtSvcMySqlHostingServer command executes as expected and removes the servers in all expected cases.
  • Issue 5 

    When you create a virtual machine through the Tenant Portal, the menu dropdown boxes are not sorted.
    When a tenant tries to create a VM and the list of items is larger than some items, it becomes very difficult to find the necessary machine image or template.

    After you apply this update, both items are found in the Gallery and in the Quick Create list.
  • Issue 6

    Attaching ISOs in a generation 2 (gen 2) VM fails after three or four attach or detach operations.

    The attach and detach operations on ISO disks and VM gen 2 allocate adapters never releases the adapters for reuse.

    After you apply this update, detaching the disk adapter enables the adapter to be reused again.
  • Issue 7 

    Other fixes to improve overall product quality

How to obtain and install Update Rollup 8 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 a Windows Azure Pack 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.

Microsoft Update Catalog

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

    • This update does not include database changes. Generally, we recommend that you keep current database backups.
    • If you are using virtual machines, you should take snapshots of their current state.
    • If you are not using VMs, make a backup of each MgmtSvc-* folder in the inetpub directory 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 are using your own theme for the Windows Azure Pack tenant site, you should follow these instructions to preserve your theme changes before you run the update.
  5. Run 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 that were installed by WAP, the update operation will replace them. You have to export the new certificate and import to the other nodes under Load Balancing. These certificates 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. Enable the new support for SQL Server Resource Governor. To do this, follow these steps:
    1. Download and open this PowerShell script by using a text editor (or Windows PowerShell ISE). This script will change the Azure Pack databases.
    2. Change the following connection string line:

      $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 computers that are running the following:
      • Usage Extension
      • Web App Gallery Extension
      • SQL Server Extension
      • MySQL Extension

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

Rollback instructions

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 you took 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. Run rollback operations on all computers on which where 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.
  3. Open the traffic to your restored nodes.

Files that are updated in this update rollup

File NameSize in BytesVersion
MgmtSvc-AdminAPI.msi4,304,896 3.28.8196.48
MgmtSvc-AdminSite.msi17,616,896 3.28.8196.48
MgmtSvc-AuthSite.msi12,083,200 3.28.8196.48
MgmtSvc-Bpa.msi917,504 3.28.8196.48
MgmtSvc-ConfigSite.msi7,950,336 3.28.8196.48
MgmtSvc-Monitoring.msi4,472,832 3.28.8196.48
MgmtSvc-Mp.msi1,519,616 3.28.8196.48
MgmtSvc-MySQL.msi3,952,640 3.28.8196.48
MgmtSvc-PowerShellAPI.msi3,850,240 3.28.8196.48
MgmtSvc-SQLServer.msi4,276,224 3.28.8196.48
MgmtSvc-TenantAPI.msi4,288,512 3.28.8196.48
MgmtSvc-TenantPublicAPI.msi4,358,144 3.28.8196.48
MgmtSvc-TenantSite.msi19,103,744 3.28.8196.48
MgmtSvc-Usage.msi4,407,296 3.28.8196.48
MgmtSvc-WebAppGallery.msi4,083,712 3.28.8196.48
MgmtSvc-WindowsAuthSite.msi4,304,896 3.28.8196.48


Article ID: 3096392 - Last Review: 10/28/2015 01:41:00 - Revision: 3.0

Microsoft System Center 2012 R2, Windows Azure Pack

  • kbqfe kbsurveynew kbfix kbexpertiseinter atdownload KB3096392