Configuration Manager 中的內容管理基本概念Fundamental concepts for content management in Configuration Manager

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

Configuration Manager 支援健全的工具和選項系統來管理軟體內容。Configuration Manager supports a robust system of tools and options to manage software content. 應用程式、套件、軟體更新和 OS 部署等軟體部署都需要內容。Software deployments such as applications, packages, software updates, and OS deployments all need content. Configuration Manager 會將內容同時儲存在站台伺服器和發佈點上。Configuration Manager stores the content on both site servers and distribution points. 在位置之間傳輸此內容時會需要大量的網路頻寬。This content requires a large amount of network bandwidth when it's being transferred between locations. 若要有效規劃及使用內容管理基礎結構,請先了解可用的選項與設定。To plan and use the content management infrastructure effectively, first understand the available options and configurations. 然後考量如何使用它們,才能最滿足您的網路環境和內容部署需求。Then consider how to use them to best fit your networking environment and content deployment needs.

提示

如需有關內容發佈程序的詳細資訊,以及尋求診斷和解決一般內容發佈問題的協助,請參閱了解 Microsoft Configuration Manager 中的內容發佈及進行疑難排解(機器翻譯)。For more information about the content distribution process and to find help in diagnosing and resolving general content distribution problems, see Understanding and Troubleshooting Content Distribution in Microsoft Configuration Manager.

下列各節是內容管理的重要概念。The following sections are key concepts for content management. 當概念需要其他資訊或複雜資訊時,便會提供連結將您導向那些詳細資料。When a concept requires additional or complex information, links are provided to direct you to those details.

用於內容管理的帳戶Accounts used for content management

下列帳戶可用於內容管理:The following accounts can be used with content management:

網路存取帳戶Network access account

用戶端用以連線到發佈點和存取內容。Used by clients to connect to a distribution point and access content. 根據預設,會先嘗試電腦帳戶。By default, the computer account is tried first.

提取發佈點也會使用此帳戶從遠端樹系中的來源發佈點下載內容。This account is also used by pull-distribution points to download content from a source distribution point in a remote forest.

某些情況下已不再需要網路存取帳戶。Some scenarios no longer require a network access account. 您可以允許站台使用具有 Azure Active Directory 驗證的增強 HTTP。You can enable the site to use Enhanced HTTP with Azure Active Directory authentication.

如需詳細資訊,請參閱網路存取帳戶For more information, see Network access account.

套件存取帳戶Package access account

根據預設,Configuration Manager 會將發佈點上的內容存取權授與一般存取帳戶使用者和系統管理員。By default, Configuration Manager grants access to content on a distribution point to the generic access accounts Users and Administrators. 不過,您可以設定其他權限以限制存取。However, you can configure additional permissions to restrict access.

如需詳細資訊,請參閱 Package access account (套件存取帳戶)。For more information, see Package access account.

頻寬節流設定和排程Bandwidth throttling and scheduling

節流和排程選項皆可協助您控制將內容從站台伺服器發佈到發佈點的時機。Both throttling and scheduling are options that help you control when content is distributed from a site server to distribution points. 這些功能類似於站台對站台檔案式複寫的頻寬控制,但並不直接相關。These capabilities are similar to, but not directly related to bandwidth controls for site-to-site file-based replication.

如需詳細資訊,請參閱在 System Center Configuration Manager 中管理網路頻寬以進行內容管理For more information, see Manage network bandwidth.

二進位差異複寫Binary differential replication

Configuration Manager 會使用二進位差異複寫 (BDR) 來更新您先前發佈至其他站台或遠端發佈點的內容。Configuration Manager uses binary differential replication (BDR) to update content that you previously distributed to other sites or to remote distribution points. 若要支援 BDR 降低頻寬使用量,請在發佈點上安裝 [遠端差異壓縮] 功能。To support BDR's reduction of bandwidth usage, install the Remote Differential Compression feature on distribution points. 如需詳細資訊,請參閱發佈點必要條件For more information, see Distribution point prerequisites.

BDR 可將用來傳送所發佈內容更新的網路頻寬降到最低。BDR minimizes the network bandwidth used to send updates for distributed content. 每當您變更內容來源檔案時,它只會重新傳送新的或已變更的內容,而不會傳送整組檔案。It resends only the new or changed content instead of sending the entire set of content source files each time you change those files.

