I'm Rob Marshall, a consultant who specialises in the Microsoft System Center Configuration Manager product. I like to share, i do so by blogging and helping out when I can in the MS SMS newsgroups and participating in the ConfigMgr MVP program.
I was awarded and joined the program in 2009. It'd be an understatement to say it has to be one of the best experiences an IT engineer can have, if they really enjoy specialising in a product.
My biggest weapon for troubleshooting is, my formidable knowledge, no, only joking, you, the community. I find if I cannot answer a question, then I can usually find the answer from using Bing\Google, pouring over the documentation, and if that doesn't work, tinkering in mine or someone elses virtual lab.
The blogs pretty much about ConfigMgr, but it is also a platform for me to express my random urges to display something I've stumbled across, and that I imagine would entertain you or what not as equally as it did me.
I had to rebuild a few Secondary Site servers recently (over 10) and each had to use a different server name but same sitecode. This is beyond normal, as we usually expect the server name and site code to be reused.
After rebuilding, copying the SMSPKG folder (and SMSSIG which is probably what did this?!) and then preloading we found that some packages would not be accepted by the Distribution Manager component on the newly built Secondary Site server.
The warning message showing up in DistMgr log:
A newer version (2) of package ABC00FFF has already arrived, delete the replication file Z:\SMS\inboxes\distmgr.box\INCOMING\01P2CEVG.PKG for version 1
Keep in mind the previous site was flushed from the hierarchy, and that there was a delay before building the replacement servers.
Doing the following had no effect
Doing the following fixed it
You can remotely delete the file (UNC'ing) as long as you have permissions, then force the resend to take place from the site the package was created at.