Im having some problems getting a new Windows 7 image to join the domain in its task sequence, the model of machine is a Dell Optiplex 780. Checking the smsts.log file I can see the error 'No adapters found in environment. Performing global configuration only.' which I cant seem to resolve. I have added the drivers from the Dell WinPE cab into my boot image and its still causing the same message, is there any other log I can look at to understand exactly what is causing the driver not to work?

Csteels, It sounds like you task sequence is working but not applying the nic driver? In your task sequence are you applying drivers or a driver package? if device drivers what is your setting? is it to look at certain categories? is it set to only apply the best driver or all compatible drivers?Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler

Hi, is the right network driver added in the Task Sequence, and is this step used before adding the device to the domain? Also try to remove the domain OU in the Task Sequence (apply network settings). This cannot be set to the Computers container. If this is not working, try to post more information (errors) from the smsts.logMy ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Hi Henk/Tom and thanks both for such fast replies. I have left the OU blank so it joins the Computers container by itself, I learned that one the hard way before! For drivers I have added the drivers here to my x86 boot image - http://www.delltechcenter.com/page/WinPE+3.0+Driver+CAB And I apply a driver package (this package http://www.delltechcenter.com/page/Windows+7+Desktop+Combo+Driver+Cab) as part of the task sequence which does seem to work, every device when I log into the OS afterwards is running the correct driver and I can then manually join the machine to the domain which led me to the conclusion that the Apply Network Settings task is using the WinPE drivers, or in this case not! Im slightly puzzled why Im hitting a brick wall, also during the build the Apply System Settings section seems to take a very very long time in case that is a clue to what is going on? Henk, which part of the smsts.log would be most helpful to post?

Try moving the apply driver package above the task squences "apply windows settings" and " apply network settings" so that the driver is installed before attempting to join the domain. See if they helps since you said the driver is being applied in device manager.Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler

Hi, the Apply Network Settings task are not using the WinPE drivers, but the drivers added in the driver package. When distributing a Windows image (WIM file), put the auto-apply drivers or driver package step directly after the "Apply Operating System" step. This way drivers (so also NIC drivers) will be available during domain join. You can also try to choose another OU for domain join (apply network settings), or check the account/password which is used for domain join! Try to post the smsts.log around the "No adapters found in environment" message. Are there any other errors yet?My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Thanks Tom, I will try that when in tomorrow morning and report back. Do you think that the NIC driver ultimately being installed in the OS will be picked up and used for the join domain task at that stage? Out of curiousity I enabled F8 in WinPE and can confirm that it is picking up a dhcp assigned address at that stage so the NIC seems to work in PE, and also be installed correctly when the image has completed applying. Very puzzled!

Double check you credentials to join the domain as mentioned by Henk. Are you adding the computer to a folder "computers" or to an OU? here is where the smsts log could reside depending on what stage of the installation you are at. http://sccmguy.com/2011/03/29/where-is-the-smsts-log-located/ Try the process we mentioned and see if that helps any. The SMSTS.log will also help us detemine what is happening when you image. Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler

Cheers guys Im staying late to try a couple of things, first Im moving the Apply Driver package immediate after the Apply OS task and will rebuild my usb drive to test deploy again. Tom, Ive left the OU blank and am using a domain admin account to join the domain. Although if this one fails I will re-enter the credentials and try again just to double check Ive not made any mistake entering the password, hopefully it wont come to that as the smsts.log does seem to point towards driver related issues.

Check the Net Setup.log in C:\Windows\Debug\ on a target machine for any errors. Th actual domain join (unless you are using a Join Domain or Workgroup task) is the responsibility of WIndows setup.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

When creating a new Task Sequence to deploy an existing image, the drivers step will be placed after the Apply Windows/Network Settings step. This is not an logical place, because the drivers (NIC) drivers are needed during domain join. So move the drivers step directly after the "Apply Operating System" step will resolve this.My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

After running the task sequence with the Apply Driver Pack immediately before Apply Windows Settings with Apply Network Settings next it seems to have made no difference to the problem. Looking into the Net Setup.log file there is no activity in there other that when I had joined and removed the domain whilst prepping the image a few days ago. In smsts.log the section still showing the No adapters found in environment is here, please let me know if any more of it is needed to help - ==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Command line: "osdnetsettings.exe" configure OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Setting %SystemRoot% to "D:\Windows" OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Loading existing answer file "D:\Windows\panther\unattend\unattend.xml" OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Configuring global network settings OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Join type: 0 OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Joining domain: CARTERJONAS OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "x86" OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) DNS domain: OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) DNS domain search order: OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) IP filter sec enabled: false OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) No adapters found in environment. Performing global configuration only. OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Writing configuration information to D:\Windows\panther\unattend\unattend.xml OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Successfully saved configuration information to D:\Windows\panther\unattend\unattend.xml OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) OSDNetSettings finished: 0x00000000 OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Process completed with exit code 0 TSManager 08/04/2011 09:27:44 1836 (0x072C) !--------------------------------------------------------------------------------------------! TSManager 08/04/2011 09:27:44 1836 (0x072C) What Im confused about most is that in WinPE I can F8 and see that the adapter has got an IP address, and once the image is applied the NIC is in device manager... But somewhere in between it isnt available?

Thanks Henk, that does make perfect sense but doesnt seem to have made a difference to the task sequence running the join domain task. I posted some more info above, apologies for posting out of sequence!

Hi, maybe this wil help: http://www.windows-noob.com/forums/index.php?/topic/2948-unattended-join/ Is this the case? "I was using an image that I sysprep'd but I did not choose the generalize option"My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

If I have Im not aware of having done so... I captured the wim image of the reference machine using a capture media I had created using the boot image if that helps at all... Do I need to have done anything prior to capturing other than putting the machine into a workgroup, and making the local admin account active and with a blank password?

Sorry for the length of this log section, Ive gone further up to the tasks preceding Apply Network settings in the hope it shows what is happening. ============================[ OSDDriverClient.exe ]============================ OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Command line: "osddriverclient.exe" /install:P0100090 /unsigned:false OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Driver path is D:\_SMSTaskSequence\drivers OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Applying driver package "P0100090". OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Found the location for the package _SMSTSP0100090. The location is on file:VOL001:\SMS\PKG\P0100090 OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Searching C:\ for Fullmedia content OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Searching D:\ for Fullmedia content OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Searching E:\ for Fullmedia content OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Searching F:\ for Fullmedia content OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Found Fullmedia content in drive F:\. OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\audio" to Windows driver store. OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\audio" to the Windows driver store. OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\chipset" to Windows driver store. OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:25:35 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\chipset" to the Windows driver store. OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\communication" to Windows driver store. OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:25:56 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\communication" to the Windows driver store. OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\controlpoint" to Windows driver store. OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:00 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\controlpoint" to the Windows driver store. OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\input" to Windows driver store. OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:04 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\input" to the Windows driver store. OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\network" to Windows driver store. OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:07 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\network" to the Windows driver store. OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\security" to Windows driver store. OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:44 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\security" to the Windows driver store. OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\storage" to Windows driver store. OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:47 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\storage" to the Windows driver store. OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Adding "F:\SMS\PKG\P0100090\video" to Windows driver store. OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Setting %SystemRoot% to "D:\Windows" OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86" OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Added list item with key value '1' OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Writing configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Successfully saved configuration information to D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Setting temporary directory to 'D:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Command line for extension .exe is "%1" %* OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Set command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Executing command line: "X:\windows\Pkgmgr\dism.exe" /image:"D:" /windir:"Windows" /apply-unattend:"D:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"D:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 08/04/2011 09:26:50 1064 (0x0428) Process completed with exit code 0 OSDDriverClient 08/04/2011 09:27:43 1064 (0x0428) Dism successfully added drivers to the offline driver store. OSDDriverClient 08/04/2011 09:27:43 1064 (0x0428) Successfully added "F:\SMS\PKG\P0100090\video" to the Windows driver store. OSDDriverClient 08/04/2011 09:27:43 1064 (0x0428) Successfully applied driver package "P0100090". OSDDriverClient 08/04/2011 09:27:43 1064 (0x0428) Entering ReleaseSource() for F:\SMS\PKG\P0100090 OSDDriverClient 08/04/2011 09:27:43 1064 (0x0428) The user tries to release a source directory F:\SMS\PKG\P0100090 that is either already released or we have not connected to it OSDDriverClient 08/04/2011 09:27:43 1064 (0x0428) Exiting with return code 0x00000000 OSDDriverClient 08/04/2011 09:27:43 1064 (0x0428) Process completed with exit code 0 TSManager 08/04/2011 09:27:43 1836 (0x072C) !--------------------------------------------------------------------------------------------! TSManager 08/04/2011 09:27:43 1836 (0x072C) Successfully complete the action (Apply 745-780 Win7 x86 Driver Pack) with the exit win32 code 0 TSManager 08/04/2011 09:27:43 1836 (0x072C) Sending status message . . . TSManager 08/04/2011 09:27:43 1836 (0x072C) Do not send status message in full media case TSManager 08/04/2011 09:27:43 1836 (0x072C) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 08/04/2011 09:27:43 1836 (0x072C) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 08/04/2011 09:27:43 1836 (0x072C) Expand a string: %_SMSTSMDataPath%\Logs TSManager 08/04/2011 09:27:43 1836 (0x072C) Clear local default environment TSManager 08/04/2011 09:27:43 1836 (0x072C) Updated security on object D:\_SMSTaskSequence. TSManager 08/04/2011 09:27:43 1836 (0x072C) Set a global environment variable _SMSTSNextInstructionPointer=11 TSManager 08/04/2011 09:27:43 1836 (0x072C) Set a TS execution environment variable _SMSTSNextInstructionPointer=11 TSManager 08/04/2011 09:27:43 1836 (0x072C) Set a global environment variable _SMSTSInstructionStackString=9 TSManager 08/04/2011 09:27:43 1836 (0x072C) Set a TS execution environment variable _SMSTSInstructionStackString=9 TSManager 08/04/2011 09:27:43 1836 (0x072C) Save the current environment block TSManager 08/04/2011 09:27:43 1836 (0x072C) Successfully save execution state and environment to local hard disk TSManager 08/04/2011 09:27:44 1836 (0x072C) Start executing an instruciton. Instruction name: Apply Windows Settings. Instruction pointer: 11 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSCurrentActionName=Apply Windows Settings TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSNextInstructionPointer=11 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDLocalAdminPassword TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDComputerName TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDProductKey TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDRandomAdminPassword TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDRegisteredOrgName TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDRegisteredUserName TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDServerLicenseConnectionLimit TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDTimeZone TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 08/04/2011 09:27:44 1836 (0x072C) Expand a string: osdwinsettings.exe /config TSManager 08/04/2011 09:27:44 1836 (0x072C) Expand a string: TSManager 08/04/2011 09:27:44 1836 (0x072C) Command line for extension .exe is "%1" %* TSManager 08/04/2011 09:27:44 1836 (0x072C) Set command line: osdwinsettings.exe /config TSManager 08/04/2011 09:27:44 1836 (0x072C) Start executing the command line: osdwinsettings.exe /config TSManager 08/04/2011 09:27:44 1836 (0x072C) !--------------------------------------------------------------------------------------------! TSManager 08/04/2011 09:27:44 1836 (0x072C) Expand a string: WinPE TSManager 08/04/2011 09:27:44 1836 (0x072C) Executing command line: osdwinsettings.exe /config TSManager 08/04/2011 09:27:44 1836 (0x072C) ============================[ OSDWinSettings.exe ]============================ OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Command line: "osdwinsettings.exe" /config OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Setting %SystemRoot% to "D:\Windows" OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Loading existing answer file "D:\Windows\panther\unattend\unattend.xml" OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Computer Name: win7new OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "x86" OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Registered Owner: Carter Jonas OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Getting namespace "Microsoft-Windows-Shell-Setup" for architecture "x86" OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Registered Organization: Carter Jonas OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Time Zone: GMT Standard Time OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Time zone: GMT Standard Time OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) The OSDProductKey variable is not set in the environment. Not setting the product key in the unattend answer file. OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Setting local admin password. OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Writing configuration information to D:\Windows\panther\unattend\unattend.xml OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Successfully saved configuration information to D:\Windows\panther\unattend\unattend.xml OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Exiting with return code 0x00000000 OSDWinSettings 08/04/2011 09:27:44 1580 (0x062C) Process completed with exit code 0 TSManager 08/04/2011 09:27:44 1836 (0x072C) !--------------------------------------------------------------------------------------------! TSManager 08/04/2011 09:27:44 1836 (0x072C) Successfully complete the action (Apply Windows Settings) with the exit win32 code 0 TSManager 08/04/2011 09:27:44 1836 (0x072C) Sending status message . . . TSManager 08/04/2011 09:27:44 1836 (0x072C) Do not send status message in full media case TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 08/04/2011 09:27:44 1836 (0x072C) Expand a string: %_SMSTSMDataPath%\Logs TSManager 08/04/2011 09:27:44 1836 (0x072C) Clear local default environment TSManager 08/04/2011 09:27:44 1836 (0x072C) Updated security on object D:\_SMSTaskSequence. TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSNextInstructionPointer=12 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a TS execution environment variable _SMSTSNextInstructionPointer=12 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSInstructionStackString=9 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a TS execution environment variable _SMSTSInstructionStackString=9 TSManager 08/04/2011 09:27:44 1836 (0x072C) Save the current environment block TSManager 08/04/2011 09:27:44 1836 (0x072C) Successfully save execution state and environment to local hard disk TSManager 08/04/2011 09:27:44 1836 (0x072C) Start executing an instruciton. Instruction name: Apply Network Settings. Instruction pointer: 12 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSCurrentActionName=Apply Network Settings TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSNextInstructionPointer=12 TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDDomainName TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDJoinPassword TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDJoinAccount TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a local default variable OSDNetworkJoinType TSManager 08/04/2011 09:27:44 1836 (0x072C) Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 08/04/2011 09:27:44 1836 (0x072C) Expand a string: osdnetsettings.exe configure TSManager 08/04/2011 09:27:44 1836 (0x072C) Expand a string: TSManager 08/04/2011 09:27:44 1836 (0x072C) Command line for extension .exe is "%1" %* TSManager 08/04/2011 09:27:44 1836 (0x072C) Set command line: osdnetsettings.exe configure TSManager 08/04/2011 09:27:44 1836 (0x072C) Start executing the command line: osdnetsettings.exe configure TSManager 08/04/2011 09:27:44 1836 (0x072C) !--------------------------------------------------------------------------------------------! TSManager 08/04/2011 09:27:44 1836 (0x072C) Expand a string: WinPEandFullOS TSManager 08/04/2011 09:27:44 1836 (0x072C) Executing command line: osdnetsettings.exe configure TSManager 08/04/2011 09:27:44 1836 (0x072C) ==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Command line: "osdnetsettings.exe" configure OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Setting %SystemRoot% to "D:\Windows" OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Loading existing answer file "D:\Windows\panther\unattend\unattend.xml" OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Configuring global network settings OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Join type: 0 OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Joining domain: OURDOMAINNAME OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "x86" OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) DNS domain: OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) DNS domain search order: OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) IP filter sec enabled: false OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) No adapters found in environment. Performing global configuration only. OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Writing configuration information to D:\Windows\panther\unattend\unattend.xml OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Successfully saved configuration information to D:\Windows\panther\unattend\unattend.xml OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) OSDNetSettings finished: 0x00000000 OSDNetSettings 08/04/2011 09:27:44 2020 (0x07E4) Process completed with exit code 0 TSManager 08/04/2011 09:27:44 1836 (0x072C) !--------------------------------------------------------------------------------------------! TSManager 08/04/2011 09:27:44 1836 (0x072C) Successfully complete the action (Apply Network Settings) with the exit win32 code 0 TSManager 08/04/2011 09:27:44 1836 (0x072C)

Not much to see in the smsts.log file. Which information is seen in D:\Windows\panther\unattend\unattend.xml on the target machine? Is the information displayed right there? (domain/OU information, account/password for domain join) Can you also check the netsetup.log (%SystemRoot%\debug) and setupact.log (C:\$Windows.~BT\Sources\Panther) on the target machine for errors? Have you tried already to choose another OU for domain join (apply network settings)?My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Have you checked the Windows 7 setup logs as I suggested? Like I said, joining the domain is the responsibility of Windows setup, not the task sequence. Specifically c:\WIndows\Debug\netsetup.log and possibly setact.log (http://technet.microsoft.com/en-us/library/dd744583(WS.10).aspx) to verify your assumption that drivers are not being loaded?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Henk I cant see an unattend.xml file on the c: drive post task sequence, I think during the task sequence there is a c: and d: drive which is the 100mb system reserved partition and then the rest of the drive is d:, which then becomes C: once the image is applied. Does the file only exist whilst its running through the task sequence? The netsetup.log isnt being touched at all, the datestamp is from the day I was preparing the image and only has the entries from when I had joined to the domain and removed it as part of the reference image build. What I was curious about in smsts.log was this entry - Command line: "osddriverclient.exe" /install:P0100090 /unsigned:false OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Does that mean if the driver is unsigned it wont be able to use it? Im unsure but though Id ask as Im so confused that I have a working NIC in WinPE and the OS after the task sequence completes but not at the inbetween part when it tries to join the domain. Jason, I've checked the setupact.log file and found the following - 2011-04-08 09:32:09, Info [DJOIN.EXE] Unattended Join: Joining domain [CARTERJONAS]... 2011-04-08 09:32:09, Info [DJOIN.EXE] Unattended Join: Calling DsGetDcName for CARTERJONAS... 2011-04-08 09:32:24, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:32:44, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:33:04, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:33:24, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:33:44, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:34:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:34:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:34:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:35:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:35:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:35:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:36:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:36:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:36:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:37:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:37:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:37:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:38:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:38:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:38:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:39:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:39:10, Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355] 2011-04-08 09:39:10, Error [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b 2011-04-08 09:39:10, Info [DJOIN.EXE] Unattended Join: Exit, returning 0x0

Henk I cant see an unattend.xml file on the c: drive post task sequence, I think during the task sequence there is a c: and d: drive which is the 100mb system reserved partition and then the rest of the drive is d:, which then becomes C: once the image is applied. Does the file only exist whilst its running through the task sequence? The netsetup.log isnt being touched at all, the datestamp is from the day I was preparing the image and only has the entries from when I had joined to the domain and removed it as part of the reference image build. What I was curious about in smsts.log was this entry - Command line: "osddriverclient.exe" /install:P0100090 /unsigned:false OSDDriverClient 08/04/2011 09:25:29 1064 (0x0428) Does that mean if the drive is unsigned it wont be able to use it? Im unsure but though Id ask as Im so confused that I have a working NIC in WinPE and the OS after the task sequence completes but not at the inbetween part when it tries to join the domain. Jason, I've checked the setupact.log file and found the following - 2011-04-08 09:32:09, Info [DJOIN.EXE] Unattended Join: Joining domain [CARTERJONAS]... 2011-04-08 09:32:09, Info [DJOIN.EXE] Unattended Join: Calling DsGetDcName for CARTERJONAS... 2011-04-08 09:32:24, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:32:44, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:33:04, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:33:24, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:33:44, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:34:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:34:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:34:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:35:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:35:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:35:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:36:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:36:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:36:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:37:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:37:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:37:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:38:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:38:25, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:38:45, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:39:05, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... 2011-04-08 09:39:10, Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355] 2011-04-08 09:39:10, Error [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b 2011-04-08 09:39:10, Info [DJOIN.EXE] Unattended Join: Exit, returning 0x0

So now you/we definitively know that's it's either a name resolution or connectivity issue. This could still be caused by lack of NIC driver. During Windows setup, you can push Shift-F10 to get a command-prompt and test (don't do this till after the domain join phase though). Also note, drivers in WinPE have nothing to do with driver injection into the OS being deployed; they are not transfered in any way. After the TS finishes (successful or not) can you in and do you then have connectivity?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi, I found this article regarding your setupact.log: http://networkadminkb.com/kb/Knowledge%20Base/Windows2008/How%20to%20troubleshoot%20sysprep%20issues%20when%20joining%20a%20domain.aspx [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355] [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b Error 1355: The specified domain either does not exist or could not be contacted. Typically this error signifies network, DNS, or WINS issues.

I tried to get into the Shift-F10 command prompt during the black windows 7 setup screens with no joy. The only one I can get into is the F8 one in the WinPE area where when I run ipconfig I have one adapter with a dhcp assigned address/dns/domain name which looks to be good. I have checked the winpe drivers I have in the boot image and all are signed as I though it may be something there possibly. Michael I had just read somethign similar a few minutes ago, Im using a Getcomputername task to name the machine and they had suggested to get round a similar issue they entered the name as the FQDN instead of just a flat name which Im now trying. Im still puzzled why my netsetup.log isnt being updated at all and is still the same as when I put the reference image together, which my first though on is that its just not seeing a network adapter at all. Even more baffling as I can see it in Winpe and Win7 once the image is applied. Will report back on the results of trying the FQDN shortly!

No luck with that and the task sequence actually errored when I tried that, although now as it had no computer name variable its stalled at the Windows Setup part prompting for a name. I can get into the Shift-F10 command prompt at that point and see that the Local Area Connection has a 169.254 ip address not a dhcp assigned one. Also there are 2 other adapters named Tunnel Adapter isatap.domainname and Tunnel Adapter Local Area Connection* 11 When I open device manager from compmgmt.msc I can see all of the devices have drivers, including the network adapter. When I try to run ipconfig /renew at the command prompt I get the message - An error occurred while renewing interface Local Area Connection : The RPC server is unavailable. An error occurred while releasing interface Loopback Pseudo-Interface 1 : The system cannot find the file specified.

Do you have STP portfast enabled on your switch port(s)?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi Jason we dont have STP portfast on as far as I know, the switches for the mostpart are gigabit speed 3com devices so not even sure theyre that advanced. Im home now for the weekend but will be back on this first thing Monday morning, although not sure where to head with it as I cant understand why no network connectivity when the device and driver were showing correctly and even at that stage of getting the 169.254 address had a status of working correctly in device manager...

Can't say for sure in your case, but it commonly happens because the switch is going through its STP calculations to ensure there are no loops in the network. During the STP phases, the port is disabled; this often takes longer than the OS start up time so the OS cannot aquire a DHCP address as the port is diabled. Setting portfast tells the swicth that the port is connected to a single endpoint and thus does not need to be considered for a loop in the network and nearly eliminates the delay in enabling the port thus enabling the OS to aquire an IP address from DHCP. You don't normally see this in Windows because Windows compensates for this behavior by retrying the DHCP request; WinPE does not.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Ive used the same WinPE boot.wim to apply a task sequence that applies an XP image, would knowing it worked to deploy the old image rule out the potential STP issue as that did join the domain successfully?

That's a little different though. WIndows XP setup did not use WinPE, it used a custom mini-OS. Win 7 uses WinPE. Note this has nothing to do with your boot image. Once Windows setup is running, it is in its own WinPE instance (for Win 7, for XP its the blue-screen setup OS) completely different than your boot image. The Windows XP setup mini-OS is probably slower than WinPE at requesting the DHCP address or just waits till somewhere further where the port is available. Like I said, I can't be 100% sure on this for your enivronment, but I have seen it happen before multiple times and have seen many reports of it also. And, really, why else would you be getting the APIPA address unless the network were not available? You wouldn't get an address at all (not even the APIPA one) if the drivers weren't loaded and the OS didn't see the NIC. That moves the culprit to the networking layer.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Thanks Jason, I'll be able to pick this up Monday and try to get it cracked as Im under pressure to roll Windows 7 into an office for testing as soon as I can manage to! On a side note, I recall somebody having issues when Vista first came out with the capture/deploy working with this same sccm server but I dont remember how they left the server, all I know is they did give up with using Vista and decided to stick with XP. I can see on the MS download site there is WAIK 3.0 and a Win7 SP1 supplemental install, checking our server its showing WAIK being 2.0?! The boot.wim image version in sccm is showing as 6.1.7600.16385 (when it loads it has the 7 style splash screen so assuming its correct) Should I go ahead with getting WAIK up to date and run the supplement through for SP1 as thats what I am using in my image before I do anything else?

6.1.7600.16385 is definitely the the WinPE version corresponding to Win 7. Your WAIK should be at 3.0 though; if it is listed as 2.0 in Programs then you should uninstall it and install 3.0. There is no real need to upgrade to 3.1 unless you are facing a couple of very specific challenges like 801.2x: http://blogs.technet.com/b/mniehaus/archive/2011/02/17/windows-aik-for-windows-7-sp1-released.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Thanks Jason It is showing as version 2.0 so Im going to uninstall that and get up to the latest one, also for peace of mind Im going to import the new boot image myself so I am certain it is the latest and correct image (and also to be sure it is the deployment one and not the one from the Windows 7 install dvd, which at the moment I cant be 100% about as the image I mentioned before looks to have been a manually imported one by somebody in the past)

Still getting exactly the same problems. Would it be of benefit to post somewhere the full setupact.log and smsts.log? Also is it worth going to Microsoft support with this to see if they can help, as Im at my wits end and cant think of anything else to try?

The issue was and is related to network connectivty though. Have you reviewed the STP configuraiton of the switch port?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

I couldnt figure out if was enabled for the port on the 3com switch Im using but did find the way to set the ports up. I disabled STP on the port I have connected my machine directly to and again it didnt make any difference, do I need to also disable it on the port that the dhcp server is connected to?

Im just trying again with STP disabled across all ports on both switches connected to the subnet Im working on

Thats still doing the same with STP disabled. I also ran the task sequence with the apply network settings at the very end which made no difference. Im all out of ideas now and seem to be just trying anything in the hope it will change something so going to see if Microsoft support can help pinpoint what is (or in this case isnt) going on.

Thats still doing the same with STP disabled

The apply network settings merely updates unattend.xml (or whatever the approrpiate unattend file for the TS is). Moving it to the end is essentially a no-op because the unattend file has already been used during setup. I'm not a networking expert, but it's not STP that you have to disable, you must enable STP portfast on the switch port. Not sure if disabling STP altogether will effectively result in the shorter port enabling time or not. Have you verified the network cable and the other physical networking components? I know this sounds trivial, but I've seen bad cables cause weird behavior like this before. Have you tried a different switch?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi Jason thanks for coming back, Ive tried connecting into 2 different switches (on the same subnet) and have used a different cable in each one. I though it may be worth posting the task sequence steps to make sure they are in an order that makes sense to the end result we are trying to get, just in case there is anything silly Ive got out of order or not configured correctly - ------------------------------------------ Restart in WinPE Format and Partition Disk (2 partitions, both NTFS quick format) - System Reserved (Primary, 100mb, make this boot partition ticked) - OS (Primary, 100% of remaining space) Prompt for machine name (runs GetComputerName.vbs to get name variable) Apply System Reserved/Bitlocker Image (apply data image, image 1-1, next available formatted partition) Apply Windows 7 x86 Image (apply OS image, image 2-2, next available formatted partition) Apply Optiplex Combo Driver Pack Apply Windows Settings (user, organization and local admin password set) Apply Network Settings (entered domain and join account, left OU blank to join Computers container) Setup Windows and ConfigMgr ------------------------------------------ In the meantime though I have a service request raised with the SCCM team at Microsoft and have sent them over all the relevant log files to go through to see what they can come up with, thankfully I was able to use one of our last remaining service requests for the year!

Have you tried reviewing the DHCP logs or setting up a sniffer to watch/monitor the DHCP traffic?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Could this be related to the joindomain account ?