Have you checked your domain accounts to ensure that they carried over? Tools --> Options and then choose the Domain Accounts tab. You might double-check that the appropriate account is listed as well as that it is not locked out in the domain.

Yes all that is ok. this is on all of my Deployment Servers now. Besides it uses the same account to do the manual configuration.

And this isn't a sysprep'd or hardware independent image is it? Generally, you wouldn't want it to automatically configure your computer name if that was the case. You would want this to be a separate task.



Error 122 points to a buffer size that is too small (based upon my quick google search).



I have yet to upgrade to SP1 and because I have a hardware independent image that requires the HAL and drivers to be injected, I prevent my systems from automatically configuring directly after imaging. I have another configuration task that runs after the image/sysprep has finished that renames the computer to it's service tag to ensure that I don't have duplicate names on the network.

I have the same problem

And I found out that you have to upgrade the machine agent to the new version to fix the problem. But I have another one using the new agent I'm not able to remote control computer

I've been dealing with this also.  I'm not sure what is up.  I even removed all of those domain accounts, re-added them, and ensured the password was up to date.  It fails after the imaging job, but works fine when doing it manually.