使用 BDR 時,Configuration Manager 會針對您之前發佈的每一組內容,識別來源檔案的變更。When BDR is used, Configuration Manager identifies the changes that occur to source files for each set of content that you previously distributed.

  • 當來源內容中的檔案發生變更時,站台會建立該內容的新累加版本。When files in the source content change, the site creates a new incremental version of the content. 然後只將已變更的檔案複寫到目的地站台和發佈點。It then replicates only the changed files to destination sites and distribution points. 如果您將檔案重新命名、移動或變更檔案的內容,系統就會將該檔案視為已變更。A file is considered changed if you renamed or moved it, or if you changed the contents of the file. 舉例來說,如果您替換之前發佈至數個站台之驅動程式套件中的一個驅動程式檔案,系統只會複寫那個已變更的驅動程式檔案。For example, if you replace a single driver file for a driver package that you previously distributed to several sites, only the changed driver file is replicated.

  • Configuration Manager 最多可支援五個累加版本的內容集。Configuration Manager supports up to five incremental versions of a content set before it resends the entire content set. 在第五次更新之後,下次對內容集進行變更時,站台就會建立一個新版本的內容集。After the fifth update, the next change to the content set causes the site to create a new version of the content set. Configuration Manager 便會發佈新的內容集以取代舊的內容集以及任何累加版本。Configuration Manager then distributes the new version of the content set to replace the previous set and any of its incremental versions. 在發佈新的內容集之後,稍後對來源檔案進行的累加變更會再次由 BDR 複寫。After the new content set is distributed, later incremental changes to the source files are again replicated by BDR.

系統支援階層中每個父子站台之間的 BDR。BDR is supported between each parent and child site in a hierarchy. 在站台內的站台伺服器與其標準發佈點之間可支援 BDR。BDR is supported within a site between the site server and its regular distribution points. 不過,提取發佈點和雲端發佈點則不支援使用 BDR 來傳輸內容。However, pull-distribution points and cloud distribution points don't support BDR to transfer content. 提取發佈點支援檔案層級的差異、傳送新的檔案,但不支援檔案內的區塊。Pull-distribution points support file-level deltas, transferring new files, but not blocks within a file.

應用程式會一律使用二進位差異複寫。Applications always use binary differential replication. BDR 對套件而言是選用的,預設不會啟用。BDR is optional for packages and isn't enabled by default. 若要針對套件使用 BDR,請為每個套件啟用此功能。To use BDR for packages, enable this functionality for each package. 當您建立或編輯套件時,請選取 [啟用二進位差異複寫] 選項。Select the option Enable binary differential replication when you create or edit a package.

BDR 或差異複寫BDR or delta replication

下列清單摘要說明「二進位差異複寫」(BDR) 與「差異複寫」之間的不同。The following lists summarize the differences between binary differential replication (BDR) and delta replication.

二進位差異複寫摘要Summary of binary differential replication

  • Configuration Manager 對 Windows「遠端差異壓縮」的稱呼Configuration Manager's term for Windows Remote Differential Compression
  • 「區塊」層級的差異Block-level differences
  • 針對應用程式一律啟用Always enabled for apps
  • 在舊版套件上為選用Optional on legacy packages
  • 如果檔案已經存在於發佈點上而有變更,站台就會使用 BDR 來複寫區塊層級的變更,而不會複寫整個檔案。If a file already exists on the distribution point, and there's a change, the site uses BDR to replicate the block-level change instead of the entire file. 只有當啟用物件來使用 BDR 時,才會套用此行為。This behavior only applies when you enable the object to use BDR.

差異複寫摘要Summary of delta replication

  • 「檔案」層級的差異File-level differences
  • 預設為開啟,無法設定On by default, not configurable
  • 當套件發生變更時,站台會檢查對個別檔案的變更,而不會檢查對整個套件的變更。When a package changes, the site checks for changes to the individual files instead of the entire package.
    • 如果檔案發生變更,請使用 BDR 來進行工作If a file changes, use BDR to do the work
    • 如果有新檔案,請複製新檔案If there's a new file, copy the new file

對等快取技術Peer caching technologies

