Issues that are fixed in this update rollup
- For stand-alone virtual machines (VMs) whose templates specified multiple network adapters, the tenant user cannot associate a particular network to each network adapter.
Symptom: If the user is creating a VM that's based on a template that contains multiple network adapters, the Tenant Site VM extension will automatically assign the first available network.
Resolution: The tenant user now has the necessary user interface (UI) to select a particular network for a particular network adapter.
- Developers who use Web Site Cloud to deploy PHP applications do not have an option to specify PHP 5.5 version.
Symptom: If the user wants to deploy a PHP 5.5 application, there is no option to specify that version of PHP.
Resolution: The user now has the PHP 5.5 version option.
- Usage records that contain more than 4,000 characters of resource data are not supported.
Symptom: If the Usage Collector encounters a usage record that has more than 4,000 characters, it fails and shuts down the usage pipeline for System Center usage data.
Resolution: Some of the instructions in this article involve running an SQL script that will increase the size of the table field to nvarchar(max).
- Tenants experience unexpected behavior in the portal when they create websites that have the same name in different plan subscriptions that are each on a separate Web Site cloud.
Symptom: When a tenant creates two websites that have the same name on different Web Site clouds and subscriptions, the portal may display inaccurate information about one or both of the websites.
Resolution: Users can now create websites that have the same name through separate subscriptions and clouds without seeing incorrect information about their sites or subscriptions.
- Tenants who create an ASP.NET site by using Web Site Cloud cannot specify whether the Application Pool will be running in Classic or Integrated Mode.
Symptom: When a tenant tries to create a website, the user notices that the Application Mode setting is not available. If the application requires Classic Mode, it will run the risk of failing at run time.
Resolution: Users can now specify the Application Pool mode for their applications.
- Administrators cannot use Fully Qualified Domain Names (FQDN) when they configure SQL Always-On Listeners, because the Windows Azure Pack Resource Provider for SQL Server does not support it.
Symptom: When an administrator enters an FQDN in the SQL Extension of the Administration site, the SQL Resource Provider accepts it, but an error is returned after the provider tries to process the FQDN.
Resolution: FQDNs are now fully supported by the Resource Provider.
- When a tenant creates a VM, the name that is provided is not honored. Instead, a name is generated.
Symptom: When tenants build a VM on premises, they expect the name that they provided to be honored as the NetBIOS name of the computer. This is not the case; the VM extension generates a name to maintain uniqueness in System Center Virtual Machine Manager.
Resolution: Now the VM Resource Provider generates a name that's based on the name that the user provides in the following pattern:Computer Name = name + "###"The numbers are added to the end of the name to guarantee uniqueness in System Center Virtual Machine Manager.
- The metrics that are associated with websites that are located in separate clouds whose endpoint credentials differ from each other are sometimes not retrieved; instead an error message is displayed.
Symptom: When the tenant or administrator accesses information about websites that are located in clouds that are configured to use different endpoint access credentials, you receive the following error message from the Administration site:The server could not retrieve metrics (Internal Server Error).
Resolution: The monitoring service responsible for retrieving the websites data now returns the correct metrics instead of an error.
- The SQL Resource Provider grants DB Owner permissions to tenants when during database provisioning.
Symptom: When a SQL Server Database is provisioned by a tenant, the SQL Resource Provider grants DB Owner permissions to the corresponding SQL login.
Resolution: Tenant logins that are created after you apply Update Rollup 3 are no longer granted DB Owner permissions. Existing tenant logins and already existing databases are not affected. To retroactively give existing tenant logins the same set of permissions and to remove the DB Owner level access, see the following TechNet article:
- SQL Server Integrated Security or Windows Authentication is not supported by the Windows Azure Pack Tenant Site SQL extension.
Symptom: When the tenant tries to create a database, no option for Windows Authentication is provided.
Resolution: The SQL Tenant Site Extension now supports Windows Authentication.
How to obtain and install Update Rollup 3 for Windows Azure Pack
Download informationUpdate packages for Windows Azure Pack are available from Microsoft Update or by manual download.
Microsoft UpdateTo obtain and install an update package from Microsoft Update, follow these steps on a computer that has an applicable System Center 2012 R2 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:
Installation instructionsThese installation instructions are for the following Windows Azure Pack components:
- Tenant site
- Tenant API
- Tenant Public API
- Administration site
- Administration API
- Tenant Authentication
- Administration Authentication
- Usage Extension
- Monitoring Extension
- SQL Server Extension
- MySQL Extension
- Web App Gallery Extension
- Configuration site
- Best Practices Analyzer
- PowerShell API
To install the update .msi files for each Windows Azure Pack component, follow these steps:
- 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.
- Stop or redirect customer traffic to sites that you consider satisfactory.
- Create backups of the computers and databases:
- Because this update includes a database change, backing up your Windows Azure Pack databases is required.
- If you are using virtual machines, take snapshots of their current state. Otherwise, go to the next step.
- 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.
- 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:
- 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, and Administrator API nodes.
- Update the Administrator and Tenant sites.
- To address Issue 3 and Issue 10, run the following PowerShell Script:Import-Module -Name MgmtSvcConfig
Install-MgmtSvcDatabase -Schema SqlServer -Server "$env:ComputerName" -UserName "sysadmin_login" -Password "sysadmin_password"
Note Run the Windows PowerShell ISE application in Administrator mode.
- Update tenant user access to SQL Server. This is an optional step. We do not recommend this step if you think that it may affect your current tenant database access. This step is included for those organizations that want to improve the security of their existing tenant databases by changing the current DB Owner access to more limited permissions (Issue 9). For detailed instructions and the SQL script for this step, follow these instructions.
- If everything is updated and functioning as expected, you can start to 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 step 3B 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 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.
- Open the traffic to your restored nodes.