Open ankushsvc opened 3 years ago
Hello, We are getting same issue, Driver Packages are not getting downloaded from Peer cache source devices. When OSDContentDownload.exe inside WinPE client is making request to MP for available download locations, its replying DP locations only in contentreply response, it doesn't contain Peer Cache Source machine, Package is downloaded from SCCM DP location, even though peer cache information is present in SCCM DP for driver package. If we directly reference the same package in Run command line, then its able to identify the Peer cache location.
Hello folks, well I've found a workaround by analysing smsts logs. It seems that peers are found at the beginning of the sequence by >KNOWN< referenced packages.
Us folks normally have a sequence to precache drivers on "superpeer" machines. Well what ive done is adding that sequence to my main sequence with a "dumb" variable, just so the task sequence manager sees all packages and find peers perfore launching. This is the way it works apparently. Look at what I've got (image).
I also have a script to generate/update the superpeer task sequence. Its helpful.
We are using Peer cache in windows PE and works properly in downloading OS.wim and other packages using peer cache. Invoke-CMApplyDriverPackage.ps1 uses osdcontentdownload.exe to download content but somehow it is not downlaoding from peer cache and downloading directly from DP. Any suggestions