Introduction
This article describes the issues that are fixed in Update Rollup 7 for Windows Azure Pack. It also contains the installation instructions for Update Rollup 7 for Windows Azure Pack.
Issues that are fixed in this update rollup
Windows Azure Pack
-
Tenants cannot delete the checkpoints of their virtual machinesTenants can create a checkpoint for a virtual machine in their subscription but cannot delete it afterward.After this update is installed, tenants can delete the checkpoint created for their virtual machines.
-
Support for VM names of up to 15 charactersTenants cannot enter VM names longer than 12 characters.After this update is installed, an administrator can create plans that let tenants enter VM names of up to 15 characters.
-
Displaying VHD items during virtual machine creation when there are no hardware profiles in the planEven when the plan only has VM templates or when there are no hardware profiles associated, VHDs are still shown to the tenants when they create virtual machines.After this update is installed, tenants no longer see the irrelevant VHDs.
-
Incompatible VHDs are offered to the tenant when attaching a VHD to a virtual machineWhen attaching a VHD to a virtual machine, the list shows VHDs with incompatible operating systems.After this update is installed, tenants no longer see the incompatible VHDs.
-
Support for tenant plan viewing and self-subscription permission based on security groupsAdministrators have no way of preventing tenants from viewing and self-subscribing to a plan based on security groups.After this update is installed, administrators can now associate security groups with a plan to let only those tenants in the security groups to view and self-subscribe to the particular plans. This includes corresponding PowerShell administration commands.
-
Support for Shielded Virtual Machine Management when it's run on Windows 10 Server PreviewOn Windows Server 2016 Preview, tenants cannot create and manage Shielded Virtual Machines.After this update is installed, administrators can enable Shielded VM support in plans for tenants' access to these resources. This functionality is supported only in Windows Server 2016 Preview.
-
Virtual Machine performance data displayed in the tenant portalNot all performance data is displayed on the tenant virtual machine dashboard.After this update is installed, tenants can see performance data on their dashboard.
-
Product qualityThis update includes other fixes to improve overall product quality.
How to obtain and install Update Rollup 7 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 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 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 (WAP) component, follow these steps:
-
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.
-
Stop or redirect customer traffic to sites that you consider satisfactory.
-
Create backups of the computers.Notes
-
This update does not include database changes, backing up and restoring databases is not necessary. Generally, we recommend that you keep current database backups.
-
If you are using virtual machines, take snapshots of their current state.
-
If you are 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 related to your certificates, host headers, and any port changes.
-
-
If you are 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 using Microsoft Update either directly on each node or through the Windows Server Update Services (WSUS) server.
-
For each node under Load Balancing, run the updates for components in the following order:
-
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 import to the other nodes under Load Balancing. These certs have 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.
-
-
To enable the new support for SQL Server Resource Governor, follow these steps:
-
Download and open with a text editor (or Windows PowerShell ISE) this PowerShell script. This script will change the Azure Pack Databases.
-
Change the connection string line to the following:
$wapConnectionString = "server=yourservername;uid=sa;pwd=yourpassword;database=master;"
-
Run this script as an administrator on the machines that contain the Mgmt-Svc-PowerShellAPI module; these are those computers that are running:
-
Usage Extension
-
Web App Gallery Extension
-
SQL Server Extension
-
MySQL Extension
-
-
-
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 under 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 under step 3 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 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.
|
File name |
Version |
|---|---|
|
MgmtSvc-SQLServer.msi |
3.25.8196.75 |
|
MgmtSvc-TenantAPI.msi |
3.25.8196.75 |
|
MgmtSvc-TenantPublicAPI.msi |
3.25.8196.75 |
|
MgmtSvc-TenantSite.msi |
3.25.8196.75 |
|
MgmtSvc-Usage.msi |
3.25.8196.75 |
|
MgmtSvc-WebAppGallery.msi |
3.25.8196.75 |
|
MgmtSvc-WindowsAuthSite.msi |
3.25.8196.75 |
|
MgmtSvc-AdminAPI.msi |
3.25.8196.75 |
|
MgmtSvc-AdminSite.msi |
3.25.8196.75 |
|
MgmtSvc-AuthSite.msi |
3.25.8196.75 |
|
MgmtSvc-Bpa.msi |
3.25.8196.75 |
|
MgmtSvc-ConfigSite.msi |
3.25.8196.75 |
|
MgmtSvc-Monitoring.msi |
3.25.8196.75 |
|
MgmtSvc-MySQL.msi |
3.25.8196.75 |
|
MgmtSvc-PowerShellAPI.msi |
3.25.8196.75 |
