Hello All, As most of us already are aware of, the "Hotfix - http://support.microsoft.com/kb/2213600", resolves the issue that you cannot import driver files to driver packages if the driver is already imported to the SCCM Site. This Hotfix resolves above issue, but it doesn't address following issue: 1. "Driver Files" imported multiple times from different "Source Paths" are not threated as unique "Driver Files" 2. When deleting a "Driver File", it is deleted entirely from all "Driver Files Folders" you may have, meaning the driver is shared. Example: You have to hardware models, HP2530p and HP2540p and would like to create 1 driver package for each model. You organize your drivers according to this directory structure: .\Source\HP2530p\Audio .\Source\HP2530p\Nic etc .\Source\HP2540p\Audio .\Source\HP2540p\Nic etc In both Audio directories for both HP laptop models, the audio driver is equal (same version, same file name etc). First time you import the Audio Driver Files, you add them to your "HP2530p" category and the driver folder "HP2530p" inside the SCCM Console. Second time when you import the HP2540p (second model) Audio Driver Files, you add them to your "HP2540p" category and the driver folder "HP2540p" inside the SCCM Console. After doing this, you will discover that both driver category and driver source for HP2540p, will refer to the category of HP2530p and the source directory for HP2530p, instead of HP2540p. This means that driver files that are equal are re-used if it they already exist in the driver store of SCCM. If you decide to delete the Audio driver for one of the models, the driver is deleted at both places (in Driver Folder and in Driver Package (when you update it)) inside the SCCM Console. If you want to have 100% control of your drivers pr. hardware model (as listed above), simply use the old workaround as used before the hotfix KB2213600 was released, where you create one TXT file in each directory, as described here http://myitforum.com/cs2/blogs/jsandys/archive/2010/04/05/duplicate-drivers-helper-script.aspx By doing this, SCCM will threat each drivers files as unique (since the driver source content will not be equal), allowing you to have multiple source paths and categories for each of your hardware models that is using same drivers. In my opinion, this will ease your Drivers Administration. I hope that you find this useful, it worked for me :) Best Regards Anders Horgen