Here is a rundown of whats happening.
Before R2 update, everything was quick. No long download times for software packages, driver packages, boot images etc.
R2 applied, Slow package downloads no matter what it was.
KB2905002 applied, boot imaged updated, clients updated, boot image no longer slow to download, Operating system image no longer slow to download (bout 3 mins 3.5gb) and most software packages are speedy again.
I am still having trouble with the Apply Driver package and the client install during the task.
I ran a test this morning, it took about 45mins to download the hp elite 8300 driver package its 890mb. Then the newly created patched client install for KB2905002 (175mb) takes around 2-3 mins to download. This was NOT an issue before R2.
After the client has installed, and machine rebooted, most packages are speedy again.
Office 2013 (700mb) about 1 min, Windows live Essentials (131mb) less than 30 sec.
BUT then some packages are slow such as
Google Earth (187mb) 4 min, Adobe CS5 (10gb) 30 mins
I have looked through the smsts.log on the local machine during WINPE stage and have found nothing that stands out as an issue.
You can check logs here: http://sdrv.ms/1eJDscR
As for using driver package vs auto apply, I would rather use a driver package. Personal choice.
Driver packages are just WMI query to apply to correct model computer ( SELECT * FROM Win32_ComputerSystem WHERE Model LIKE '%HP Compaq Elite 8300 SFF%' ).
Packages are all coming from right DP for the boundary set.
I am thinking for a test, to delete the HP Compaq Elite 8300 driver package from the DP and re-create.
Also note, its not just this driver package, its any of them.