I have built couple of Windows 7 enterprise images recently and SCCM task sequence is failing to add them to domain using "Apply Network Settings" task. Few things I have made sure: - Same TS if I change the image to an old one, domain join works. So it might not be related to network drivers. Old image does not have NIC drivers embedded. - No errors in Sysprep log. - DsGetDcName failed: 0x54b error in UnattendGB\setupact.log - I have rebuilt the image almost four times on two types of VM's. All failed. - Our new images are mostly similar to our old ones. Created them to refresh updates, software etc. Added couple of local GP scripts. Thats all. Anything else to troubleshoot? Thanks for reading.

Look in netsetup.log on the client, you find the log file in \Windows\Debug.

Hi, have you seen this threads already? http://blogs.technet.com/b/configurationmgr/archive/2008/11/18/configmgr-2007-pc-does-not-join-the-domain-if-the-computers-container-is-specified-as-the-domain-ou.aspx It mentions: If you want the PC to join the Domain as part of a Domain OU, change the Domain OU field to specify a valid OU and not the Computers container. http://social.technet.microsoft.com/Forums/zh/configmgrosd/thread/0e0eda03-b665-43e0-a265-5873053a5343 It mentions: Have a look at both SMSTS.log + Netsetup.log. and also verify in your task sequence that you havn't specified the Computers container as the target OUMy blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn

I have looked at all previous relevant threads on these forums. I am placing OSD systems in a custom OU and the permissions are fine. I have mentioned in my first point that if I change the image to an old one everything works fine on the same TS. So I believe it more related to the image itself. BTW there is no netsetup.log file. I am using the "Apply Network Settings" step to join it to the domain. Update: I have built a new Win7 enterprise with nothing but a few hotfixes and patches and the domain join works perfectly with the same task sequence. I will try to do this in stages to narrow down the problem.

just a FYI - The netsetup.log is located in "C:\Windows\debug". I have actually run into this recently, have not resolved it either, but the task sequence would not name the device what I tell it using OSDComputerName variable. It would name it something else completely random, not even using its normal standard of MININT-######.