Hi everyone, I have a little problem running some package through Task Sequence. I have a TS with no boot image, running only one package wich is Acrobat X Pro 10.1.3. If I leave the default option to donwload the content if required the installation will faile with the hash value is not correct error. If I install the same package using a normal advertisement (not in a TS) I have no problem at all. If I run the package in a TS specifying to run the package from the distribution point, no problem at all. If I run the package in a TS but I specify to download the content before running the TS, there is no problem either. The only point in commun that I can find so far is that those packages where done using administrative install to update the MSI with MSP. Onc done, the new files are copied over the DFS in the source folder then the package is created in ConfigMgr 2007. There is no hidden files and the package was removed and created again. If someone can help me get an idea of what is going on the would be nice. Thanks

If I install the same package using a normal advertisement (not in a TS) I have no problem at all. Is the advertisement set to "download & execute" then?Torsten Meringer | http://www.mssccmfaq.de

Yes, download content from distribution point and run locally. The problem happen when Download content locally when needed by running task sequence is selected and that the package is part of the task sequence.

Still nothing new on my side. I took the package and add them into a test environment I had. One of the package did worked well the other no. I anyojne have a clue or an idea, I'll take it! Mat

Did you update the DP? Please verify the Package Hash in Source, DP, and DB. Is there any clue in the SMSTS.log?Sabrina TechNet Community Support

Not sure it will make a difference but worth a shot, open the properties for your package and goto the advanced tab and tick the box "Allow this program to be installed from the Install Software task sequence without being advertised".

Sorry for the late answer, yes, I did updates my distribution point and validate the hash value using HashDir on the Source, Distribution point and the database. The version is always the same. There is no clue at all in the SMSTS.log, only that the hash mismatch. I'll make another test and get more info about the smsts.log and edit my post. EDIT: the smsts.log did not helped at all, nothing in there except the same old good error 80091007. If I take the same exact package and program, deploy them using any other way ot will work.

This is already done because if I haven't done that I would not be able to select that program to install from a TS. But thanks, it worth the shot to mention it.

So, no one is having an idea. I just made another package for Adobe Acrobat X (administrative install) and still the same issue. And the problem is not with OSD. I am using a TS to deploy the software but not during an OSD.

Is your source number higher than 1? I have run into problems with driver packages that if the source number was 1 during OSD i would get Hash missmatch. Maybe the same issue you are having with your package. Also check that there are no hidden files in the package source and also no non-standard characters like the copyright (r) or the tiny tm. If there are just delete those characters in the file names.

Have you checked, that there is no file, which would WebDAV not distribute to the client? There are some file extensions which will be excluded.

I do not think that there is any file blocked by WeDAV because all the files are downloaded and that the hash is being calculated. I just checked for extended characters and there is no such things in the filename. The problem is probably related to administrative install (msiexec /a) of the software but I do not see how this would affect the hash while being downloaded by the task sequence when required. I wrote a post on the Adobe forum also to see if anyone there have seen an issue that could look like this one. Here is the link if it can be of any help: http://forums.adobe.com/thread/997468 Again, I'll post here any infomation that I can get.

That is right, i also could not Imaging, how the program can have an Impact to the Hash Value. Do you get your Pacakge Folder under %windir%\system32\ccm\cache?

The packages are downloaded to c:\_SMSTaskSequence\Packages when using a Task Sequence. there is nothing under the cache folder. I managed to get a copy of the files downloaded and I am trying to find out why the hash do not match the package on the DP.

