OK - there are some weird things in this post.
First, DA doesn't boot the PC to anything. All DA does is scan the system, copy some drivers to the OS drive, and modify the Unattend.XML file. That's it. Rebooting to ... whatever, is handled by the task and agent. VERY important distinction because of troubleshooting the issue.
So, be aware that this is all DA did. It DID modify the Unattend.XML file, and at that point, you may want to see what it did. You have a custom file - see what it added or subtracted.
In the past, what I saw that MIGHT affect this was one of two things:
- DA added another "version" of the same section that was already there, or modified the section already there incorrectly.
- The sections already there may have incorrect architectures specified in them (in the Unattend.XML file) and break when DPInst runs.
Remember, the 3rd part of driver injection (the DA method anyway) is to run DPInst during Mini-Setup. This is not something most people put into their own Unattend.XML file. To do this, DA tries tell the Unattend file to have MiniSetup create a GhostUser admin account, log in as that account so that is has rights, and then run DPInst. All this COULD affect (or be affected by) something you already have in there.
OR DPInsta my itself be failing. The installation logs during MiniSetup can tell you that (capture those back in automation after it fails from the production drive: c:\windows\panther)
Most likely, your problem lies in that area.
ONE other thought. DA is ... interesting and a headache to many out here. Many of us have taken to using DISM for driver injection instead of relying on DA. DISM is nearly 100% reliable on Win7 and above. Really nice once you know how to do it and have it set up correctly. However, it is NOT supported. My point? Maybe for these models you need a different job/method, while Symantec Dev figures out how to fix it. Just saying.