Search the Community

Maybe I'm being a little over concerned but i seem to be noticing a trend in my Configmgr environment. The last few packages are causing issues being distributed. When a new packages is added it distributes fine and clients at the remote site can install the package. a day or so later i notice pkgxfermgr.log is copying the package again. For example I recently added Autocad 2013 it copied out to multiple DP's without issue and was able to be installed by clients. i left for the weekend and returned to note in the console the package was showing failed on a number of distribution points. after checking pkgxfermgr.log it was clearly checking the source folder against the different DP's content stores to see if all the files existed. This copy/verify process seems to move at a snails pace i assume due to the fact its hash checking each file. The problem seems to be that the process runs so long the job ends and restarts again only to be checking the same files all over again. Can anyone send some light into what might be happening or which log file i should dig deeper into? Some information about the environment. One site Main Configmgr server is running on server 2008r2 with most roles with SQL being local, all remote DP's are a mix of 2003 and 2003 R2 most with WDS running on them also Package sources are all stored on a single server (2003R2) but accessed via DFS paths to reduce the effort of re-targeting sources when the server is later retired.