I have a scripted install job task for Windows 7 that goes as follows:
- Install WinPE
- Boot to Automation
- Erase Disk
- Partition Disk
- Install w7x64
- Boot to Production
- Join domain
- "Fix users"; a .bat to delete local "Altiris" account and change local "Administrator" password to helpdesk's default password
- Unininstall WinPE
- Install MSIE11
I've got this down to a science; it works perfectly with one exception. On a Dell OptiPlex 390, it stalls on "Boot to Production"--it sits there for an hour, then the job fails. If I go to the PC to see what happened, it's sitting there, powered on, I can log in with username "Altiris" and password "password", and the Symantec Management Agent is connected. In fact, I can use the console to join the domain and perform whatever other tasks/jobs I want to on this PC.
I have, in the past, successfully done scripted installs on 390s start to finish, so I'm pretty sure this is related to a driver that I have put in DeployAnywhere in the time since I last got a 390 to install successfully. The question is...how do I track down the culprit driver?
Thoughts?
Thanks!
