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.

2008 内部版本参考2008 build reference

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

更新类型Update type

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

与以前的更新相比,2008 更新包更大。The 2008 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. 在我们的内部测试中,2008 更新的预期运行时间如下 - 4 个节点:13-20 小时,8 个节点:16-26 小时,12 个节点:19-32 小时,16 个节点:22-38 小时。The 2008 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. 此运行时近似值特定于 2008 更新,不应与其他 Azure Stack Hub 更新进行比较。This runtime approximation is specific to the 2008 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

  • Azure Stack Hub 现在支持 VNET 对等互连,这样,你便可以在不使用网络虚拟设备 (NVA) 的情况下连接 VNET。Azure Stack Hub now supports VNET peering, which gives the ability to connect VNETs without a Network Virtual Appliance (NVA). 有关详细信息,请参阅新 VNET 对等互连文档For more information, see the new VNET peering documentation.
  • Azure Stack Hub blob 存储现在允许用户使用不可变 blob。Azure Stack Hub blob storage now enables users to use an immutable blob. 通过在容器上设置不可变的策略,可将业务关键型数据对象以 WORM(写入一次,读取多次)状态进行存储。By setting immutable policies on a container, you can store business-critical data objects in a WORM (Write Once, Read Many) state. 在此版本中,不可变的策略只能通过 REST API 或客户端 SDK 来设置。In this release, immutable policies can only be set through the REST API or client SDKs. 在此版本中,也不可能执行追加 blob 写入。Append blob writes are also not possible in this release. 有关不可变 blob 的详细信息,请参阅使用不可变存储来存储业务关键型 blob 数据For more information about immutable blobs, see Store business-critical blob data with immutable storage.
  • Azure Stack Hub 存储现在支持 Azure 存储服务 API 版本 2019-07-07。Azure Stack Hub Storage now supports Azure Storage services APIs version 2019-07-07. 有关与新 REST API 版本兼容的 Azure 客户端库,请参阅 Azure Stack Hub 存储开发工具For Azure client libraries that is compatible with the new REST API version, see Azure Stack Hub storage development tools. 对于 Azure 存储服务管理 API,已添加对 2018-02-01 的支持,其中包含全部可用功能的子集。For Azure Storage services management APIs, 2018-02-01 has been add of support, with a subset of total available features.
  • Azure Stack Hub 计算现在支持 Azure 计算 API 版本 2020-06-01,其中包含全部可用功能的子集。Azure Stack Hub compute now supports Azure Compute APIs version 2020-06-01, with a subset of total available features.
  • Azure Stack Hub 托管磁盘现在支持 Azure 计算 API 版本 2019-03-01,其中包含可用功能的子集。Azure Stack Hub managed disks now support Azure Disk APIs version 2019-03-01, with a subset of the available features.
  • Windows Admin Center 的预览版现在可以连接到 Azure Stack Hub,以便在支持操作期间提供有关基础结构的深入见解(需要不受限)。Preview of Windows Admin Center that can now connect to Azure Stack Hub to provide in-depth insights into the infrastructure during support operations (break-glass required).
  • 能够在部署时将登录横幅添加到特权终结点 (PEP)。Ability to add login banner to the privileged endpoint (PEP) at deployment time.
  • 发布了更多“独占操作”横幅,这可提高当前在系统上发生的操作的可见性,并禁止用户启动任何其他独占操作(并随后失败)。Released more Exclusive Operations banners, which improve the visibility of operations that are currently happening on the system, and disable users from initiating (and subsequently failing) any other exclusive operation.
  • 在每个 Azure Stack Hub 市场项的产品页中引入了两个新横幅。Introduced two new banners in each Azure Stack Hub Marketplace item's product page. 如果从市场下载时失败,操作员可以查看错误详细信息,并尝试执行建议的步骤来解决此问题。If there is a Marketplace download failure, operators can view error details and attempt recommended steps to resolve the issue.
  • 发布了一个评级工具供客户提供反馈。Released a rating tool for customers to provide feedback. 这将使 Azure Stack Hub 可以度量和优化客户体验。This will enable Azure Stack Hub to measure and optimize the customer experience.
  • 此版本的 Azure Stack Hub 包含 Azure Kubernetes 服务 (AKS) 和 Azure 容器注册表 (ACR) 的个人预览版。This release of Azure Stack Hub includes a private preview of Azure Kubernetes Service (AKS) and Azure Container Registry (ACR). 该个人预览版的目的是收集有关 Azure Stack Hub 上 AKS 和 ACR 的质量、功能和用户体验的反馈。The purpose of the private preview is to collect feedback about the quality, features, and user experience of AKS and ACR on Azure Stack Hub.
  • 此版本包含使用 AKS 引擎 0.55.4 的 Azure CNI 和 Windows 容器的公共预览版。This release includes a public preview of Azure CNI and Windows Containers using AKS Engine v0.55.4. 有关如何在 API 模型中使用它们的示例,请参阅 GitHub 上的此示例For an example of how to use them in your API model, see this example on GitHub.
  • 通过 AKS 引擎 0.55.4 部署的群集上现在支持 Istio 1.3 部署There is now support for Istio 1.3 deployment on clusters deployed by AKS Engine v0.55.4. 有关详细信息,请参阅此处的说明For more information, see the instructions here.
  • 现在已支持使用 AKS 引擎 v 0.55.4 部署专用群集There is now support for deployment of private clusters using AKS Engine v0.55.4.
  • 此版本包括对从 Azure 和 Azure Stack Hub Key Vault 实例获得 Kubernetes 配置机密来源的支持。This release includes support for sourcing Kubernetes configuration secrets from Azure and Azure Stack Hub Key Vault instances.

改进Improvements

  • 实现了网络控制器和 SLB 主机代理的内部监视,因此,如果服务进入停止状态,则会被自动修正。Implemented internal monitoring for Network Controller and SLB host agents, so the services are auto-remediated if they ever enter into a stopped state.
  • 现在,当客户已在其自己的 AD FS 服务器上轮换了令牌签名证书后,Active Directory 联合身份验证服务 (AD FS) 会检索新的令牌签名证书。Active Directory Federation Services (AD FS) now retrieves the new token signing certificate after the customer has rotated it on their own AD FS server. 若要为已配置的系统充分利用这一新功能,必须重新配置 AD FS 集成。To take advantage of this new capability for already configured systems, the AD FS integration must be configured again. 有关详细信息,请参阅将 AD FS 标识与 Azure Stack Hub 数据中心集成For more information, see Integrate AD FS identity with your Azure Stack Hub datacenter.
  • 更改了基础结构角色实例及其在缩放单元节点上的依赖项的启动和关闭过程。Changes to the startup and shutdown process on infrastructure role instances and their dependencies on scale unit nodes. 这会增加 Azure Stack Hub 启动和关闭的可靠性。This increases the reliability for Azure Stack Hub startup and shutdown.
  • 已更新 Test-azurestack 验证工具的 AzSScenarios 套件,从而使云服务提供商能够在对所有客户帐户强制实施多重身份验证的情况下成功运行此套件。The AzSScenarios suite of the Test-AzureStack validation tool has been updated to enable Cloud Service Providers to run this suite successfully with multi-factor authentication enforced on all customer accounts.
  • 通过为生命周期操作期间 29 个面向客户的警报添加抑制逻辑,提高了警报可靠性。Improved alert reliability by adding suppression logic for 29 customer facing alerts during lifecycle operations.
  • 你现在可以查看详细的日志收集 HTML 报表,其中提供了有关日志收集的角色、持续时间和状态的详细信息。You can now view a detailed log collection HTML report which provides details on the roles, duration, and status of the log collection. 此报表的用途是帮助用户提供已收集日志的摘要。The purpose of this report is to help users provide a summary of the logs collected. 然后,Azure 客户支持服务可以快速评估该报表以评估日志数据,并帮助排查和缓解系统问题。Azure Customer Support Services can then quickly assess the report to evaluate the log data, and help to troubleshoot and mitigate system issues.
  • 基础结构故障检测覆盖范围已扩展,用户方案中增加了 7 个新监视器(如 CPU 利用率和内存消耗),以帮助提高故障检测的可靠性。The infrastructure fault detection coverage has been expanded with the addition of 7 new monitors across user scenarios such as CPU utilization and memory consumption, which helps to increase the reliability of fault detection.

更改Changes

  • SRP API 版本 2016-01-01 和 2016-05-01 中的 supportHttpsTrafficOnly 存储帐户资源类型属性已启用,但 Azure Stack Hub 不支持此属性。The supportHttpsTrafficOnly storage account resource type property in SRP API version 2016-01-01 and 2016-05-01 has been enabled, but this property is not supported in Azure Stack Hub.

  • 已将卷容量利用率警报阈值从 80%(警告)和 90%(严重)提高到 90%(警告)和 95%(严重)。Raised volume capacity utilization alert threshold from 80% (warning) and 90% (critical) to 90% (warning) and 95% (critical). 有关详细信息,请参阅存储空间警报For more information, see Storage space alerts

  • 在此版本中,AD Graph 配置步骤已更改。The AD Graph configuration steps change with this release. 有关详细信息,请参阅将 AD FS 标识与 Azure Stack Hub 数据中心集成For more information, see Integrate AD FS identity with your Azure Stack Hub datacenter.

  • 为了与为 Windows Server 2019 定义的当前最佳做法保持一致,Azure Stack Hub 正在更改为利用附加流量类或优先级来进一步分离服务器到服务器通信,以支持故障转移群集控制通信。To align to the current best practices defined for Windows Server 2019, Azure Stack Hub is changing to utilize an additional traffic class or priority to further separate server to server communication in support of the Failover Clustering control communication. 这些更改的结果为故障转移群集通信提供了更好的复原能力。The result of these changes provides better resiliency for Failover Cluster communication. 此流量类和带宽预留配置是通过对 Azure Stack Hub 解决方案的架顶式 (ToR) 交换机以及 Azure Stack Hub 的主机或服务器的更改实现的。This traffic class and bandwidth reservation configuration is accomplished by a change on the top-of-rack (ToR) switches of the Azure Stack Hub solution and on the host or servers of Azure Stack Hub.

    请注意,这些更改是在 Azure Stack Hub 系统的主机级别添加的。Note that these changes are added at the host level of an Azure Stack Hub system. 请与 OEM 联系,以便安排在架顶式 (ToR) 网络交换机上进行所需的更改。Please contact your OEM to arrange making the required changes at the top-of-rack (ToR) network switches. 此 ToR 更改可在更新到 2008 版本之前执行,也可在更新到 2008 版本后执行。This ToR change can be performed either prior to updating to the 2008 release or after updating to 2008. 有关详细信息,请参阅网络集成文档For more information, see the Network Integration documentation.

  • 在此内部版本中,支持 GPU 的 VM 大小 NCas_v4 (NVIDIA T4) 已替换为 VM 大小 NCasT4_v3,以便与 Azure 保持一致。The GPU capable VM sizes NCas_v4 (NVIDIA T4) have been replaced in this build with the VM sizes NCasT4_v3, to be consistent with Azure. 请注意,这些 VM 大小在门户中尚不可见,只能通过 Azure 资源管理器模板使用。Note that those are not visible in the portal yet, and can only be used via Azure Resource Manager templates.

修复项Fixes

  • 修复了删除未附加到正在运行的 VM 的 NIC 的 NSG 时失败的问题。Fixed an issue in which deleting an NSG of a NIC that is not attached to a running VM failed.
  • 修复了在修改关联到负载均衡器的公共 IP 的 IdleTimeoutInMinutes 值时导致公共 IP 进入失败状态的问题。Fixed an issue in which modifying the IdleTimeoutInMinutes value for a public IP that is associated to a load balancer put the public IP in a failed state.
  • 修复了 Get-AzsDisk cmdlet,以便为已附加的托管磁盘返回正确的“Attached”状态,而不是“OnlineMigration”。Fixed the Get-AzsDisk cmdlet to return the correct Attached status, instead of OnlineMigration, for attached managed disks.

安全更新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. 在更新到 2008 之前,请确保安装最新 2005 修补程序。Make sure you install the latest 2005 hotfix before updating to 2008. 此外,从 2005 版开始,更新到新的主版本(如 1.2005.x 到1.2008.x)时,新的主版本中最新的修补程序(如果在下载包时可用)会自动安装。Also, starting with the 2005 release, when you update to a new major version (for example, 1.2005.x to 1.2008.x), the latest hotfixes (if any are available at the time of package download) in the new major version are installed automatically. 这样,你的 2008 安装将具有最新的所有修补程序。Your 2008 installation is then current with all hotfixes. 在此之后,如果发布了适用于 2008 的修补程序,则应安装它。From that point forward, if a hotfix is released for 2008, 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.

提示

如果希望收到有关每个修补程序版本的通知,请订阅 RSS 源以收取有关每个修补程序的通知。If you want to be notified about each hotfix release, subscribe to the RSS feed to be notified about each hotfix release.

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

由于 Azure Stack Hub 修补程序是累积的,因此,作为最佳做法,你应安装已为你的内部版本发布的所有修补程序,以确保主要版本之间的最佳更新体验。Because Azure Stack Hub hotfixes are cumulative, as a best practice you should install all hotfixes released for your build, to ensure the best update experience between major releases. 更新到新的主版本(如 1.2005.x 到1.2008.x)时,新的主版本中最新的修补程序(如果在下载包时可用)会自动安装。When you update to a new major version (for example, 1.2005.x to 1.2008.x), the latest hotfixes (if any are available at the time of package download) in the new major version are installed automatically.

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

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.

更新类型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 wire server 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).
  • 执行硬件监视所需的用户加密设置已从 DES 更改为 AES,以提高安全性。The user encryption setting that is required for hardware monitoring was changed from DES to AES to increase security. 请联系你的硬件合作伙伴,了解如何更改基板管理控制器 (BMC) 中的设置。Please reach out to your hardware partner to learn how to change the setting in the base board management controller (BMC). 在 BMC 中进行更改后,可能需要使用特权终结点再次运行命令 Set-BmcCredential。After the change is made in the BMC, it may require you to run the command Set-BmcCredential again using the privileged endpoint. 有关详细信息,请参阅在 Azure Stack Hub 中轮换机密For more information, see Rotate secrets in Azure Stack Hub

修复项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.
  • 修复了一个问题,现在允许向虚拟机规模集添加扩展。Fixed an issue to allow extensions to be added to a virtual machine 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.