I'm hoping someone is able to assist me with this issue. What I am trying to accomplish is to dynamically apply driver packs during imaging without having to associate the driver pack to the task sequence. The reason for this is that the number of supported hardware models ballons the size of the task sequence by having to add the driver packs. I prefer driver packs over "Auto Apply Drivers" since I know exactly which drivers the machine is getting. The idea here is to add the Driver Pack ID to the customsettings.ini file under each hardware model. This would be the package for osddriverclient.exe to use for obtaining the drivers. After the OS is applied and a Driver Pack would normally be applied, I am running the Toolkit job again and then trying to run osddriverclient.exe manually as a run command line action. osddriverclient.exe /install:%OSDApplyDriverDriverPackageID% /unsigned:%OSDAllowUnsignedDriver% The two step prior to this I set the OSDApplyDriverDriverPackageID and OSDAllowUnsignedDriver task sequence variables (for testing...would be set in customsettings.ini once working). The problem is that it is unable to find the SCCM Package on the DP by HTTP which I would understand, but then it also fails to find it by SMB. I thought that SCCM would be smart enought to be able to find where a package is by the UNC share that is already there during imaging. Any tips or tricks on getting this to work is appreciated. Thank you