I have the following SCCM server installation. Windows Server 2008 Standard x64 SCCM 2007 SP1 MDT 2008 Update 1 SQL 2005 SP2 x64 installed locally One primary site. No other primary or secondary sites. The server is upgraded from SMS 2003 in a side-by-side upgrade. I have setup deployment of Windows XP, using a MDT Client task sequence, using manually applied driver packages pr. PC model meaning no Auto Apply Drivers. The system is working fine and I can deploy XP on a couple of PC models. My problem is the following: I create a new driver package for a new PC model. I add the driver package to the TS and add a network driver to the driver package. Then I copy the driver package to my distribution point and then I am ready to try to deploy XP to my new PC model (well aware that there will be needed more drivers to the PC later). When I try to deploy XP to the new PC model, the deployment will fail in the part where the dependencies for the TS are checked. Getting policy for CCM_SoftwareDistribution[AdvertID="LB120000", PackageID="LB100011", ProgramID="*"] TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) FALSE, HRESULT=80040104 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2301) TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) Failed to find CCM_SoftwareDistribution object for AdvertID="LB120000", PackageID="LB100011", ProgramID="*" TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) (*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040104 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862) TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS:olicy::TaskSequence::ResolvePolicy | TS:olicy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040104 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1207) TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) Failed to resolve selected task sequence dependencies. Code(0x80040104) TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) hrReturn, HRESULT=80040104 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408) TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040104) TSMBootstrap 25-09-2008 15:37:45 760 (0x02F8) ThreadToResolveAndExecuteTaskSequence returned code 0x80040104 TSMBootstrap 25-09-2008 15:37:45 1300 (0x0514) Setting wizard error: This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, please contact your system administrator or helpdesk operator. TSMBootstrap 25-09-2008 15:37:45 1300 (0x0514) It seems like there is something wrong with the package I just created. I can check the DP directory and see that the package is copied there. If I go into the SQL Server Management studio and take a look at the actual package in the dbo.SMS_Packages table I can see that the fields for the HASH and New HASH are empty. If I do an Update Distribution Points the HASH values will be filled out and the TS will run without errors. Why does SCCM fail to fill out those HASH fields when I copy the package to the distribution point?

BUMP... Anyone?

I am seeing something similar. In my case I attempted to create Task Sequence Media and get the following in my CreateTsMedia.log:Staging package SMS00038 CreateTsMedia 10/1/2008 8:40:46 AM 7264 (0x1C60)Failed to stage package SMS00038 (0x80091007) CreateTsMedia 10/1/2008 8:42:02 AM 7264 (0x1C60)Failed to create media (0x80091007) CreateTsMedia 10/1/2008 8:42:02 AM 7264 (0x1C60)CreateTsMedia failed with error 0x80091007, details="SMS" CreateTsMedia 10/1/2008 8:42:02 AM 7264 (0x1C60)MediaGenerator::~MediaGenerator() CreateTsMedia 10/1/2008 8:42:02 AM 7264 (0x1C60)I also did a refresh on the DP as well as removed it and re-added it to the DP. I also checked in dbo.SMSPackages and saw Hash and NewHash contain no data. Now an update did work as it finally filled in the HASH value and I was able to create my TS Media.

When you added the drivers to the driver package was the option"Update Distribution" checked? If you did not check this option then wha you said above can happen. I am thinking you did this - a> Created an empty driver package (this will create package with version 1 with no hashvalue since no driver content in the package) b> Added some drivers to the pakage but did not chose the option to update the Distribution points. (This will not change the package hash or versionbut will only copy the driver content to the package source location. Package hash is calculated whenever you update the package by selecing update DP option.) c> Added distribution points to the driver package. (This will copy everything from the package source to the distribution points). Let me know if you think you did something else and still the package hash was empty. -Thanks

Hi Bippen, Thanks for your answer. What I did was this: Created an empty Driver Package. Added drivers to the package and did NOT check the update distribution point because it has not been copied to any DP's yet. Choose to manage DP's and copied the package to my DP But I dont understand why the "Copy package to distribution point" does not fill in the hash values because a package on a DP without HASH values is useless.

Hash value for the package content is generated when the package is updated (Update DP option) or initially when its created. Ideally you would do an update package action when there is a change in the package content and therefore SCCM generates the new hash value and stamps the package with a new package version (incremental). When the DPs are added to the package, the package content is just copied over to the DPs from the package source (or compressed copy of the package if thats the option selectedfor the package). There is no need to generate hash since there is no change in the content. In your case, since you only createed the package and at the time of the create there was no content in the package therefore the hash value was empty. Later on when you added the drivers to the package, since no update package was done, there no hash was generated.

Thanks Bippen, brilliant explanation. Solved my problem nicely :)

hi, i've encountered a similar problem with the incorrect hash value. in the source package make sure there isn't any hidden and operating system files (for example thumbs.db). so make sure that all files on the package are "normal" files. when the sccm server creates a package, it generates a hash value based on all "normal files" in the package. After, it sends the package to the distribution point. if the package contains hidden files, the files won't be hidden on the distribution point. So, after receiving the files, the distribution point tries to generate a hash value with all files ! This is the reason why the result is a "hash vallue is not correct" when comparing the two hashes. So modified all files in the package to be not hidden files. after that, in the SCCM console, select your package and click on distribution point. Right click on "distribution point" and select "manage disitribution point". Finally, select "update distribution point with a new package source version". this action force the sccm server to create a new package and a new hash. after that, the new package will be sent to all DPs. regards, Régis

I had the same issue. I was trying to add the driver package to TS and create TS Media. I followed above procedure did not work. I tried below steps on top of above steps 1. Follow steps by Bippen ( above ) 2. Update the distribution point ( this will make source version as 2) 3. Right click manage -> refresh Distribution point. Thanks uday