This article describes the issues that are fixed in Update Rollup 13 for Windows Azure Pack Web Sites. It also includes the installation instructions for Update Rollup 13 for Windows Azure Pack Web Sites.
Important This is the final update for Windows Azure Pack Web Sites version 2. Windows Azure Pack Web Sites version 2 has entered Extended Support, as discussed at https://aka.ms/wapwebsiteslifecycle.
Issues that are fixed in this update
This update fixes the following issues:
Issue 1: NTLM V2 cannot be enabled. This fix lets customers enable NTLM V2.
Issue 2: Security issues: This fix updates NodeJS versions 4.8.4, 6.11.1, 7.10.1 and 8.1.4 as referenced at https://github.com/Azure/app-service-announcements/issues/19.
Issue 3: Respecting existing firewall rules: This fix does not override firewall rules for HTTP that are already in place between Front End and Web Worker roles.
Issue 4: Two sites that use Windows Authentication cannot talk to one another if they are co-located on the same web worker.
Issue 5: TLS 1.0: This fix lets customers disable TLS 1.0.
Issue 6: Client Certificates usage: This fix enables Client Certificates when sites are running a custom application pool identity in a domain-joined environment.
Issue 7: When you use Request Filtering to remove server headers, the management server is rendered unstable.
Issue 8: Users cannot create websites through Windows PowerShell in Update Rollup 12.
Issue 9: The Remove Worker role intermittently does not remove the worker from the data role cache.
Issue 10: String or binary data is truncated when calling Set-WebSitesConfig -type DefaultAppHostConfig -SectionName “system.webServer/proxyHelper” -SectionXml if the -SectionXML value is specified by using a large value.
Issue 11: This update adds support for PHP 7.1.
Framework and component updates included in this update rollup
PHP updated versions and new versions installed
- PHP 5.6.30
- PHP 7.0.18 x86 and x64
- PHP 7.1.4 x86 and x64
WinCache 2.0 for PHP 7.1 (x86 and x64)
Update packages for Windows Azure Pack Web Sites version 2 are available from Windows Update or by manual download.
Note If the target operating system is Windows Server 2012 R2, all Web Worker roles muct have the April 2014 Rollout Upgrade Package installed in order to support Visual C++ 2015 Redistributable. If this package is not installed, the Web Worker roles will not be marked as ready, and the Web Worker logs in the Web Management Console will indicate that dependency failed.
Method 1: Windows Update
To obtain and install an update package from Microsoft Update, follow these steps on a computer that has the Windows Azure Pack Web Sites Controller 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 that you want, and then click OK.
- Click Install updates to install the update package.
- Wait for the Web Sites Management Console snap-in to appear on the desktop. (This is also searchable through the Start menu.) Then, follow these steps:
- Open the console.
- Start the Web Sites controller.
- Monitor the roles upgrade process.
Method 2: Microsoft Update Catalog
This update rollup is available for manual download and installation from the Microsoft Update Catalog:
Method 3: Microsoft Download Center
This update rollup is available for manual download and installation from the Microsoft Download Center.
Installation and upgrade instructions are documented in the Start the installation of Windows Azure Pack: Web Sites topic on the TechNet website. These instructions describe how to upgrade to Update Rollup 12 for Windows Azure Pack Web Sites version 2.
Notice that the installation and upgrade process changed significantly in Update Rollup 6. Therefore, please take the time to review the documentation.
The TechNet topic provides additional guidance to monitor the upgrade and to check the upgrade status.
Because of the changes that were made to the data stores in addition to the executable, this update cannot be rolled back.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.