Well that is just the PowerShell cmdlets. The API's are there. We got an executable that allows you to do the same, not released though.
Thought all people were on Windows 10 by now. ;-) //A From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: den 10 augusti 2016 00:15 To: [email protected] Subject: AW: [mssms] Content for Apps broken in Prestage media, workaround using Branchcache? All would be mood if I there is no way to do that on Win7. There isn't? I mean after all that cmdlet makes it simple, but maybe it can be simulated with more code? -roland Von: [email protected]<mailto:[email protected]> [mailto:[email protected]] Im Auftrag von Phil Wilcock Gesendet: Dienstag, 9. August 2016 15:11 An: [email protected]<mailto:[email protected]> Betreff: RE: [mssms] Content for Apps broken in Prestage media, workaround using Branchcache? 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]] 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
