Answered by:
Failed to distribute Configuration Manager Client Package and Configuration Manager Client Package upgrade package

Question
-
Hi Team,
Above this two package showing inprogress from long time (week). It not showing failed. Yesterday I distribute 500mb package that is reached.. Why this one take this much time..
I am using SCCM 2012 R2 CU2
Wednesday, November 5, 2014 4:31 PM
Answers
-
re-create the package mate. keep an eye on your distmgr.log via cmtrace to check at which point its stopping.
Blog: http://heinrichandsccm.blogspot.co.uk
- Proposed as answer by Xin GuoMicrosoft contingent staff Thursday, November 20, 2014 2:56 AM
- Marked as answer by Xin GuoMicrosoft contingent staff Monday, December 8, 2014 3:32 AM
Thursday, November 6, 2014 9:53 AM
All replies
-
Failed? What error code was displayed?
Torsten Meringer | http://www.mssccmfaq.de
Wednesday, November 5, 2014 5:29 PM -
Hi,
Is the SCCM site server a member of the local administrator group on the DP that is failing?
Blog: www.danielclasson.com/blog | LinkedIn: Daniel Classon | Twitter: @danielclasson
Wednesday, November 5, 2014 7:19 PM -
Do you have Antivirus exclusions in place. Is it on a remote location.Wednesday, November 5, 2014 7:40 PM
-
check out the distmgr.log on your management point and look for errors. I had this happen a few times, it was caused by antivirus and or firewall.Thursday, November 6, 2014 1:51 AM
-
Yes. it's part of local admin. It's not failing.. it still showing inprogress.. I refreshed using powershell.. but no luck..Thursday, November 6, 2014 4:45 AM
-
Mcafee is installed. but all the other package moved smoothly .. the problem only for the particular package is showing inprogress even after refresh/redistributeThursday, November 6, 2014 4:47 AM
-
I agreed your point. if antivirus no package reached to the distribution point. But the problem particular this package is showing inprogress.. There is no error in distmgr. it showing processing that's itThursday, November 6, 2014 4:48 AM
-
re-create the package mate. keep an eye on your distmgr.log via cmtrace to check at which point its stopping.
Blog: http://heinrichandsccm.blogspot.co.uk
- Proposed as answer by Xin GuoMicrosoft contingent staff Thursday, November 20, 2014 2:56 AM
- Marked as answer by Xin GuoMicrosoft contingent staff Monday, December 8, 2014 3:32 AM
Thursday, November 6, 2014 9:53 AM