afran1488
commented
3 years ago Bump on this. I also like the Driver Package over the Standard Package and would like to see faster performance. I thought it was my environment. SCCM is not installed on the C drive, so I put the DAT on the same drive as Config Manager, shortened the paths and I'm still seeing 2 models done in about 3 hours. I know I have some .trn file fixing to do too cause at some point the tool hangs and I have to start all over. So I only do 2 or 3 models at a time now to prevent the app from crashing. Great tool and appreciate the work behind it.
This was touched on in a 2017 Q&A post on the Technet Gallery but not addressed as far as I can tell. Is there any alternative to the way DAT adds drivers into SCCM driver packages? Currently, it seems to create a driver package then add each driver one at a time, creating a new revision of the package each time. This is quite slow and a relatively small HP driver pack takes ~45 minutes to add the drivers.
The revision thing can be seen by simply checking the revision number after DAT has finished creating a driver package. Without me touching it, the HP ProBook 640 G5 package shows revision 58. When adding drivers to a package in the SCCM console, drivers are all added in one go, is this somehow possible in PowerShell?
I saw the "Standard Package" workaround mentioned on Technet but I do prefer to stick with Driver Packages.
Other than that, this is a fantastic tool which you should be extremely proud of, thank you.