Packages are not distributed to Child Sites

This behavior can occur because the Sms\Inboxes\Schedule.box\Uid folder is empty or does not exist or incorrect files in the \SMS\inboxes\schedule.box\UID folder can stop or inhibit communications

To resolve this behavior, you must open the Sms\Inboxes\Schedule.box\Uid folder and create two empty text files called nnnnnnnn.job and nnnnnnnn.req, where nnnnnnnn is the number in the filename, which is greater than any of the files' names that were already found in the directory SMS\Inboxes\Schedule.box (Guess what could be the greater name???? it took for me some time but finally the file name should be… ZZZZZZZZ …..I have mentioned below the process for how to do it)

How to do it:-

Stop the SMS Executive Service.

Verify that the \SMS\inboxes\schedule.box\UID folder exists. Create it if it does not.

Place two files in this folder. Because the scheduler processes jobs in a sequential fashion, you will want to create files that are at the end of the processing cycle. Name the first one ZZZZZZZZ.JOB and the other ZZZZZZZZ.REQ. 

Start the SMS Executive Service.

In some cases communications will be in stopped state, but there are two files already in the UID directory, Just delete them and adding the "Z" files.

Note:- Make sure there are 8 "Z"'s in the file name

~~~~~~~~~~

Enjoy

SCCM 2012 Replication – What is replicated in each type From where to where

 

There are TWO types of replication can happen

1) Database Replication
2) File-Based Replication

Database Replication Includes Global Data & Site Data

Global data that replicates by using database replication.

Site data that replicates by using database replication.

Note:- Apart from above two there is local data this is just to specific to the local site.

Global data includes below : these are flow from CAS to below the Hierarchy

Alert rules

Client discovery

Collections rules and count

Configuration Items metadata

Deployments

Operating system images (boot images and driver packages)

Package metadata

Program metadata

Site control file

Site security objects (security roles and security scopes)

Software updates metadata

System Resource List (site system servers)

 

Site Data Replication: These are from Client to reporting/assigned Site

Alert messages

Asset Intelligence client access license (CAL) tracking data

Client Health data

Client Health history

Collection membership results

Component and Site Status Summarizers

Hardware inventory

Software distribution status details

Software inventory and metering

Software updates site data

Status messages

Status summary data

File-Based Replication: Earlier products there was only one type of Replication and this is file type. Now with SCCM 2012 this was limited two below types, Mainly used for Software packages and software updates.

File content that replicates by using file-based replication.

File based Data	To the Destination
Package files used by deployments	Sent to primary and secondary sites.
Data from secondary sites	Sent to the primary site (parent) of the secondary site.
Fallback status point state messages	Forwarded to the assigned site when only a single fallback status point is in use.
Discovery data records	Forwarded to the assigned site when not processed at the site where they are generated.

What kind of Data Will be flow between the Sites

 

Child sites send the following information to their direct parent sites:

1. Discovery information
2. Inventory information
3. Site control information
4. Status messages

The Data collected from a child site to a parent site are listed here:

1. Discovery data records (DDRs)
2. Inventory data
3. License balancing data
4. Site control files
5. Status messages

The Data passed from a parent site to its associated child sites are listed here

1. Advertisements
2. Collections
3. Package definitions
4. Site control files
5. Software metering data