Azure Stack Hub 发行说明Azure Stack Hub release notes

本文介绍 Azure Stack Hub 更新包的内容。This article describes the contents of Azure Stack Hub update packages. 此更新包括最新版 Azure Stack Hub 的改进和修复。The update includes improvements and fixes for the latest release of Azure Stack Hub.

若要访问不同版本的发行说明,请使用左侧目录上方的版本选择器下拉列表。To access release notes for a different version, use the version selector dropdown above the table of contents on the left.

重要

此更新包仅适用于 Azure Stack Hub 集成系统。This update package is only for Azure Stack Hub integrated systems. 请勿将此更新程序包应用于 Azure Stack 开发工具包 (ASDK)。Do not apply this update package to the Azure Stack Development Kit (ASDK).

重要

如果 Azure Stack Hub 实例落后于两个以上的更新,则认为它不符合。If your Azure Stack Hub instance is behind by more than two updates, it's considered out of compliance. 必须至少更新到最低支持版本才能获得支持You must update to at least the minimum supported version to receive support.

更新规划Update planning

应用更新之前,请务必查看以下信息:Before applying the update, make sure to review the following information:

有关对更新和更新过程进行故障排除的帮助,请参阅对 Azure Stack Hub 的修补和更新问题进行故障排除For help with troubleshooting updates and the update process, see Troubleshoot patch and update issues for Azure Stack Hub.

下载更新Download the update

可使用 Azure Stack Hub 更新下载程序工具下载 Azure Stack Hub 更新包。You can download the Azure Stack Hub update package using the Azure Stack Hub update downloader tool.

2005 内部版本参考2005 build reference

Azure Stack Hub 2005 更新内部版本号为 1.2005.6.53。The Azure Stack Hub 2005 update build number is 1.2005.6.53.

重要

随着 2002 版 Azure Stack Hub 的推出,为了支持世界各地应对新冠病毒肺炎的客户以及可能对其 Azure Stack Hub 系统做出重要决策的客户,Microsoft 暂时扩展支持策略以包含三个以前的更新版本 (N-3)。With the 2002 release of Azure Stack Hub and in support of our customers around the world who are responding to COVID-19 and who may be making important decisions about their Azure Stack Hub systems, Microsoft temporarily extended its support policy to include three previous update versions (N-3). 在 2005 版本中,我们将此扩展继续延长 45 天(至 2020 年 9 月 25 日)。With the 2005 release we are continuing this extension for an additional 45 days (to 25th September 2020). 因此,将支持新发布的 2005 更新以及以前的三个更新版本(2002、1910 和 1908 或 N-3)之一。As a result, the newly released 2005 update and any one of the three previous update versions (2002, 1910, and 1908, or N-3) will be supported. 45 天后(2020 年 9 月 25 日后),我们将恢复标准支持策略,这意味着支持的版本将为 2005、2002 和 1910 或 N-2。After these 45 days (after 25th September 2020), we will return to our standard support policy, meaning the supported versions will then be 2005, 2002 and 1910, or N-2.

更新类型Update type

Azure Stack Hub 2005 更新内部版本类型为“完整”。The Azure Stack Hub 2005 update build type is Full.

与以前的更新相比,2005 更新包更大。The 2005 update package is larger in size compared to previous updates. 增加的大小会导致下载时间更长。The increased size results in longer download times. 此更新将长时间保留为“正在准备”状态,操作员可预期此过程所需的时间长于以前的更新。The update will remain in the Preparing state for a long time, and operators can expect this process to take longer than with previous updates. 在我们的内部测试中,2005 更新的预期运行时间如下 - 4 个节点:13-20 小时,8 个节点:16-26 小时,12 个节点:19-32 小时,16 个节点:22-38 小时。The 2005 update has had the following expected runtimes in our internal testing- 4 nodes: 13-20 hours, 8 nodes: 16-26 hours, 12 nodes: 19-32 hours, 16 nodes: 22-38 hours. 确切的更新运行时间通常取决于租户工作负荷在系统上使用的容量、系统网络连接(如果已连接到 Internet),以及系统的硬件规格。Exact update runtimes typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware specifications. 运行时间短于或长于预期值并不常见。因此,除非更新失败,否则不需要 Azure Stack Hub 操作员执行操作。Runtimes that are shorter or longer than the expected value are not uncommon and do not require action by Azure Stack Hub operators unless the update fails. 此运行时近似值特定于 2005 更新,不应与其他 Azure Stack Hub 更新进行比较。This runtime approximation is specific to the 2005 update and should not be compared to other Azure Stack Hub updates.

有关更新内部版本类型的详细信息,请参阅在 Azure Stack Hub 中管理更新For more information about update build types, see Manage updates in Azure Stack Hub.

新增功能What's new

  • 此内部版本支持 3 个新的 GPU VM 类型:NCv3 (Nvidia V100)、NVv4 (AMD MI25) 和 NCas_v4 (NVIDIA T4) VM 大小。This build offers support for 3 new GPU VM types: NCv3 (Nvidia V100), NVv4 (AMD MI25), and NCas_v4 (NVIDIA T4) VM sizes. 对于具有正确硬件并且已加入 Azure Stack Hub GPU 预览计划的用户,VM 部署将会成功。VM deployments will be successful for those who have the right hardware and are onboarded to the Azure Stack Hub GPU preview program. 如果你感兴趣,请在 https://aka.ms/azurestackhubgpupreview 注册 GPU 预览计划。If you are interested, sign up for the GPU preview program at https://aka.ms/azurestackhubgpupreview. 有关详细信息,请参阅此处For more information, see.
  • 此版本提供了一项支持自动修复的新功能,可检测故障、评估影响并安全地缓解系统问题。This release provides a new feature that enables an autonomous healing capability, which detects faults, assesses impact, and safely mitigates system issues. 借助此功能,我们可以努力提高系统的可用性,而无需手动干预。With this feature, we are working towards increased availability of the system without manual intervention. 对于版本 2005 及更高版本,客户遇到警报将会减少。With release 2005 and later, customers will experience a reduction in the number of alerts. 除非另行通知,否则此管道中的任何故障都不需要 Azure Stack Hub 操作员进行操作。Any failure in this pipeline doesn't require action by Azure Stack Hub operators unless notified.
  • Azure Stack Hub 管理门户中有一个新选项,气隙/断开连接的 Azure Stack Hub 客户可使用该选项在本地保存日志。There is a new option in the Azure Stack Hub admin portal for air-gapped/disconnected Azure Stack Hub customers, to save logs locally. 当 Azure Stack Hub 与 Azure 断开连接时,可以将日志存储在本地 SMB 共享中。You can store the logs in a local SMB share when Azure Stack Hub is disconnected from Azure.
  • 如果系统操作已在进行中,Azure Stack Hub 管理门户现在会阻止某些操作。The Azure Stack Hub admin portal now blocks certain operations if a system operation is already in progress. 例如,如果正在进行更新,则不能添加新的缩放单元节点。For example, if an update is in progress, it is not possible to add a new scale unit node.
  • 此版本在 1910 之前创建的 VM 中提供了与 Azure 更高的结构一致性。This release provides more fabric consistency with Azure on VMs created pre-1910. 对于 1910,Azure 宣布所有新创建的 VM 将使用 wireserver 协议,使客户能够使用与 Azure 相同的 WALA 代理和 Windows 来宾代理,从而更轻松地在 Azure Stack Hub 上使用 Azure 映像。In 1910, Azure announced that all newly created VMs will use the wireserver protocol, enabling customers to use the same WALA agent and Windows guest agent as Azure, making it easier to use Azure images on Azure Stack Hub. 在此版本中,将自动迁移所有在 1910 前创建的 VM 以使用 wireserver 协议。With this release, all VMs created earlier than 1910 are automatically migrated to use the wireserver protocol. 这也提供了更可靠的 VM 创建、VM 扩展部署以及稳定状态运行时间方面的改进。This also brings more reliable VM creation, VM extension deployment, and improvements in steady state uptime.
  • Azure Stack Hub 存储现在支持 Azure 存储服务 API 版本2019-02-02。Azure Stack Hub storage now supports Azure Storage services APIs version 2019-02-02. 对于 Azure 客户端库,它与新的 REST API 版本兼容。For Azure client libraries, that is compatible with the new REST API version. 有关详细信息,请参阅 Azure Stack Hub 存储开发工具For more information, see Azure Stack Hub storage development tools.
  • Azure Stack Hub 现在支持最新版本的 CreateUiDefinition(版本 2)Azure Stack Hub now supports the latest version of CreateUiDefinition (version 2).
  • 批处理 VM 部署的新指南。New guidance for batched VM deployments. 有关详细信息,请参阅此文For more information see this article.
  • Azure Stack Hub 市场 CoreOS 容器 Linux 项的生命周期即将结束The Azure Stack Hub Marketplace CoreOS Container Linux item is approaching its end-of-life. 有关详细信息,请参阅从 CoreOS 容器 Linux 迁移For more information, see Migrating from CoreOS Container Linux.

改进Improvements

  • 对存储基础结构群集服务日志和事件的改进。Improvements to Storage infrastructure cluster service logs and events. 存储基础结构群集服务的日志和事件的保留时间最长为 14 天,以便更好地进行诊断和故障排除。Logs and events of Storage infrastructure cluster service will be kept for up to 14 days, for better diagnostics and troubleshooting.
  • 提高启动和停止 Azure Stack Hub 的可靠性的改进。Improvements that increase reliability of starting and stopping Azure Stack Hub.
  • 使用分散化和删除依赖项减少更新运行时的改进。Improvements that reduce the update runtime by using decentralization and removing dependencies. 与 2002 更新相比,4 个节点标记更新时间从 15-42 小时缩短到 13-20 小时。Compared to the 2002 update, the 4 nodes stamp update time is reduced from 15-42 hours to 13-20 hours. 8 个节点标记更新时间从 20-50 小时缩短到 16-26 小时。8 nodes is reduced from 20-50 hours to 16-26 hours. 12 个节点标记更新时间从 20-60 小时缩短到 19-32 小时。12 nodes is reduced from 20-60 hours to 19-32 hours. 16 个节点标记更新时间从 25-70 小时缩短到 22-38 小时。16 nodes is reduced from 25-70 hours to 22-38 hours. 确切的更新运行时间通常取决于租户工作负荷在系统上使用的容量、系统网络连接(如果已连接到 Internet),以及系统的硬件规格。Exact update runtimes typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware specifications.
  • 现在,如果发生某些无法恢复的错误,更新会提前失败。The update now fails early if there are certain unrecoverable errors.
  • 提高了从 Internet 下载时更新包的复原能力。Improved resiliency of the update package while downloading from the internet.
  • 提高了对 VM 停止解除分配的复原能力。Improved resiliency of stop-deallocating a VM.
  • 提高了网络控制器主机代理的复原能力。Improved resiliency of the Network Controller Host Agent.
  • 向 syslog 消息的 CEF 有效负载添加了其他字段,以报告用于连接到特权终结点和恢复终结点的源 IP 和帐户。Added additional fields to the CEF payload of the syslog messages to report the source IP and the account used to connect to the privileged endpoint and the recovery endpoint. 有关详细信息,请参阅通过 Syslog 转发将 Azure Stack Hub 与监视解决方案集成See Integrate Azure Stack Hub with monitoring solutions using syslog forwarding for details.
  • 向通过 syslog 客户端发出的事件列表添加了 Windows Defender 事件(事件 ID 5001、5010、5012)。Added Windows Defender events (Event IDs 5001, 5010, 5012) to the list of events emitted via the syslog client.
  • 在 Azure Stack 管理员门户中为 Windows Defender 相关事件添加了警报,以报告 Defender 平台和签名版本不一致以及无法对检测到的恶意软件采取操作。Added alerts in the Azure Stack Administrator portal for Windows Defender-related events, to report on Defender platform and signatures version inconsistencies and failure to take actions on detected malware.
  • 添加了将 Azure Stack Hub 集成到数据中心时对 4 个边界设备的支持。Added support for 4 Border Devices when integrating Azure Stack Hub into your datacenter.

更改Changes

  • 从管理员门户中删除了停止、关闭和重启基础结构角色实例的操作。Removed the actions to stop, shut down, and restart an infrastructure role instance from the admin portal. 还在 Fabric 资源提供程序中删除了相应的 API。The corresponding APIs have also been removed in the Fabric Resource Provider. Azure Stack Hub 的管理员 RM 模块和 AZ 预览版中的以下 PowerShell cmdlet 不再有效:Stop-AzsInfrastructureRoleInstance、Disable-InfrastructureRoleInstance 和 Restart-InfrastructureRoleInstance 。The following PowerShell cmdlets in the admin RM module and AZ preview for Azure Stack Hub no longer work: Stop-AzsInfrastructureRoleInstance, Disable-InfrastructureRoleInstance, and Restart-InfrastructureRoleInstance. 将从 Azure Stack Hub 的下一个管理员 AZ 模块版本中删除这些 cmdlet。These cmdlets will be removed from the next admin AZ module release for Azure Stack Hub.
  • Azure Stack Hub 2005 现在仅支持 Azure Stack Hub 2020(版本 87.x)上的应用服务Azure Stack Hub 2005 now only supports App Service on Azure Stack Hub 2020 (versions 87.x).

修复项Fixes

  • 修复了以下问题:修复缩放单元节点可能因找不到基础 OS 映像的路径而失败。Fixed an issue that could cause a repair scale unit node to fail because it could not find the path to the base OS image.
  • 修复了对修复缩放单元节点具有级联影响的支持基础结构角色的横向缩减和横向扩展的问题。Fixed an issue with scale-in and scale-out for the support infrastructure role that has a cascading effect on repairing scale unit nodes.
  • 修复了以下问题:当操作员通过“所有服务”>“计算”>“VM 映像”>“添加”,将自己的映像添加到 Azure Stack Hub 管理员门户时,不允许使用 .VHD 扩展(而不是 .vhd)。Fixed an issue in which the .VHD extension (instead of .vhd) was not allowed when operators added their own images to the Azure Stack Hub administrator portal on All services > Compute > VM Images > Add.
  • 修复了以下问题:在执行任何其他 VM 更新操作(添加磁盘、标记等)后,以前的 VM 重启操作随后出现意外重启。Fixed an issue in which a previous VM restart operation caused a subsequent unexpected restart after any other VM update operation (adding disks, tags, etc.).
  • 修复了创建重复 DNS 区域导致门户停止响应的问题。Fixed an issue in which creating a duplicate DNS zone caused the portal to stop responding. 它现在应显示相应的错误。It should now show an appropriate error.
  • 修复了以下问题:Get-AzureStackLogs 不收集所需日志来解决网络问题。Fixed an issue in which Get-AzureStackLogs was not collecting the required logs to troubleshoot networking issues.
  • 修复了以下问题:门户允许附加的 NIC 比它实际允许的 NIC 少。Fixed an issue in which the portal allowed fewer NICs to be attached than what it actually allows.
  • 修复了代码完整性策略,以免为某些内部软件发出违规事件。Fixed code integrity policy to not emit violation events for certain internal software. 这可减少通过 syslog 客户端发出的代码完整性违规事件产生的干扰。This reduces noise in code integrity violation events emitted via syslog client.
  • 修复了 Set-TLSPolicy cmdlet 以强制实施新策略,而无需重启 https 服务或重启主机。Fixed Set-TLSPolicy cmdlet to enforce new policy without requiring restart of the https service or the reboot of the host.
  • 修复了以下问题:使用 Linux NTP 服务器错误地在管理门户中生成警报。Fixed an issue in which using a Linux NTP server erroneously generates alerts in the administration portal.
  • 修复了以下问题:备份控制器服务实例的故障转移导致禁用自动备份。Fixed an issue where failover of Backup Controller service instance resulted in automatic backups getting disabled.
  • 修复了以下问题:在基础结构服务未建立 Internet 连接的情况下,内部机密轮替失败。Fixed an issue where internal secret rotation fails when infrastructure services do not have internet connectivity.
  • 修复了用户无法使用 Azure Stack Hub 门户查看订阅权限的问题。Fixed an issue in which users could not view subscription permissions using the Azure Stack Hub portals.

安全更新Security updates

有关此 Azure Stack Hub 更新中的安全更新的信息,请参阅 Azure Stack Hub 安全更新For information about security updates in this update of Azure Stack Hub, see Azure Stack Hub security updates.

修补程序Hotfixes

Azure Stack Hub 定期发布修补程序。Azure Stack Hub releases hotfixes on a regular basis. 从 2005 版开始,更新到新的主版本(如 1.2002.x 到1.2005.x)时,新的主版本中最新的修补程序(如果有)会自动安装。Starting with the 2005 release, when you update to a new major version (for example, 1.2002.x to 1.2005.x), the latest hotfixes (if any) in the new major version are installed automatically. 在此之后,如果发布了适用于你的内部版本的修补程序,则应安装它。From that point forward, if a hotfix is released for your build, you should install it.

备注

Azure Stack Hub 修补程序版本是累积性的;你只需安装最新的修补程序即可获取该版本的任何以前修补程序版本中包含的所有修补程序。Azure Stack Hub hotfix releases are cumulative; you only need to install the latest hotfix to get all fixes included in any previous hotfix releases for that version.

有关详细信息,请参阅我们的服务策略For more information, see our servicing policy.

Azure Stack Hub 修补程序仅适用于 Azure Stack Hub 集成系统;请勿尝试在 ASDK 上安装修补程序。Azure Stack Hub hotfixes are only applicable to Azure Stack Hub integrated systems; do not attempt to install hotfixes on the ASDK.

先决条件:应用 2005 更新之前Prerequisites: Before applying the 2005 update

必须在包含以下修补程序的版本 2002 中应用 Azure Stack Hub 版本 2005:The 2005 release of Azure Stack Hub must be applied on the 2002 release with the following hotfixes:

成功应用 2005 更新之后After successfully applying the 2005 update

从 2005 版开始,更新到新的主版本(如 1.2002.x 到1.2005.x)时,新的主版本中最新的修补程序(如果有)会自动安装。Starting with the 2005 release, when you update to a new major version (for example, 1.2002.x to 1.2005.x), the latest hotfixes (if any) in the new major version are installed automatically.

安装 2005 之后,如果以后发布了任何 2005 修补程序,应安装这些修补程序:After the installation of 2005, if any 2005 hotfixes are subsequently released, you should install them:

2002 内部版本参考2002 build reference

Azure Stack Hub 2002 更新内部版本号为 1.2002.0.35The Azure Stack Hub 2002 update build number is 1.2002.0.35.

重要

在 Azure Stack Hub 2002 更新中,我们暂时扩展了 Azure Stack Hub 支持策略声明With the Azure Stack Hub 2002 update, We are temporarily extending our Azure Stack Hub support policy statements. 我们正在与世界各地应对 COVID-19 的客户合作,这些客户可能正在就其 Azure Stack Hub 系统以及如何更新和管理这些系统做出重要决策,以确保其数据中心业务操作继续正常运行。We are working with customers around the world who are responding to COVID-19 and who may be making important decisions about their Azure Stack Hub systems, how they are updated and managed, and as a result, ensuring their data center business operations continue to operate normally. 为支持客户,我们提供了临时支持策略更改扩展,以包括以前的三个更新版本。In support of our customers, we are offering a temporary support policy change extension to include three previous update versions. 因此,将支持新发布的 2002 更新以及以前的三个更新版本(例如 1910、1908 和 1907)之一。As a result, the newly released 2002 update and any one of the three previous update versions (e.g. 1910, 1908, and 1907) will be supported.

更新类型Update type

Azure Stack Hub 2002 更新内部版本类型为“完整”。The Azure Stack Hub 2002 update build type is Full.

与以前的更新相比,2002 更新程序包更大。The 2002 update package is larger in size compared to previous updates. 增加的大小会导致下载时间更长。The increased size results in longer download times. 此更新将长时间保留为“正在准备”状态,操作员可预期此过程所需的时间长于以前的更新。The update will remain in the Preparing state for a long time, and operators can expect this process to take longer than with previous updates. 在我们的内部测试中,2002 更新的预期运行时间如下 - 4 个节点:15-42 小时,8 个节点:20-50 小时,12 个节点:20-60 小时,16 个节点:25-70 小时。The 2002 update has had the following expected runtimes in our internal testing- 4 nodes: 15-42 hours, 8 nodes: 20-50 hours, 12 nodes: 20-60 hours, 16 nodes: 25-70 hours. 确切的更新运行时间通常取决于租户工作负荷在系统上使用的容量、系统网络连接(如果已连接到 Internet),以及系统的硬件规格。Exact update runtimes typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware specifications. 运行时间短于或长于预期值并不常见。因此,除非更新失败,否则不需要 Azure Stack Hub 操作员执行操作。Runtimes that are shorter or longer than the expected value are not uncommon and do not require action by Azure Stack Hub operators unless the update fails. 此运行时近似值特定于 2002 更新,不应与其他 Azure Stack Hub 更新进行比较。This runtime approximation is specific to the 2002 update and should not be compared to other Azure Stack Hub updates.

有关更新内部版本类型的详细信息,请参阅在 Azure Stack Hub 中管理更新For more information about update build types, see Manage updates in Azure Stack Hub.

新增功能What's new

  • 提供了基于 AzureRM 的 Azure Stack Hub 管理员 PowerShell 模块的一个新版本 (1.8.1)。A new version (1.8.1) of the Azure Stack Hub admin PowerShell modules based on AzureRM is available.
  • 已推出新版 Azure Stack Hub 管理员 REST API。A new version of the Azure Stack Hub admin REST API is available. 可在 API 参考中找到有关终结点和中断性变更的详细信息。You can find details about endpoints and breaking changes in the API Reference.
  • 将在 2020 年 4 月 15 日为 Azure Stack Hub 发布新的 Azure PowerShell 租户模块。New Azure PowerShell tenant modules will be released for Azure Stack Hub on April 15, 2020. 当前使用的 Azure RM 模块会继续工作,但在内部版本 2002 后将不再更新。The currently used Azure RM modules will continue to work, but will no longer be updated after build 2002.
  • 在 Azure Stack Hub 管理员门户上添加了新的警告警报,用于报告所配置的 syslog 服务器的连接问题。Added new warning alert on the Azure Stack Hub administrator portal to report on connectivity issues with the configured syslog server. 警报标题是 Syslog 客户端发送 Syslog 消息时遇到网络问题Alert title is The Syslog client encountered a networking issue while sending a Syslog message.
  • 在 Azure Stack Hub 管理员门户上添加了新的警告警报,用于报告网络时间协议 (NTP) 服务器的连接问题。Added new warning alert on the Azure Stack Hub administrator portal to report on connectivity issues with the Network Time Protocol (NTP) server. 警报标题是 [node name] 上的时间来源无效Alert title is Invalid Time Source on [node name].
  • 由于 2002 中与 TLS 限制相关的一个中断性变更,Java SDK 发布了新的程序包。The Java SDK released new packages due to a breaking change in 2002 related to TLS restrictions. 你必须安装新的 Java SDK 依赖项。You must install the new Java SDK dependency. 可以在 Java 和 API 版本配置文件中找到相关说明。You can find the instructions at Java and API version profiles.
  • 新版 (1.0.5.10) System Center Operations Manager - Azure Stack Hub MP 已发布,该版本是运行 2002 的所有系统所必需的,因为存在中断性 API 变更。A new version (1.0.5.10) of the System Center Operations Manager - Azure Stack Hub MP is available and required for all systems running 2002 due to breaking API changes. API 变更会影响备份和存储性能仪表板,建议你先将所有系统更新为 2002,然后再更新 MP。The API changes impact the backup and storage performance dashboards, and it is recommended that you first update all systems to 2002 before updating the MP.

改进Improvements

  • 此更新包含对更新过程的更改,这些更改会显著提高将来的完整更新的性能。This update contains changes to the update process that significantly improve the performance of future full updates. 这些更改将随 2002 发行版之后的下一次完整更新生效,具体目标是提高完整更新期间对主机操作系统进行更新的阶段的性能。These changes take effect with the next full update after the 2002 release, and specifically target improving the performance of the phase of a full update in which the host operating systems are updated. 提高主机操作系统更新的性能会大大减小租户工作负荷在完整更新过程中受影响的时间窗口。Improving the performance of host operating system updates significantly reduces the window of time in which tenant workloads are impacted during full updates.
  • Azure Stack Hub 就绪性检查器工具现在使用分配给 AD Graph 的所有 TCP IP 端口来验证 AD Graph 集成。The Azure Stack Hub readiness checker tool now validates AD Graph integration using all TCP IP ports allocated to AD Graph.
  • 脱机联合工具已更新,改进了可靠性。The offline syndication tool has been updated with reliability improvements. 该工具在 GitHub 上不再可用,已移到 PowerShell 库中。The tool is no longer available on GitHub, and has been moved to the PowerShell Gallery. 有关详细信息,请参阅将市场项下载到 Azure Stack HubFor more information, see Download Marketplace items to Azure Stack Hub.
  • 将引入一项新的监视功能。A new monitoring capability is being introduced. 针对物理主机和基础结构 VM 的磁盘空间不足警报将由平台自动修正。仅当此操作失败时,该警报才会显示在 Azure Stack Hub 管理员门户中,供操作员执行操作。The low disk space alert for physical hosts and infrastructure VMs will be auto-remediated by the platform and only if this action fails will the alert be visible in the Azure Stack Hub administrator portal, for the operator to take action.
  • 诊断日志收集的改进。Improvements to diagnostic log collection. 新的体验优化和简化了诊断日志收集,它不需要预先配置 blob 存储帐户。The new experience streamlines and simplifies diagnostic log collection by removing the need to configure a blob storage account in advance. 存储环境已预先配置,因此你可以在创建支持案例之前发送日志,并减少支持人员通话时间。The storage environment is preconfigured so that you can send logs before opening a support case, and spend less time on a support call.
  • 主动日志收集和按需日志收集所花费的时间已缩短 80%。Time taken for both Proactive Log Collection and the on-demand log collection has been reduced by 80%. 日志收集时间可能会比此预期值长,但不需要 Azure Stack Hub 操作员执行操作,除非日志收集失败。Log collection time can take longer than this expected value but doesn't require action by Azure Stack Hub operators unless the log collection fails.
  • 启动更新后,“更新”边栏选项卡中会显示 Azure Stack Hub 更新程序包的下载进度。The download progress of an Azure Stack Hub update package is now visible in the update blade after an update is initiated. 这仅适用于那些选择通过自动下载功能准备更新程序包且已连接的 Azure Stack Hub 系统。This only applies to connected Azure Stack Hub systems that choose to prepare update packages via automatic download.
  • 改进了网络控制器主机代理的可靠性。Reliability improvements to the Network Controller Host agent.
  • 引入了一个名为 DNS Orchestrator 的新微服务,它改进了在修补和更新期间内部 DNS 服务的复原逻辑。Introduced a new micro-service called DNS Orchestrator that improves the resiliency logic for the internal DNS services during patch and update.
  • 添加了一个新的请求验证,用于在创建 VM 时使启动诊断存储帐户参数的无效 blob URI 失败。Added a new request validation to fail invalid blob URIs for the boot diagnostic storage account parameter while creating VMs.
  • 为 Rdagent 和主机代理(主机上用于方便执行 VM CRUD 操作的两个服务)添加了自动修正和日志记录改进。Added auto-remediation and logging improvements for Rdagent and Host agent - two services on the host that facilitate VM CRUD operations.
  • 向市场管理添加了一项新功能,使 Microsoft 能够添加属性,目的是防止管理员下载由于存在各种属性(例如 Azure Stack 版本或计费模型)而与其 Azure Stack 不兼容的市场产品。Added a new feature to marketplace management that enables Microsoft to add attributes that block administrators from downloading marketplace products that are incompatible with their Azure Stack, due to various properties, such as the Azure Stack version or billing model. 只有 Microsoft 才能添加这些属性。Only Microsoft can add these attributes. 有关详细信息,请参阅使用门户下载市场项For more information, see Use the portal to download marketplace items.

更改Changes

  • 管理员门户现在会指示操作是否正在进行,并在 Azure Stack 区域旁显示一个图标。The administrator portal now indicates if an operation is in progress, with an icon next to the Azure Stack region. 当你将鼠标悬停在该图标上时,它会显示操作的名称。When you hover over the icon, it displays the name of the operation. 这使你可以识别正在运行的系统后台操作;例如,可能会运行几个小时的备份作业或存储扩展。This enables you to identify running system background operations; for example, a backup job or a storage expansion which can run for several hours.

  • 以下管理员 API 已弃用:The following administrator APIs have been deprecated:

    资源提供程序Resource provider 资源Resource 版本Version
    Microsoft.Storage.AdminMicrosoft.Storage.Admin 农场farms 2015-12-01-preview2015-12-01-preview
    Microsoft.Storage.AdminMicrosoft.Storage.Admin farms/acquisitionsfarms/acquisitions 2015-12-01-preview2015-12-01-preview
    Microsoft.Storage.AdminMicrosoft.Storage.Admin farms/sharesfarms/shares 2015-12-01-preview2015-12-01-preview
    Microsoft.Storage.AdminMicrosoft.Storage.Admin farms/storageaccountsfarms/storageaccounts 2015-12-01-preview2015-12-01-preview
  • 以下管理员 API 已替换为较新版本 (2018-09-01):The following administrator APIs have been replaced by a newer version (2018-09-01):

    资源提供程序Resource provider 资源Resource 版本Version
    Microsoft.Backup.AdminMicrosoft.Backup.Admin backupLocationbackupLocation 2016-05-012016-05-01
    Microsoft.Backup.AdminMicrosoft.Backup.Admin backupsbackups 2016-05-012016-05-01
    Microsoft.Backup.AdminMicrosoft.Backup.Admin 操作operations 2016-05-012016-05-01
  • 使用 PowerShell 创建 Windows VM 时,如果希望 VM 部署扩展,请确保添加 provisionvmagent 标志。When creating a Windows VM using PowerShell, make sure to add the provisionvmagent flag if you want the VM to deploy extensions. 如果没有此标志,则会创建不带来宾代理的 VM,这将移除部署 VM 扩展的功能:Without this flag, the VM is created without the guest agent, removing the ability to deploy VM extensions:

    $VirtualMachine = Set-AzureRmVMOperatingSystem `
       -VM $VirtualMachine `
       -Windows `
       -ComputerName "MainComputer" `
       -Credential $Credential -ProvisionVMAgent
    

