Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Task Sequence taking twice the amount of time to complete after enabling Pre-Release

  • Thread starter Thread starter RiDER07
  • Start date Start date
  • Replies Replies 2
  • Views Views 2K
Status
Not open for further replies.

RiDER07

Member
Messages
17
Reaction score
0
Points
1
My TS OSD used to take around 35-40 minutes to complete. But after enabling Pre-Release in Hierarchy, my TS now takes over 1 hour. It struggles when it gets to packages/applications.
This is the changes I made after enabling pre-release

Time it takes to complete the TS


OLD TS

After enabling Pre-Release and Share Content

It looks like it's waiting for something to happen, but I don't know what.
How do I fix this? Or go back to how apps/packages are deployed.
Many thanks,
 
Solution
Reminds me of a note about Peer cache here -

Note: When a client seeks content from a Peer Cache Source the client will look for Peer Cache Source in the in the same subnet and boundary group. Clients will not seek content from a neighbor boundary group. If a Peer Cache Source is not available to provide the requested content the client will fall back to the Distribution Point.

Can you check from where is the content being downloaded from?.
Reminds me of a note about Peer cache here -

Note: When a client seeks content from a Peer Cache Source the client will look for Peer Cache Source in the in the same subnet and boundary group. Clients will not seek content from a neighbor boundary group. If a Peer Cache Source is not available to provide the requested content the client will fall back to the Distribution Point.

Can you check from where is the content being downloaded from?.
 
Solution
Reminds me of a note about Peer cache here -

Note: When a client seeks content from a Peer Cache Source the client will look for Peer Cache Source in the in the same subnet and boundary group. Clients will not seek content from a neighbor boundary group. If a Peer Cache Source is not available to provide the requested content the client will fall back to the Distribution Point.

Can you check from where is the content being downloaded from?.

Shouldn't OSD gets all its data from the DP? I mean if I'm building several machines at the same time, and they are all waiting for each other for the content...it will never work.
 
Status
Not open for further replies.
Back
Top