Hi to all,
Great news, System Center Updates Publisher June 2019 Preview is now available!
What’s news?
Improvements include a new authoring mode to help you author your updates. When you enable authoring mode, a Categories Workspace is added to the start screen. The categories workspace enables update authors to organize updates that belong together.
A new Detectoid button is also added to the Updates Workspace when authoring mode is enabled. Detectoids are useful when you have multiple updates that use the same rule (or a set of rules) to determine applicability.
Hi,
In this post, I explain you how to configure and use the peer cache with Sccm CB application, package and OSD deployment.
For the start, it’s need to be clarify one point, the Peer Cache feature is available since the SCCM 1610 version.
Configuration Manager doesn’t enable this optional feature by default. You must enable this feature before using it. For more information, see Enable optional features from updates.
For enable the peer cache feature, it’s necessary to activate the feature in Administration>Overview>Updates and Servicing>Features
You can minimize and improve the network transferts in activated the option below (Configure client peer cache sources to divide content into parts. These parts minimize the network transfer to reduce WAN utilization):
After that, le’t go for the peer cache configuration!
The first one is the prerequisite:
Reminder for the peer client cache configuration:
A-Peer cache configuration and requirement parameters
1-Create the target collection for the peer cache client (in my example, i have two clients)
2-Create a new custom clients settings with this parameter under:
Configure client cache size = Yes
Maximum cache size (in my example, i put the maximum for the cache client=65000)
Maximum cache size = 20
Enable Configuration Manager client un full OS to share content = Yes
Port for initial network broadcast = 8004 (You don’t miss to open this port on yours firewalls)
Por for content download from peer = 8003 (You don’t miss to open this port on yours firewalls)
3-Create a second collection with all clients included in the same boundaries group that the peer cache client (This collection is used for generalize application deployment = after you will deploy the application on yours peer cache client)
4-Deploy an application to the peer cache clients (in my example, i take 7-Zip = ELY00029=Package ID)
5-At this moment, i can check in CAS.log if the package is donwloaded in the cache of my client by the distribution point and if his present in the cache (this step is necessary and it’s just for one time, the first time)
6-Now, if i install the 7 Zip package on another workstation included in the same boundaries group, the package is good downloaded by the peer cache client (DataTransferService.log)
7-The 7-Zip application installed correctly and by the peer client cache
B-Configure Peer cache for OS Deployment
In this example, the peer cache works the same way that the application and package model deployment, it’s necesseray to deploy your OS image and package OSD for the first one in your branch
1-Prepare your task sequence to deploy OSD
2-For that your peer cache client keep all objects OSD in her cache, it’s necessery to add variable in collection SMSTSPreserveContent=True
For information, when you have finish and you want to deploy OS using the peer cache feature, it’s necessary to put the variable (SMSTSPeerDownload=True) on the collection
3-Launch your OS Deployment…
4-After you will find the config manager client cache with the package OSD in his cache, you first peer cache client for OSD is ready!
5-You can see the log result of smsts.log and that he use good the peer cache feature (network)
Package ID=ELY00004
Package ID=ELY00014
Package ID=ELY00015
Finish
Enjoy!
Sources Peer cache for Configuration Manager clients
