Best practices for removing old driver packages from Configuration Manager if the driver packages are in a live task sequence environment

Question

_{Wednesday, August 3, 2016 1:40 PM}

Good morning,

My company has old driver packages within Configuration Manager that are no longer needed and they need to be removed/deleted.   The old driver packages are currently within task sequences that are part of our live environment.

What is the best practice for removing old driver packages from Configuration Manager if they are part of a live environment task sequence?    Do I need to disable the driver package within the task sequence first; save the changes; remove it from the task sequence; save those changes; and then finally delete or remove the driver package from Configuration Manager?   Or are there other steps involved in removing the driver package from Configuration Manager in this instance?

Thank you for your time.

All replies (4)

_{Tuesday, August 9, 2016 6:46 AM ✅Answered}

Hi,

    IMO, just remove the specific apply drive package steps from your task sequence, and then delete them from console. There's no need do disable the driver package first.

Best regards,

Jimmy 

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, August 9, 2016 7:54 AM ✅Answered}

There one tricky here. If there are drivers, which were first time imported to a driver catalog, which after you import same drivers again for a different model, the first driver unc path will stay. So if you remove driver package and remove sources, and then you desided to update the second driver package which still uses unc from the first driver import, it will fail the content update, since the original source was removed.

I never removed old drivers like this, but this is my theoretical observation :)

_{Tuesday, August 9, 2016 12:55 PM}

Thank you Jimmy,

That is what I was thinking, but wasnt entirely sure.

Thank you for your time and getting back with me.

_{Tuesday, August 9, 2016 1:34 PM}

Thank you Yannara for the information,

Unfortunately we have models that are no longer supported and have been removed within our environment; so those driver packages will need to be deleted to free up space on our servers.   The newer models are pointing to a separate folder on the servers and are also newer versions of the driver.  Mostly the older models being removed are ones that are still under x86.   The ones we are not getting rid of are being migrated to x64 with those drivers being migrated as well; these are only a hand full though.    Everything else is strictly under the x64 architecture.  So we have previously taken your observation into account during our implementing phases and have thought about that as well.    

This does help though.  :)     

Thank you for your time and getting back with me.