Windows Server 2016 only: Support for Encryption Supported virtual machines (VMs).
Windows Server 2016, Virtual Machine Manager (VMM) and Service Provider Foundation (SPF) provide support for Encrypted Supported VMs, now WAP provides support for the three type of VMs in Windows Server 2016: regular VMs, Shielded VMs, and Encryption Supported VMs.
Windows Server 2016 only: Fix to incorrect Format of volume Signature in PDK File downloaded through WAP.
When a tenant updates a VM Size, the Hardware Profile ID is passed along to the SPF/VMM Virtual Machine Update event. This enables custom runbooks to change other properties as necessary.
Fix to Virtual Network property labels in the Quota page. The quotas for "Site-to-Site VPN" and "External IP addresses" labels in the Admin Portal VM Resource Provider are misleading because they read "per network." They are actually "per subscription."
Fix: When you update the VM Cloud Resource Provider, a duplicate Port setting is added leading ManagementOData to fail and return an error message that reads, "An item with the same key has already been added."
Windows Server 2016 only: Ability for the tenant user to add a network adapter to a VM while the VM is running. In UR 9.1 and earlier versions, new NICs could be added only after the VM was stopped.
Ability for the WAP Admin to include a SQL Server into multiple availability groups for High Availablility (HA) configurations. Available only in configurations that do not use SQL Resource Governor
Ability for the WAP Administyrator to include a server that's running Microsoft SQL Server into multiple availability groups for HA configurations.
Ability for the WAP user to enable the "Always On" feature of WAP websites.
Microsoft UpdateTo obtain and install an update package from Microsoft Update, follow these steps on a computer that has an applicable 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 packages that you want to install, and then click OK.
- Click Install updates to install the selected update packages.
Manual download of the update packagesGo to the following website to manually download the update packages from the Microsoft Update Catalog:
Download the Windows Azure Pack update package now.
- Tenant site
- Tenant API
- Tenant Public API
- Administration site
- Administration API
- Windows Authentication
- Microsoft SQL
- Web Application Gallery
- Configuration site
- Best Practices Analyzer
- PowerShell API
- If the system is currently operational (handling customer traffic), schedule downtime for the Azure Pack servers. The Windows Azure Pack currently doesn't support rolling upgrades.
- Stop or redirect customer traffic to sites that you consider satisfactory.
- Create backup images of the web servers and the SQL Server databases.
- If you're using virtual machines, take snapshots of their current state.
- If you're not using VMs, take a backup of each MgmtSvc-* folder in the Inetpub directory on each virtual machine that has a WAP component installed.
- Collect information and files that are related to your certificates, host headers, and any port changes.
- If you're using your own theme for the Windows Azure Pack Tenant site, follow these instructionsto preserve your theme changes 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 the MgmtSvc-AdminAPI.msi on the computer that's running "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 that are installed by WAP, the update operation replaces them. You have to export the new certificate and import 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 necessary. 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\Database
- 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 snapshots are available from the second note item in 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 items in step 3 in 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 on which Windows Azure Pack was installed, even if the update failed on 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.
Номер статьи: 3158609 — последний просмотр: 15 июля 2016 г. — редакция: 1