Here is another error related to Task Sequence and MDT 2008. After creating and advertising a task sequence, most probably you will run it :). Make sure you have the latest version of your packages on the distribution point, otherwise you will receive an error while running the task sequence. This will be something like “Task Sequence: your task sequence name has failed with the error code (0x80091007). For more information, please contact you system administrator or helpdesk operator.”
In the log file you will find this: “The hash value is not correct.”
What you can do to resolve this? Two things:
to update your distribution point with the latest version of the packages. To be sure the package was updated successfully, you can put a txt file somewhere and verify if it is on the DP.
modify the advertisement to not download the files locally but access the files directly from the DP, although I’d not recommend it.
Today I came across an interesting problem in ConfigMgr while creating a Windows Vista image of reference computer. And again, ConfigMgr 2007 displays the error with not much intuitive help.
I’m using Microsoft Deployment Toolkit 2008 with ConfigMgr 2007 when I need to deploy an operating system. At the end of the imported Task Sequence, after the wizards creates the .wim image, it copies the image to a share specified by me. During this step I received the following error: “Error while importing Microsoft Deployment Toolkit Task Sequence. Details: The ConfigMgr Provider reported an error”.
Checking smsprov.log I have found the error code – 5. Yes, 5 :). From the log file: “Failed to make a copy of the source WIM file due to error 5”. Nice… what could I say? Shortly, error 5 is about permissions.
I started to play with share permission. Granted read permission to admin account I was using and to the ConfigMgr computer account but I had no success. Granted full control permissions to these accounts. Same error :(.
Well, the problem was because ConfigMgr is accessing local shares using NT AUTHORITYSYSTEM account and not computer account (the shared folder was on the same computer). I granted full control permissions to SYSTEM account and next time I run the task sequence to create an image of the reference computer, it was ok and the image was copied to my shared folder.