Configuration Manager Technical Preview 2008 版中的功能Features in Configuration Manager technical preview version 2008

適用於: Configuration Manager (Technical Preview 分支)Applies to: Configuration Manager (technical preview branch)

此文章介紹 Configuration Manager Technical Preview 2008 版中可用的功能。This article introduces the features that are available in the technical preview for Configuration Manager, version 2008. 安裝此版本進行更新,並將新功能新增到您的 Technical Preview 網站。Install this version to update and add new features to your technical preview site.

請先檢閱 Technical Preview 文章,再安裝此更新。Review the technical preview article before installing this update. 該篇文章會讓您熟悉使用 Technical Preview 的一般需求和限制、如何在版本之間進行更新,以及如何提供意見反應。That article familiarizes you with the general requirements and limitations for using a technical preview, how to update between versions, and how to provide feedback.

下列各節說明要在此版本中試用的新功能:The following sections describe the new features to try out in this version:

集合查詢預覽Collection query preview

您現在可以在建立或編輯集合成員資格的查詢時預覽查詢結果。You can now preview the query results when you're creating or editing a query for collection membership. 從 [查詢陳述式內容] 對話方塊中預覽查詢結果。Preview the query results from the query statement properties dialog. 當您選取 [編輯查詢陳述式] 時,請選取集合查詢內容上的綠色三角形,以顯示 [查詢結果預覽] 視窗。When you select Edit Query Statement, select the green triangle on the query properties for the collection to show the Query Results Preview window. 如果您想要停止長時間執行的查詢,請選取 [停止]。Select Stop if you want to stop a long running query.

用戶端資料來源儀表板

針對功能更新分析 SetupDiag 錯誤Analyze SetupDiag errors for feature updates

隨著 Windows 10 2004 版的推出,SetupDiag (部分機器翻譯) 診斷工具也已包含在 Windows 安裝程式中。With the release of Windows 10, version 2004, the SetupDiag diagnostic tool is included with Windows Setup. 如果升級發生問題,SetupDiag 便會自動執行以判斷失敗的原因。If there's an issue with the upgrade, SetupDiag automatically runs to determine the cause of the failure.

針對使用 Windows 10 服務的功能更新部署,Configuration Manager 現在會收集並彙總 SetupDiag 結果。Configuration Manager now gathers and summarizes SetupDiag results from feature update deployments with Windows 10 servicing.

Configuration Manager 主控台 [軟體程式庫] 工作區中的 [Windows 10 服務] 儀表板現在包含 [集合錯誤] 的磚:The Windows 10 Servicing dashboard in the Software Library workspace of the Configuration Manager console now includes a tile for Collection Errors:

[Windows 10 服務] 儀表板中 [集合錯誤] 磚的螢幕擷取畫面

您可以將磚的範圍設定為特定集合。You can scope the tile to a specific collection. 每列都會顯示具有指定錯誤碼的失敗裝置數目。Each bar shows the number of devices that failed with the specified error code. 如需詳細資訊,請參閱 Windows 升級錯誤碼 (部分機器翻譯)。For more information, see Windows upgrade error codes.

分析 SetupDiag 錯誤的先決條件Prerequisites to analyze SetupDiag errors

  • 搭配 Configuration Manager 的 Windows 10 服務Windows 10 servicing with Configuration Manager

  • Windows 10 2004 版或更新版本Windows 10, version 2004, or later

監視案例健康情況Monitor scenario health

Configuration Manager 因其複雜性而較難進行疑難排解。Configuration Manager is complicated to troubleshoot. 系統延遲與元件之間的待辦項目特別複雜,而難以了解。It's especially complex to understand system latency and the backlog between components. 附加於雲端服務的功能也會增加此複雜性。Cloud service-attached features increase that complexity.

您現在可以使用 Configuration Manager 來監視端對端案例的健康情況。You can now use Configuration Manager to monitor the health of end-to-end scenarios. 其會模擬活動以公開效能計量與失敗點。It simulates activities to expose performance metrics and failure points. 這些綜合活動類似於 Microsoft 用來監視其雲端服務中某些元件的方法。These synthetic activities are similar to methods that Microsoft uses to monitor some components in its cloud services. 使用此額外資料來深入了解活動的時間範圍。Use this additional data to better understand timeframes for activities. 如果發生失敗,其能協助縮小調查範圍。If failures occur, it can help focus your investigation.

