Hello, Consider the following scenario: ------ You image Win7 Pro computers using WDS and an injected answerfile generated by WSIM. In the "4 specialize" pass you do not specify a computer name so one is generated randomly. Say, COMP1234. In the same pass you have it join the domain contoso.com with specific credentials. The machine COMP1234 is now a part of the domain. Eventually you come to oobe where it asks you for a computer name. You put in "MYPC". You then attempt to login to contoso.com\username. However, when you hit enter you receive the following error message: "The security database on the server does not have a computer account for this workstation trust relationship" ----- I imagine this is because the computer was joined with the name "COMP1234" and you changed it in OOBE to "MYPC". You were not authenticated when this happened so AD no longer recognizes your computer name. I'd like to confirm I'm understanding the situation correctly. A thread linked at the end of this post [1] stated this was expected behaviour and MDT should be used. I'm investigating that now. I'm wondering if this is something Microsoft may be looking at..."changing/fixing" in the next Windows release? Or is MDT the pure answer? I'm also posting for future searchers who come across this issue. Thank you for any feedback! [1] http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/27392d0c-2c54-4e87-abfe-d43e802f4c4f

Windows 7 has updated the security quite a bit. Its better for portables who need to connect to the company servers If you change the computer name, the AD records will not match and logon will fail So leave the machine name alone My MVP is for Windows XP, Vista and Windows 7 IT, and I am getting increasingly good with Visual Studio. Developer | Windows IT | Chess | Economics | Hardcore Games | Vegan Advocate | PC Reviews