Driver management part 2!
Hi, OK... as per my previous post regarding drivers... I have gone with the default method of basically creating a folder structure thus: C:\Source\Drivers\WindowsXPx86\Model\NIC etc Now I import this into SCCM under the drivers node which has a structure of this: Drivers\WindowsXPx86\Model Then from this I create a package which I store at \\server\driverpackages... Now I have had two issues with this which I am not sure how to deal with... Issue 1: After creating a package etc I decide that the source folder name is incorrect... I thus remove the package from SCCM and remove the drivers from the drivers node... the problem is I cannot rename the folder because SCCM seems to have a lock on it (Checked via Process Explorer) Issue 2: I realised I had missed a driver file (a dll) off the list of a machine model, so I added it to the source folder and selected to import again specifying the source folder... this worked but errored on the already existing drivers... When I updated the package, the OSD deployment actually created three folders on the client, one with the mass storage driver, one with everything else except this dll, and one with just the dll on, (Probably because of the way I did it)... How is this done...
August 4th, 2011 10:20am

you could use process explorer to find out what is holding on to the files, or just bite the bullet, reboot the server and try again, if that doesnt resolve you could boot into WinPE and delete that directory. My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
August 4th, 2011 12:28pm

I'm not completely following your question's train of thought. However below you find a couple articles outlining best practices for the importing of drivers into SCCM: Part 1: http://scug.be/blogs/sccm/archive/2009/02/27/sccm-2007-best-practice-importing-drivers-part-1-creating-a-driver-package.aspx Part 2: http://scug.be/blogs/sccm/archive/2009/03/03/sccm-2007-best-practice-importing-drivers-part-2-importing-a-driver-into-the-sccm-database.aspxChris Raschke | C/D/H - www.CDH.com | Twitter: raschkec
August 4th, 2011 12:33pm

Hi, After re-reading my post perhaps its not too clear... Issue 1: Basically I want to rename the driver source folder on the server, so for example a folder C:\Source\Drivers\WindowsXPx86\Dell\NIC C:\Source\Drivers\WindowsXPx86\Dell\Mass Storage To C:\Source\Drivers\WindowsXPx86\Dell E6400\NIC I have removed everything from the SCCM console (Drivers and driver packages) but I cannot rename this folder because SCCM is holding open three .cat files... This happened to me before and I had to reboot the server before I could remove the folder...?
Free Windows Admin Tool Kit Click here and download it now
August 5th, 2011 7:24am

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

Other recent topics Other recent topics