none
hash mismatch and retry download questions RRS feed

  • Question

  • Consider this scenario: A software package is created and advertised to a client with a mandatory schedule. The client downloads the package as soon as the policy is received. The administrator makes some changes to the package and refreshes the distribution point to make sure that the changes get applied at the DP. Once the advertisement deadline is reached, client tries to verify the package in its cache with the hash value of the package on DP. The download fails since the hash values don’t match.

    1. I can see that the version of package in client's cache is XYZ00012.13 whereas the latest version of package on DP is XYX00012.15. How do clients discover it when there's a new version of package available? Why are my clients not downloading the new version of package?

    2. If the package download failed the first time, why don’t clients retry downloading it assuming there is more than 1 hour before the advertisement deadline and client policies refresh every hour? It appears the client just reports a failure when the deadline is reached even after I had already resolved the problem hours ago.


    Mayur
    Monday, November 21, 2011 8:58 PM

Answers

All replies

  • The Possible... causes.. If the client has old Machine Policy and not updated with old policy then it could happend...

    This could also happens if the AV not excluded................... http://blogs.technet.com/b/configurationmgr/archive/2010/11/30/configmgr-2007-antivirus-scan-and-exclusion-recommendations.aspx

    refer to these post http://richardbalsley.com/sccm-program-failed-download-failed-content-mismatch-for-advertisement-failures

    http://aditan.wordpress.com/2009/11/16/sccm-2007-clients-may-report-a-hash-mismatch-when-we-run-a-package-that-has-been-configured-to-download-and-run/

    http://anoopmannur.wordpress.com/2011/05/09/configmgr-sccm-hash-mismatch-issue/

     


      


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, November 22, 2011 2:47 AM
  • Have you tried deleting the package from cache and tested it ? Is this issue only for one machine?

    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Tuesday, November 22, 2011 3:03 AM
  • 1. I can see that the version of package in client's cache is XYZ00012.13 whereas the latest version of package on DP is XYX00012.15.

    It could also be possible that there are replication issues IF this is happening on a child site. That reason is not applicable on a single site setup.
    Torsten Meringer | http://www.mssccmfaq.de
    Tuesday, November 22, 2011 7:58 AM
    Moderator
  • 1. Client's request specific versions of packages based upon whatever is in their policy. If the policy they have recieved doesn't reference the latest version, they won't know to download the latest version.

    2. They don't check the hash until they try to use the content so there isn't really time for them to retry the download. Not saying this is ideal, but that's the way it is.


    Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys
    Tuesday, November 22, 2011 2:19 PM
    Moderator
  • Have you tried deleting the package from cache and tested it ? Is this issue only for one machine?

    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    I have not tried it on this machine. But I have done it in the past. If I remember correctly, it caused a another problem with the error along the line of "content is missing or an administrator has manually deleted the content from the local cache". The advertisement wouldn’t run after that. I had to create a new advertisement. Sorry I don’t have a whole lot of details on what had happened but I decided not to delete the cache manually again.

    It's happening on all of my test computers.


    Mayur
    Wednesday, November 23, 2011 7:05 PM
  • 1. I can see that the version of package in client's cache is XYZ00012.13 whereas the latest version of package on DP is XYX00012.15.

    It could also be possible that there are replication issues IF this is happening on a child site. That reason is not applicable on a single site setup.
    Torsten Meringer | http://www.mssccmfaq.de

    We only have one site. The client is located at the primary site.
    Mayur
    Wednesday, November 23, 2011 7:06 PM
  • 1. Client's request specific versions of packages based upon whatever is in their policy. If the policy they have recieved doesn't reference the latest version, they won't know to download the latest version.

    2. They don't check the hash until they try to use the content so there isn't really time for them to retry the download. Not saying this is ideal, but that's the way it is.


    Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys

    Do clients get notified via policy refresh when a package is updated? If so, will they try to download the new version of the package if there's still time before the advertisement deadline?
    Mayur
    Wednesday, November 23, 2011 7:09 PM
  • Yes. If the content is refreshed, the client policy does get updated on its next policy retrieval period.

     

    Thursday, December 8, 2011 9:10 PM