SCCM Configmgr Task Sequence does not replicate to Child Sites

Thought of sharing nice post on Task sequence replication issue to child site by Frank Rojas.
Symptoms :

When creating a new Task Sequence or updating an existing Task Sequence on a parent primary site in System Center Configuration Manager 2007, the Task Sequence may not replicate down to child primary sites. Packages and other Task Sequences replicate to the child primary site without issue.

Examining the logs associated with site replication (despool.log, replmgr.log, sched.log, sender.log) on both the parent and child primary sites does not reveal any errors. However examining the distmgr.log on the child primary site reveals the following errors:

Processing incoming file <ConfigMgr_Install_Directory>\inboxes\distmgr.box\INCOMING\<Random>.PKG. SMS_DISTRIBUTION_MANAGER
Adding package <Task_Sequence_ID> to the active package array. SMS_DISTRIBUTION_MANAGER
Adding these contents to the package <Task_Sequence_ID> version <x>. SMS_DISTRIBUTION_MANAGER
Updated replicated package info for package <Task_Sequence_ID> SMS_DISTRIBUTION_MANAGER
Failed to insert SMS Program ID <y> because the referenced program <Software_Package_ID>-<Software_Program_Name> is not present in the PkgPrograms table. Will try later. SMS_DISTRIBUTION_MANAGER
Cannot update the package program for package <Task_Sequence_ID> in the package source, error = 40 SMS_DISTRIBUTION_MANAGER
Removing package <Task_Sequence_ID> from the active package array. SMS_DISTRIBUTION_MANAGER

Cause

This issue is caused by a software package specified in the Task Sequence not replicating down to the child primary site. Any other Task Sequence that also has the problematic software package will also not replicate to child primary sites. However any Task Sequence that does not have the problematic software package will replicate to child primary sites without issues.

The problematic software package will be contained in the distmgr.log in the following line:

Failed to insert SMS Program ID <y> because the referenced program <Software_Package_ID>-<Software_Program_Name> is not present in the PkgPrograms table. Will try later.

Use the package ID and package name to identify the problematic software package.

Please note that not replicating to the child primary site means that information about the software package has not been replicated to the child primary site. It does not mean that the software package has not been copied to the child primary site's Distribution Point.

There could be several reasons why the software package has not replicated to the child primary site, but usually the cause is that the software package has a bad property in it such as invalid path to its source files.

Read Complete post on http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2012/06/29/a-system-center-configuration-manager-2007-task-sequence-does-not-replicate-to-a-child-site.aspx

Leave a Reply