SCCM Task Sequence big packages taking hours to complete

I have an issue with a task sequence when building computers , the .wim and driver pack are taking hours to deploy during the build. I have re-distributed them all good and chcked the internal speed of the remote DP. This ame task sequence works normally on all other distribution points. I ahve checked the dp settings and they are the same as others and boundaries are all good. Any help or advice would be much appreciated.

2 Comments   [ + ] Show comments
  • Is the any unusual activity being flagged in the following log files?
    DistMgr.log & PkgXferMgr.log - Maidens 1 year ago
    • Just that the remote site is comi g back to primary site dp for constant even though its redistributed out fine to the proper onsite dp and I've disabled all fallback, no matter what I do - robertmmk 1 year ago
  • Sounds as if there is a problem with the boundary group and relationship by virtue of the fact it's defaulting to the primary site DP. Task sequence location priority goes in the following order

    1- Peer cache source
    2- DP in the current boundary group
    3- DP in the neighbour Boundary group.

    You could try removing the boundary and recreating? - Maidens 1 year ago

Answers (1)

Posted by: nagendrasingh 1 year ago
Black Belt

It could be the software's fault as well. How many software are getting installed in that TS apart from drivers?

Some software like Matlab takes hours to install. Granted that it is a large software but I have seen some larger software getting installed under an hour.

How long does the basic image take to install?

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