此版本中的第一個案例適用於 SQL Server Service BrokerThe first scenario in this release is for SQL Server Service Broker. Service Broker 是站台資料庫的必要設定。The service broker is a required configuration for the site database. Configuration Manager 中有許多核心子系統都會使用 Service Broker。Many of the core subsystems in Configuration Manager use the service broker.

案例健康情況的先決條件Prerequisites for scenario health

  • Configuration Manager 中的 [系統高權限管理員] 角色,其範圍涵蓋至頂層站台Full administrator role in Configuration Manager, with scope to the top-level site

試試看!Try it out!

請嘗試完成工作。Try to complete the tasks. 接著,傳送意見反應以及您對於此功能的想法。Then send Feedback with your thoughts on the feature.

  1. 前往 Configuration Manager 主控台中的 [監視] 工作區,然後選取 [案例健全狀況] 節點。In the Configuration Manager console, go to the Monitoring workspace, and select the Scenario Health node.

    清單檢視會顯示可用的案例。The list view displays the available scenarios.

    主控台中的 [案例健全狀況] 節點

  2. 選取 [Service Broker 健全狀況] 案例,然後選取功能區中的 [顯示狀態]。Select the Service Broker Health scenario, then in the ribbon, select Show Status.

    此動作會開啟具有詳細資訊的視窗。This action opens a window with more information. 頂端區段會顯示每個站台的整體狀態。The top section shows the overall status per site. 選取某個站台,以在底部區段中查看該站台更加詳細的狀態。Select a site, to see more detailed status for that site in the bottom section.

    Service Broker 綜合活動狀態

  3. 從 [Service Broker 健全狀況] 節點,選取功能區中的 [案例設定]。From the Service Broker Health node, in the ribbon, select Scenario Settings. 您可以設定此案例的設定,例如其是否啟用,以及以分鐘為單位的時間間隔。You can configure the settings for this scenario, such as whether it's enabled, and the time interval in minutes.

  4. 從 [Service Broker 健全狀況] 節點,選取功能區中的 [歷程記錄]。From the Service Broker Health node, in the ribbon, select History. 此節點會顯示綜合交易先前的執行個體。This node displays the previous instances of the synthetic transaction. 使用此歷程記錄來追蹤案例在一段時間內的健康情況。Use this history to track the scenario's health over time. 從 [歷程記錄] 節點,您也可以針對特定執行個體使用 [顯示狀態]。From the history node, you can also Show Status of a specific instance.

透過此健康情況資訊,您便可以了解 SQL Server 透過 Service Broker 交換訊息所需的時間。With this health information, you can see how long it takes for SQL Server to exchange messages via the service broker. 較長的延遲或逾時,便代表處理佇列中出現待辦項目。A longer delay or timeout shows a backlog in the processing queue. 失敗表示 Service Broker 出現較大的問題,例如佇列已停用。A failure indicates a larger problem with the service broker, such as the queue is disabled. 由於 SQL Server Service Broker 是核心元件,其發生問題可能會影響到許多其他案例。Since SQL Server service broker is a core component, issues with it can impact many other scenarios. 例如用戶端通知用戶端狀態,以及某些租用戶附加功能。For example, client notifications, client status, and some tenant attach features.

集合評估檢視Collection evaluation view

我們已將集合評估檢視器的功能整合到 Configuration Manager 主控台。We've integrated the functionality of Collection Evaluation Viewer into the Configuration Manager console. 此變更能為系統管理員提供集中式位置,以檢視集合評估程序並對其進行疑難排解。This change provides administrators a central location to view and troubleshoot the collection evaluation process. 主控台現在會顯示下列資訊:The console now displays the following information:

  • 完整與增量集合評估的歷史與即時資訊Historic and live information for full and incremental collection evaluations
  • 評估佇列狀態The evaluation queue status
  • 完成集合評估的時間The time for collection evaluations to complete
  • 目前正在評估的集合Which collections are currently being evaluated
  • 啟動與完成集合評估的預估時間The estimated time that a collection evaluation will start and complete

為 [裝置集合] 節點新增欄Add columns for the Device Collections node

  1. 在 Configuration Manager 主控台中,移至 [資產與合規性] > [概觀] > [裝置集合]。In the Configuration Manager console, go to Assets and Compliance > Overview > Device Collections.
  2. 新增下列任一或所有欄,其前面會以評估類型來區分:Add any or all of the following columns prefixed by the type of evaluation:
    • 評估 (完整)Evaluation (Full)
      • 上次完成時間:上一次集合評估完成的時間 (預設欄)Last Completion Time: When the last collection evaluation completed (default column)
      • 執行階段:前次集合評估已執行多久 (秒)Run Time: How long the last collection evaluation ran, in seconds
      • 下次重新整理時間:下一個完整評估開始的時間Next Refresh Time: When the next full evaluation starts
      • 成員變更:前次集合評估中的成員變更。Member Changes: The member changes in the last collection evaluation. 正數表示已新增成員,而負數表示已移除成員。Positive numbers mean members were added while negative numbers mean members were removed.
      • 前次成員變更時間:集合評估中發生成員資格變更的最近時間Last Member Change Time: The most recent time that there was a membership change in the collection evaluation
    • 評估 (增量)Evaluation (Incremental)
      • 前次評估完成時間:前次集合評估完成時間Last Evaluation Completion Time: When the last collection evaluation completed
      • 執行階段:前次集合評估已執行多久 (秒)Run Time: How long the last collection evaluation ran, in seconds
      • 成員變更:前次集合評估中的成員變更。Member Changes: The member changes in the last collection evaluation. 這些變更是加上 (新增成員) 或減去 (已移除成員)。These changes are either plus (members added) or minus (members removed).
      • 前次成員變更時間:集合評估中發生成員資格變更的最近時間Last Member Change Time: The most recent time that there was a membership change in the collection evaluation

檢視集合摘要資訊View collection summary information

  1. 從 [裝置集合] 節點中選取集合。Select a collection from the Device Collections node.
  2. 在集合的 [摘要] 群組窗格中,檢閱與評估相關的資訊。In the Summary group pane for collection, review the evaluation-related information.
  3. [相關物件] 會提供連結,以在 [監視] 工作區中 [集合評估] 節點底下的特定佇列中檢視集合的狀態。The Related Objects give links to view status of the collection in the specific queue under the Collection Evaluation node in the Monitoring workspace.
    • 此動作會建立新節點,您可以在其中查看指定集合的評估狀態。This action creates a new node is created where you can see the evaluation status for the specific collection.

選取集合之 [摘要] 群組中的評估相關資訊

監視集合評估佇列Monitoring collection evaluation queues

  1. 在 [監視] 工作區中,移至 [集合評估] 節點。From the Monitoring workspace, go to the Collection Evaluation node. 下列佇列會加以摘要並具有自己的節點:The following queues are summarized and have their own nodes:

    • 完整評估佇列:針對要完整評估的集合Full Evaluation Queue: For collections due for full evaluation
    • 累加評估佇列:針對具有增量評估的集合Incremental Evaluation Queue: For collections with incremental evaluation
    • 手動評估佇列:針對系統管理員已手動從主控台選取要評估的集合Manual Evaluation Queue: For collections that an administrator has manually selected for evaluation from the console
    • 新評估佇列:針對新建立的集合New Evaluation Queue: For newly created collections
  2. 在 [集合評估] 節點中,會將佇列中的集合總數與佇列長度列為摘要。From the Collection Evaluation node, the total number of collections in queue and queue length is listed as a summary. 此外,也會列出評估佇列的下列狀態摘要:Additionally, the following status summaries for the evaluation queues are listed:

    • 佇列中的集合數Number of collections in queue
    • 佇列長度Queue length
    • 目前評估集合Current evaluation collection
    • 目前評估開始時間Current evaluation started on
    • 目前評估經過時間 (秒)Current evaluation elapsed (seconds)
  3. 選取佇列的節點會顯示佇列的詳細狀態,包括:Selecting the node for a queue brings up detailed status for the queue including:

    • 名稱:集合的名稱Name: Name of the collection
    • 集合識別碼:集合的識別碼Collection ID: ID of the collection
    • 預估完成時間:評估預估完成時間Estimated Completion Time: When the evaluation is estimated to complete
    • 預估執行時間:評估預估執行多久,格式為 day:hour:minute:secondEstimated Run Time: How long the evaluation is estimated to run, in day:hour:minute:second format

    [手動評估佇列] 節點,其具有每個集合之評估的詳細資訊

