Configuration Manager 中站台系統角色的設定選項Configuration options for site system roles in Configuration Manager

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

Configuration Manager 站台系統角色的大部分設定選項都是一目了然,或是您在設定它們時就已在精靈或對話方塊中加以說明。Most configuration options for Configuration Manager site system roles are self-explanatory or are explained in the wizard or dialog boxes when you configure them. 下列各節說明其設定可能需要其他資訊的站台系統角色。The following sections explain site system roles whose settings might require additional information.

應用程式類別目錄網站點Application catalog website point

重要

從 1806 最新分支版本開始即不支援應用程式類別目錄的 Silverlight 使用者體驗。The application catalog's 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 the following articles:

如需有關如何設定應用程式類別目錄網站點的詳細資訊,請參閱規劃和設定應用程式管理For more information about how to set up the application catalog website point, see Plan for and configure application management.

應用程式類別目錄 Web 服務點Application catalog web service point

重要

從 1806 最新分支版本開始即不支援應用程式類別目錄的 Silverlight 使用者體驗。The application catalog's 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 the following articles:

如需如何設定應用程式類別目錄 Web 服務點的詳細資訊,請參閱規劃和設定應用程式管理For more information about how to set up the Application Catalog web service point, see Plan for and configure application management.

憑證登錄點Certificate registration point

如需如何設定憑證登錄點的詳細資訊,請參閱憑證設定檔簡介For more information about how to set up the certificate registration point, see Introduction to certificate profiles.

發佈點Distribution point

如需如何設定內容部署發佈點的詳細資訊,請參閱管理內容與內容基礎結構For more information about how to set up the distribution point for content deployment, see Manage content and content infrastructure.

如需如何設定 PXE 部署發佈點的詳細資訊,請參閱使用 PXE 透過網路部署 WindowsFor more information about how to set up the distribution point for PXE deployments, see Use PXE to deploy Windows over the network.

如需如何設定多點傳送部署發佈點的詳細資訊,請參閱使用多點傳送透過網路部署 WindowsFor more information about how to set up the distribution point for multicast deployments, see Use multicast to deploy Windows over the network.

在 Configuration Manager 需要時安裝並設定 IISInstall and configure IIS if required by Configuration Manager

選取此選項,讓 Configuration Manager 在站台系統上安裝及設定 IIS (如果尚未安裝)。Select this option to let Configuration Manager install and set up IIS on the site system if it's not already installed. IIS 必須安裝在所有發佈點上,而且您必須選取此設定以在精靈中繼續操作。IIS must be installed on all distribution points, and you must select this setting to continue in the wizard.

站台系統安裝帳戶Site system installation account

對於安裝在站台伺服器的發佈點,只有站台伺服器的電腦帳戶可以當成站台系統安裝帳戶來使用。For distribution points that are installed on a site server, only the computer account of the site server is supported for use as the site system installation account. 如需詳細資訊,請參閱帳戶For more information, see Accounts.

註冊點Enrollment point

註冊點可用來安裝 macOS 電腦,以及註冊您利用內部部署行動裝置管理所管理的裝置。Enrollment points are used to install macOS computers and enroll devices that you manage with on-premises mobile device management. 如需詳細資訊,請參閱下列文章:For more information, see the following articles:

允許的連線Allowed connections

HTTPS 設定會自動選取,且需要在伺服器上提供 PKI 憑證,才能用於對註冊 Proxy 點進行伺服器驗證,並透過 SSL 進行資料加密。The HTTPS setting is automatically selected and requires a PKI certificate on the server for server authentication to the enrollment proxy point, and encryption of data over SSL. 如需詳細資訊,請參閱 PKI 憑證需求For more information, see PKI certificate requirements.

如需伺服器憑證的範例部署,以及如何在 IIS 中進行設定的相關資訊,請參閱為執行 IIS 的站台系統部署 Web 伺服器憑證For an example deployment of the server certificate and information about how to configure it in IIS, see Deploying the web server certificate for site systems that run IIS.

註冊 Proxy 點Enrollment proxy point

如需如何為行動裝置設定註冊 Proxy 點的詳細資訊,請參閱使用者如何使用內部部署 MDM 註冊裝置For more information about how to set up an enrollment proxy point for mobile devices, see How users enroll devices with on-premises MDM.

用戶端連線Client connections

系統會自動選取 HTTPS 設定。The HTTPS setting is automatically selected. 它在伺服器上需要有下列 PKI 憑證:It requires the following PKI certificates on the server:

  • 對您使用 Configuration Manager 註冊的行動裝置和 Mac 電腦進行的伺服器驗證For server authentication to mobile devices and Mac computers that you enroll with Configuration Manager
  • 透過安全通訊端層 (SSL) 的資料加密For encryption of data over Secure Sockets Layer (SSL)