Configuration Manager 支援數個選項來管理相同網路上對等裝置之間的內容:Configuration Manager supports several options for managing content between peer devices on the same network:

使用下表來比較這些技術的主要功能:Use the following table to compare major features of these technologies:

功能Feature 對等快取Peer cache 傳遞最佳化Delivery Optimization BranchCacheBranchCache
跨子網路Across subnets Yes Yes No
頻寬節流處理Throttle bandwidth 是 (BITS)Yes (BITS) 是 (原生)Yes (native) 是 (BITS)Yes (BITS)
部分內容Partial content Yes Yes Yes
控制磁碟上的快取大小Control cache size on disk Yes Yes Yes
對等來源探索Peer source discovery 手動 (用戶端設定)Manual (client setting) 自動Automatic 自動Automatic
同儕節點探索Peer discovery 透過管理點 (使用界限群組)Via management point using boundary groups DO 雲端服務DO cloud service 廣播Broadcast
報告Reporting 用戶端資料來源儀表板Client data sources dashboard 用戶端資料來源儀表板Client data sources dashboard 用戶端資料來源儀表板Client data sources dashboard
WAN 使用控制WAN usage control 界限群組Boundary groups DO GroupIDDO GroupID 僅限子網路Subnet only
支援的內容Supported content 所有 ConfigMgr 內容All ConfigMgr content Windows 更新、驅動程式、市集應用程式Windows updates, drivers, store apps 所有 ConfigMgr 內容All ConfigMgr content
原則控制Policy control 用戶端代理程式設定Client agent settings 用戶端代理程式設定 (部分)Client agent settings (partial) 用戶端代理程式設定Client agent settings

建議Recommendations

  • 現代化管理:如果您已經在使用現代化工具 (例如 Intune),請實作「傳遞最佳化」Modern management: If you're already using modern tools such as Intune, implement Delivery Optimization

  • Configuration Manager 和共同管理:使用對等快取與「傳遞最佳化」的組合。Configuration Manager and co-management: Use a combination of peer cache and Delivery Optimization. 使用對等快取搭配內部部署發佈點,並針對雲端案例使用「傳遞最佳化」。Use peer cache with on-premises distribution points, and use Delivery Optimization for cloud scenarios.

  • 已實作的現有 BranchCache:同時使用這全部三種技術。Existing BranchCache implemented: Use all three technologies in parallel. 針對 BranchCache 所不支援的案例,使用對等快取和「傳遞最佳化」。Use peer cache and Delivery Optimization for scenarios that aren't supported by BranchCache.

BranchCacheBranchCache

BranchCache 是一項 Windows 技術。BranchCache is a Windows technology. 用戶端如果支援 BranchCache 並已下載您為 BranchCache 設定的部署,便可作為其他支援 BranchCache 之用戶端的內容來源。Clients that support BranchCache, and have downloaded a deployment that you configure for BranchCache, then serve as a content source to other BranchCache-enabled clients.

例如,您有一個執行 Windows Server 2012 或更新版本的發佈點,並且設定為 BranchCache 伺服器。For example, you have a distribution point that runs Windows Server 2012 or later, and is configured as a BranchCache server. 當第一個支援 BranchCache 的用戶端從此伺服器要求內容時,用戶端會下載並快取該內容。When the first BranchCache-enabled client requests content from this server, the client downloads that content and caches it.

  • 接著,該用戶端會將內容提供給相同子網路上支援 BranchCache 的額外用戶端,這些用戶端也會快取該內容。That client then makes the content available for additional BranchCache-enabled clients on the same subnet that also cache the content.
  • 相同子網路上的其他用戶端就不需從發佈點下載內容。Other clients on the same subnet don't have to download content from the distribution point.
  • 該內容會分散在多個用戶端上以供未來傳輸。The content is distributed across multiple clients for future transfers.

如需詳細資訊,請參閱對 Windows BranchCache 的支援For more information, see Support for Windows BranchCache.

傳遞最佳化Delivery Optimization

