• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 866
  • Last Modified:

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\hman.box\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.
0
glavinfocz
Asked:
glavinfocz
  • 5
  • 3
1 Solution
 
merowingerCommented:
You can give this a try, but i strongly  recommend a full backup of all Systems in advance
http://www.myitforum.com/forums/m203540-print.aspx
Also check this:
http://blog.coretech.dk/kea/the-serial-number-game/
0
 
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
0
 
merowingerCommented:
what about increasing it higher? 963 e.g.?
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

 
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.
0
 
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.
0
 
merowingerCommented:
You may have to execute a site reset.
0
 
glavinfoczAuthor Commented:
We waited until next day and it seems that SCCM corrected itself.
0
 
glavinfoczAuthor Commented:
We waited until next day and it seems that SCCM corrected itself.
0
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.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

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

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now