Archive: Posts Tagged ‘for the’

SCCM CB | How to configure and use Peer Cache in SCCM CB (Application, package and OSD)

Commentaires fermés avril 30th, 2019


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:

  • One or many workstations dedicated to be peer cache client
  • Boundaries and boundaries Group configured
  • Collection with Clients Settings configured with the peer cache option

Reminder for the peer client cache configuration:

A peer cache source rejects requests for content when it meets any of the following conditions at the time a peer requests content:
  1. Low battery mode
  2. Processor load exceeds 80%
  3. Disk I/O has an AvgDiskQueueLength that exceeds 10
  4. There are no more available connections to the computer

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


Enjoy! :-)

Sources Peer cache for Configuration Manager clients

SCCM 2012 R2 | Cumulative Update 1 for the System Center 2012 R2 Configuration Manager clients for UNIX and Linux !!!

Commentaires fermés avril 30th, 2014

Hi to all,

Great news, a new Cumulative Update 1 for the System Center 2012 R2 Configuration Manager clients for UNIX and Linux is available !!!

Issues that are fixed by the CU1

UNIX and Linux clients

  • In some cases, Linux clients may not initialize while the Scxcm.log file grows quickly. Additionally, the following warning message is logged in the /var/opt/microsoft/scxcm.log file:
  • datetime Warning [scx.client.agents.InventoryAgentState:338:27298:140010010693376] Hardware Inventory endpoint Notify gained the policy lock, but the system is not yet ready. Retrying. LinuxUNIXClient 01.01.1601 00:00:00 2666765960 (0×9EF39E88)
  • After a client upgrade, the UNIX or Linux client does not send the new client version number to the server.
  • When you run the ccmexec –v command, a version number is displayed that is inconsistent with the client version number that is reported to the server.
  • The Universal Linux client does not install on Linux computers that use OpenSSL versions greater than 1.0.0 if the library file does not exist. Additionally, you receive the following error message from the installation script
  • Checking Prerequisites…
    Running preinstall validator
    /tmp/ccm/preinstallvalidator: error while loading shared libraries: cannot open shared object file: No such file or directory
    Pre-Install validator failed. Please check the version of OpenSSL with CM installation requirements.
  • The client does not install on Linux computers that have an Athlon kernel.
  • In some cases, the client may not install on AIX-based computers. Additionally, you receive the following error message from the installation script:
  • Registering Providers…
    exec(): 0509-036 Cannot load program /opt/microsoft/omi/bin/omireg.bin because of the following errors:
    0509-150 Dependent module could not be loaded.
    0509-022 Cannot load module
    0509-026 System error: A file or directory in the path name does not exist.
    An error occurred while registering providers.
  • If multiple Network Access accounts (NAAs) are configured, and if one or more of the accounts is invalid for the distribution point, software distribution to a UNIX or Linux client may not retrieve the package.
  • When the server sends a policy resync command to the UNIX or Linux client, the client may stop sending inventory to the server or stop processing software distribution. Additionally, the following warning message is logged in the /var/opt/microsoft/scxcm.log file
  • Info [scx.client.scheduler.IScheduledTrigger:256:51452:140230841011968] Loaded a one-shot trigger that has already completed. Trigger will not be fired again.
  • Hardware inventory does not return serial number properties for the PC BIOS class for UNIX-based and Linux-based computers.
  • Hardware inventory returns no data for the PC BIOS class for AIX-based computers.

data-ad-slot="8215329516"> change of web hosting for to meet the large number of visits , see IT!

Commentaires fermés février 23rd, 2010

Hi everybody,

I bring great news for all members and visitors to the site of the community
The web hosting has been replaced in favor of a more powerful machine to meet the very large number of connection requests on the site.
I let you search and find on which server we migrated (see the copy screen). lol

Please visit the comments section for the answer… ;)

Good reading and good luck especially for the little riddle


The team