Up until last week I was always using nLite to inject mass storage drivers into XP, then I finally took the time to figure out how to apply driver packages before the XP mini setup to inject the drivers. During my testing I had the task sequence apply the operating system package, auto apply drivers, and then apply the mass storage driver using an advertisement that was set to access content directly. The testing went great, so I went ahead and applied it to one of my main task sequences only to find that the mass storage driver step fails every time. The only difference between the two task sequences is that the testing task sequence accesses content directly and the main task sequence downloads content locally.
So, I suppose my question is do I have to have my task sequences accessing content directly in order to apply mass storage drivers with driver packages?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
*RESOLVED*
Hey everyone,
Up until last week I was always using nLite to inject mass storage drivers into XP, then I finally took the time to figure out how to apply driver packages before the XP mini setup to inject the drivers. During my testing I had the task sequence apply the operating system package, auto apply drivers, and then apply the mass storage driver using an advertisement that was set to access content directly. The testing went great, so I went ahead and applied it to one of my main task sequences only to find that the mass storage driver step fails every time. The only difference between the two task sequences is that the testing task sequence accesses content directly and the main task sequence downloads content locally.
So, I suppose my question is do I have to have my task sequences accessing content directly in order to apply mass storage drivers with driver packages?
Thanks in advance.
Edit1:
Maybe the error information would be useful.
ttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3002) DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3130) ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3031) TS::Utility::ResolveSource( pszPackageId, sSource ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,472) pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,409) Exiting with return code 0x80091007 Failed to determine the driver source location. Code 0x80091007 Failed to provision driver. Code 0x80091007
Share this post
Link to post
Share on other sites