修复项Fixes

  • 修复了在虚拟机的同一 NIC 上添加多个公共 IP 会导致 Internet 连接问题的问题。Fixed an issue where adding more than one public IP on the same NIC on a Virtual Machine resulted in internet connectivity issues. 现在,具有两个公共 IP 的 NIC 能够按预期方式工作。Now, a NIC with two public IPs works as expected.
  • 修复了一个导致系统引发警报的问题,该警报指出需要配置 Azure AD 主目录。Fixed an issue that caused the system to raise an alert indicating that the Azure AD home directory needs to be configured.
  • 修复了一个导致警报无法自动关闭的问题。Fixed an issue that caused an alert to not automatically close. 该警报指出必须配置 Azure AD 主目录,但是,即使问题得到缓解,该警报也不关闭。The alert indicated that the Azure AD home directory must be configured, but did not close even after the issue was mitigated.
  • 修复了一个因更新资源提供程序存在内部故障而导致更新在更新准备阶段失败的问题。Fixed an issue that caused updates to fail during the update preparation phase as a result of internal failures of the update resource provider.
  • 修复了一个在执行 Azure Stack Hub 机密轮换后导致附加产品资源提供程序操作失败的问题。Fixed an issue causing add-on resource provider operations to fail after performing Azure Stack Hub secret rotation.
  • 修复了一个问题,该问题是由于 ERCS 角色的内存压力导致 Azure Stack Hub 更新失败的常见原因。Fixed an issue that was a common cause of Azure Stack Hub update failures due to memory pressure on the ERCS role.
  • 修复了“更新”边栏选项卡中的一个 bug:在 Azure Stack Hub 更新的准备阶段,更新状态显示为“正在安装”而不是“正在准备”。Fixed a bug in the update blade in which the update status showed as Installing instead of Preparing during the preparation phase of an Azure Stack Hub update.
  • 修复了虚拟交换机上的 RSC 功能导致不一致并丢弃流经负载均衡器的流量的问题。Fixed an issue where the RSC feature on the virtual switches was creating inconsistences and dropping the traffic flowing through a load balancer. 现在,RSC 功能默认处于禁用状态。The RSC feature is now disabled by default.
  • 修复了问题:NIC 上的多个 IP 配置导致流量在出站连接中被错误路由和阻止。Fixed an issue where multiple IP configurations on a NIC was causing traffic to be misrouted and prevented outbound connectivity.
  • 修复了在 NIC 的 MAC 地址被缓存的情况下将该地址分配给另一资源导致 VM 部署失败的问题。Fixed an issue where the MAC address of a NIC was being cached, and assigning of that address to another resource was causing VM deployment failures.
  • 修复了来自零售渠道的 Windows VM 映像无法通过 AVMA 激活其许可证的问题。Fixed an issue where Windows VM images from the RETAIL channel could not have their license activated by AVMA.
  • 修复了当 VM 所请求的虚拟核心数等于节点的物理核心数时无法创建 VM 的问题。Fixed an issue where VMs would fail to be created if the number of virtual cores requested by the VM was equal to the node's physical cores. 我们现在允许 VM 的虚拟核心数等于或少于节点的物理核心数。We now allow VMs to have virtual cores equal to or less than the node's physical cores.
  • 修复了不允许将许可证类型设置为“null”以将即用即付映像切换到 BYOL 的问题。Fixed an issue where we do not allow the license type to be set to "null" to switch pay-as-you-go images to BYOL.
  • 修复了一个问题,现在允许向 VM 规模集添加扩展。Fixed an issue to allow extensions to be added to a VM scale set.

安全更新Security updates

有关此 Azure Stack Hub 更新中的安全更新的信息,请参阅 Azure Stack Hub 安全更新For information about security updates in this update of Azure Stack Hub, see Azure Stack Hub security updates.

修补程序Hotfixes

Azure Stack Hub 定期发布修补程序。Azure Stack Hub releases hotfixes on a regular basis. 将 Azure Stack Hub 更新到 2002 之前,请务必先安装 1910 的最新 Azure Stack Hub 修补程序。Be sure to install the latest Azure Stack Hub hotfix for 1910 before updating Azure Stack Hub to 2002.

备注

Azure Stack Hub 修补程序版本是累积性的;你只需安装最新的修补程序即可获取该版本的任何以前修补程序版本中包含的所有修补程序。Azure Stack Hub hotfix releases are cumulative; you only need to install the latest hotfix to get all fixes included in any previous hotfix releases for that version.

Azure Stack Hub 修补程序仅适用于 Azure Stack Hub 集成系统;请勿尝试在 ASDK 上安装修补程序。Azure Stack Hub hotfixes are only applicable to Azure Stack Hub integrated systems; do not attempt to install hotfixes on the ASDK.

有关修补程序的详细信息,请参阅 Azure Stack Hub 服务策略For more information about hotfixes, see the Azure Stack Hub servicing policy.

先决条件:应用 2002 更新之前Prerequisites: Before applying the 2002 update

必须在包含以下修补程序的版本 1910 中应用 Azure Stack Hub 版本 2002:The 2002 release of Azure Stack Hub must be applied on the 1910 release with the following hotfixes:

成功应用 2002 更新之后After successfully applying the 2002 update

安装此更新之后,请安装所有适用的修补程序。After the installation of this update, install any applicable hotfixes.

1910 内部版本参考1910 build reference

Azure Stack Hub 1910 更新内部版本号为 1.1910.0.58The Azure Stack Hub 1910 update build number is 1.1910.0.58.

更新类型Update type

从版本 1908 开始,运行 Azure Stack Hub 的底层操作系统已更新为 Windows Server 2019。Starting with 1908, the underlying operating system on which Azure Stack Hub runs was updated to Windows Server 2019. 此更新可以实现核心基础增强,并将更多功能引入 Azure Stack Hub。This update enables core fundamental enhancements and the ability to bring additional capabilities to Azure Stack Hub.

Azure Stack Hub 1910 更新内部版本类型为“快速”。The Azure Stack Hub 1910 update build type is Express.

与以前的更新相比,1910 更新包更大,因此下载时间更长。The 1910 update package is larger in size compared to previous updates, which results in longer download times. 此更新将长时间保留为“正在准备”状态,操作员可预期此过程所需的时间长于以前的更新。The update will remain in the Preparing state for a long time and operators can expect this process to take longer than previous updates. 无论 Azure Stack Hub 环境中有多少个物理节点,完成 1910 更新的预估时间都大约为 10 小时。The expected time for the 1910 update to complete is approximately 10 hours, regardless of the number of physical nodes in your Azure Stack Hub environment. 确切的更新运行时间通常取决于租户工作负荷在系统上使用的容量、系统网络连接(如果已连接到 Internet),以及系统的硬件规格。Exact update runtimes typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware specifications. 运行时间超过预期值并不常见,除非更新失败,否则无需 Azure Stack Hub 操作员采取措施。Runtimes lasting longer than the expected value aren't uncommon and don't require action by Azure Stack Hub operators unless the update fails. 此运行时近似值特定于 1910 更新,不应与其他 Azure Stack Hub 更新进行比较。This runtime approximation is specific to the 1910 update and shouldn't be compared to other Azure Stack Hub updates.

有关更新内部版本类型的详细信息,请参阅在 Azure Stack Hub 中管理更新For more information about update build types, see Manage updates in Azure Stack Hub.

新增功能What's new

  • 管理员门户现在会在区域属性菜单中显示特权终结点 IP 地址,以方便进行发现。The administrator portal now shows the privileged endpoint IP addresses in the region properties menu for easier discovery. 此外,还会显示当前配置的时间服务器和 DNS 转发器。In addition, it shows the current configured time server and DNS forwarders. 有关详细信息,请参阅使用 Azure Stack Hub 中的特权终结点For more information, see Use the privileged endpoint in Azure Stack Hub.

  • 现在,在发生错误时,Azure Stack Hub 运行状况和监视系统可针对各种硬件组件引发警报。The Azure Stack Hub health and monitoring system can now raise alerts for various hardware components if an error happens. 这些警报需要额外的配置。These alerts require additional configuration. 有关详细信息,请参阅监视 Azure Stack Hub 硬件组件For more information, see Monitor Azure Stack Hub hardware components.

  • Azure Stack Hub 的 Cloud-init 支持:Cloud-init 是一种广泛使用的方法,用于在首次启动 Linux VM 时对其进行自定义。Cloud-init support for Azure Stack Hub: Cloud-init is a widely used approach to customize a Linux VM as it boots for the first time. 可使用 cloud-init 来安装程序包和写入文件,或者配置用户和安全性。You can use cloud-init to install packages and write files, or to configure users and security. 由于是在初始启动过程中调用 cloud-init,因此无需额外的步骤且无需代理来应用配置。Because cloud-init is called during the initial boot process, there are no additional steps or required agents to apply your configuration. 市场中的 Ubuntu 映像已更新为支持使用 cloud-init 进行预配。The Ubuntu images on the marketplace have been updated to support cloud-init for provisioning.

  • 与 Azure 一样,Azure Stack Hub 现在支持所有 Windows Azure Linux 代理版本。Azure Stack Hub now supports all Windows Azure Linux Agent versions as Azure.

  • 提供了新版 Azure Stack Hub 管理员 PowerShell 模块。A new version of Azure Stack Hub admin PowerShell modules is available.

  • 2020 年 4 月 15 日为 Azure Stack Hub 发布了新的 Azure PowerShell 租户模块。New Azure PowerShell tenant modules were released for Azure Stack Hub on April 15, 2020. 当前使用的 Azure RM 模块会继续工作,但在内部版本 2002 后将不再更新。The currently used Azure RM modules will continue to work, but will no longer be updated after build 2002.

  • 已在特权终结点 (PEP) 中添加 Set-AzSDefenderManualUpdate cmdlet,用于为 Azure Stack Hub 基础结构中的 Windows Defender 定义配置手动更新。Added the Set-AzSDefenderManualUpdate cmdlet in the privileged endpoint (PEP) to configure the manual update for Windows Defender definitions in the Azure Stack Hub infrastructure. 有关详细信息,请参阅更新 Azure Stack Hub 上的 Windows Defender AntivirusFor more information, see Update Windows Defender Antivirus on Azure Stack Hub.

  • 已在特权终结点 (PEP) 中添加 Get-AzSDefenderManualUpdate cmdlet,用于为 Azure Stack Hub 基础结构中的 Windows Defender 定义检索手动更新配置。Added the Get-AzSDefenderManualUpdate cmdlet in the privileged endpoint (PEP) to retrieve the configuration of the manual update for Windows Defender definitions in the Azure Stack Hub infrastructure. 有关详细信息,请参阅更新 Azure Stack Hub 上的 Windows Defender AntivirusFor more information, see Update Windows Defender Antivirus on Azure Stack Hub.

  • 已在特权终结点 (PEP) 中添加 Set-AzSDnsForwarder cmdlet,用于在 Azure Stack Hub 中更改 DNS 服务器的转发器设置。Added the Set-AzSDnsForwarder cmdlet in the privileged endpoint (PEP) to change the forwarder settings of the DNS servers in Azure Stack Hub. 有关 DNS 配置的详细信息,请参阅 Azure Stack Hub 数据中心 DNS 集成For more information about DNS configuration, see Azure Stack Hub datacenter DNS integration.

  • 已在特权终结点 (PEP) 中添加 Get-AzSDnsForwarder cmdlet,用于在 Azure Stack Hub 中检索 DNS 服务器的转发器设置。Added the Get-AzSDnsForwarder cmdlet in the privileged endpoint (PEP) to retrieve the forwarder settings of the DNS servers in Azure Stack Hub. 有关 DNS 配置的详细信息,请参阅 Azure Stack Hub 数据中心 DNS 集成For more information about DNS configuration, see Azure Stack Hub datacenter DNS integration.

  • 添加了对使用 AKS 引擎管理 Kubernetes 集群的支持。Added support for management of Kubernetes clusters using the AKS engine. 从此更新开始,客户可以部署生产 Kubernetes 群集。Starting with this update, customers can deploy production Kubernetes clusters. 借助 AKS 引擎,用户能够:The AKS engine enables users to:

    • 管理其 Kubernetes 群集的生命周期。Manage the life cycle of their Kubernetes clusters. 创建、更新和扩展群集。They can create, update, and scale clusters.
    • 使用 AKS 和 Azure Stack Hub 团队生成的托管映像维护其群集。Maintain their clusters using managed images produced by the AKS and the Azure Stack Hub teams.
    • 利用集成了 Azure 资源管理器的 Kubernetes 云提供程序,该提供程序使用本机 Azure 资源构建群集。Take advantage of an Azure Resource Manager-integrated Kubernetes cloud provider that builds clusters using native Azure resources.
    • 在已连接或断开连接的 Azure Stack Hub 戳中部署和管理其群集。Deploy and manage their clusters in connected or disconnected Azure Stack Hub stamps.
    • 使用 Azure 混合功能:Use Azure hybrid features:
      • 与 Azure Arc 集成。Integration with Azure Arc.
      • 用适用于容器的 Azure Monitor 进行集成。Integration with Azure Monitor for Containers.
    • 将 Windows 容器与 AKS 引擎一起使用。Use Windows Containers with AKS engine.
    • 为其部署接收 Azure 支持和工程支持。Receive Azure Support and engineering support for their deployments.

改进Improvements

  • Azure Stack Hub 的功能已得到改进,可自动补救一些修补升级问题,过去,这些问题会导致更新失败,或者使操作员无法启动 Azure Stack Hub 更新。Azure Stack Hub has improved its ability to auto-remediate some patch and update issues that previously caused update failures or prevented operators from being able to initiate an Azure Stack Hub update. 因此,Test-AzureStack -UpdateReadiness 组中包含的测试较少。As a result, there are fewer tests included in the Test-AzureStack -UpdateReadiness group. 有关详细信息,请参阅验证 Azure Stack Hub 系统状态For more information, see Validate Azure Stack Hub system state. 以下三项测试保留在 UpdateReadiness 组中:The following three tests remain in the UpdateReadiness group:

    • AzSInfraFileValidationAzSInfraFileValidation
    • AzSActionPlanStatusAzSActionPlanStatus
    • AzsStampBMCSummaryAzsStampBMCSummary
  • 添加了审核规则来报告外部设备(例如 USB 密钥)装载到 Azure Stack Hub 基础结构节点的时间。Added an auditing rule to report when an external device (for example, a USB key) is mounted to a node of the Azure Stack Hub infrastructure. 审核日志通过 syslog 发出,并显示为“Microsoft-Windows-Security-Auditing:6416|即插即用事件”。The audit log is emitted via syslog and will be displayed as Microsoft-Windows-Security-Auditing: 6416|Plug and Play Events. 有关如何配置 syslog 客户端的详细信息,请参阅 Syslog 转发For more information about how to configure the syslog client, see Syslog forwarding.

  • Azure Stack Hub 的内部证书即将改用 4096 位 RSA 密钥。Azure Stack Hub is moving to 4096-bit RSA keys for the internal certificates. 运行内部机密轮换会将旧的 2048 位证书替换为 4096 位长的证书。Running internal secret rotation will replace old 2048-bit certificates with 4096-bit long certificates. 有关 Azure Stack Hub 中的机密轮换的详细信息,请参阅在 Azure Stack Hub 中轮换机密For more information about secret rotation in Azure Stack Hub, see Rotate secrets in Azure Stack Hub.

  • 将多个内部组件升级到符合国家安全系统委员会 - 政策 15(CNSSP-15,该政策提供使用公共标准来安全共享信息的最佳做法)的密码编译算法复杂性和密钥强度。Upgrades to the complexity of cryptographic algorithms and key strength for several internal components to comply with the Committee on National Security Systems - Policy 15 (CNSSP-15), which provides best practices for the use of public standards for secure information sharing. 其中的改进包括,在 Kerberos 身份验证中使用 AES256,以及在 VPN 加密中使用 SHA384。Among the improvements, there's AES256 for Kerberos authentication and SHA384 for VPN encryption. 有关 CNSSP-15 的详细信息,请参阅国家安全系统委员会的“政策”页For more information about CNSSP-15, see the Committee on National Security Systems, Policies page.

  • 由于上述升级,Azure Stack Hub 现在对 IPsec/IKEv2 配置使用新的默认值。Because of the above upgrade, Azure Stack Hub now has new default values for IPsec/IKEv2 configurations. Azure Stack Hub 端使用的新默认值如下:The new default values used on the Azure Stack Hub side are as follows:

    IKE 阶段 1(主模式)参数IKE Phase 1 (Main Mode) parameters

    属性Property ValueValue
    SDK 版本IKE Version IKEv2IKEv2
    Diffie-Hellman 组Diffie-Hellman Group ECP384ECP384
    身份验证方法Authentication method 预共享密钥Pre-shared key
    加密和哈希算法Encryption & Hashing Algorithms AES256、SHA384AES256, SHA384
    SA 生存期(时间)SA Lifetime (Time) 28,800 秒28,800 seconds

    IKE 阶段 2(快速模式)参数IKE Phase 2 (Quick Mode) parameters

    属性Property ValueValue
    SDK 版本IKE Version IKEv2IKEv2
    加密和哈希算法(加密)Encryption & Hashing Algorithms (Encryption) GCMAES256GCMAES256
    加密和哈希算法(身份验证)Encryption & Hashing Algorithms (Authentication) GCMAES256GCMAES256
    SA 生存期(时间)SA Lifetime (Time) 27,000 秒27,000 seconds
    SA 生存期(千字节)SA Lifetime (Kilobytes) 33,553,40833,553,408
    完全向前保密 (PFS)Perfect Forward Secrecy (PFS) ECP384ECP384
    死对等体检测Dead Peer Detection 支持Supported

    默认的 IPsec/IKE 提案文档中也反映了这些更改。These changes are reflected in the default IPsec/IKE proposal documentation as well.

  • 基础结构备份服务改进了计算备份所需的可用空间的逻辑,而不是依赖固定的阈值。The infrastructure backup service improves logic that calculates desired free space for backups instead of relying on a fixed threshold. 该服务使用备份大小、保留策略、预留和外部存储位置的当前利用率,来确定是否需要对操作员引发警告。The service will use the size of a backup, retention policy, reserve, and current utilization of external storage location to determine if a warning needs to be raised to the operator.

更改Changes

  • 将市场项从 Azure 下载到 Azure Stack Hub 时,可以使用新的用户界面来指定项的版本(如果存在多个版本时)。When downloading marketplace items from Azure to Azure Stack Hub, there's a new user interface that enables you to specify a version of the item when multiple versions exist. 新 UI 可用于联网场景和离线场景。The new UI is available in both connected and disconnected scenarios. 有关详细信息,请参阅将市场项从 Azure 下载到 Azure Stack HubFor more information, see Download marketplace items from Azure to Azure Stack Hub.

  • 从版本 1910 开始,Azure Stack Hub 系统需要额外的 /20 专用内部 IP 空间。Starting with the 1910 release, the Azure Stack Hub system requires an additional /20 private internal IP space. 有关详细信息,请参阅 Azure Stack 的网络集成规划See Network integration planning for Azure Stack for more information.

  • 如果在上传过程中外部存储位置耗尽了容量,基础结构备份服务将会删除部分上传的备份数据。The infrastructure backup service deletes partially uploaded backup data if the external storage location runs out of capacity during the upload procedure.

  • 基础结构备份服务将标识服务添加到 AAD 部署的备份有效负载。The infrastructure backup service adds identity service to the backup payload for AAD deployments.

  • Azure Stack Hub PowerShell 模块已更新为适用于版本 1910 的 1.8.0 版。The Azure Stack Hub PowerShell Module has been updated to version 1.8.0 for the 1910 release.
    更改包括:Changes include:

    • 新的 DRP 管理模块:使用部署资源提供程序 (DRP) 能够以协调的方式将资源提供程序部署到 Azure Stack Hub。New DRP Admin module: The Deployment Resource Provider (DRP) enables orchestrated deployments of resource providers to Azure Stack Hub. 这些命令与 Azure 资源管理器层交互,从而与 DRP 交互。These commands interact with the Azure Resource Manager layer to interact with DRP.
    • BRPBRP:
      - 支持 Azure stack 基础结构备份的单个角色还原。- Support single role restore for Azures stack infrastructure backup.
      - 将参数 RoleName 添加到 cmdlet Restore-AzsBackup- Add parameter RoleName to cmdlet Restore-AzsBackup.
    • FRP:“驱动器”和“卷”资源的中断性变更,提供 API 版本 2019-05-01FRP: Breaking changes for Drive and Volume resources with API version 2019-05-01. Azure Stack Hub 1910 和更高版本支持的功能:The features are supported by Azure Stack Hub 1910 and later:
      - IDNameHealthStatusOperationalStatus 的值已更改。- The value of ID, Name, HealthStatus, and OperationalStatus have been changed.
      - 支持“驱动器”资源的新属性 FirmwareVersionIsIndicationEnabledManufacturerStoragePool- Supported new properties FirmwareVersion, IsIndicationEnabled, Manufacturer, and StoragePool for Drive resources.
      - 已弃用“驱动器”资源的属性 CanPoolCannotPoolReason;改用 OperationalStatus- The properties CanPool and CannotPoolReason of Drive resources have been deprecated; use OperationalStatus instead.

修复项Fixes

  • 修复了以下问题:在 Azure Stack Hub 1904 版本之前部署的环境中无法强制实施 TLS 1.2 策略。Fixed an issue that prevented enforcing TLS 1.2 policy on environments deployed before the Azure Stack Hub 1904 release.
  • 修复了以下问题:创建时已启用 SSH 授权的 Ubuntu 18.04 VM 不允许使用 SSH 密钥登录。Fixed an issue where an Ubuntu 18.04 VM created with SSH authorization enabled doesn't allow you to use the SSH keys to sign in.
  • 从虚拟机规模集 UI 中删除了“重置密码”。Removed Reset Password from the Virtual Machine Scale Set UI.
  • 修复了以下问题:从门户删除负载均衡器不会删除基础结构层中的对象。Fixed an issue where deleting the load balancer from the portal didn't result in the deletion of the object in the infrastructure layer.
  • 修复了以下问题:管理员门户上的网关池用量警报显示不正确的百分比。Fixed an issue that showed an inaccurate percentage of the Gateway Pool utilization alert on the administrator portal.

安全更新Security updates

有关此 Azure Stack Hub 更新中的安全更新的信息,请参阅 Azure Stack Hub 安全更新For information about security updates in this update of Azure Stack Hub, see Azure Stack Hub security updates.

可从 Qualys 网站下载此版本的 Qualys 漏洞报告。The Qualys vulnerability report for this release can be downloaded from the Qualys website.

修补程序Hotfixes

Azure Stack Hub 定期发布修补程序。Azure Stack Hub releases hotfixes on a regular basis. 将 Azure Stack Hub 更新到 1910 之前,请务必先安装 1908 的最新 Azure Stack Hub 修补程序。Be sure to install the latest Azure Stack Hub hotfix for 1908 before updating Azure Stack Hub to 1910.

备注

Azure Stack Hub 修补程序版本是累积性的;你只需安装最新的修补程序即可获取该版本的任何以前修补程序版本中包含的所有修补程序。Azure Stack Hub hotfix releases are cumulative; you only need to install the latest hotfix to get all fixes included in any previous hotfix releases for that version.

Azure Stack Hub 修补程序仅适用于 Azure Stack Hub 集成系统;请勿尝试在 ASDK 上安装修补程序。Azure Stack Hub hotfixes are only applicable to Azure Stack Hub integrated systems; do not attempt to install hotfixes on the ASDK.

先决条件:应用 1910 更新之前Prerequisites: Before applying the 1910 update

必须在包含以下修补程序的版本 1908 中应用 Azure Stack 版本 1910:The 1910 release of Azure Stack Hub must be applied on the 1908 release with the following hotfixes:

成功应用 1910 更新之后After successfully applying the 1910 update

安装此更新之后,请安装所有适用的修补程序。After the installation of this update, install any applicable hotfixes. 有关详细信息,请参阅我们的服务策略For more information, see our servicing policy.

1908 内部版本参考1908 build reference

Azure Stack Hub 1908 更新内部版本号为 1.1908.4.33The Azure Stack Hub 1908 update build number is 1.1908.4.33.

更新类型Update type

对于 1908,运行 Azure Stack Hub 的底层操作系统已更新为 Windows Server 2019。For 1908, the underlying operating system on which Azure Stack Hub runs has been updated to Windows Server 2019. 此更新可以实现核心基础增强,并将更多功能引入 Azure Stack Hub。This update enables core fundamental enhancements and the ability to bring additional capabilities to Azure Stack Hub.

Azure Stack Hub 1908 更新内部版本类型为“完整”。The Azure Stack Hub 1908 update build type is Full. 因此,1908 更新的运行时间比快速更新(例如 1906 和 1907)更久。As a result, the 1908 update has a longer runtime than express updates like 1906 and 1907. 完整更新的确切运行时间通常取决于 Azure Stack Hub 实例包含的节点数目、租户工作负荷在系统上使用的容量、系统的网络连接(如果已连接到 Internet),以及系统的硬件配置。Exact runtimes for full updates typically depend on the number of nodes that your Azure Stack Hub instance contains, the capacity used on your system by tenant workloads, your system's network connectivity (if connected to the internet), and your system hardware configuration. 在我们的内部测试中,1908 更新的预期运行时间如下:4 个节点 - 42 小时,8 个节点 - 50 小时,12 个节点 - 60 小时,16 个节点 - 70 小时。The 1908 update has had the following expected runtimes in our internal testing: 4 nodes - 42 hours, 8 nodes - 50 hours, 12 nodes - 60 hours, 16 nodes - 70 hours. 更新运行时间超过这些预期值并不常见,因此,除了更新失败之外,无需要求 Azure Stack Hub 操作员执行操作。Update runtimes lasting longer than these expected values aren't uncommon and don't require action by Azure Stack Hub operators unless the update fails.

有关更新内部版本类型的详细信息,请参阅在 Azure Stack Hub 中管理更新For more information about update build types, see Manage updates in Azure Stack Hub.

  • 确切的更新运行时间通常取决于租户工作负荷在系统上使用的容量、系统网络连接(如果已连接到 Internet),以及系统的硬件配置。Exact update runtimes typically depend on the capacity used on your system by tenant workloads, your system network connectivity (if connected to the internet), and your system hardware configuration.
  • 运行时间超过预期值并不常见,除非更新失败,否则无需 Azure Stack Hub 操作员采取措施。Runtimes lasting longer than expected aren't uncommon and don't require action by Azure Stack Hub operators unless the update fails.
  • 此运行时近似值特定于 1908 更新,不应与其他 Azure Stack Hub 更新进行比较。This runtime approximation is specific to the 1908 update and shouldn't be compared to other Azure Stack Hub updates.

新增功能What's new

  • 对于 1908,请注意,运行 Azure Stack Hub 的底层操作系统已更新为 Windows Server 2019。For 1908, note that the underlying operating system on which Azure Stack Hub runs has been updated to Windows Server 2019. 此更新可以实现核心基础增强,并将更多功能引入 Azure Stack Hub。This update enables core fundamental enhancements and the ability to bring additional capabilities to Azure Stack Hub.
  • Azure Stack Hub 基础结构的所有组件现在都以 FIPS 140-2 模式运行。All components of Azure Stack Hub infrastructure now operate in FIPS 140-2 mode.
  • Azure Stack Hub 操作员现在可以删除门户用户数据。Azure Stack Hub operators can now remove portal user data. 有关详细信息,请参阅从 Azure Stack Hub 中清除门户用户数据For more information, see Clear portal user data from Azure Stack Hub.

改进Improvements

  • Azure Stack Hub 的静态数据加密已得到改进,可将机密持久保存到物理节点的硬件受信任平台模块 (TPM)。Improvements to data at rest encryption of Azure Stack Hub to persist secrets into the hardware Trusted Platform Module (TPM) of the physical nodes.

更改Changes

  • 硬件提供商将在 Azure Stack Hub 版本 1908 的同一发布时间发布 OEM 扩展包 2.1 或更高版本。Hardware providers will be releasing OEM extension package 2.1 or later at the same time as Azure Stack Hub version 1908. 必须安装 OEM 扩展包 2.1 或更高版本才能使用 Azure Stack Hub 版本 1908。The OEM extension package 2.1 or later is a prerequisite for Azure Stack Hub version 1908. 有关如何下载 OEM 扩展包 2.1 或更高版本的详细信息,请与系统的硬件提供商联系,并参阅 OEM 更新一文。For more information about how to download OEM extension package 2.1 or later, contact your system's hardware provider, and see the OEM updates article.

修复项Fixes

  • 修复了与将来的 Azure Stack Hub OEM 更新兼容的问题,以及使用客户用户映像进行 VM 部署的问题。Fixed an issue with compatibility with future Azure Stack Hub OEM updates and an issue with VM deployment using customer user images. 此问题是在 1907 中发现的,已在修补程序 KB4517473 中予以修复This issue was found in 1907 and fixed in hotfix KB4517473
  • 修复了 OEM 固件更新的问题,并更正了 Fabric Ring Health 的 Test-AzureStack 中的诊断错误。Fixed an issue with OEM Firmware update and corrected misdiagnosis in Test-AzureStack for Fabric Ring Health. 此问题是在 1907 中发现的,已在修补程序 KB4515310 中予以修复This issue was found in 1907 and fixed in hotfix KB4515310
  • 修复了 OEM 固件更新过程的问题。Fixed an issue with OEM Firmware update process. 此问题是在 1907 中发现的,已在修补程序 KB4515650 中予以修复This issue was found in 1907 and fixed in hotfix KB4515650

安全更新Security updates

有关此 Azure Stack Hub 更新中的安全更新的信息,请参阅 Azure Stack Hub 安全更新For information about security updates in this update of Azure Stack Hub, see Azure Stack Hub security updates.

可从 Qualys 网站下载此版本的 Qualys 漏洞报告。The Qualys vulnerability report for this release can be downloaded from the Qualys website.

下载更新Download the update

可从 Azure Stack Hub 下载页下载 Azure Stack Hub 1908 更新包。You can download the Azure Stack Hub 1908 update package from the Azure Stack Hub download page.

修补程序Hotfixes

Azure Stack Hub 定期发布修补程序。Azure Stack Hub releases hotfixes on a regular basis. 将 Azure Stack Hub 更新到 1908 之前,请务必先安装 1907 的最新 Azure Stack Hub 修补程序。Be sure to install the latest Azure Stack Hub hotfix for 1907 before updating Azure Stack Hub to 1908.

Azure Stack Hub 修补程序仅适用于 Azure Stack Hub 集成系统;请勿尝试在 ASDK 上安装修补程序。Azure Stack Hub hotfixes are only applicable to Azure Stack Hub integrated systems; don't attempt to install hotfixes on the ASDK.

先决条件:应用 1908 更新之前Prerequisites: Before applying the 1908 update

必须在包含以下修补程序的版本 1907 中应用 Azure Stack Hub 版本 1908:The 1908 release of Azure Stack Hub must be applied on the 1907 release with the following hotfixes:

Azure Stack Hub 1908 更新需要系统硬件提供商提供的 Azure Stack Hub OEM 2.1 或更高版本The Azure Stack Hub 1908 Update requires Azure Stack Hub OEM version 2.1 or later from your system's hardware provider. OEM 更新包括 Azure Stack Hub 系统硬件的驱动程序和固件更新。OEM updates include driver and firmware updates to your Azure Stack Hub system hardware. 有关应用 OEM 更新的详细信息,请参阅应用 Azure Stack Hub 原始设备制造商更新For more information about applying OEM updates, see Apply Azure Stack Hub original equipment manufacturer updates

成功应用 1908 更新之后After successfully applying the 1908 update

安装此更新之后,请安装所有适用的修补程序。After the installation of this update, install any applicable hotfixes. 有关详细信息,请参阅我们的服务策略For more information, see our servicing policy.

1907 已存档的发行说明1907 archived release notes

1906 已存档的发行说明1906 archived release notes

1905 已存档的发行说明1905 archived release notes

1904 已存档的发行说明1904 archived release notes

1903 已存档的发行说明1903 archived release notes

1902 已存档的发行说明1902 archived release notes

1901 已存档的发行说明1901 archived release notes

1811 已存档的发行说明1811 archived release notes

1809 已存档的发行说明1809 archived release notes

1808 已存档的发行说明1808 archived release notes

1807 已存档的发行说明1807 archived release notes

1805 已存档的发行说明1805 archived release notes

1804 已存档的发行说明1804 archived release notes

1803 已存档的发行说明1803 archived release notes

1802 已存档的发行说明1802 archived release notes

可以访问 TechNet 库中旧版本 Azure Stack Hub 的发行说明You can access older versions of Azure Stack Hub release notes on the TechNet Gallery. 提供这些已存档文档仅供参考,并不意味着支持这些版本。These archived documents are provided for reference purposes only and do not imply support for these versions. 有关 Azure Stack Hub 支持的信息,请参阅 Azure Stack Hub 服务策略For information about Azure Stack Hub support, see Azure Stack Hub servicing policy. 如需进一步的帮助,请联系 Microsoft 客户支持服务。For further assistance, contact Microsoft Customer Support Services.