如需憑證需求的詳細資訊,請參閱 PKI 憑證需求For more information about the certificate requirements, see PKI certificate requirements.

如需伺服器憑證的範例部署,以及如何在 IIS 中進行設定的相關資訊,請參閱為執行 IIS 的站台系統部署 Web 伺服器憑證For an example deployment of the server certificate and information about how to configure it in IIS, see Deploying the web server certificate for site systems that run IIS.

後援狀態點Fallback status point

狀況訊息數目和節流間隔 (秒)Number of state messages and Throttle interval (in seconds)

這些選項的預設設定是 10,000 則狀況訊息和 3,600 秒的節流間隔。The default settings for these options are 10,000 state messages and 3,600 seconds for the throttle interval. 雖然這些設定足以應付大部分的情況,但您可能必須在下列兩個條件都成立時變更它們:While these settings are sufficient for most circumstances, you might have to change them when both of the following conditions are true:

  • 後援狀態點僅接受來自內部網路的連線。The fallback status point accepts connections only from the intranet.

  • 在為多部電腦進行用戶端部署首展期間,您會使用後援狀態點。You use the fallback status point during a client deployment rollout for many computers.

在此案例中,持續的狀況訊息資料流可能會造成狀況訊息的積存,該積存會使得站台伺服器上處理器使用量過高的情況持續一段時間。In this scenario, a continuous stream of state messages might create a backlog of state messages that causes high processor usage on the site server for a sustained period. 此外,您可能會看不到 Configuration Manager 主控台以及在用戶端部署報告中用戶端部署的最新資訊。In addition, you might not see up-to-date information about the client deployment in the Configuration Manager console and in the client deployment reports.

這些後援狀態點的設計,主要是針對用戶端部署期間所產生狀態訊息進行設定。These fallback status point settings are designed to be set up for state messages that are generated during client deployment. 這些設定並不是針對用戶端通訊問題而設計的,例如,當網際網路上的用戶端無法連線到以網際網路為基礎的管理點時。The settings aren't designed to be set up for client communication issues, like when clients on the internet can't connect to their internet-based management point. 由於後援狀態點無法只將這些設定套用到在用戶端部署期間所產生的狀況訊息,因此,請勿在後援狀態點接受來自網際網路的連線時設定這些設定。Because the fallback status point can't apply these settings just to the state messages that are generated during client deployment, don't configure these settings when the fallback status point accepts connections from the internet.

成功安裝 Configuration Manager 用戶端的每一部電腦,都會將下列四種狀況訊息傳送到後援狀態點:Each computer that successfully installs the Configuration Manager client sends the following four state messages to the fallback status point:

  • 已啟動用戶端部署Client deployment started

  • 成功完成用戶端部署Client deployment succeeded

  • 已啟動用戶端指派Client assignment started

  • 成功完成用戶端指派Client assignment succeeded

無法安裝的電腦或指派 Configuration Manager 用戶端的電腦,都會傳送其他的狀況訊息。Computers that can't be installed or that assign the Configuration Manager client send additional state messages.

例如,假設您將 Configuration Manager 用戶端部署到 20,000 部電腦,部署可能會傳送 80,000 個狀態訊息到後援狀態點。For example, if you deploy the Configuration Manager client to 20,000 computers, the deployment might send 80,000 state messages to the fallback status point. 因為預設的節流設定可每 3600 秒 (1 小時) 傳送 10,000 個狀態訊息到後援狀態點,所以狀態訊息可能會積存在後援狀態點上。Because the default throttling configuration lets 10,000 state messages to be sent to the fallback status point each 3,600 seconds (1 hour), state messages might become backlogged on the fallback status point. 此外,也必須考慮到後援狀態點和站台伺服器之間的可用網路頻寬,以及可處理許多狀況訊息之站台伺服器的處理能力。Also consider the available network bandwidth between the fallback status point and the site server and the processing power of the site server to process many state messages.

為避免發生這些問題,請考慮增加狀態訊息數目,並縮短節流間隔時間。To help prevent these issues, consider an increase in the number of state messages and a decrease in the throttle interval.

如果下列其中一項條件為 True,請重設後援狀態點的節流值:Reset the throttle values for the fallback status point if either of the following conditions is true:

  • 您估計目前的節流值,比處理來自後援狀態點之狀況訊息所需的節流值還要高。You calculate that the current throttle values are higher than required to process state messages from the fallback status point.

  • 您發現目前的節流設定會在站台伺服器上導致高處理器使用量。You find that the current throttle settings create high processor usage on the site server.

除非您了解會產生何種結果,否則請勿變更後援狀態點節流設定的設定值。Don't change the settings for the fallback status point throttle settings unless you understand the consequences. 例如,當您提高節流設定時,站台伺服器上的處理器使用量就會增高,進而造成所有的站台作業變得緩慢。For example, when you increase the throttle settings to high, the processor usage on the site server can increase to high, which slows down all site operations.