Thursday, 26 March 2015

SCCM 2007 - How Site to Site Communications directional flow

Site to Site Communications directional flow Data sent from Parent to Child


• Collection Rules

• Package Definitions

• Optionally compress and send package source files if a DP on the child site is specified

• Advertisement definitions

• Software metering rules - optionally if configured for child sites

• Site control files for child sites - allows parent site to administer the child site

• Assigned resources to child secondary sites

Data sent from Child to Parent

• Discovery data

• Hardware and software inventory data

• Status Messages

• Status message for advertisements only go to the originating site of the advert

• Software metering usage data

Replication Process between sites

Site control files are replicated:

• When the child/parent relationship is first established

• Every time a change is made to local site settings

• Every 24 hours if changes are not made

Note: Establishment of a child/parent relationship results in a large volume of data transfer between the two site servers. This should be taken into consideration while planning such an endeavor.
Troubleshooting Flow

Normal intra-site components do their assigned work. If the assigned work includes data that must be replicated to a different site:

1. A send request is made to Replication Manager – replmgr.log

2. Replication Manager creates a mini-job

3. Mini-Job goes to Scheduler

4. Scheduler creates a send request (?) and an instruction file and a package file - sched.log

5. Sender component then sends the data - sender.log


On the Child site


1. Despooler component receives the data - despooler.log

2. Despooler hands it off to Replication Manager Component

3. Replication Manager hands the data to the appropriate component - replmgr.log

No comments:

Post a Comment