Nah, the local path of the content lib, not the URL. BC doesn’t care about file names etc. Just file data, or chunks of it to be precise. Using the publish-bcwebcontent command this way is a good way of showing how cool BC is, you can even run that on a client without having any web server around. ☺
So when you publish the content, it basically makes the hashes, then you zip it up with the other command Export-BCCachePackage which creates the zip with the actual data. To answer the inline questions: Are you saying the "publish-bcwebcontent" command line would be run against the content library itself through the web interface of the DP? Yes. Wouldn't it have to be the DP that these clients would be checking the BC hash against? No, as long as the server secret is the same. This is what the secret BranchCache checkbox on the DP’s does. And wouldn't a successful deployment using the branchcache option be needed first, to create the hashes for the content that you would be "manually caching". No, that’s what publish-bcwebcontent does, it creates the hashes. Do you have to do a piece of content at a time if you were caching it this way? No, it can recurse through a folder structure, so maybe contentlib can be challenging, maybe get it from the source directly? How could you do this in batches for large amounts of content from the library? How much data are we talking? I am not sure I would do it this way at all to begin though. Are you building via USB? So a little unsure what you are trying to achieve and how, but from a technical standpoint most things are doable. But it doesn’t make sense to stage an app into BC for it to then be installed using BC again, as it is most likely already installed on other PC’s and in their BranchCache cache. Describe the scenario a bit more and we might be able to help you better. //A From: [email protected] [mailto:[email protected]] On Behalf Of Jay Marsett Sent: den 9 augusti 2016 21:27 To: [email protected] Subject: Re: [mssms] Content for Apps broken in Prestage media, workaround using Branchcache? Phil, Are you saying the "publish-bcwebcontent" command line would be run against the content library itself through the web interface of the DP? Wouldn't it have to be the DP that these clients would be checking the BC hash against? And wouldn't a successful deployment using the branchcache option be needed first, to create the hashes for the content that you would be "manually caching". Do you have to do a piece of content at a time if you were caching it this way? How could you do this in batches for large amounts of content from the library? Still this might be better than deploying the content to get it into the cache for any static content. Also toyed with deployment availability and deadlines far far into the future to stage the branchcache, but haven't seen that work at scale yet. Other thought I had was to use offline media task sequence deployments to stage the content on branchcache/WinPE peercache peers, but I have no idea if that is supported, or if it would work. Jay On Tue, Aug 9, 2016 at 8:10 AM, Phil Wilcock <[email protected]<mailto:[email protected]>> wrote: What’s your actual command line for publish-bcwebcontent? You need to point it at the actual content not the BC cache folders… You can’t import on Win7. All this cool stuff only exists on Win 8 or above Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Roland Janus Sent: 09 August 2016 08:55 To: [email protected]<mailto:[email protected]> Subject: [mssms] Content for Apps broken in Prestage media, workaround using Branchcache? I guess not many use Prestage media, otherwise it would have been noticed that content usage of applications is broken since 1511 (up to 1606). Basically, while the content is there it isn’t used and everything downloaded anyway I’ve opened a case with 1511 and it was confirmed and that a fix doesn’t make it in 1606. Does anyone know about this or any planned fixes? Since it’s broken I was looking for an alternative solution (or workaround): Branchcache. I’ve brought this up in the past and Andreas helped (kind of ☺ ), now I’d like to actually do this: • Export all BC content from the server • Create a package and have it applied during OSD before applications are used (which does work for prestage) • When the content is requested, local BC is used. When this was discussed before it was basically about that: http://2pintsoftware.com/2psfaqs/branchcache-caching-faq/ But I don’t get it. On The Server 1. Stage the Content Publish-BCWebContent -Path c:\inetpub\wwwroot\MyBigWIMFile.WIM -StageData -StagingPath c:\temp That is throwing an error: ObjectNotFound. Isn’t that where the content is: PS U:\> dir C:\Windows\ServiceProfiles\NetworkService\AppData\Local\PeerDistPub Directory: C:\Windows\ServiceProfiles\NetworkService\AppData\Local\PeerDistPub Mode LastWriteTime Length Name ---- ------------- ------ ---- d---- 17.06.2015 13:53 PrimaryHashStore d---- 17.06.2015 13:53 TempHashStore -a--- 09.08.2016 00:08 8192 edb.chk -a--- 09.08.2016 00:08 5242880 edb.log -a--- 09.08.2016 00:08 5242880 edbres00001.jrs -a--- 09.08.2016 00:08 5242880 edbres00002.jrs -a--- 09.08.2016 00:08 5242880 edbtmp.log -a--- 09.08.2016 00:08 8454144 PeerDistPubCatalog.pds PS U:\> dir C:\Windows\ServiceProfiles\NetworkService\AppData\Local\PeerDistRepub Directory: C:\Windows\ServiceProfiles\NetworkService\AppData\Local\PeerDistRepub Mode LastWriteTime Length Name ---- ------------- ------ ---- d---- 17.06.2015 13:53 Store -a--- 30.07.2016 02:46 8192 edb.chk -a--- 30.07.2016 02:46 5242880 edb.log -a--- 17.06.2015 13:53 5242880 edbres00001.jrs -a--- 17.06.2015 13:53 5242880 edbres00002.jrs -a--- 17.06.2015 16:09 5242880 edbtmp.log -a--- 30.07.2016 02:47 8454144 PeerDistRepubStoreCatalog.pds How do I export that content then? 2. Export the content to a package (creates a handy .zip file) Export-BCCachePackage -StagingPath c:\temp -Destination c:\MyBCPackage That would work once 1 works? On The Client 1.Import the Package Created in Step 2 Above Import-BCCachePackage -Path C:\temp\pkg\PeerDistPackage.zip And on Win 7? ..And you’re done! The content and is in the client cache ready for access by other computers, and the hashes are on the server (they get generated during the Staging part). cheers, Roland
