http://blogs.technet.com/b/mniehaus/archive/2010/04/29/configmgr-2007-driver-management-the-novel-part-2.aspxIn the previous posting at http://blogs.technet.com/mniehaus/archive/2010/04/29/configmgr-2007-driver-management-the-novel-part-1.aspx , I mentioned that it should be possible to script the importing of drivers into the ConfigMgr driver store to helpen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/mniehaus/archive/2010/04/29/configmgr-2007-driver-management-the-novel-part-2.aspx#3428295Wed, 11 May 2011 19:37:29 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3428295Michael Niehaus<p>No, you would need to strip the &quot;release.dat&quot; file from the extracted CAB file contents before importing the drivers into ConfigMgr.</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3428295" width="1" height="1">http://blogs.technet.com/b/mniehaus/archive/2010/04/29/configmgr-2007-driver-management-the-novel-part-2.aspx#3428294Wed, 11 May 2011 19:34:24 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3428294davidpyu<p>Does this script include logic to look for release.dat file that defeats the duplicate detection so that it does not import these drivers that are really duplicates. You mentioned in the first post that this logic was added to MDT 2010, but is it added to this script?</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3428294" width="1" height="1">