Deploying Win7 works fine with BC from PE 8.1, it can be downgraded to use the old HASH version. The only issue is that BranchCache can only upgrade or use same CACHE version, not downgrade, i.e. the "stuff".
So even though WinPE 8.1 is using a Win7 HASH, it's using a Windows 8.1 CACHE, which cannot be transferred to Win7. A few options at the top of my head: 1. Store both CACHE's on the USB and transfer the right one. 2. Use WinPE 3.1 to deploy, that's the Win7 version of the CACHE. 3. Don't care about the transfer to the full OS and use V2 HASH? 4. Upgrade to Windows 10 ;-) //A From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: den 8 juni 2015 20:59 To: [email protected] Subject: RE: [mssms] Prepopulate branchcache on client for ConfigManager I must have missed the answer to my question :) Deploying Win7 with PE 8.1. That seems to be a showstopper for Branchcache OSD? Also if I don't need to transfer the content to the OS? -Roland From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Donnerstag, 4. Juni 2015 00:51 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Prepopulate branchcache on client for ConfigManager Just before you send me an updated version :) Would I have an issue (see below)? The version issue between PE5 and Win7 is the topic. -Roland From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Mittwoch, 3. Juni 2015 17:42 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Prepopulate branchcache on client for ConfigManager Adding another question: Deploying Win7 with PE 8.1. That seems to be a showstopper for Branchcache OSD? Also if I don't need to transfer the content to the OS? I need 8.x: bitlocker used space only. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: Mittwoch, 3. Juni 2015 16:45 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Prepopulate branchcache on client for ConfigManager 1. Does what exactly? Don't get the relation with the wim file. Is that the PE wim? The cache is stored in inetpub? I think I should be ok with the secret. It's the first time the TS runs, as boot media, where I would inject the content. There is nothing then. Once it is in the prestaged media t should use the already existing content (from CM) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Phil Wilcock Sent: Mittwoch, 3. Juni 2015 16:22 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Prepopulate branchcache on client for ConfigManager If you export packages from the server you don't have to set the same server secret, http://2pintsoftware.com/2psfaqs/branchcache-caching-faq/ On The Server 1. Stage the Content Publish-BCWebContent -Path c:\inetpub\wwwroot\MyBigWIMFile.WIM -StageData -StagingPath c:\temp 2. Export the content to a package (creates a handy .zip file) Export-BCCachePackage -StagingPath c:\temp -Destination c:\MyBCPackage On The Client 1.Import the Package Created in Step 2 Above Import-BCCachePackage -Path C:\temp\pkg\PeerDistPackage.zip If you're talking about just taking a bunch of content that is already local then you have the set the same server-secret.. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: 03 June 2015 12:24 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Prepopulate branchcache on client for ConfigManager 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]> [mailto:[email protected]] On Behalf Of Roland Janus Sent: den 3 juni 2015 12:32 To: [email protected]<mailto:[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