Copy this to notepad and name it badfiles.vbs. The syntax from the command prompt is cscript.exe badfiles.vbs <Path to package/Drivers>. So for instance if your installer files (the installer from adobe in this case) is in F:\Applications\Adobe\Professional then it would be cscript.exe badfiles.vbs f:\applications\adobe\professional. This will check for ASCI characters and hidden files and give you feedback if there is any. I found this online somewhere and have used it, it does not delete or rename anything. ' Syntax is cscript.exe badfiles.vbs <path> Option Explicit Dim sPath, oFSO Set oFSO = CreateObject("Scripting.FileSystemObject") sPath = WScript.Arguments(0) Find sPath Sub Find(ByVal sPath) Dim oFolder, oFile Set oFolder = oFSO.GetFolder(sPath) If Err.Number = 0 Then For Each oFile in oFolder.Files If Err.Number = 0 Then DoChecks oFile.Path, False Else Err.Clear End If Next For Each oFolder in oFolder.SubFolders If Err.Number = 0 Then DoChecks oFolder.Path, True Find oFolder.Path Else Err.Clear End If Next Else Err.Clear End If End Sub Sub DoChecks(ByVal sName, ByVal bIsFolder) Dim sString, i, oFileFolder If bIsFolder = True Then Set oFileFolder = oFSO.GetFolder(sName) Else Set oFileFolder = oFSO.GetFile(sName) End If If Err.Number = 0 Then If oFileFolder.Attributes AND 2 Then WScript.Echo "HIDDEN: " & sName End If Else Err.Clear End If sString = Mid(sName, InStrRev(sName, "\") + 1, Len(sName)) For i = 1 To Len(sString) If Asc(Mid(sString, i, 1)) < 32 Or Asc(Mid(sString, i, 1)) > 126 Then WScript.Echo "BAD CHARACTER: " & sName End If Next End Sub

Also this is how I do reader, I know you are doing pro. msiexec /i AcroRead.msi TRANSFORMS=AcroRead.mst

You're right, I forgot about the TS. Have you tried to deploy the package with a collection/advertisement? Just to get nearer to the error. What you also could try, is to run this with the Option "Run from Distribution Point". This would'nt download the package.

Thank you for the script, I did tried it right away on a copy of my package. Just a quick warning, it renamed the all bad files :) but with other bizarre characters. The bad files it did find are actually files for french and deutch like: Prparer pour la rvision.sequ and Vertrauliche Dokumente verffentlichen.sequ As for the command line used, yes I am using similar command line to launch the software install and when using the same exact package with a standard software distribution (not form a task sequence) it does work. The execute form distribution point option is good and is actually what we are doing right now but we have atask sequence that use variable to install software depending on the client colleciton membership and this will not work, unless we change the execution of the whole task sequence to run from the dp.

Hmm, guess I have never noticed it rename, even with other bizarre characters. I beleive the "" and like characters can cause the mismatch. This also includes the "". I beleive there is a document somewhere and I will try and find it for you. Here is the document I was refering to. http://blogs.technet.com/b/smsandmom/archive/2008/10/09/configmgr-2007-smsts-error-hash-could-not-be-matched-for-the-downloaded-content.aspx

Good, I did saw this article some time before but I did applied the hotfix for that behavior: http://support.microsoft.com/kb/2507187/en-us I guess that the problem is not fixed. I did checked the dll version and it is the good one.

Did you get this resolved?

Yes and no, we called MS and they said that the client update KB2276865 (even if nothing is said about this) will resolve the issue. The version of the TSCore.dll is changed from this update and the problem seem to be fixed. While this is fixing the issue, the other problem we have is that only one update can be installed during the task sequence and we install KB977384. I did tried the command line wich will chian the updates separated with ; with no success, I have an error that the installer is not able to make a local copy of the update and it failed. We are working on a way to apply both update in the order we want and again, no success so far. If someone have any idea on how to apply more than opne update during the TS, I will be really happy :) So, this is all for now. Mathieu

Ok so definately, the KB227865 did the trick. The TSCore.dll must be at version 2152 in my case to make it work without problem. To install many patches, there is two scripts available: 1- MS recommand me that one: http://blogs.technet.com/b/deploymentguys/archive/2010/08/13/automatically-populate-the-patch-property-for-the-configmgr-2007-client-installation.aspx It will work well but will fail if you have a disk with two partition like we have. 2- This is an updated verison of the firts one that will work if you have two partition: http://www.myitforum.com/absolutenm/templates/Articles.aspx?articleid=26282&zoneid=89 So here we go, problem fixed and everything is fine! Mathieu