What is allow peer downloads in this boundary group?
When an application is deployed and installed on the peer cache source, the Content Access service generates a state message of topic type 7200. Deploy an application to the peer cache source The following example is used to show how peer cache works during content deployment. Select the Options tab, and then enable the Allow peer downloads in this boundary group setting. Right-click the boundary group, and then select Properties. Locate the boundary group that contains the peer cache clients and peer cache sources. In the Configuration Manager console, go to the Administration workspace, and then select Hierarchy Configuration > Boundary Groups. Show
When the site server receives the state message, it calls the spUpdateSuperPeerStatus stored procedure to update the following tables:Ĭonfigure boundary group options for peer downloads You'll see the following entry in the MP_Relay.log file: Message Body :ġ1GUID:xxxx.1015TestClient43710331]]>8003 The state message is formatted as XML, and then sent to the management point (MP_RelayEndpoint) through CCMMessaging. State message(State ID : 2) with TopicType 7201 and TopicId Super Peer is now active has been recorded for SYSTEM The following entries are logged in StateMessage.log: Adding message with TopicType 7201 and TopicId Super Peer is now active to WMI The following entries are logged in CAS.log: SuperPeerController main thread has started.Ī state message of topic type 7201 is generated. Notifying endpoint 'SuperPeerController' of _InstanceModificationEvent settings change on object CCM_SuperPeerClientConfig.SiteSettingsKey=1 for user 'SID'. The following entries are logged in CcmExec.log: Notifying endpoint 'SuperPeerController' of 1 settings change(s). The value of the CanBeSuperPeer property is changed to True. In the WMI class instance CCM_SuperPeerClientConfig.SiteSettingsKey=1 under ROOT\ccm\Policy\Machine\ActualConfig: When the client cache setting is deployed to the device collection, you'll see the following changes on the peer cache sources: Changes on clients that act as peer cache sources When you enable clients to be peer cache sources, the management point includes them in the list of content location sources. You don't have to enable peer cache clients. In the navigation pane, select Client Cache Settings, set Enable as peer cache source to Yes, and then specify the ports.ĭeploy this custom client setting to the device collection that you created in step 1. Select Create Custom Client Device Settings, specify a name and description, and then select the Client Cache Settings group. Go to the Administration workspace, and then select the Client Settings node. Determine which clients you want to enable as peer cache sources, and add them to the collection. In the Configuration Manager console, create a device collection. To enable clients to be peer cache sources, follow these steps: For more information, see Peer cache for Configuration Manager clients. Use peer cache to help manage deployment of content to clients in remote locations. It extends traditional content deployment solutions, such as distribution points. Peer cache is a built-in solution for Microsoft Endpoint Configuration Manager that enables clients to share content with other clients directly from their local cache. Applies to: Microsoft Endpoint Configuration Manager (current branch) One of the big issues with Peer Cache is that clients can only get content from Peer Cache sources (“Super Peers”) when the Peer Cache source has got all of the content.Operationally, this means when you deploy something new (e.g. a critical patch) to all clients in a remote location at the same time, you expect them all to pull the content from the remote DP over the WAN.
When you do this, Peer Cache source computers (‘Super Peers’) targeted with content will download the content in blocks.Block 1 downloads first.
If another Super Peer requests the same content while the first is downloading block 1, it will start to download block 2 and so on. This can be seen observing the ContentTransferManager.log on two ‘Super Peers’: As each Super Peer aggregates all the blocks, it updates the Management Point and then other clients in the Boundary Group can get the content from it.10/15/2018 9:27:56 PM Download complete for all 4 blocks So how does this compare with Nomad?
What is the purpose of a boundary group?Clients use boundary groups to: Find an assigned site: Boundary groups enable clients to find a primary site for client assignment. This behavior is also known as automatic site assignment. Find certain site system roles they can use: Associate a boundary group with certain site system roles.
What is peer caching?Peer cache is a built-in solution for Microsoft Endpoint Configuration Manager that enables clients to share content with other clients directly from their local cache. It extends traditional content deployment solutions, such as distribution points.
How does peer cache work?Peer cache is a P2P feature built into ConfigMgr in which clients share content from the ConfigMgr cache. Peer cache works with other P2P technologies, such as BranchCache, but it can also work independently. Peer cache supports partial content, so it sends data before the entire content type is available.
What is a boundary group in SCCM?Boundary groups that are logical groups of boundaries that provide clients access to resources such as updates, operating systems, installations et cetera. In SCCM each boundary and boundary group you configure is available throughout the entire hierarchy. You don't need to configure them for individual sites.
|