I've got a hardware independent imaging procedure that is setup and working properly on several models of hardware. They complete the automation portion successfully, restart, and then run through the production steps of the job. IBM/Lenovo X60s, however, don't seem to work.
The x60s successfully deploy the image and then begin the other remaining automation jobs (driver and software copy jobs run as .bat files). x60s complete all automation jobs prior to this one (a software copy job) without issue. The very last line of this particular job echoes a complete message to a log file on the server (a procedure all of the other jobs also follow). The log file is updated with the 'Complete' line but the job never finishes. The dAgent session in automation goes to "Session Terminated." The remaining automation jobs are never run.
I checked the MSGS folder on the express share and saw the following for the affected machine:
Sent Message - [06/11/09 10:24:14.729]
Request=WorkToDo
Schedule-ID=100012092
Task-Sequence-ID=10
Execute=.\Temp\5000514.bat
Task-Type=RunScript
OS-Required=Windows
Boot-Env=Automation
Data - 10:51:57.51 - 06/11/2009
Error reading from socket (1316), Error: 10054 (10054 (WSAECONNRESET))
Data - 10:51:57.51 - 06/11/2009
Closing Session Down.
I've tried updating the WinPE image with the most current NIC drivers (Vista versions) for the x60. I'm also in the process of updating the BIOS to see if that helps and am working on testing the .bat job as well (though it is fine on all other models). Sadly this is happening on 4 different x60s and I do not think that it is faulty hardware.
Any thoughts?