I have an issue with packages seeming to deploy to DPs they are not being published to.
We have an aging SCCM 2007 system, which is currently being wound down, so we can migrate to Config Manager 2012.
The 2007 system currently has 3 servers acting as DPs - one for general software distribution (DP1), one for OSD deployments (DP2) and one for Patch Deployment (DP3).
DP settings for each package are configured so that general software packages are only published to DP1, all packages related to OSD are only published to DP2, and all Software Updates packages are only published to DP3.
For historical reasons, DP1 is also a secondary site server, however, this now manages site boundaries for the full estate, prior to migration to SCCM 2012
I have just returned from a very pleasant annual leave to find that DP1 is flooded with site status messages for the SMS_DISTRIBUTION_MANAGER component; these are repetitions of the same three messages:
"SMS Distribution Manager is beginning to process package ..."
"SMS Distribution Manager is starting to distribute package ..."
"SMS Distribution Manager successfully processed package ..."
The package in question is an OS Image, which is only published to DP2. I am at a loss to understand why it is continually trying to publish to DP1 (over 33,000 entries for this component as I write this)
Note that these messages are "information" level messages, not errors, but are causing the Site Status for DP1 to continually "red flag"
Are there any logs etc I can check on this server to debug and diagnose why this rogue package is trying to process itself on this server? And any steps I can take to kill this?
Thanks
Stan