Posted by Ami Questions: 67, Answers: Add comment. PC2 performs a local broadcast to see if anyone else has this content. Notify me when answered.
Those content servers will generate hashes for their content, so that BranchCache clients can download them instead of the whole content. The location of those hashes is called Publication Cache. To change this number, use one of the following commands:. If a BranchCache client wants to access a remote file share, the BranchCache will sense the latency to the remote file share server.
If the latency is below 80 ms default value , then the client will not use BranchCache. This is only applicable for accessing remote file shares and note web sites not applicable for http or BITS traffic.
Another important note that laptops on battery will not participate in BranchCache if it is participating in Distributed Cache mode. This is the default behavior to preserver power. As explained before, content servers are those servers with content that you want to cache content from.
Examples are you WSUS server or file share servers. Those content servers will generate hashes for content that is requested only. So, when the first client requests a certain file, the file is downloaded completely and the hashes start to generate on the server.
You need three different clients to request the same file to start getting benefit from BranchCache. Also note that hashes are generated for files bigger than 64k in size, so you will not benefit from BranchCache when dealing with files less than 64 in size.
Hashes on the content servers will be lost or deleted if the BranchCache service restarted. BranchCache service will then start generated hashes again when files are accessed. Q: What are the requirements for clients to participate in BranchCache Technology? A: Clients should be running supported edition of Windows and have the BranchCache local service set to Automatic. After that, the clients should be under the scope of a group policy that will enable them for BranchCache and will open couple of local Windows firewall exceptions.
Q: What are the requirements for my WSUS server or file server so that clients can cache content from? A: Absolutely NO. Q: In Distributed Cache mode, clients will cache content locally on their hard disk. Can you tell me more and will it fill up the client hard disk? Make sure that you have enough space on your C drive to handle cache files.
Q: If my machines are using BranchCache, is it possible that they may get old cached data from neighbor peers? A: NO. You will never ever get old data. BranchCache is designed to ensure it can work perfectly even with the most dynamic web sites that have content changing very quickly. The reason why this is true, is that clients will always connect to the live web site or share, get the newest hashes, and then requesting it from its neighbor machines if they have such data in their cache.
Q: If the main link between the branch and the main site is down, will my branch machines continue getting cached content from their neighbor peers?
Because each machine should connect to the content server first that is located in the main site, to get those hashes that describe the data, before requesting the complete data from neighbor peers. Q: What should I do if I want to troubleshoot a problem from my BranchCache client that cannot access a certain internal web site or file share? How can I temporarily disable BranchCache on that machine so I can troubleshoot the problem? A: Just stop the BranchCache Service, troubleshoot your problem, and then enable it again.
A: Well, it depends. But this requires that you install a server in the branch site with BranchCache supported edition from Windows Server. Finally, always remember to have your Windows client machines with good space on their C drive just in case. Q: Is it possible for neighbor machines to request access to cache content on my machine without being authorized to do so?
Because each BranchCache client will encrypt the data with a unique key that is shared with the content server. So neighbor machines should connect to the content server first, authenticate, get that encryption key, before asking your machine for cache content. Q: I am concerned about security and I am not sure if I can trust such technology and have sensitive files cached everywhere. A: Take it easy. BranchCache security is a long and complicated topic that I will be very pleased to discuss it with you if you drop me an email, and I will explain to you how BranchCache uses effective cryptography to protect data.
Q: What will happen if the BranchCache service fail to download content from neighbor peer or from the content server? Looking for consumer information? BranchCache is a bandwidth-optimization feature that has been available since the Windows Server R2 and Windows 7 operating systems. Each client has a cache and acts as an alternate source for content that devices on its own network request.
Distributed Cache mode operates like the Delivery Optimization feature in Windows client: each client contains a cached version of the BranchCache-enabled files it requests and acts as a distributed cache for other clients requesting that same file.
Distributed Cache mode is preferred to Hosted Cache mode for Windows clients updates to get the most benefit from peer-to-peer distribution. In Hosted Cache mode, designated servers at specific locations act as a cache for files requested by clients in its area. Unfortunately, connecting branch offices to the main office is just the first problem. Regardless of the method used to connect the branch office to the main office, the speed of the connection is typically limited.
This creates a productivity challenge for branch office workers. Employees need access to information at the main office in order to get their work done, but all the employees at the branch office need to share the same limited bandwidth available to the branch office.
If all the workers need access to files at the main office at the same time, there is going to be a bandwidth problem. Even if all the users do not need to access the main office at the same, a single user might need to access large files in the multi-megabyte range, which can take minutes to hours to download. Clearly, this is no efficient way to run a branch office. The goal of all of these solutions is to make branch office users more productive by speeding up access to information obtained over relatively slow WAN links.
The big problem with most of the WAFS solutions out there is that they prohibitively expense and are often very complex to set up and configure. The combination of the high cost on-boarding experience with the significant expenses involved with ramping up the IT group on using the solution make it debatable whether the outlay for the WAFS solutions increases productivity enough to make for a good return on investment. What we really need is a cost effective solution that is easy to manage.
It would be even better if the technologies were baked into the client and server operating systems used on the network. Windows Server R2 and Windows 7 are just the solutions you have been waiting for.
BranchCache is a new Microsoft technology that allows branch offices to cache content that branch office employees obtain from the main office. BranchCache works with other network encryption schemes you might already have in place. So if users at the branch office access content on an SSL site hosted at the main office, BranchCache will work with those connections with no extra configuration or effort on the part of IT or the end user.
In the same way, if you use IPsec on your network, for example in a server or domain isolation environment, BranchCache will work with IPsec protected connections. This is great news to those of you who are worried about IPv6 because of DirectAccess.
BranchCache needs to be enabled on both the client and the server. When a user tries to access information on a BranchCache enabled file or Web server, the user is still authenticated in the same way the user would be authenticated even if BranchCache were not deployed.
After the user is authenticated, the user is then authorized, again in the same way that it would take place even if BranchCache was not enabled.
0コメント