This article describes the issues that are fixed in Update Rollup 6 for Windows Azure Pack Web Sites version 2. Additionally, this article contains the installation instructions for Update Rollup 6 for Windows Azure Pack Web Sites version 2.
Update highlightsThis release introduces a new interactive installation, upgrade, and offline installation process that addresses user feedback about the original process. A new Windows Azure Pack Web Sites Microsoft Management Console (MMC) snap-in is included in this update. This updates offers functionality that was previously available only through Windows PowerShell commands. In addition, the MMC snap-in can be used to perform clean installations on a stand-alone or preconfigured file server and to configure a secondary controller.
New featuresUpdate Rollup 6 for Windows Azure Pack Web Sites version 2 adds the following new features to the platform:
- Web Jobs
Windows Azure Pack Web Sites enables tenants to run custom jobs (running executables or scripts) on your web app in one of three ways: on demand or continuously. For more information, see How to Using the WebJobs feature of Windows Azure Pack Websites.
- Site Slots
Windows Azure Pack Web Sites enables tenants to deploy a separate deployment slot. For example, a tenant could create a deploymentto a staging slot to validate changes before swapping the staging slot with the production slot. For more information, see How to Use the Site Slots feature in Windows Azure Pack Websites.
Windows Azure Pack Web Sites can now take advantage of the HttpPlatformHandler to host Java and other runtimes. For more information, see How to Use the HttpPlatformHandler feature in Windows Azure Pack Websites.
- By default, SSL Version 3 is disabled. For more information, see How to enable SSL v3 in Windows Azure Pack Websites.
- IP SSL functionality has new UI capabilities. However, some elements will not be upgraded. For more information, see IP SSL Changes in Windows Azure Pack Websites Version 2 Update 6.
If you implemented IP-based SSL by using VIP mapping or local address mappings with IPv6 addresses, please do not upgrade to Update Rollup 6 unless you migrate to IPv4 before you apply this update. This scenario is not supported in this update. However, it will be supported in a future update.
- Roles have to be repaired for the following configuration changes to take effect. (This may cause the role to restart.)
- Add/delete/update VIP Mappings
- Add/delete/update IP range for IP Restrictions
- Upload new publishing certificate
- Upload new default certificate
- Add/delete/update VIP Mappings
- Ports that are used by Update Rollup 6 for Windows Azure Pack Web Sites version 2
Because of changes to IP-based SSL, Update Rollup 6 for Windows Azure Pack Websites version 2 uses additional TCP ports for communication between roles. These changes are listed in the following table. Those changes that are displayed in bold type are new in Update Rollup 6. Before you install or upgrade, you should make sure that communication with these ports is enabled.
Role Service Port Database Server SQL Server 1433 or a nondefault port if is configured File Server SMB 445 Web Farm Framework Agent 8173 WinRM (HTTP) 5985 WinRM (HTTPS) 5986 FrontEnd HTTP 80 HTTP 443 HTTP/HTTPS Any ports that are used in nonstandard port VIP Mappings Certificate Sync Service 1233 Kudu Credential Cache Listener 1233 WinRM (HTTP) 5985 WinRM (HTTPS) 5986 Management Server Web Farm Framework Agent 8173 WinRM (HTTP) 5985 WinRM (HTTPS) 5986 Publisher FTP 21 Web Deploy 443/8172 Web Farm Framework Agent 8173 WinRM (HTTP) 5985 WinRM (HTTPS) 5986 Web Worker DWAS/W3WP 80 Web Farm Framework Agent 8173 WinRM (HTTP) 5985 WinRM (HTTPS) 5986 Worker Management Endpoint 456
Issues that are fixed in this update rollupThis update fixes the following issues:
- Issue 1
By default, SSL version 3 is enabled in Windows Azure Pack Web Sites version 2.
- Issue 2
You cannot add workers from the administrator portal.
- Issue 3
If services are currently running when the upgrade is started, a webhosting.msi upgrade may fail.
- Issue 4
Controller may operate on remote servers that do not belong to the controller. This issue can be caused by stale DNS entries.
- Issue 5
Installation fails when Hosting or Metering databases are already present, and no useful error messages are displayed.
- Issue 6
You cannot delegate IPSecurity settings for IPRestrictions to users who run the following Windows PowerShell cmdlet:Set-DefaultAppHostConfigSection -SectionName "system.webServer/security/ipSecurity" -OverrideModeDefault Allow
The cmdlet seems to finish. But when an IP restriction in a site's Web.config file occurs, a 500.19 Http response is returned when a request to the site is made.
- Issue 7
After they upgrade to Update Rollup 4 for Windows Azure Pack Web Sites version 2 , users cannot access usage statistics from the metering database.
- Issue 8
If TrustedHosts is configured by Group Policy, Windows Azure Pack Web Sites cannot configure the TrustedHosts setting. This setting is needed to communicate with the file server through Windows Remote Management.
How to obtain and install Update Rollup 6 for Windows Azure Pack Web Sites
Download informationUpdate packages for Windows Azure Pack Web Sites 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 Operational Manager 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 update package.