Issues that are fixed in this update rollupIssue 1
Web Site Active Directory integration enablement causes all the websites in a web space to be considered integrated instead of just the one site intended. This fix will make it so that when a tenant enables AD integration on a website, it affects only that website. A tenant can have multiple AD integrated websites. But that is set on a per-website basis.
The Web Site Active Directory integration interfaces that were provided for user interface (UI) enablement did not adequately support the UI requirements. Several missing calls had to be added together with some improved features. Among the improvements is a change to prevent enablement of the feature if the workers are not all in the same domain.
Note The user interface enablement for website Active Directory integration is in the release of Windows Azure Pack Portal and API v1 Update 2 that is releasing at the same time as this update for Windows Azure Pack (WAP) websites.
SQL Integrated authentication (application identity pool) enablement breaks website publishing when it is enabled.
Quota enforcement on custom actions are not run in a domain environment. The metering serverName did not have a DNS suffix. Therefore, it was different from the controller host name in the controller owner table. This caused the quota enforcement service never to think that it had ownership.
IP restrictions are not being correctly respected on the worker. This could allow for website access when it should be prevented by the IP restriction configuration.
Multiple Powershell commands are not working correctly. Also, multiple functions that are not adequately covered by PowerShell command support. PowerShell support in this release should provide total functional coverage. This includes new PowerShell commands to support Active Directory integration.
Because of an issue in the database, it was not possible to create a website on a deployment that was installed on a Spanish version of the operating system.
SSL certificate validation checking experienced several issues that prevented correct analysis and classification of an SSL certificate.
The Usage Service generated the same value for the number of dedicated instances that was used for all subscriptions. The value that was generated had no correlation to the actual number of instances that was used by the tenant.
The creation of subscriptions required many more calls to the database than the number that was desired. The large number of calls caused performance issues and an unnecessary load on the database.
The PHP versions used were not completely up-to-date. PHP 5.4 is now increased to PHP 5.4.25, and PHP 5.3 is now 5.3.28. Additionally, PHP 5.5 is added.
Python support was not completely up-to-date. It is now updated to use the most recently released integration libraries.
How to obtain and install Update Rollup 2 for Windows Azure Pack Web Sites version 2
Download informationThis update can be downloaded from the Microsoft Update Catalog.
Installation instructionsLearn about the installation instructions for this update in the Upgrading Windows Azure Pack: Web Sites from Preview Versions topic on the Microsoft TechNet website.
These instructions explain how to upgrade to Update Rollup 2 for Windows Azure Pack Web Sites version 2. Additionally, the instructions provide guidance about how to monitor the upgrade and check the upgrade status.
Note Because of changes that are made to data stores in addition to executable file changes, this update cannot be rolled back.
Files updated in Update Rollup 2
|Files that changed||Size||Version|
Article ID: 2932947 - Last Review: 23 Jun 2014 - Revision: 1