Hi

We are in the process of implementing SCCM across multiple sites. From our central site, I assigned several packages todistribution points on the remote servers.Replication is taking place via the LAN senders. Currently, changes to collections, task sequences and advertisements are not replicating fromthe central site to child sites.

I have changed the package send priorityfrom Medium to Low and have a few questions:
1. Does a packagesend prioritychange (mid replication) have anyeffect?

2. What is the default send priority for collectiondefinition changes, task sequences, advertisements etc.?

3. Is therea way to prioritize inter-site replication of collections etc.?

4. Ifthe answer is "no" to 3 then will the replication of collections etc only take place when all the package data has been replicated?

5. Is there a way to cancel the replication of packages to distribution points?

Any assistance would be appreciated

Adrian

Adrian Thomas said:

I have changed the package send priorityfrom Medium to Low and have a few questions:
1. Does a packagesend prioritychange (mid replication) have anyeffect?

2. What is the default send priority for collectiondefinition changes, task sequences, advertisements etc.?

3. Is therea way to prioritize inter-site replication of collections etc.?

4. Ifthe answer is "no" to 3 then will the replication of collections etc only take place when all the package data has been replicated?

5. Is there a way to cancel the replication of packages to distribution points?

(1) sure. It depends on how the address to the remote site is configured (http://technet.microsoft.com/en-us/library/bb693803.aspx). This will become effective only for package transfers that are not already ongoing.

(2) don't know exactly without digging deeper (my guess is that collection and advertisement stuff will always be replicated because that's only very few data; you could see that in the logs)

(3) not that I am aware of

(4) no. That has nothing to do with each other.

(5) there's no supported way (as far as I know)

1.No

2.Low

Adrian for you question no 3 check this article

http://technet.microsoft.com/en-us/library/bb632389.aspx

3.No

4.No

5. there is no way to cancel the replication of packges getting copy to the DPs.only think you can schedule it.

Sanka

I actually thought most of our replication processes, including collections, were set to normal (or medium) by default. You can change some of them via the console when you create your own objects, but not all.

5.  There is a way to cancel the replication of the packages.

1) Deleting the DP from packages wont stop the package replication and it will be still continue. The reason is registry key for package ins Packages Being Processed will be still exists
2) Check on the database and see all the entries are still exist or not.
3)
Go to below registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER

you will find

Name :- Packages Being Processed
Data :-  <Package ID>
4) Delete the <Package ID > for which you want to stop the replication
5) Before deleting the package ID please stop SMS_distribution manager and then start it after deleting.

Please do the test before doing it on production.
 
However i dont know whether this procedure is supported or not.

I have had similar issues while replicating large packages across multi-site hierarchies.  Typically I see this if I have more than one primary targeted with a large package and we have often been forced to replicate large images after hours rather than risk typing up sending for collection membership and advertisements.
I have posted similar threads with no true answer - but have not had the issue manifest itself enough to call PSS to try to trace the actual issue.
I have tried adding additional sending threads (this can be done through the console), but I have started to wonder if it has more to do with the despooler and hash validation process on the primaries being tied up with the constant receiving and checking of files from the package.  You might check to see if the files are actually making it to the primary and just not being processed (check the child primaries inboxes and the sender log at the central).
I have also tried to prioritize some of the items but have still not found that perfect balance.  Luckily these large packages (typically images) only occur infrequently and most packages (smaller than 1 GB) don't seem to cause big issues in replication timing.
No answers here - just a few thoughts and potentially a few more places to look!  If I ever come up with the answer on this one - I'll repost again (or if I decide to burn some more PSS hours some free day I have).

Answers in series :

1. yes , it does but it should be done before the package is distributed

2. Low

3. No

4. These are two different things

5. there is no supported way .