您可以使用 Configuration Manager 界限群組,來定義和規範在您的公司網路上以及到遠端辦公室的內容發佈。You use Configuration Manager boundary groups to define and regulate content distribution across your corporate network and to remote offices. Windows 傳遞最佳化是一種雲端式點對點技術,可在 Windows 10 裝置之間共用內容。Windows Delivery Optimization is a cloud-based, peer-to-peer technology to share content between Windows 10 devices. 請設定讓「傳遞最佳化」在於同儕節點之間共用內容時,使用您的界限群組。Configure Delivery Optimization to use your boundary groups when sharing content among peers. 用戶端設定會套用界限群組識別碼作為用戶端上的「傳遞最佳化」群組識別碼。Client settings apply the boundary group identifier as the Delivery Optimization group identifier on the client. 當用戶端與「傳遞最佳化」雲端服務進行通訊時,它會使用此識別碼來尋找含有內容的同儕節點。When the client communicates with the Delivery Optimization cloud service, it uses this identifier to locate peers with the content. 如需詳細資訊,請參閱傳遞最佳化用戶端設定。For more information, see delivery optimization client settings.

傳遞最佳化是針對適用於 Windows 10 品質更新的快速安裝檔案,將 Windows 10 更新傳遞最佳化的建議技術。Delivery Optimization is the recommended technology to optimize Windows 10 update delivery of express installation files for Windows 10 quality updates. 從 Configuration Manager 1910 版開始,必須要能透過網際網路存取「傳遞最佳化」雲端服務,才能使用其中的點對點功能。Starting in Configuration Manager version 1910, Internet access to the Delivery Optimization cloud service is a requirement to utilize its peer-to-peer functionality. 如需所必要網際網路端點的資訊,請參閱傳遞最佳化的常見問題集For information about the needed internet endpoints, see Frequently asked questions for Delivery Optimization. 最佳化可用於所有 Windows 更新。Optimization can be used for all Windows updates. 如需詳細資訊,請參閱將 Windows 10 更新傳遞最佳化For more information, see optimize Windows 10 update delivery.

Microsoft 連線快取Microsoft Connected Cache

您可以在發佈點上安裝 Microsoft 網內快取伺服器。You can install a Microsoft Connected 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.

注意

從 1910 版開始,這項功能現在稱為 Microsoft 連線快取Starting in version 1910, this feature is now called Microsoft Connected Cache. 先前稱為傳遞最佳化網路內快取 (DOINC)。It was previously known as Delivery Optimization In-Network Cache.

此快取伺服器可視需要以透明方式快取傳遞最佳化所下載的內容。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 的發佈點內容。This cache is separate from Configuration Manager's distribution point content. 如果您選擇與發佈點角色相同的磁碟機,則會另外儲存內容。If you choose the same drive as the distribution point role, it stores content separately.

如需詳細資訊,請參閱 Configuration Manager 中的 Microsoft 連線快取For more information, see Microsoft Connected Cache in Configuration Manager.

對等快取Peer cache

用戶端對等快取可協助您管理對遠端位置中用戶端進行的內容部署。Client peer cache helps you manage deployment of content to clients in remote locations. 對等快取是一個內建的 Configuration Manager 解決方案,可讓用戶端直接從其本機快取與其他用戶端共用內容。Peer cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.

先將啟用對等快取的用戶端設定部署至集合。First deploy client settings that enable peer cache to a collection. 該集合的成員即可作為相同界限群組中其他用戶端的對等內容來源。Then members of that collection can act as a peer content source for other clients in the same boundary group.

用戶端對等快取來源可以將內容分割成組件。Client peer cache sources can divide content into parts. 這些組件會將網路傳輸減到最少以降低 WAN 使用量。These parts minimize the network transfer to reduce WAN utilization. 管理點可提供內容組件的更詳細追蹤。The management point provides more detailed tracking of the content parts. 它會嘗試排除對每一界限群組的相同內容進行多重下載的情況。It tries to eliminate more than one download of the same content per boundary group.

如需詳細資訊,請參閱 Configuration Manager 用戶端的對等快取For more information, see Peer cache for Configuration Manager clients.

Windows PE 對等快取Windows PE peer cache

