Just to confirm, yes the operating system is joined to the Active Directory during the specialize phase <http://technet.microsoft.com/en-us/library/dd744341(v=ws.10).aspx> of Windows Setup. I think the mini-setup term was abandoned with XP. Vista and later use the new "setup phases" model. But other than that, yes, Todd is right. :)
To verify the domain join process, check out %windir%\debug\netsetup.log. Cheers, Trevor Sullivan Microsoft PowerShell MVP From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, June 5, 2014 9:38 AM To: [email protected] Subject: [MDT-OSD] RE: What TS step joins the domain? I definitely feel its driver related, but not much I can do until Lenovo gets me a fix. It also only happens on Win7, not Win8. If I wait 5 minutes or so, then join the domain manually I get an IP and it works. Thanks Todd. Daniel Ratliff From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, June 05, 2014 10:27 AM To: [email protected] <mailto:[email protected]> Subject: [MDT-OSD] RE: What TS step joins the domain? This is a guess, but an educated one. The computer is joined to the domain during the "Setup Windows and ConfigMgr" step. The machine should be joined to the domain during the mini-setup phase that runs to finish the installation of Windows. The process is driven by the Unattend.xml file that is in your CustomSettings package. All the steps up to that point are preparing the computer and unattend.xml to proceed with the regular Windows mini-setup. Once mini-setup is complete, there are commands in there that start up the Task Sequence again. It is like the process is out of the hands of ConfigMgr for a little while at this time while the normal Windows minisetup process runs. I am not sure there is a way to add a delay into the process, but if there was, I am pretty confident that it would need to be done by editing the unattend.xml file in some way. There is a possibility too that you might be able to edit the registry in the master image to force a "wait additional time for the network" delay in some way. I know in group policy there is a possibility to introduce an additional wait for the network that is required on some nets where DHCP is delayed in receiving an IP. The delay is there to make sure GPOs apply on networks with this problem. It might be coming into play here too. It is surprising to me that windows wouldn't automatically wait for the network. It "feels" like a driver problem where it is signaling Windows that the network is ready before it really is. I would rate my confidence in this answer at 80% or so. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, June 05, 2014 8:33 AM To: [email protected] <mailto:[email protected]> Subject: [MDT-OSD] What TS step joins the domain? http://social.technet.microsoft.com/Forums/en-US/260cb3a4-65ee-4adb-b04a-b11 d14fd8fff/not-joining-domain-during-osd?forum=configmanagerosd I am working on the issue above (Lenovo Yoga not joining domain because USB NIC doesn't initialize in time). I would like to test adding a delay before it attempts to join the domain. What step does the task sequence actually join the domain? Apply Network Settings? The reason I question it is because all my Apply Driver steps are after that step, so if the NIC driver hasn't been applied how does it join the domain? Does Apply Network Settings just set the configuration and the Setup Windows and ConfigMgr step actually join the domain? Thanks! Daniel Ratliff The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. _____ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. _____ The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