試試看!Try it out!

請嘗試完成工作。Try to complete the tasks. 接著,傳送意見反應以及您對於此功能的想法。Then send Feedback with your thoughts on the feature.

  1. 從 [裝置集合] 節點中選取集合。Select a collection from the Device Collections node. 在資訊窗格中,檢閱評估相關狀態,以及每個評估佇列狀態的 [相關物件] 連結。In the information pane, review the evaluation-related status and the Related objects links for each evaluation queue's status.
  2. 將評估相關的欄新增到集合檢視。Add an evaluation-related column to the collection view.
  3. 在 [監視] 節點中檢閱集合評估狀態:Review the collection evaluation status in Monitoring node:
    • 觸發集合評估 (例如更新成員資格規則),然後瀏覽到 [集合評估] 節點以檢視狀態。Trigger a collection evaluation (such as updating a membership rule), then navigate to the Collection Evaluation node to view the status.
    • 觸發集合評估,然後檢視不同類型評估的佇列狀態節點,例如 [手動評估佇列]。Trigger a collection evaluation, then view queue status nodes for the different types of evaluation such as the Manual Evaluation Queue.

在主控台中查看工作順序大小See task sequence size in the console

此版本會繼續針對 Technical Preview 2004 版2007 版中的變更進行修改,以協助您管理工作順序的大小。This release continues to iterate on changes in technical preview version 2004 and version 2007 to help you manage the size of task sequences. 當您在 Configuration Manager 主控台中檢視工作順序的清單時,請新增 [大小 (KB)] 欄。When you view the list of task sequences in the Configuration Manager console, add the Size (KB) column. 使用此欄來識別可能會導致問題的大型工作順序。Use this column to identify large task sequences that can cause problems.

注意

此值會在系統儲存工作順序時更新。This value is updated when the task sequence is saved. 在升級之後,該值將會顯示為 0KB,直到已編輯工作順序並儲存變更為止。After upgrade the value will show as 0KB until the task sequence is edited and changes are saved.

刪除過時的已收集診斷檔案工作Delete Aged Collected Diagnostic Files task

您現在會有新的維護工作,可用來清除已收集的診斷檔案You now have a new maintenance task available for cleaning up collected diagnostic files. [刪除過時的已收集診斷檔案] 會使用 14 天的預設值來尋找需要清除的診斷檔案,且不會影響一般收集到的檔案。Delete Aged Collected Diagnostic Files uses a default value of 14 days when looking for diagnostic files to clean up and doesn't affect regular collected files. 這個新的維護工作預設會啟用。The new maintenance task is enabled by default.

將物件匯入到目前的資料夾Import objects to current folder

根據您的意見反應,現在當您在 Configuration Manager 主控台中匯入物件時,其會匯入到目前的資料夾。Based on your feedback, now when you import an object in the Configuration Manager console, it imports to the current folder. 之前,Configuration Manager 一律會將匯入的物件置於根節點。Previously, Configuration Manager always put imported objects in the root node. 這個新的行為適用於應用程式、套件、驅動程式套件,以及工作順序。This new behavior applies to applications, packages, driver packages, and task sequences.

例如:For example:

  1. 在 Configuration Manager 主控台中,移至 [軟體程式庫]**** 工作區,展開 [應用程式管理]****,然後選取 [套件]**** 節點。In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node.
  2. 在功能區的 [資料夾] 索引標籤上,選取 [建立資料夾]。In the ribbon, on the Folder tab, select Create Folder. 將其命名為 TestName it Test. 如果尚未選取新的資料夾,請加以選取。If it's not already selected, select the new folder.
  3. 在功能區的 [常用] 索引標籤上,選取 [匯入]。In the ribbon, on the Home tab, select Import. 匯入套件物件。Import a package object.

Configuration Manager 主控台會將套件匯入到 [Test] 資料夾,而非根 [套件] 節點。The Configuration Manager console imports the package into the Test folder, instead of the root Packages node.

後續步驟Next steps

如需安裝或升級 Technical Preview 分支的詳細資訊,請參閱 Technical PreviewFor more information about installing or updating the technical preview branch, see Technical preview.

如需 Configuration Manager 不同分支的詳細資訊,請參閱我應該使用哪個 Configuration Manager 分支?For more information about the different branches of Configuration Manager, see Which branch of Configuration Manager should I use?.