使用 Configuration Manager 來部署新 OS 時,執行工作順序的電腦可以使用 Windows PE 對等快取。When you deploy a new OS with Configuration Manager, computers that run the task sequence can use Windows PE peer cache. 它們會從對等快取來源下載內容,而不會從發佈點下載內容。They download content from a peer cache source instead of from a distribution point. 此行為有助於在分公司沒有本機發佈點的案例中,將 WAN 流量降到最低。This behavior helps minimize WAN traffic in branch office scenarios where there's no local distribution point.

如需詳細資訊,請參閱 Windows PE 對等快取For more information, see Windows PE peer cache.

Windows LEDBATWindows LEDBAT

Windows Low Extra Delay Background Transport (LEDBAT) 是 Windows Server 的一個網路壅塞控制功能,可協助管理背景網路傳輸。Windows Low Extra Delay Background Transport (LEDBAT) is a network congestion control feature of Windows Server to help manage background network transfers. 針對所支援 Windows Server 版本上執行的發佈點,啟用一個選項來協助調整網路流量。For distribution points running on supported versions of Windows Server, enable an option to help adjust network traffic. 然後用戶端只會使用網路頻寬 (可用時)。Then clients only use network bandwidth when it's available.

如需 Windows LEDBAT 的一般詳細資訊,請參閱 New transport advancements (新的傳輸功能改善) 部落格文章。For more information on Windows LEDBAT in general, see the New transport advancements blog post.

當您設定一般的發佈點設定時,如需如何搭配 Configuration Manager 發佈點使用 Windows LEDBAT 的詳細資訊,請參閱 [調整下載速度來使用未使用的網路頻寬 (Windows LEDBAT)] 設定。For more information on how to use Windows LEDBAT with Configuration Manager distribution points, see the setting to Adjust the download speed to use the unused network bandwidth (Windows LEDBAT) when you Configure the general settings of a distribution point.

用戶端位置Client locations

用戶端可從下列位置存取內容:The following are locations that clients access content from:

  • 內部網路 (內部部署):Intranet (on-premises):

    • 發佈點可以使用 HTTP 或 HTTPS。Distribution points can use HTTP or HTTPs.

    • 請只在內部部署發佈點無法使用時,才將雲端發佈點用於後援。Only use a cloud distribution point for fallback when on-premises distribution points aren't available.

  • 內部網路Internet:

    • 需要網際網路對向發佈點接受 HTTPS。Requires internet-facing distribution points to accept HTTPS.

    • 可以使用雲端發佈點或雲端管理閘道 (CMG)。Can use a cloud distribution point or cloud management gateway (CMG).

      CMG 也可將內容提供給用戶端。A CMG can also serve content to clients. 這項功能可減少 Azure VM 所需的憑證和成本。This functionality reduces the required certificates and cost of Azure VMs. 如需詳細資訊,請參閱修改 CMGFor more information, see Modify a CMG.

  • 工作群組Workgroup:

    • 需要發佈點接受 HTTPS。Requires distribution points to accept HTTPS.

    • 可使用雲端發佈點或 CMG。Can use a cloud distribution point or CMG.

內容來源優先順序Content source priority

當用戶端需要內容時,會對管理點提出內容位置要求。When a client needs content, it makes a content location request to the management point. 管理點會傳回對所要求內容有效的來源位置清單。The management point returns a list of source locations that are valid for the requested content. 這份清單會根據特定案例、使用的技術、站台設計、界限群組和部署設定而有所不同。This list varies depending upon the specific scenario, technologies in use, site design, boundary groups, and deployment settings. 例如,當工作順序執行時,完整的 Configuration Manager 用戶端不一定會執行,因此行為可能有所不同。For example, when a task sequence runs, the full Configuration Manager client isn't always running, so the behaviors may differ.

下列清單包含 Configuration Manager 用戶端可使用的所有可能內容來源位置,並依其優先順序列出:The following list contains all of the possible content source locations that the Configuration Manager client can use, in the order in which it prioritizes them:

  1. 作為用戶端之相同電腦上的發佈點The distribution point on the same computer as the client
  2. 相同網路子網路中的對等來源A peer source in the same network subnet
  3. 相同網路子網路中的發佈點A distribution point in the same network subnet
  4. 相同界限群組中的對等來源A peer source in the same boundary group
  5. 目前界限群組中的發佈點A distribution point in the current boundary group
  6. 設定後援之鄰近界限群組中的發佈點A distribution point in a neighbor boundary group configured for fallback
  7. 預設站台界限群組中的發佈點A distribution point in the default site boundary group
  8. Windows Update 雲端服務The Windows Update cloud service
  9. 網際網路對向發佈點An internet-facing distribution point
  10. Azure 中的雲端發佈點A cloud distribution point in Azure

「傳遞最佳化」不適用於此來源優先順序。Delivery Optimization isn't applicable to this source prioritization. 此清單是 Configuration Manager 用戶端尋找內容的方式。This list is how the Configuration Manager client finds content. 「Windows Update 代理程式」會下載適用於「傳遞最佳化」的內容。The Windows Update Agent downloads content for Delivery Optimization. 如果「Windows Update 代理程式」找不到該內容,則 Configuration Manager 用戶端會使用此清單來搜尋它。If the Windows Update Agent can't find the content, then the Configuration Manager client uses this list to search for it.

只有當您啟用 BranchCache 的發佈點時,BranchCache 才會套用到此清單。BranchCache applies to this list only when you enable a distribution point for BranchCache. 例如,如果用戶端到達優先順序清單中的選項 #3,其會先要求 BranchCache 中繼資料的發佈點。For example, if a client gets to option #3 in the prioritization list, it first asks the distribution point for BranchCache metadata. 已啟用 BranchCache 的發佈點會為用戶端提供 BranchCache 同儕節點探索的資訊。The BranchCache-enabled distribution point is what provides the client information for BranchCache peer discovery. 如果可以,用戶端將會從 BranchCache 同儕節點下載內容。The client will download content from a BranchCache peer if it can. 如果用戶端無法透過 BranchCache 下載內容,其會先嘗試發佈點本身,然後再嘗試內容來源清單中的後續項目。If it can't download the content via BranchCache, it then tries the distribution point itself, before continuing down the list of content sources. 系統會在用戶端使用已啟用 BranchCache 的發佈點或雲端發佈點時,於優先順序清單中的任何位置套用此行為。This behavior applies at any point in the priority list where the client uses a BranchCache-enabled distribution point or cloud distribution point.

界限群組選項的設定可以修改此優先順序清單的排序次序。The configuration of boundary group options can modify the sort order of this priority list.

內容庫Content library

內容庫是 Configuration Manager 中內容的單一執行個體存放區。The content library is the single-instance store of content in Configuration Manager. 此內容庫可縮減您所發佈內容的整體大小。This library reduces the overall size of content that you distribute.

發佈點Distribution points

Configuration Manager 使用發佈點來儲存在用戶端電腦上執行軟體所需要的檔案。Configuration Manager uses distribution points to store files that are required for software to run on client computers. 用戶端必須能存取至少一個發佈點,且必須可從該發佈點下載檔案以用於您所部署的內容。Clients must have access to at least one distribution point from which they can download the files for content that you deploy.

基本 (非特製化) 發佈點通常是指標準發佈點。The basic (non-specialized) distribution point is commonly referred to as a standard distribution point. 標準發佈點有以下兩個值得特別注意的變化:There are two variations on the standard distribution point that receive special attention:

  • 提取發佈點:發佈點的變化,發佈點可在此取得其他發佈點 (來源發佈點) 中的內容。Pull-distribution point: A variation of a distribution point where the distribution point obtains content from another distribution point (a source distribution point). 此程序類似於用戶端從發佈點下載內容的方式。This process is similar to how clients download content from distribution points. 當站台伺服器將內容直接發佈到每個發佈點時,提取發佈點可協助您避免這段期間所發生的網路頻寬瓶頸,提升內容發佈的效率。Pull-distribution points can help you avoid network bandwidth bottlenecks that occur when the site server must directly distribute content to each distribution point. 使用提取發佈點Use a pull-distribution point.

  • 雲端發佈點:為安裝於 Microsoft Azure 上的一種發佈點變化。Cloud distribution point: A variation of a distribution point that's installed on Microsoft Azure. 了解如何使用雲端發佈點Learn how to use a cloud distribution point.

