Fail to copy drivers to driver package
I am trying to import drivers to driver package so that I can run "auto apply drivers" in the task sequence. Basically, I chose all drivers for a specific model on the driver node and drag them into one of the driver packages so that it can be copied to DP. I get the following error message: "Some packages can not be updated. Please see the log file for more information". I thought that it might be permission issue, so I give everyone full right on share and NTFS on the folder that the package references to, but I still get the same error message. What is weird is that I can add some drivers and update the DP successfully, but most drivers I can't add them to the package and get theerror above. Sometimes, I drag only one driver, for instance, SATA controllerfrom the driver catalog to the driver package andthe driver package is populated with 46 drivers in different categories. After so many different attemps and failed. I even deleted all driver packages, then re-create the "all drivers" package then drag all the drivers in the drivers node to the "all drivers" package, but still get the same error message as shown above. What else can I try?
January 21st, 2009 3:09am

Hi, Couple of thoughts: 1. Drivers are copied from their source location to the driver package using the SMS Providers machine account (therefore it is critical to give this account rights to read from the driver source and write to the driver package not the users who are initiating the operation) 2. Check the smsprov.log right after you see the error message in the UI to see the specific driver that failed Please let us know how it goes. Thanks, -- BrettThis posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
January 21st, 2009 8:27pm

The permission is fine. I checked the log as you suggested and I get the following:[16F8][Wed 01/21/2009 14:39:33]:SspPackageInst::AddContent() called with these CIContentSourcePath - {"\\mystery\pkgsource$\OS Deployment\Drivers\Latitute E4300\ChipSet\R182522\Vista"}[16F8][Wed 01/21/2009 14:39:33]:RefreshDPs value is FALSE. DP(s) will not be updated at the end of the operation [16F8][Wed 01/21/2009 14:39:33]:These Contents will be added to Software Updates Package - VMC00067 with PackageSource - \\mystery\pkgsource$\OS Deployment\Drivers\E-Series Laptops\All Es Drivers[16F8][Wed 01/21/2009 14:39:33]:Adding Content with ID 19094, UniqueID 48472F02-1117-46F9-B047-BD090BE8872B and ContentSource \\mystery\pkgsource$\OS Deployment\Drivers\Latitute E4300\ChipSet\R182522\Vista to the Packagee:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\ssppackage.cpp(3544) : Downloaded content specified in package source directory is in wrong location[16F8][Wed 01/21/2009 14:39:33]:Downloaded content specified in package source directory is in wrong location [16F8][Wed 01/21/2009 14:39:33]:SspPackageInst::ImportContent() failed. [16F8][Wed 01/21/2009 14:39:33]:CExtUserContext::LeaveThread : Releasing IWbemContextPtr=36572392what does "Downloaded content specified in package source directory is in wrong location" mean?
January 22nd, 2009 1:43am

What happens is that I changed the source path after I imported the drivers to driver catalog causing the path error when I move the drivers to the package on DP. I expect that the path will be referenced accordingly after I moved the drivers into a different source path, but it didnt. I got it fixed now.
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2009 3:04am

I too have changed the source path to the original drivers that I imported (moved the drivers later but imported path shows original)When I check the properties of the driver in the imported Drivers nodei.e. Drivers.Dell.rightclick on driver for properties.... the original path that I used when I first imported the driver is displayed... not the new path.Subsequently, when I try to add these drivers to a new package it fails because the drivers are no longer in that path.I missed the part about how you cleared out these drivers (just deleting them and reimporting them) so that I can use my revised folder structure.Where are the SCCM drivers stored?Thanks alot,AllisonAsutherland
February 18th, 2009 4:48am

I found this in my trouble shooting of the exact same issue. Status messages says things like not acces to DP og loong filename etc. but log says content wrong location. I had a long file name auto generated from drag and drop: HP Compaq 8100 Elite Small Form Factor PC - Intel Gigabit Network Connection Drivers for Microsoft Windows XP - HP Business Support Center I tryed renaming file, deleting file but to no use. Issue resolved by fyrst changing sourcefile name(s), then reimport the drivers. Lla ta anon
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2010 6:16pm

Unfortunately I run into the same issue and already did everything to solve this issue - unsuccesfully. - I gave full access onto the share for the SCCM-User (Domain User) the SCCM Domain Adminaccount, the System account and the machine itself - I gave NTFS full access rights for the SCCM-User (Domain User) the SCCM Domain Adminaccount, the System account and the machine itself - I renamed the folders and drivers to prevent long directory- and file names - I didn't make any changes to paths after driver import - The folder for the driver packages is other than the source folder to prevent any trouble caused by reading and writing from and into the same folder - I deleted all drivers and reimported them to prevent any old references to paths or packages - The drivers are simple HP network, audio and display drivers for the Elite Desktop 8100 SFF series I've already checked this thread, have visited this one and currently checking this one. I hope this will help me out since currently I'm absolutely clueless how to solve this issue. Further on I'm not sure if this is party of the failure of capturing my reference machine (Windows XP). When trying to install the deployment tools, the task sequence ends with an error (0x00000002). The installation itself is succesful but capturing fails. When logging on to Windows and opening the device manager I see that neither the display and audio drivers are installed nore the network and chipset drivers, although being included in the Boot Image. When this annoying issue is solved I'll be really happy and relieved. :)
January 13th, 2011 7:00am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics