When adding or updating multiple drivers for SCCM the "Driver Automaton temp" folder cleanup is very last step which can lead to the "Driver Automaton temp" drive running out of space. After each driver is processed there are 3 copies of the driver package (initial driver package, the uncompressed driver package and the MDM compressed driver package) filling the drive even after it has been added to SCCM. So if you are adding or updating drivers for 5+ models it can take a lot of disk space.
Would it be possible to run the cleanup step after each driver has been processed? Or if that isn't possible, minimise the disk usage by deleting the initial drive package and the uncompressed driver package before moving on to the next driver.
m08e
commented
1 year ago
When adding or updating multiple drivers for SCCM the "Driver Automaton temp" folder cleanup is very last step which can lead to the "Driver Automaton temp" drive running out of space. After each driver is processed there are 3 copies of the driver package (initial driver package, the uncompressed driver package and the MDM compressed driver package) filling the drive even after it has been added to SCCM. So if you are adding or updating drivers for 5+ models it can take a lot of disk space.
Would it be possible to run the cleanup step after each driver has been processed? Or if that isn't possible, minimise the disk usage by deleting the initial drive package and the uncompressed driver package before moving on to the next driver.