No matter how I set the auto join domain parameters in unattend.xml, after I sysprep the base machine and boot up, it just don't join to the domain. In the end I conclude that only MDT or SCCM or WDS services can activate the autojoin domain function of sysprep, is that true? I finally solve the auto join problem using a vbs script as a post sysprep script which runs after the auto one time log in of administrator. Ideas ? Comments? Thank you

Sysprep doesn't join the domain, Windows setup/mini-setup joins the domain. You can use unattend.txt/sysprep.inf in XP or unattend.xml in Vista/7 to tell setup and mini-setup to join the domain for you, but the actual work of joining the domain is not performed by sysprep. This process has nothing to do with MDT or ConfigMgr though and is a function of Windows setup.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Wow, that's a fast response, thanks Jason. Totally agree with you that sysprep doesn't join the domain, let me re-phrase it. Back to the good old XP days, yes, using the sysprep.inf with the mini-setup ticked, auto join domain is easily done. However for windows 7, we are supposed to use the imaging tool to create the autounattend.xml file, and I couldn't find anywhere to specify the similar mini-setup interrface. Also one other problem (or feature, may be), even with the sysprep, we are forced to create a new local user at the first start up after sysprep, and I need to use a post script, again, to remvoe this account. Wonderring is there anyway not to do it? Thanks

unattend.xml can be created by hand or through the use of SIM; either way it's just xml. If you are using OSD or MDT, all they do is update unattend.xml for you. There are definitely options in SIM also: http://www.windows-noob.com/forums/index.php?/topic/578-how-can-i-join-a-domain-using-windows-sim/. I totally don't follow your second issue. Why are you creating an account after sysprep?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I did exactly what was described in the post, and somehow it does not work. As for the second point, I use the sysprep /generalize /oobe /shutdown command to do sysprep, so after the process finish, the system will shutdown. Then once I onback the system, at the stage of input computer name, it will ask for a new user name as well, same as the windows 7 installation process. My question is can we skip that? i.e, supply a computer name without supplying a user name, as we have already prepared the needed local account.

What edition of Windows are you using? Have you checked the Windows setup logs? http://technet.microsoft.com/en-us/library/dd744583(WS.10).aspx. If the system successfully joins the domain, you won't have any of this. Are you you using ConfigMgr at all? Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi, would be interested to know if you resolved your issue with windows 7 sysprep and auto joining to the domain, along with that stupid setup screen to create a local account! Think the deployment tools for windows 7 are a step back in some ways for corporations trying to make a Corp image! Almost given up trying with sysprep, mini setup etc! But don't want to have to script the whole thiing once logged on!

I had to resort to using WDS on our domain and a custom sysprepdomain.xml using pxe. What happens is that when you create an reference os .wim and you boot into a PE environment build from WDS, it will ask for domain credentials. Once that is defined the installation works fine and it joins to the domain. The problem doing it as a customized sysprep is that even tho you can put in the credentials for the domain administration, the proceedure will join to the domain, but for some reason will not create a machine token in the AD OU you choose to initially put the machines into. Dell is aware of this problem and seem to have a powerscript that they use as a run command during the sysprep stage but I have not seen it. I like the WDS, and the interaction with the Deployment Workbench. However, I do have a second issue. It seems only my account as a domain admin works. I have given domain group permissions in various shares and the ability to add computers and users to the domain, but it doesn't work very well. If there are any answers to that I'd appreciate it. -B

I got the default user creation to stop by putting windows-shell-setup and setting the oobe part to skip user oobe to true and it skips the user creating a local account and then you can enable the local admin account for temporary purposes.

In OSD TS, domain join is succsessful by entering domain parametrs in step settings. In MDT TS, even I set same settings, machine is always a workgroup memeber. I have to look into unattended.xml, but just wondering why step settings is not enough?