Configuration Manager Current Branch 版本 1906 中的新增功能What's new in version 1906 of Configuration Manager current branch

适用范围:Configuration Manager (Current Branch)Applies to: Configuration Manager (current branch)

Configuration Manager Current Branch 的更新 1906 作为控制台中更新提供。Update 1906 for Configuration Manager current branch is available as an in-console update. 将此更新应用于运行版本 1802 或更高版本的站点。Apply this update on sites that run version 1802 or later. 本文汇总了 Configuration Manager 版本 1906 中的更改和新增功能。This article summarizes the changes and new features in Configuration Manager, version 1906.

始终查看安装此更新的最新清单。Always review the latest checklist for installing this update. 有关详细信息,请参阅用于安装更新 1906 的清单For more information, see Checklist for installing update 1906. 更新站点后,还可以查看更新后清单After you update a site, also review the Post-update checklist.

若要利用 Configuration Manager 的新功能,更新站点后,还请将客户端更新到最新版本。To take full advantage of new Configuration Manager features, after you update the site, also update clients to the latest version. 尽管在更新站点和控制台时 Configuration Manager 控制台中会显示新功能,但只有在客户端版本也是最新版本之后,完整方案才能正常运行。While new functionality appears in the Configuration Manager console when you update the site and console, the complete scenario isn't functional until the client version is also the latest.

提示

若要在此页面更新时收到通知,请将以下 URL 复制并粘贴到 RSS 源阅读器中:https://docs.microsoft.com/api/search/rss?search=%22what%27s+new+in+version+1906+-+Configuration+Manager%22&locale=en-usTo get notified when this page is updated, copy and paste the following URL into your RSS feed reader: https://docs.microsoft.com/api/search/rss?search=%22what%27s+new+in+version+1906+-+Configuration+Manager%22&locale=en-us

要求更改Requirement changes

版本 1906 客户端需要 SHA-2 代码签名支持Version 1906 client requires SHA-2 code signing support

由于 SHA-1 算法中存在缺点,并且为了符合行业标准,Microsoft 现在仅使用更安全的 SHA-2 算法来对 Configuration Manager 二进制文件进行签名。Because of weaknesses in the SHA-1 algorithm and to align to industry standards, Microsoft now only signs Configuration Manager binaries using the more secure SHA-2 algorithm. 以下 Windows OS 版本需要更新才能获得 SHA-2 代码签名支持:The following Windows OS versions require an update for SHA-2 code signing support:

  • Windows 7 SP1Windows 7 SP1
  • Windows Server 2008 R2 SP1Windows Server 2008 R2 SP1
  • Windows Server 2008 SP2Windows Server 2008 SP2

有关详细信息,请参阅 Windows 客户端的先决条件For more information, see Prerequisites for Windows clients.

站点基础结构Site infrastructure

站点服务器维护任务改进Site server maintenance task improvements

在站点服务器的详细信息视图上,站点服务器维护任务现可通过它们各自的选项卡进行查看和编辑。Site server maintenance tasks can now be viewed and edited from their own tab on the details view of a site server. 新的“维护任务”选项卡提供了如下信息:The new Maintenance Tasks tab gives you information such as:

  • 任务是否已启用If the task is enabled
  • 任务计划The task schedule
  • 上次启动时间Last start time
  • 上次完成时间Last completion time
  • 任务是否已成功完成If the task completed successfully

站点服务器详细信息视图中用于维护任务的新选项卡

有关详细信息,请参阅维护任务For more information, see Maintenance tasks.

Configuration Manager 更新数据库升级监视Configuration Manager update database upgrade monitoring

应用 Configuration Manager 更新时,现可在安装状态窗口中查看“升级 ConfigMgr 数据库”任务的状态。When applying a Configuration Manager update, you can now see the state of the Upgrade ConfigMgr database task in the installation status window.

  • 如果数据库升级受阻,则会收到“正在进行,需要注意”的警告。If the database upgrade is blocked, then you'll be given the warning, In progress, needs attention.

    • cmupdate.log 将记录阻止数据库升级的 SQL Server 中的程序名和会话 ID。The cmupdate.log will log the program name and sessionid from SQL Server that is blocking the database upgrade.
  • 数据库升级不再受阻时,状态将重置为“正在进行”或“完成” 。When the database upgrade is no longer blocked, the status will be reset to In progress or Complete.

    • 如果数据库升级受阻,则每 5 分钟进行一次检查,查看其是否仍然受阻。When the database upgrade is blocked, a check is done every 5 minutes to see if it's still blocked.

    安装过程中的数据库升级监视

有关详细信息,请参阅安装控制台内部更新For more information, see Install in-console updates.

NTLM 回退的管理见解规则Management insights rule for NTLM fallback

管理见解包含一项新的规则,用于检测是否为站点启用了安全级别较低的 NTLM 身份验证回退方法:已启用 NTLM 回退。Management insights includes a new rule that detects if you enabled the less secure NTLM authentication fallback method for the site: NTLM fallback is enabled.

有关详细信息,请参阅管理见解For more information, see Management insights.

对 SQL Server Always On 可用性组的支持的改进Improvements to support for SQL Server Always On availability groups

  • 从安装程序添加新的同步副本Add a new synchronous replica from setup:现在可以将新的次要副本节点添加到现有可用性组。: You can now add a new secondary replica node to an existing availability group. 使用 Configuration Manager 安装程序来进行此更改,而不使用手动过程。Instead of a manual process, use Configuration Manager setup to make this change. 有关详细信息,请参阅配置可用性组For more information, see Configure an availability group.

  • 多子网故障转移Multi-subnet failover:现在可以在 SQL Server 中启用 MultiSubnetFailover 连接字符串关键字: You can now enable the MultiSubnetFailover connection string keyword in SQL Server. 你还需要手动配置站点服务器。You also need to manually configure the site server. 有关详细信息,请参阅多子网故障转移先决条件。For more information, see the Multi-subnet failover prerequisite.

  • 对分布式视图的支持Support for distributed views:站点数据库可以托管在可用性组上,并且可以启用数据库复制链接来使用分布式视图: The site database can be hosted on an availability group, and you can enable database replication links to use distributed views.

    备注

    此更改不适用于 SQL Server Always On 故障转移群集实例。This change doesn't apply to SQL Server Always On failover cluster instances.

  • 站点恢复可以在可用性组中重新创建数据库。Site Recovery can recreate the database on an availability group. 此过程适用于手动和自动种子设定。This process works with both manual and automatic seeding.

  • 新安装程序先决条件检查:New setup prerequisite checks:

    • 可用性组副本必须都具有相同的种子设定模式Availability group replicas must all have the same seeding mode

    • 可用性组副本必须正常运行Availability group replicas must be healthy

云附加管理Cloud-attached management

Azure Active Directory 用户组发现Azure Active Directory user group discovery

现可从 Azure Active directory (Azure AD) 中发现用户组和这些组的成员。You can now discover user groups and members of those groups from Azure Active Directory (Azure AD). 站点之前未发现的 Azure AD 组中的用户将作为用户资源添加到 Configuration Manager 中。Users found in Azure AD groups that the site hasn't previously discovered are added as user resources in Configuration Manager. 如果用户组是一个安全组,则创建其资源记录。A user group resource record is created when the group is a security group. 此功能是预发行功能,必须启用。This feature is a pre-release feature and needs to be enabled.

有关详细信息,请参阅配置发现方法For more information, see Configure discovery methods.

将集合成员身份结果同步到 Azure Active Directory 组Synchronize collection membership results to Azure Active Directory groups

现在可以将集合成员身份同步到 Azure Active Directory (Azure AD) 组。You can now enable the synchronization of collection memberships to an Azure Active Directory (Azure AD) group. 此同步是一项预发行功能。This synchronization is a pre-release feature. 若要启用此功能,请参阅预发行功能To enable it, see Pre-release features.

借助同步,可以通过基于集合成员身份结果创建 Azure AD 组成员身份来使用云中的现有本地分组规则。The synchronization allows you to use your existing on-premises grouping rules in the cloud by creating Azure AD group memberships based on collection membership results. 只有具有 Azure Active Directory 记录的设备才会反映在 Azure AD 组中。Only devices with an Azure Active Directory record are reflected in the Azure AD Group. 同时支持已联接混合 Azure AD 的设备和已联接 Azure Active Directory 的设备。Both Hybrid Azure AD Joined and Azure Active Directory joined devices are supported.

有关详细信息,请参阅创建集合For more information, see Create collections.

桌面分析Desktop Analytics

桌面应用的就绪情况见解Readiness insights for desktop apps

现在可以获取桌面应用程序(包括业务线应用)的更多详细见解。You can now get more detailed insights for your desktop applications including line-of-business apps. 以前的 App Health Analyzer 工具包现已与 Configuration Manager 客户端集成。The former App Health Analyzer toolkit is now integrated with the Configuration Manager client. 此集成可简化桌面分析门户中的应用就绪情况见解的部署和可管理性。This integration simplifies deployment and manageability of app readiness insights in the Desktop Analytics portal.

有关详细信息,请参阅桌面分析中的兼容性评估For more information, see Compatibility assessment in Desktop Analytics.

DALogsCollector 工具DALogsCollector tool

使用 Configuration Manager 安装目录中的 DesktopAnalyticsLogsCollector.ps1 工具来帮助对桌面分析进行故障排除。Use the DesktopAnalyticsLogsCollector.ps1 tool from the Configuration Manager install directory to help troubleshoot Desktop Analytics. 它会运行一些基本故障排除步骤,并将相关日志收集到单个工作目录中。It runs some basic troubleshooting steps and collects the relevant logs into a single working directory.

有关详细信息,请参阅日志收集器For more information, see Logs collector.

实时管理Real-time management

在 CMPivot 中添加联接、其他运算符和聚合器Add joins, additional operators, and aggregators in CMPivot

对于 CMPivot,你现在有更多的算术运算符和聚合器,还可以添加查询联接(例如可以同时使用注册表和文件)。For CMPivot, you now have additional arithmetic operators, aggregators, and the ability to add query joins such as using Registry and File together.

有关详细信息,请参阅 CMPivotFor more information, see CMPivot.

CMPivot 独立应用CMPivot standalone

现在可以将 CMPivot 用作独立应用。You can now use CMPivot as a standalone app. CMPivot 独立应用是预发行功能,只提供英语版本。CMPivot standalone is a pre-release feature and is only available in English. 在 Configuration Manager 控制台外部运行 CMPivot,可以查看环境中设备的实时状态。Run CMPivot outside of the Configuration Manager console to view the real-time state of devices in your environment. 借助此变化,无需先安装控制台,即可在设备上使用 CMPivot。This change enables you to use CMPivot on a device without first installing the console.

可以与其他尚未在计算机上安装控制台的角色(如支持人员或安全管理员)共享功能强大的 CMPivot。You can share the power of CMPivot with other personas, such as helpdesk or security admins, who don’t have the console installed on their computer. 这些其他角色可以将 CMPivot 与他们传统上使用的其他工具并行使用,以查询 Configuration Manager。These other personas can use CMPivot to query Configuration Manager alongside the other tools that they traditionally use. 通过共享此类丰富的管理数据,你们可以一起工作,共同主动解决跨角色的业务问题。By sharing this rich management data, you can work together to proactively solve business problems that cross roles.

有关详细信息,请参阅 CMPivot预发行功能For more information, see CMPivot and Pre-release features.

已向安全管理员角色添加权限Added permissions to the Security Administrator role

已向 Configuration Manager 的内置安全管理员角色添加以下权限:The following permissions have been added to Configuration Manager's built-in Security Administrator role:

  • 读取 SMS 脚本Read on SMS Script
  • 在集合上运行 CMPivotRun CMPivot on Collection
  • 读取清单报表Read on Inventory Report

有关详细信息,请参阅 CMPivotFor more information, see CMPivot.

内容管理Content management

客户端数据源仪表板中的传递优化下载数据Delivery Optimization download data in client data sources dashboard

客户端数据源仪表板现在包括传递优化数据。The client data sources dashboard now includes Delivery Optimization data. 此仪表板可帮助你了解客户端在环境中获取内容的位置。This dashboard helps you understand from where clients are getting content in your environment.

有关详细信息,请参阅客户端数据源仪表板For more information, see Client Data Sources dashboard.

将分发点用作传递优化的网络内缓存服务器Use your distribution point as an in-network cache server for Delivery Optimization

现在可以在分发点上安装传递优化网络内缓存服务器。You can now install Delivery Optimization In-Network Cache server on your distribution points. 通过将此内容缓存在本地,你的客户端可以从传递优化功能中受益,但你可帮助保护 WAN 链接。By caching this content on-premises, your clients can benefit from the Delivery Optimization feature, but you can help to protect WAN links.

此缓存服务器充当由传递优化下载的内容的按需透明缓存。This cache server acts as an on-demand transparent cache for content downloaded by Delivery Optimization. 使用客户端设置以确保此服务器仅提供给本地 Configuration Manager 边界组的成员。Use client settings to make sure this server is offered only to the members of the local Configuration Manager boundary group.

有关详细信息,请参阅 Configuration Manager 中的传递优化网络内缓存For more information, see Delivery Optimization In-Network Cache in Configuration Manager.

客户端管理Client management

对 Windows 虚拟桌面的支持Support for Windows Virtual Desktop

Windows 虚拟桌面是 Microsoft Azure 和 Microsoft 365 的一项预览功能。Windows Virtual Desktop is a preview feature of Microsoft Azure and Microsoft 365. 现可使用 Configuration Manager 来管理在 Azure 中运行 Windows 的虚拟设备。You can now use Configuration Manager to manage these virtual devices running Windows in Azure.

与终端服务器类似,这些虚拟设备支持多个并发的活动用户会话。Similar to a terminal server, these virtual devices allow multiple concurrent active user sessions. 为帮助提高客户端性能,Configuration Manager 现在任何可支持多个用户会话的设备上禁用了用户策略。To help with client performance, Configuration Manager now disables user policies on any device that allows these multiple user sessions. 即使启用用户策略,客户端任何设备(包括 Windows 虚拟桌面和终端服务器)上也会默认禁用这些用户策略。Even if you enable user policies, the client disables them by default on these devices, which include Windows Virtual Desktop and terminal servers.

有关详细信息,请参阅客户端和设备支持的 OS 版本For more information, see Supported OS versions for clients and devices.

支持中心 OneTrace(预览)Support Center OneTrace (Preview)

OneTrace 是一个带有支持中心的新日志查看器。OneTrace is a new log viewer with Support Center. 它的工作方式与 CMTrace 类似,同时具有以下改进:It works similarly to CMTrace, with the following improvements:

  • 选项卡式视图A tabbed view
  • 可停靠窗口Dockable windows
  • 改进了搜索功能Improved search capabilities
  • 无需离开日志视图,即可启用筛选器Ability to enable filters without leaving the log view
  • 可以快速识别错误群集的滚动条提示Scrollbar hints to quickly identify clusters of errors
  • 可快速打开大型文件的日志Fast log opening for large files

OneTrace 日志查看器的屏幕截图

有关详细信息,请参阅支持中心 OneTraceFor more information, see Support Center OneTrace.

配置客户端缓存最短保持期Configure client cache minimum retention period

现在可以指定 Configuration Manager 客户端保留缓存内容的最短时间。You can now specify the minimum time for the Configuration Manager client to keep cached content. 此客户端设置定义了在需要更多空间的情况下,Configuration Manager 代理可以从缓存中删除内容之前应等待的最短时间。This client setting defines the minimum amount of time Configuration Manager agent should wait before it can remove content from the cache in case more space is needed. 在客户端设置的“客户端缓存设置”组中,配置以下设置:可以删除缓存内容前的最短持续时间(以分钟为单位)In the Client cache settings group of client settings, configure the following setting: Minimum duration before cached content can be removed (minutes).

备注

在同一个客户端设置组中,现有设置“在完整 OS 中启用 Configuration Manager 客户端以共享内容”现重命名为“启用为对等缓存源” 。In the same client setting group, the existing setting to Enable Configuration Manager client in full OS to share content is now renamed to Enable as peer cache source. 此设置的行为不会发生更改。The behavior of the setting doesn't change.

有关详细信息,请参阅客户端缓存设置For more information, see Client cache settings.

共同管理Co-management

共同管理自动注册的改进Improvements to co-management auto-enrollment

  • 新的共同管理设备现可根据其 Azure Active Directory (Azure AD) 设备令牌自动注册到 Microsoft Intune 服务。A new co-managed device now automatically enrolls to the Microsoft Intune service based on its Azure Active Directory (Azure AD) device token. 无需等待用户登录到设备,就能启动自动注册。It doesn't need to wait for a user to sign in to the device for auto-enrollment to start. 这项更改有助于减少注册状态为“挂起用户登录”的设备数量。This change helps to reduce the number of devices with the enrollment status Pending user sign in.

  • 对于已将设备注册到共同管理的客户,新设备一旦满足先决条件即可立即注册。For customers that already have devices enrolled to co-management, new devices now enroll immediately once they meet the prerequisites. 例如,将设备联接到 Azure AD 并且安装了 Configuration Manager 客户端。For example, once the device is joined to Azure AD and the Configuration Manager client is installed.

有关详细信息,请参阅启用共同管理For more information, see Enable co-management.

用于共同管理工作负载的多个试点组Multiple pilot groups for co-management workloads

现可为每个共同管理工作负载配置不同的试点集合。You can now configure different pilot collections for each of the co-management workloads. 如果能够使用不同的试点集合,那么在移动工作负载时就能采用更具体的方法。Using different pilot collections allows you to take a more granular approach when shifting workloads.

  • 在“启用”选项卡上,现可指定 Intune 自动注册集合 。In the Enablement tab, you can now specify an Intune Auto Enrollment collection.

    • Intune 自动注册集合应包含所有要加入共同管理的客户端。The Intune Auto Enrollment collection should contain all of the clients you want to onboard into co-management. 它实质上是所有其他暂存集合的超集。It's essentially a superset of all the other staging collections.
  • 在“暂存”选项卡上,现可为每个工作负载选择一个单独的集合,而不是将一个试点集合用于所有工作负载。In the Staging tab, instead of using one pilot collection for all workloads, you can now choose an individual collection for each workload.

    使用共同管理“暂存”选项卡,可为每个工作负载选择一个集合

首次启用共同管理时,也可以使用这些选项。These options are also available when you first enable co-management.

有关详细信息,请参阅启用共同管理For more information, see Enable co-management.

对政府云的共同管理支持Co-management support for government cloud

美国政府客户现在可以将共同管理用于美国版 Azure政府云 (portal.azure.us)。U.S. government customers can now use co-management with the Azure U.S. Government Cloud (portal.azure.us). 有关详细信息,请参阅启用共同管理For more information, see Enable co-management.

应用程序管理Application management

筛选部署到设备的应用程序Filter applications deployed to devices

以设备为目标的应用程序部署的用户类别在软件中心现显示为筛选器。User categories for device-targeted application deployments now show as filters in Software Center. 在其属性的“软件中心”页上,为应用程序指定“用户类别” 。Specify a user category for an application on the Software Center page of its properties. 然后,在软件中心打开应用并查看可用的筛选器。Then open the app in Software Center and look at the available filters.

有关详细信息,请参阅手动指定应用程序信息For more information, see Manually specify application information.

应用程序组Application groups

创建一组可以作为单个部署发送到用户或设备集合的应用程序。Create a group of applications that you can send to a user or device collection as a single deployment. 指定的有关应用组的元数据在软件中心中显示为单个实体。The metadata you specify about the app group is seen in Software Center as a single entity. 可以在组中对应用排序,以便客户端将其以特定顺序安装。You can order the apps in the group so that the client installs them in a specific order.

此功能是预发行功能。This feature is pre-release. 若要启用此功能,请参阅预发行功能To enable it, see Pre-release features.

有关详细信息,请参阅创建应用程序组For more information, see Create application groups.

重新安装预先审批的应用程序Retry the install of pre-approved applications

现可重试安装之前为用户或设备批准的应用。You can now retry the installation of an app that you previously approved for a user or device. 批准选项仅适用于可用部署。The approval option is only for available deployments. 如果用户卸载应用,或者初始安装过程失败,Configuration Manager 将不会重新评估其状态并重新安装。If the user uninstalls the app, or if the initial install process fails, Configuration Manager doesn't reevaluate its state and reinstall it. 此功能允许技术支持人员为需要帮助的用户快速重试应用安装。This feature allows a support technician to quickly retry the app install for a user that calls for help.

有关详细信息,请参阅批准应用程序For more information, see Approve applications.

为设备安装应用程序Install an application for a device

从 Configuration Manager 控制台,现在可以将应用程序实时安装到设备。From the Configuration Manager console, you can now install applications to a device in real time. 此功能有助于减少对每个应用程序的单独集合的需求。This feature can help reduce the need for separate collections for every application.

有关详细信息,请参阅为设备安装应用程序For more information, see Install applications for a device.

对应用审批的改进Improvements to app approvals

此版本包括对应用批准的以下改进:This release includes the following improvements to app approvals:

  • 如果在控制台中批准了应用请求,然后拒绝该请求,则现在可以再次批准该请求。If you approve an app request in the console, and then deny it, you can now approve it again. 批准后,应用将重新安装在客户端上。The app is reinstalled on the client after you approve it.

  • 在 Configuration Manager 控制台的“软件库”工作区中的“应用程序管理”下,“审批请求”节点重命名为“应用程序请求” 。In the Configuration Manager console, Software Library workspace, under Application Management, the Approval Requests node is renamed Application Requests.

  • 要删除应用批准请求,可以使用新的 WMI 方法 DeleteInstance。There's a new WMI method, DeleteInstance to remove an app approval request. 此操作不会卸载设备上的应用。This action doesn't uninstall the app on the device. 如果尚未安装,则用户无法从软件中心安装该应用。If it's not already installed, the user can't install the app from Software Center.

  • 调用 CreateApprovedRequest API,为设备上的应用创建预先批准的请求。Call the CreateApprovedRequest API to create a pre-approved request for an app on a device. 要阻止在客户端上自动安装应用,请将 AutoInstall 参数设置为 FALSETo prevent automatically installing the app on the client, set the AutoInstall parameter to FALSE. 用户可以在软件中心中看到该应用,但系统不会自动安装该应用。The user sees the app in Software Center, but it's not automatically installed.

有关详细信息,请参阅批准应用程序For more information, see Approve applications.

OS 部署OS deployment

任务序列调试程序Task sequence debugger

任务序列调试器是一种新型故障排除工具。The task sequence debugger is a new troubleshooting tool. 请将调试模式下的任务序列部署到一个设备的集合中。You deploy a task sequence in debug mode to a collection of one device. 这样便可通过可控方式单步执行任务序列,以帮助进行故障排除和调查。It lets you step through the task sequence in a controlled manner to aid troubleshooting and investigation.

任务序列调试器的屏幕截图

此功能是预发行功能。This feature is pre-release. 若要启用此功能,请参阅预发行功能To enable it, see Pre-release features.

有关详细信息,请参阅调试任务序列For more information, see Debug a task sequence.

在任务序列期间清除客户端缓存中的应用内容Clear app content from client cache during task sequence

在“安装应用程序”任务序列步骤中,现可在步骤运行后删除客户端缓存中的应用内容。In the Install Application task sequence step, you can now delete the app content from the client cache after the step runs.

有关详细信息,请参阅关于任务序列步骤For more information, see About task sequence steps.

重要

将目标客户端更新至最新版本以支持该新功能。Update the target client to the latest version to support this new feature.

回收任务序列的 SEDO 锁定Reclaim SEDO lock for task sequences

如果 Configuration Manager 控制台停止响应,你可能会被锁定而无法对任务序列做出进一步更改。If the Configuration Manager console stops responding, you can be locked out of making further changes to a task sequence. 尝试访问已锁定的任务序列时,现在可以放弃更改,并继续编辑对象。Now when you attempt to access a locked task sequence, you can now Discard Changes, and continue editing the object.

有关详细信息,请参阅使用任务序列编辑器For more information, see Use the task sequence editor.

预缓存驱动程序包和 OS 映像Pre-cache driver packages and OS images

任务序列预缓存现在包括其他内容类型。Task sequence pre-cache now includes additional content types. 预缓存内容以前仅适用于 OS 升级包。Pre-cache content previously only applied to OS upgrade packages. 现在可以使用预缓存来减少以下各项的带宽消耗:Now you can use pre-caching to reduce bandwidth consumption of:

  • OS 映像OS images
  • 驱动程序包Driver packages
  • Packages

有关详细信息,请参阅配置预缓存内容For more information, see Configure pre-cache content.

对 OS 部署的改进Improvements to OS deployment

此版本包括对 OS 部署的以下改进:This release includes the following improvements to OS deployment:

  • 使用下面两个 PowerShell cmdlet 来创建和编辑运行任务序列步骤:Use the following two PowerShell cmdlets to create and edit the Run Task Sequence step:

    • New-CMTSStepRunTaskSequenceNew-CMTSStepRunTaskSequence

    • Set-CMTSStepRunTaskSequenceSet-CMTSStepRunTaskSequence

  • 运行任务序列时,现可更加轻松地编辑变量。It's now easier to edit variables when you run a task sequence. 在“任务序列向导”窗口中选择任务序列后,用于编辑任务序列变量的页面中包含一个“编辑”按钮。After you select a task sequence in the Task Sequence Wizard window, the page to edit task sequence variables includes an Edit button. 有关详细信息,请参阅如何使用任务序列变量For more information, see How to use task sequence variables.

  • “禁用 BitLocker”任务序列步骤拥有新的重启计数器。The Disable BitLocker task sequence step has a new restart counter. 使用此选项可指定禁用 BitLocker 的重启次数。Use this option to specify the number of restarts to keep BitLocker disabled. 此更改有助于简化任务序列。This change helps you simplify your task sequence. 可以使用单个步骤,而不是添加此步骤的多个实例。You can use a single step, instead of adding multiple instances of this step. 有关详细信息,请参阅禁用 BitLockerFor more information, see Disable BitLocker.

  • 将新的任务序列变量 SMSTSRebootDelayNext 与现有的 SMSTSRebootDelay 变量结合使用。Use the new task sequence variable SMSTSRebootDelayNext with the existing SMSTSRebootDelay variable. 若要稍后执行超时值不同于第一个的任何重启,请将此新变量设置为其他值(以秒为单位)。If you want any later reboots to happen with a different timeout than the first, set this new variable to a different value in seconds. 有关详细信息,请参阅 SMSTSRebootDelayNextFor more information, see SMSTSRebootDelayNext.

  • 任务序列设置了新的只读变量“_SMSTSLastContentDownloadLocation”。The task sequence sets a new read-only variable _SMSTSLastContentDownloadLocation. 此变量包含下载任务序列或尝试下载内容的最后位置。This variable contains the last location where the task sequence downloaded or attempted to download content. 检查此变量,而不是分析客户端日志。Inspect this variable instead of parsing the client logs.

  • 当你创建任务序列媒体时,Configuration Manager 不会添加 autorun.inf 文件。When you create task sequence media, Configuration Manager doesn't add an autorun.inf file. 反恶意软件通常会阻止此文件。This file is commonly blocked by antimalware products. 如果情况需要,仍然可以包括该文件。You can still include the file if necessary for your scenario.

对 PXE 的改进Improvements to PXE

没有 WDS 的 PXE 响应程序现支持在 PXE DHCP 握手期间使用选项 82。Option 82 during the PXE DHCP handshake is now supported with the PXE responder without WDS. WDS 不支持选项 82。Option 82 is not supported with WDS.

软件中心Software Center

对软件中心选项卡自定义项的改进Improvements to Software Center tab customizations

现在可以在软件中心中添加最多五个自定义选项卡。You can now add up to five custom tabs in Software Center. 还可以编辑这些选项卡在“软件中心”中的显示顺序。You can also edit the order in which these tabs appear in Software Center.

有关详细信息,请参阅软件中心客户端设置For more information, see Software Center client settings.

软件中心基础结构的改进Software Center infrastructure improvements

此版本包括以下软件中心基础结构改进:This release includes the following infrastructure improvements to Software Center:

  • 软件中心现在可以与面向用户公开发布的应用的管理点通信。Software Center now communicates with a management point for apps targeted to users as available. 它不再使用应用程序目录。It doesn't use the application catalog anymore. 借助此变化,可以更轻松地从站点中删除应用程序目录。This change makes it easier for you to remove the application catalog from the site.

  • 过去,软件中心选择可用服务器列表中的第一个管理点。Previously, Software Center picked the first management point from the list of available servers. 自此版本起,它与客户端使用同一个管理点。Starting in this release, it uses the same management point that the client uses. 借助此变化,软件中心可以与客户端使用分配的主站点中的同一个管理点。This change allows Software Center to use the same management point from the assigned primary site as the client.

重要

对软件中心和管理点的这些迭代改进将停用应用程序目录角色。These iterative improvements to Software Center and the management point are to retire the application catalog roles.

  • 从当前分支版本 1806 开始,不支持 Silverlight 用户体验。The Silverlight user experience isn't supported as of current branch version 1806.
  • 自版本 1906 起,更新后的客户端自动使用管理点进行用户可用的应用程序部署。Starting in version 1906, updated clients automatically use the management point for user-available application deployments. 仍然无法安装新的应用程序目录角色。You also can't install new application catalog roles.
  • 版本 1910 已终止对应用程序目录角色的支持。Support ends for the application catalog roles with version 1910.

有关详细信息,请参阅删除应用程序目录为软件中心制定计划For more information, see Remove the application catalog and Plan for Software Center.

重新为最新可用的软件设计了通知Redesigned notification for newly available software

“新软件可用”通知将仅为给定应用程序和修订版本的用户显示一次。The New Software is Available notification will only show once for a user for a given application and revision. 用户每次登录时将不再看到该通知。The user will no longer see the notification each time they sign in. 只有应用程序发生更改或重新部署时,用户才会看到另外的通知。They'll only see another notification for an application if it has changed or was redeployed.

有关详细信息,请参阅创建和部署应用程序For more information, see Create and deploy an application.

更频繁的重启倒计时通知More frequent countdown notifications for restarts

现在,系统将通过间歇性倒计时通知更频繁地提醒最终用户待重启。End users will now be reminded more frequently of a pending restart with intermittent countdown notifications. 可以在“计算机重新启动”页上的“客户端设置”中定义间歇性通知的时间间隔 。You can define the interval for the intermittent notifications in Client Settings on the Computer Restart page. 更改“指定计算机重启倒计时通知的暂停持续时间(分钟)”的值,以配置在出现最终倒计时通知前提醒用户等待重启的频率。Change the value for Specify the snooze duration for computer restart countdown notifications (minutes) to configure how often a user is reminded about a pending restart until the final countdown notification occurs.

此外,向用户显示一条临时通知,指示注销用户或重启计算机之前的时间间隔(以分钟为单位),这一时间间隔的最大值从 1440 分钟(24小时)增加到了 20160 分钟(两周)。Additionally, the maximum value for Display a temporary notification to the user that indicates the interval before the user is logged off or the computer restarts (minutes) increased from 1440 minutes (24 hours) to 20160 minutes (two weeks).

有关详细信息,请参阅设备重新启动通知关于客户端设置For more information, see Device restart notifications and About client settings.

现可向用户提供直接指向软件中心自定义选项卡的链接。You can now provide users with a direct link to a custom tab in Software Center.

使用以下 URL 格式可打开软件中心的特定选项卡:Use the following URL format to open Software Center to a particular tab:

softwarecenter:page=CustomTab1

字符串 CustomTab1 是按顺序排列的第一个自定义选项卡。The string CustomTab1 is the first custom tab in order.

例如,在 Windows“运行”窗口中键入此 URL。For example, type this URL in the Windows Run window.

此语法还可用于打开软件中心的默认选项卡:You can also use this syntax to open default tabs in Software Center:

命令行Command line 选项卡Tab
AvailableSoftware 应用程序Applications
Updates 更新Updates
OSD 操作系统Operating Systems
InstallationStatus 安装状态Installation status
Compliance 设备符合性Device compliance
Options 选项Options

有关详细信息,请参阅软件中心选项卡的可见性For more information, see Software Center tab visibility.

软件更新Software updates

WSUS 维护的其他选项Additional options for WSUS maintenance

你现在具有 Configuration Manager 为维护软件更新点正常运行而执行的其他 WSUS 维护任务。You now have additional WSUS maintenance tasks that Configuration Manager can run to maintain healthy software update points. 每次同步后都会进行 WSUS 维护。The WSUS maintenance occurs after every synchronization. 除了可以拒绝 WSUS 中的过期更新外,Configuration Manager 现在还可以:In addition to declining expired updates in WSUS, Configuration Manager can now:

  • 从 WSUS 数据库中删除过时的更新。Remove obsolete updates from the WSUS database.
  • 将非聚集索引添加到 WSUS 数据库以提高 WSUS 清理性能。Add non-clustered indexes to the WSUS database to improve WSUS cleanup performance.

有关详细信息,请参阅软件更新维护For more information, see Software updates maintenance.

配置软件更新的默认最长运行时间Configure the default maximum run time for software updates

现可指定完成软件更新安装所需的最长时间。You can now specify the maximum amount of time a software update installation has to complete. 可以在软件更新点上的“最长运行时间”选项卡中指定以下各项:You can specify the following items in the Maximum Run Time tab on the Software Update Point:

  • Windows 功能更新的最长运行时间(分钟)Maximum run time for Windows feature updates (minutes)
  • Office 365 更新和 Windows 非功能更新的最长运行时间(分钟)Maximum run time for Office 365 updates and non-feature updates for Windows (minutes)

有关详细信息,请参阅规划软件更新For more information, see Plan for software updates.

配置功能更新的动态更新Configure dynamic update during feature updates

使用新客户端设置来配置 Windows 10 功能更新安装期间的动态更新Use a new client setting to configure Dynamic Update during Windows 10 feature update installs. 动态更新通过指示客户端从 Internet 下载这些更新,在 Windows 安装过程中安装语言包、按需功能、驱动程序和累积更新。Dynamic Update installs language packs, features on demand, drivers, and cumulative updates during Windows setup by directing the client to download these updates from the internet.

有关详细信息,请参阅软件更新客户端设置管理 Windows 即服务For more information, see Software update client settings and Manage Windows as a service.

新的 Windows 10 1903 版以及更高版本产品类别New Windows 10, version 1903 and later product category

Windows 10 1903 版以及更高版本都已经作为其自身产品添加到 Microsoft 更新中,而不像早期版本那样作为 Windows 10 产品的一部分进行添加 。Windows 10, version 1903 and later was added to Microsoft Update as its own product rather than being part of the Windows 10 product like earlier versions. 这项更改需要你执行许多手动步骤,才可确保客户端显示这些更新。This change caused you to do a number of manual steps to ensure that your clients see these updates. 我们已采取措施减少了需要手动对新产品执行操作的步骤数量。We've helped reduce the number of manual steps you have to take for the new product.

更新至 Configuration Manager 1906 版,并选择了 Windows 10 产品进行同步后,系统将自动执行以下操作:When you update to Configuration Manager version 1906 and have the Windows 10 product selected for synchronization, the following actions occur automatically:

  • 已添加 Windows 10 1903 版以及更高版本产品用于进行同步操作。The Windows 10, version 1903 and later product is added for synchronization.
  • 包含 Windows 10 产品的自动部署规则将更新为包含 Windows 10 1903 版和更高版本 。Automatic Deployment Rules containing the Windows 10 product will be updated to include Windows 10, version 1903 and later.
  • 维护服务计划将更新为包含 Windows 10 1903 版和更高版本产品。Servicing plans are updated to include the Windows 10, version 1903 and later product.

有关详细信息,请参阅配置要同步的分类和产品维护服务计划自动部署规则For more information, see Configure classifications and products to synchronize, Servicing plans, and Automatic deployment rules.

钻取必需更新Drill through required updates

现可深入查看符合性统计信息,了解哪些设备需要特定软件更新。You can now drill through compliance statistics to see which devices require a specific software update. 若要查看设备列表,需要具有查看更新和设备所属集合的权限。To view the device list, you need permission to view updates and the collections the devices belong to. 若要深入查看设备列表,请在更新的“摘要”选项卡中选择饼图旁的“查看所需更新”超链接 。To drill down into the device list, select the View Required hyperlink next to the pie chart in the Summary tab for an update. 单击此超链接将转到“设备”下的临时节点,可以在其中查看需要更新的设备。Clicking the hyperlink takes you to a temporary node under Devices where you can see the devices requiring the update.

可在以下位置找到“查看所需更新”超链接:The View Required hyperlink is available in the following locations:

  • “软件库” > “软件更新” > “所有软件更新” Software Library > Software Updates > All Software Updates
  • “软件库” > “Windows 10 维护服务” > “所有 Windows 10 更新” Software Library > Windows 10 Servicing > All Windows 10 Updates
  • “软件库” > “Office 365 客户端管理” > “Office 365 更新” Software Library > Office 365 Client Management > Office 365 Updates

有关详细信息,请参阅监视软件更新管理 Windows 即服务管理 Microsoft 365 应用版更新For more information, see Monitor software updates, Manage Windows as a service, and Manage Microsoft 365 Apps updates.

Office 管理Office management

Office 365 专业增强版升级就绪情况仪表板Office 365 ProPlus upgrade readiness dashboard

为了帮助你确定哪些设备可以升级到 Microsoft 365 企业应用版,我们推出了新的就绪情况仪表板。To help you determine which devices are ready to upgrade to Microsoft 365 Apps for enterprise, there's a new readiness dashboard. 它包括 Configuration Manager 当前分支版本 1902 中发布的“Office 365 专业增强版升级就绪情况”磁贴。It includes the Office 365 ProPlus upgrade readiness tile that released in Configuration Manager current branch version 1902. 在 Configuration Manager 控制台中,转到“软件库”工作区,展开“Office 365 客户端管理”,再选择“Office 365 专业增强版升级就绪情况”节点。In the Configuration Manager console, go to the Software Library workspace, expand Office 365 Client Management, and select the Office 365 ProPlus Upgrade Readiness node.

若要详细了解仪表板、先决条件和如何使用此数据,请参阅 Office 365 专业增强版集成的就绪情况For more information on the dashboard, prerequisites, and using this data, see Integration for Office 365 ProPlus readiness.

保护Protection

Windows Defender 应用程序防护文件信任标准Windows Defender Application Guard file trust criteria

通过使用新的策略设置,用户可以信任通常在 Windows Defender 应用程序防护 (WDAG) 中打开的文件。There's a new policy setting that enables users to trust files that normally open in Windows Defender Application Guard (WDAG). 成功完成后,文件将在主机设备上打开,而不是在 WDAG 中打开。Upon successful completion, the files will open on the host device instead of in WDAG.

有关详细信息,请参阅创建和部署 Windows Defender 应用程序防护策略For more information, see Create and deploy Windows Defender Application Guard policy.

Configuration Manager 控制台Configuration Manager console

文件夹的基于角色的访问Role-based access for folders

现在可以在文件夹上设置安全作用域。You can now set security scopes on folders. 如果有权访问文件夹中的对象,但无权访问文件夹,则无法查看对象。If you have access to an object in the folder but don't have access to the folder, you'll be unable to see the object. 同样,如果有权访问文件夹,但无权访问该文件夹中的对象,则无法查看对象。Similarly, if you have access to a folder but not an object within it, you won't see that object. 右键单击文件夹,选择“设置安全作用域”,然后选择要应用的安全作用域。Right-click a folder, choose Set Security Scopes, then choose the security scopes you want to apply.

有关详细信息,请参阅 Configuration Manager 控制台提示配置基于角色的管理For more information, see Configuration Manager console tips and Configure role-based administration.

将 SMBIOS GUID 列添加到设备和设备集合节点Add SMBIOS GUID column to device and device collection nodes

在设备和设备集合节点中,现在可以为“SMBIOS GUID”添加新列 。In both the Devices and Device Collections nodes, you can now add a new column for SMBIOS GUID. 此值与 System Resource 类的“BIOS GUID”属性相同。This value is the same as the BIOS GUID property of the System Resource class. 它是设备硬件的唯一标识符。It's a unique identifier for the device hardware.

对安全节点的管理服务支持Administration service support for security nodes

现可启用 Configuration Manager 控制台的某些节点以使用管理服务。You can now enable some nodes of the Configuration Manager console to use the administration service. 此项更改使控制台可以通过 HTTPS 而不是 WMI 来与 SMS 提供程序进行通信。This change allows the console to communicate with the SMS Provider over HTTPS instead of via WMI.

有关详细信息,请参阅管理服务For more information, see Administration service.

备注

从版本 1906 开始,站点属性上的“客户端计算机通信”选项卡现在称为“通信安全” 。Starting in version 1906, the Client Computer Communication tab on the site properties is now called Communication Security.

设备节点中的“集合”选项卡Collections tab in devices node

在“资产和符合性”工作区中,转到“设备”节点,然后选择设备 。In the Assets and Compliance workspace, go to the Devices node, and select a device. 在详细信息窗格中,切换到新的“集合”选项卡。此选项卡列出包含此设备的集合。In the details pane, switch to the new Collections tab. This tab lists the collections that include this device.

备注

  • 此选项卡当前在“设备集合”节点下的设备子节点中不可用。This tab currently isn't available from a devices subnode under the Device Collections node. 例如,在集合上选择“显示成员”选项时,此选项卡不可用。For example, when you select the option to Show Members on a collection.
  • 对于某些用户而言,此选项卡可能无法按预期方式填充。This tab may not populate as expected for some users. 若要查看设备所属的完整集合列表,你必须具有“完全权限管理员”安全角色。To see the complete list of collections a device belongs to, you must have the Full Administrator security role. 这是一个已知问题。This is a known issue.

应用程序节点中的“任务序列”选项卡Task sequences tab in applications node

在“软件库”工作区中,展开“应用程序管理”,转到“应用程序”节点,然后选择应用程序 。In the Software Library workspace, expand Application Management, go to the Applications node, and select an application. 在详细信息窗格中,切换到新的“任务序列”选项卡。此选项卡列出了引用此应用程序的任务序列。In the details pane, switch to the new Task sequences tab. This tab lists the task sequences that reference this application.

显示脚本的集合名称Show collection name for scripts

在“监视”工作区中,选择“脚本状态”节点 。In the Monitoring workspace, select the Script Status node. 除了列出 ID 之外,还列出了“集合名称”。It now lists the Collection Name in addition to the ID.

设备列表中的实时操作Real-time actions from device lists

有多种方法可以在“资产和符合性”工作区中的“设备”节点下显示设备列表 。There are various ways to display a list of devices under the Devices node in the Assets and Compliance workspace.

  • 在“资产和符合性”工作区中,选择“设备集合”节点。In the Assets and Compliance workspace, select the Device Collections node. 选择设备集合,然后选择“显示成员”操作。Select a device collection, and choose the action to Show members. 此操作将打开“设备”节点的子节点,其中包含该集合的设备列表。This action opens a subnode of the Devices node with a device list for that collection.

    • 选择集合子节点时,现在可以从功能区的集合组中启动“CMPivot”。When you select the collection subnode, you can now start CMPivot from the Collection group of the ribbon.
  • 在“监视”工作区中,选择“部署”节点 。In the Monitoring workspace, select the Deployments node. 选择部署,然后在功能区中选择“查看状态”操作。Select a deployment, and choose the View Status action in the ribbon. 在部署状态窗格中,双击总资产,以向下钻取到设备列表。In the deployment status pane, double-click the total assets to drill-through to a device list.

    • 在此列表中选择设备时,现在可以从功能区的“设备”组中启动“CMPivot”和“运行脚本” 。When you select a device in this list, you can now start CMPivot and Run Scripts from the Device group of the ribbon.

按任务序列中的程序名称进行排序Order by program name in task sequence

在“软件库”工作区中,展开“操作系统”,选择“任务序列”节点 。In the Software Library workspace, expand Operating Systems, and select the Task Sequences node. 编辑任务序列,然后选择或添加安装包步骤。Edit a task sequence, and select or add the Install Package step. 如果包包含多个程序,则下拉列表现在按字母顺序对程序进行排序。If a package has more than one program, the drop-down list now sorts the programs alphabetically.

正确的客户端操作名称Correct names for client operations

在“监视”工作区中,选择“客户端操作” 。In the Monitoring workspace, select Client Operations. 现在,“切换到下一个软件更新点”操作已正确命名。The operation to Switch to next Software Update Point is now properly named.

弃用的功能和操作系统Deprecated features and operating systems

已删除和已启用的项中实施支持更改之前,先了解这些更改。Learn about support changes before they're implemented in removed and deprecated items.

版本 1906 删除了对以下功能的支持:Version 1906 drops support for the following features:

  • 无法安装新的应用程序目录角色。You can't install new application catalog roles. 更新后的客户端自动使用管理点进行用户可用应用程序部署。Updated clients automatically use the management point for user-available application deployments. 有关详细信息,请参阅为软件中心制定计划For more information, see Plan for Software Center.

版本 1906 弃用了对以下产品的支持:Version 1906 deprecates support for the following products:

  • Windows CE 7.0Windows CE 7.0
  • Windows 10 移动版Windows 10 Mobile
  • Windows 10 移动企业版Windows 10 Mobile Enterprise

其他更新Other updates

从此版本开始,以下功能不再预发行版本:As of this version, the following features are no longer pre-release:

除了新增功能外,这一版还有其他变化(如缺陷修复)。Aside from new features, this release also includes additional changes such as bug fixes. 有关详细信息,请参阅 Configuration Manager Current Branch(版本 1906)的更改摘要For more information, see Summary of changes in Configuration Manager current branch, version 1906.

有关 Configuration Manager 的 Windows PowerShell cmdlet 更改的详细信息,请参阅 PowerShell 版本 1906 发行说明For more information on changes to the Windows PowerShell cmdlets for Configuration Manager, see PowerShell version 1906 release notes.

以下更新汇总 (4517869) 于 2019 年 10 月 1 日起在控制台中提供:Configuration Manager 当前分支版本 1906 的更新汇总The following update rollup (4517869) is available in the console starting on October 1, 2019: Update rollup for Configuration Manager current branch, version 1906.

后续步骤Next steps

自 2019 年 8 月 16 日起,版本 1906 公开发布,可供所有用户安装。As of August 16, 2019, version 1906 is globally available for all customers to install.

准备好安装此版本时,请参阅安装 Configuration Manager 的更新用于安装更新 1906 的清单When you're ready to install this version, see Installing updates for Configuration Manager and Checklist for installing update 1906.

提示

若要安装新站点,请使用 Configuration Manager 的基准版本。To install a new site, use a baseline version of Configuration Manager.

了解详细信息:Learn more about:

关于已知的重要问题,请参阅发行说明For known, significant issues, see the Release notes.

更新站点后,还可以查看更新后清单After you update a site, also review the Post-update checklist.