Yeah PeerCache is OK, bit of a 'stopgap' solution IMO - but does the job if you can't run BranchCache.
Also bear in mind that Apps and Software Updates always come from the DP so you'd still need BranchCache for them anyways Few more caveats, hoping to play with it a bit more later today and will report back! Phil Phil Wilcock 2Pint Software http://2pintsoftware.com @2pintsoftware From: [email protected] [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: 09 December 2015 09:09 To: [email protected] Subject: RE: [mssms] Windows PE peer cache Well... without trying to piss on someone else's parade... the best quote we got was from someone senior within MS: "BranchCache with your (2Pint Software's) add-ons is a Formula 1 car, we are building a moped" That said, it will fit the bill and help for companies that cannot use BranchCache for whatever reason. Although I still don't really see a single reason not to use BranchCache. Phil is working on a detailed comparison but here are a few items: 1. Uses Packages from CCM Cache of other machines, so needs to be package with right version and fully downloaded. 2. Only for WinPE initiated content at the moment. 3. If source is not available (see point 1) it goes over the WAN at full throttle. 4. There is no de-duplication... So new image and you got to DL the whole thing over the wire again... meanwhile BC works on chunks. So can use the old image and/or deploy loads simultaneous machines and they will all share content among the active peers. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: den 8 december 2015 23:27 To: [email protected]<mailto:[email protected]> Subject: [mssms] Windows PE peer cache https://technet.microsoft.com/en-us/library/mt613173.aspx Phil and Andreas should be interested in that subject :) Any comments? -R
