One last post here as a "symantec employee" before my status is updated. I've actually left for a consulting firm and my profile will be updated accordingly.
We've been so busy working on these issues I've not been out here to participate, but Sally and JLawson both know me well by now. :D
That said, we do know what happened to cause these issues and are actively working on a fix - well, Symantec is actively working on a fix.
For starters, if you go to the Recommended Reading List, you'll see a link there about Driver Injection. It's no longer just DA, and that is the root of Sally's problem.
For JLawson's problem, the trick was that DA runs even if not selected in the Scripted OS Install job, and this time, it WAS DA that changed - that is, it looked at Hard Disks as a critical device instead of non-critical and thus would stop the install process even though the WIM had the drivers.
Soooo, the process is changing. Look for fixes in HF5 of course, and possibly point-fixes.
IF you are striving to use DA and seeing these or simlilar problems, let Support know.
OR
Or you can script around it of course.
I should take the time to point out one weakness of scripting that, frankly, most here wont care about, but that DOES affect some Symantec customers.
ALL of the scripts I've looked at in the past uses UNC drive mapping to accomplish their goals. I do have customers that literally block all UNC mapping because it's a security risk. Symantec, being a security company, has a responsibility to find ways to accomplish goals without drive mappings. They've done this in this product by enabling HTTP/HTTPS communication for packaging and downloading packages.
Brilliant, but limited when it comes to imaging and driver installation.
It's the change to support driver downloads over HTTPS that has caused the issue you're seeing, because DA is designed to work over UNC.
Soooooooo
DS 6.9 has not been changed to use HTTPS and therefore yes, DA works just the same there as it always has and will NOT see these issues.
I hope that clears things up a bit. Yes, the problems still exist, though Sally and JLawson will be getting fixes as quickly as they can off the press. And yes, Symantec will make driver injection work as designed, and yes, people will continue to script around it. But at least you know the facts.
Sorry about my delay at getting out here. :D I'll strive to do better in the future!