SCCM doesn't replicate site changes up to the hierarchy

In our SCCM2007 R3 hierarchy we have a central site and a child primary site.

We need to add a branch distribution point to the child primary site. We add it in the console connected to the database of the child site. However on central site the new BDP is not visible.

We checked the hman.log and found a record saying that:
The serial number (961) for the site control file U:\SCCM\BIN\inboxes\\W61FQW74.CT2 (site = XXX) is out of date, discard it, the current site serial number is 963

We checked the DB (in the table site control) and also the site config file and in both, there is the serial number 963.

The situation is very strange, because if we change some other site configuration (e.g. paramaters of HW inventory client agent), it is replicated to the central site without any problem.

We 'd appreciate any hint.
Who is Participating?
glavinfoczConnect With a Mentor Author Commented:
We waited until next day and it seems that SCCM corrected itself.
You can give this a try, but i strongly  recommend a full backup of all Systems in advance
Also check this:
glavinfoczAuthor Commented:
We read both articles.

We tried to change the serial number in the site control file.
1. Before the change, the serial number in the file and in the DB was 959
2. We stopped SMS_EXECUTIVE service
3. We incremented serial number in the file to 960
4. We started SMS_EXECUTIVE service
5. After the startup of the SMS_EXECUTIVE the serial number in the file and in the DB was the same again, 960
6. When we tried to add the BDP, we received the message about the outdated serial number
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

what about increasing it higher? 963 e.g.?
glavinfoczAuthor Commented:
We tried to do that. We increased by 2, but after starting SMS_EXECUTIVE, ID in both locations (file and DB) were the same again.
glavinfoczAuthor Commented:
Just to be complete:

We discovered that in the database on the parent site, we have also a delta serial number for the child site. In the table SiteControl we see a record with
SiteCode = <childsitecode>
TypeFlag = 2
SerialNumber = 62
BinaryData = <binarystring>

Maybe it could help to troubleshoot.
You may have to execute a site reset.
glavinfoczAuthor Commented:
We waited until next day and it seems that SCCM corrected itself.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.