none
BranchCache

    Question

  • Hi
    Here's the scenario I've done

    http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=89422460-1092-4679-93bc-39e1700d75b4

    Why for the first time a "client 1" does not cache the incoming file?

     when the client 1get the file for first time.

    For the first time the file is not cached in the client 1.

    Then client 2 get the same file and now file store in a client 2.

    Why for the first time a "client 1" does not cache the incoming file?

    Thanks
    Sunday, January 06, 2013 8:22 AM

Answers

  • It should. It maybe something that wasn't configured correctly. Here's more info on how it works:

    BranchCache Overview  (Distrubuted or Hosted)
    http://technet.microsoft.com/en-us/library/hh831696.aspx

    Video: BranchCache Overview  (Distrubuted or Hosted)
    The cache can be hosted centrally on a server in the branch location, or can be distributed across user PCs.
    http://technet.microsoft.com/en-us/windows/branchcache.aspx


    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Sunday, January 06, 2013 10:06 PM
    1.    A client computer, Client-01, requests a Web page from the BranchCache content Web server, Content-01.
    2.    Content-01 automatically generates the content information for the requested Web page. Content-01 sends the content, but not the content information, to Client-01.
    3.    Another client computer, Client-02, requests the same Web page from Content-01. The Web server sends the content information to Client-02. Client-02 uses the content information to query other client computers in the branch office for the content, and discovers that none of the clients have the content in the branch office. Client-02 then requests and receives the actual content from the Web server. Because Client-02 now has both the Web page and the content information for the Web page, Client-02 stores the content in its BranchCache cache.
    4.    Another client computer, Client-03, requests the same Web page from Content-01. The Web server sends only the content information to Client-03. Client-03 then uses the content information to query other client computers to find out if they have the content. Client-02 matches the content information to the content in its cache, and sends the requested Web page to Client-03.

    The above description
    Client 1 get the file directly and
    doesn't cache for the first time.
    And the clienthas asked for a second time on the same file.This is get directly file and cached now.

    Why client 1 doesn't cache file for first time?

    Thank you for your answer.

    The answer is in the steps. Client1 gets the content, but not the content information. Client2 and subsequent clients gets the content information, not the first one. Apparently when the webserver is also configured for BrancheCache, it doesn't send it to the first request, only subsequent requests. Seems like if there's only one request, then it's not worth caching, but if more than one request, it will then send the content info.

    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Monday, January 07, 2013 7:01 AM

All replies

  • It should. It maybe something that wasn't configured correctly. Here's more info on how it works:

    BranchCache Overview  (Distrubuted or Hosted)
    http://technet.microsoft.com/en-us/library/hh831696.aspx

    Video: BranchCache Overview  (Distrubuted or Hosted)
    The cache can be hosted centrally on a server in the branch location, or can be distributed across user PCs.
    http://technet.microsoft.com/en-us/windows/branchcache.aspx


    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Sunday, January 06, 2013 10:06 PM
    1.    A client computer, Client-01, requests a Web page from the BranchCache content Web server, Content-01.
    2.    Content-01 automatically generates the content information for the requested Web page. Content-01 sends the content, but not the content information, to Client-01.
    3.    Another client computer, Client-02, requests the same Web page from Content-01. The Web server sends the content information to Client-02. Client-02 uses the content information to query other client computers in the branch office for the content, and discovers that none of the clients have the content in the branch office. Client-02 then requests and receives the actual content from the Web server. Because Client-02 now has both the Web page and the content information for the Web page, Client-02 stores the content in its BranchCache cache.
    4.    Another client computer, Client-03, requests the same Web page from Content-01. The Web server sends only the content information to Client-03. Client-03 then uses the content information to query other client computers to find out if they have the content. Client-02 matches the content information to the content in its cache, and sends the requested Web page to Client-03.

    The above description
    Client 1 get the file directly and
    doesn't cache for the first time.
    And the clienthas asked for a second time on the same file.This is get directly file and cached now.

    Why client 1 doesn't cache file for first time?

    Thank you for your answer.

    Monday, January 07, 2013 6:20 AM
    1.    A client computer, Client-01, requests a Web page from the BranchCache content Web server, Content-01.
    2.    Content-01 automatically generates the content information for the requested Web page. Content-01 sends the content, but not the content information, to Client-01.
    3.    Another client computer, Client-02, requests the same Web page from Content-01. The Web server sends the content information to Client-02. Client-02 uses the content information to query other client computers in the branch office for the content, and discovers that none of the clients have the content in the branch office. Client-02 then requests and receives the actual content from the Web server. Because Client-02 now has both the Web page and the content information for the Web page, Client-02 stores the content in its BranchCache cache.
    4.    Another client computer, Client-03, requests the same Web page from Content-01. The Web server sends only the content information to Client-03. Client-03 then uses the content information to query other client computers to find out if they have the content. Client-02 matches the content information to the content in its cache, and sends the requested Web page to Client-03.

    The above description
    Client 1 get the file directly and
    doesn't cache for the first time.
    And the clienthas asked for a second time on the same file.This is get directly file and cached now.

    Why client 1 doesn't cache file for first time?

    Thank you for your answer.

    The answer is in the steps. Client1 gets the content, but not the content information. Client2 and subsequent clients gets the content information, not the first one. Apparently when the webserver is also configured for BrancheCache, it doesn't send it to the first request, only subsequent requests. Seems like if there's only one request, then it's not worth caching, but if more than one request, it will then send the content info.

    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Monday, January 07, 2013 7:01 AM