Join to domain issue during Operating System Deployment
I'm using ConfigMgr 2007 R2 with SP2 to deploy Windows 7, I notice one issue, machine still in workgroup and also notice that when trying to join to domain, it's not giving any error message, Task Sequence continue installation of CCM agent and restoring user profile. after machine finish I join machine manually with the same user account, then I found user profile is migrated. any one has any suggestionsBest Regards --- Abduljalil Abolzahab Technical Specialist - Microsoft Technical Forum: http://Forum.fourtyfivecorp.net
October 14th, 2010 3:41pm

Unless you are specifically using the Join Domain or Workgroup task which is not used by default, the responsibility for joining a system to the domain during OSD is that of the OS setup. Thus, the TS has no real way of knowing if the domain join failed or succeeded. Thus, to figure out why the OS setup failed to join the system to the domain, you must examine the OS setup log files: http://support.microsoft.com/kb/927521. I think setuperr.log is your best bet, but you may need to check the others also.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2010 4:13pm

as Jason says, plus as a matter of interest are you specifying an OU in the join domain step in the TS ? if it is the COMPUTERS container it will fail as it is not an OU, check the following log c:\windows\debug\netsetup.log to reveal the domain join failure cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady
October 14th, 2010 4:30pm

Thanks all problem solved by adding additional task sequence (Join to domain), I don't know why it didn't work with current one.Best Regards --- Abduljalil Abolzahab Technical Specialist - Microsoft Technical Forum: http://Forum.fourtyfivecorp.net
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2010 8:40am

Although this make work for you, you are just fixing the symptom and not the problem. I would recommend you troubleshoot and resolve the real issue as there are other potential implications.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
October 17th, 2010 9:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics