Configuration Manager 最新分支 1906 版的新功能What's new in version 1906 of Configuration Manager current branch

適用於:Configuration Manager (最新分支)Applies to: Configuration Manager (current branch)

Configuration Manager 最新分支的更新 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 的程式名稱與 sessionid。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 可以在可用性群組上重新建立資料庫。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).

注意

在相同的用戶端設定群組中,[Enable Configuration Manager client in full OS to share content] (在完整作業系統中啟用 Configuration Manager 用戶端以共用內容) 的現有設定現在已重新命名為 [Enable as peer cache source] (啟用為對等快取來源)。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 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.

  • 工作順序會設定新的唯讀變數 _SMSTSLastContentDownloadLocationThe 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

您現在具有其他 WSUS 維護工作,可讓 Configuration Manager 執行來維護良好的軟體更新點。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. 動態更新會引導用戶端從網際網路下載這些更新,以在 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 Update,而不是像舊版一樣作為 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 Apps 更新For more information, see Monitor software updates, Manage Windows as a service, and Manage Microsoft 365 Apps updates.

Office 管理Office management

Office 365 ProPlus 升級整備儀表板Office 365 ProPlus upgrade readiness dashboard

為協助您判斷哪些裝置已準備好升級至 Microsoft 365 Apps 企業版,已提供新的整備儀表板。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 ProPlus 升級整備圖格。It includes the Office 365 ProPlus upgrade readiness tile that released in Configuration Manager current branch version 1902. 在 Configuration Manager 主控台中,移至 [軟體程式庫] 工作區,展開 [Office 365 用戶端管理],然後選取 [Office 365 ProPlus 升級整備] 節點。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 ProPlus 整備的整合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. 這個值與系統資源類別的 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 和簡訊提供者通訊,而非透過 Wi-Fi。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. 它現在除了識別碼之外,還會列出 [集合名稱]。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.

    • 當您選取集合的子節點時,您現在可以從功能區的 [集合] 群組啟動 。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 MobileWindows 10 Mobile
  • Windows 10 Mobile EnterpriseWindows 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 最新分支 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.

自 2019 年 10 月 1 日起,就可在主控台中使用更新彙總套件 (4517869):適用於 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.