FAN Out Distribution SCCM

Home Page

Friends !! I am back to write yet another post on SCCM . This post is regarding the Distribution of a Package or a Patch in the SCCM Hierarchy . One very Important concept in this regard is Fan Out Distribution .

The concept is very handy when it comes to saving bandwidth .

Below Image shows the concept of Fan out :

Image

 

Fan out Distribution : 

When distributing packages to child sites, you can reduce the workload on the initiating site by using the fan-out feature. The fan-out feature allows sites to distribute package content to lower level sites through child sites, rather than directly. Fan-out distribution occurs automatically if the initiating site does not have an SMS address for the destination site. For example, if a site needs to distribute a package to its child site and to its grandchild site, the originating site has two options:

  1. Distribute the package to the child site and to the grandchild site. This happens if the initiating site has addresses to both sites.

  2. Use the fan-out feature and distribute the package only to the child site. The child site then distributes the package to its child site, which is the grandchild of the originating site. This happens if the initiating site has the address of the child site and only the child site has the address of the grandchild site.

Besides reducing the workload of the initiating site, this also reduces the load on the network link between the initiating site and the rest of the sites, which is often a significant issue. This is especially efficient when distributing large software packages such as Windows XP. Figure 3.3 describes the added load on the central site when fan-out is not used.

2 thoughts on “FAN Out Distribution SCCM

  1. thanks abheek…I would like to know which are the log files we are using mainly for troubleshooting software distribution and patch management it if failed for some clients…

    1. SCCM log files can be found here: %systemroot%\SysWOW64\CCM\Logs

      CAS.log – Content Access service. Maintains the local package cache.
      CcmExec.log – Records activities of the client and the SMS Agent Host service.
      CertificateMaintenance.log – Maintains certificates for Active Directory directory service and management points.
      ClientIDManagerStartup.log – Creates and maintains the client GUID.
      ClientLocation.log – Site assignment tasks.
      ContentTransferManager.log – Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
      DataTransferService.log – Records all BITS communication for policy or package access.
      Execmgr.log – Records advertisements that run.
      FileBITS.log – Records all SMB package access tasks.
      Fsinvprovider.log – Windows Management Instrumentation (WMI) provider for software inventory and file collection.
      InventoryAgent.log – Creates discovery data records (DDRs) and hardware and software inventory records.
      LocationServices.log – Finds management points and distribution points.
      Mifprovider.log – The WMI provider for .MIF files.
      Mtrmgr.log – Monitors all software metering processes.
      PolicyAgent.log – Requests policies by using the Data Transfer service.
      PolicyAgentProvider.log – Records policy changes.
      PolicyEvaluator.log – Records new policy settings.
      RemoteControl.log – Logs when the remote control component (WUSER32) starts.
      Scheduler.log – Records schedule tasks for all client operations.
      Smscliui.log – Records usage of the Systems Management tool in Control Panel.
      StatusAgent.log – Logs status messages that are created by the client components.
      SWMTRReportGen.log – Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

      Execmgr.log is a very key file used for troubleshooting Software Distribution issues , WUAHandler.log iss used in patch management , There are loads of articles which will explain which files to use for troubleshooting . But without any doubt the above files are key files.

Leave a Reply

Your email address will not be published. Required fields are marked *