標準發佈點可支援一系列設定和功能:Standard distribution points support a range of configurations and features:

  • 使用排程頻寬節流設定之類的控制項,來協助控制此傳輸。Use controls such as schedules or bandwidth throttling to help control this transfer.

  • 使用其他選項 (包括預先設置的內容提取發佈點) 將網路使用量降到最低和進行控制。Use other options, including prestaged content, and pull-distribution points to minimize and control network consumption.

  • BranchCache對等快取傳遞最佳化是您部署內容時,可用來降低網路頻寬的對等技術。BranchCache, peer cache, and Delivery Optimization are peer-to-peer technologies to reduce the network bandwidth that's used when you deploy content.

  • 針對 OS 部署,有各種不同的設定,例如 PXE多點傳送There are different configurations for OS deployments, such as PXE and Multicast

  • 適用於行動裝置的選項Options for mobile devices

雲端發佈點和提取發佈點支援上述許多相同設定,但每種發佈點變化亦有其特定限制。Cloud and pull distribution points support many of these same configurations, but have limitations that are specific to each distribution point variation.

發佈點群組Distribution point groups

發佈點群組是可簡化內容發佈的發佈點邏輯群組。Distribution point groups are logical groupings of distribution points that can simplify content distribution.

如需詳細資訊,請參閱管理發佈點群組For more information, see Manage distribution point groups.

發佈點優先順序Distribution point priority

發佈點優先順序值的依據是將先前部署傳送到該發佈點所花費的時間。The distribution point priority value is based on how long it took to transfer previous deployments to that distribution point.

  • 此值會自我調整。This value is self-tuning. 您可以在每個發佈點上設定此值,以協助 Configuration Manager 更快將內容傳輸至更多發佈點。It's set on each distribution point to help Configuration Manager more quickly transfer content to more distribution points.

  • 將內容同時發佈至多個發佈點,或發佈至某個發佈點群組時,站台會先將內容傳送至優先順序最高的伺服器。When you distribute content to multiple distributions points at the same time, or to a distribution point group, the site first sends the content to the server with the highest priority. 然後才將該相同內容傳送至優先順序較低的發佈點。Then it sends that same content to a distribution point with a lower priority.

  • 發佈點優先順序不會取代套件的發佈優先順序。Distribution point priority doesn't replace the distribution priority for packages. 套件優先順序仍然是站台何時傳送不同內容的決定因素。Package priority remains the deciding factor of when the site sends different content.

例如,您有一個套件優先順序高的套件。For example, you have a package that has a high package priority. 您將它發佈至發佈點優先順序低的伺服器。You distribute it to a server with a low distribution point priority. 這個高優先順序套件的傳輸順序一律會在優先順序低的套件之前。This high priority package always transfers before a package that has a lower priority. 即使站台將優先順序較低的套件發佈至發佈點優先順序較高的伺服器,仍然會套用套件優先順序。The package priority applies even if the site distributes lower priority packages to servers with higher distribution point priorities.

套件的高優先順序可確保 Configuration Manager 先將該內容發佈至發佈點,然後才傳送任何優先順序較低的套件。The high priority of the package ensures that Configuration Manager distributes that content to distribution points before it sends any packages with a lower priority.

注意

提取發佈點也會使用優先順序的概念來排序其來源發佈點的順序。Pull-distribution points also use a concept of priority to order the sequence of their source distribution points.

  • 對伺服器進行之內容傳輸的發佈點優先順序,與提取發佈點所使用的優先順序截然不同。The distribution point priority for content transfers to the server is distinct from the priority that pull-distribution points use. 提取發佈點在從來源發佈點搜尋內容時,會使用自己的優先順序。Pull-distribution points use their priority when they search for content from a source distribution point.
  • 如需詳細資訊,請參閱使用提取發佈點For more information, see Use a pull-distribution point.

後援Fallback

Configuration Manager 最新分支在關於用戶端如何尋找具有內容的發佈點方面有數項變更,包括後援。Several things have changed with Configuration Manager current branch in the way that clients find a distribution point that has content, including fallback.

用戶端如果無法從與其目前界限群組關聯的發佈點中找到內容,可切換回使用與鄰近界限群組關聯的內容來源位置。Clients that can't find content from a distribution point that's associated with their current boundary group fall back to use content source locations associated with neighbor boundary groups. 鄰近界限群組必須與用戶端的目前界限群組具有已定義的關聯性,才能用於後援。To be used for fallback, a neighbor boundary group must have a defined relationship with the client's current boundary group. 此關聯性包括一段設定的時間,而用戶端必須在此時間內在本機找不到內容,才能將來自鄰近界限群組的內容來源納入其搜尋範圍。This relationship includes a configured time that must pass before a client that can't find content locally includes content sources from the neighbor boundary group as part of its search.

不再使用慣用發佈點概念,也不再提供或強制執行 [允許內容的後援來源位置] 設定。The concepts of preferred distribution points are no longer used, and settings for Allow fallback source locations for content are no longer available or enforced.

如需詳細資訊,請參閱界限群組For more information, see Boundary groups.

網路頻寬Network bandwidth

若要協助管理發佈內容時所用的網路頻寬量,您可以使用下列選項:To help manage the amount of network bandwidth that's used when you distribute content, you can use the following options:

  • 預先設置的內容:將內容傳輸至某個發佈點,而不將內容發佈至整個網路。Prestaged content: Transferring content to a distribution point without distributing the content across the network.

  • 使用排程及節流:此設定可協助您控制將內容發佈到發佈點的時機和方式。Scheduling and throttling: Configurations that help you control when and how content is distributed to distribution points.

如需詳細資訊,請參閱在 System Center Configuration Manager 中管理網路頻寬以進行內容管理For more information, see Manage network bandwidth.

內容來源的網路連線速度Network connection speed to content source

Configuration Manager 最新分支在關於用戶端如何尋找具有內容的發佈點方面有數項變更。Several things have changed with Configuration Manager current branch in the way that clients find a distribution point that has content. 這些變更包括對內容來源的網路速度。These changes include the network speed to a content source.

不再使用將發佈點定義為的網路連線速度。Network connection speeds that define a distribution point as Fast or Slow are no longer used. 相反地,與界限群組相關聯的每個站台系統都會視為相同。Instead, each site system that's associated with a boundary group is treated the same.

如需詳細資訊,請參閱界限群組For more information, see Boundary groups.

依需求發佈內容On-demand content distribution

依需求發佈內容是一個適用於個別應用程式和套件部署的選項。On-demand content distribution is an option for individual application and package deployments. 此選項可讓您依需求將內容發佈至慣用的伺服器。This option enables on-demand content distribution to preferred servers.

  • 若要為部署啟用這項設定,請啟用:[將此套件的內容發佈至慣用發佈點]。To enable this setting for a deployment, enable: Distribute the content for this package to preferred distribution points.

  • 如果您啟用此選項進行部署,而用戶端要求該內容,但用戶端的任何慣用發佈點上皆未提供內容,則 Configuration Manager 會自動將該內容發佈到用戶端的慣用發佈點。When you enable this option for a deployment, and a client requests that content but the content isn't available on any of the client's preferred distribution points, Configuration Manager automatically distributes that content to the client's preferred distribution points.

  • 雖然這會觸發 Configuration Manager 自動將內容發佈到該用戶端的慣用發佈點,但是用戶端可能會在用戶端的慣用發佈點收到部署之前,先從其他發佈點取得該內容。Although this triggers Configuration Manager to automatically distribute the content to that client's preferred distribution points, the client might obtain that content from other distribution points before the preferred distribution points for the client receive the deployment. 發生此行為時,內容就會出現在該發佈點上,以供下一個搜尋該部署的用戶端使用。When this behavior occurs, the content will then be present on that distribution point for use by the next client that seeks that deployment.

如需詳細資訊,請參閱界限群組For more information, see Boundary groups.

套件傳輸管理員Package transfer manager

套件傳輸管理員是站台伺服器元件,可將內容傳輸至其他電腦上的發佈點。Package transfer manager is the site server component that transfers content to distribution points on other computers.

如需詳細資訊,請參閱套件傳輸管理員For more information, see Package transfer manager.

預先設置內容Prestage content

預先設置內容是一個將內容傳輸至某個發佈點,而不將內容發佈至整個網路的程序。Prestaging content is a process of transferring content to a distribution point without distributing the content across the network.

如需詳細資訊,請參閱在 System Center Configuration Manager 中管理網路頻寬以進行內容管理For more information, see Manage network bandwidth.