Yeah, doable, but a little tricky! Another cache can be injected as is or by using the PowerShell cmdlets. Extract the info from the server using the powershell cmdlets allows of course to select packages but is a little time consuming to inject into the cache. It's a bit vague and undocumented, so asked the devs to clarify this a little, in our testing we had to set the servers secret key to match the client before importing content or it wouldn't be used. Unsure if it's a bug or "by design".
One of the steps in the upcoming version searches the local HD's for an old cache to inject before starting up BC. So what exactly did you have in mind? A build DVD like the secret MS "hybrid" media approach, build over the wire but with local content? //Andreas From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: den 3 juni 2015 12:32 To: [email protected] Subject: [mssms] Prepopulate branchcache on client for ConfigManager Something for Andreas and Phil Assuming I use your branchcache for PE, which I guess is a pre-req for what I want to do anyway, is there a way to prepopulate the branchcache cache so that PE can use it? Like the toolkit package or the boot image if it needs to be downloaded. Also assuming I have a local source available with that content. That assumes :) I can get my hands on the content, extract it somehow. Ypu get the idea? -roland
