Hello, I have created a Task Sequence to Build and Capture a base WIM image. I am trying to apply this image in another Task Sequence (on a Lenovo M90P) and have the machine join the domain and cant get it to work. I always end up with the following in the Task Sequence event log : ==============================[ OSDNetSettings.exe ]=========================== Command line: "osdnetsettings.exe" configure Setting %SystemRoot% to "C:\Windows" Loading existing answer file "C:\Windows\panther\unattend\unattend.xml" Configuring global network settings Join type: 0 Joining domain: XXXXX Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "x86" DNS domain: DNS domain search order: IP filter sec enabled: false No adapters found in environment. Performing global configuration only. Writing configuration information to C:\Windows\panther\unattend\unattend.xml Successfully saved configuration information to C:\Windows\panther\unattend\unattend.xml Configuring "OSDNetSettings.exe finalize" to run on first bootOSDNetSettings finished: 0x00000000. Concerning the No Adapters found in environment, I suspected a problem with the NIC driver so I checked the network settings using F8 and when the join domain command runs, I confirmed that I have an IP address on my network and can ping the DC. Even when the PC boots up at the end (but not on the domain) the network drivers are present and working so I dont think it is a NIC driver issue I also reapplied the NIC driver and added a reboot before adding the computer to the domain, just in case, with no luck I confirmed the account has the rights to add a computer to the domain. Also tried different OU, no OU (so it would go in Computers), still not working. I also checked the following log file and here is what I have C:\Windows\panther\unattendGC\setupact.LOG Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355] Error [DJOIN.EXE] Unattended Join: Unable to join; gdwerror = 0x54b The file C:\Windows\Debug\Netsetup.log has nothing new but what has been done when I first created the base image (joining the domain to WORKGROUP) Does anybody have a clue of what could be the problem? I also tried to recreate and recapture the Base image, with no luck. Could that be a problem with the unattend.xml that I use while creating the base image ? Do I need something special in there ? Or is it really something on the network that could prevent OSD from reaching the DC even if it can be pinged but would not allow OSD to communicate to add the computer to the domain ? I am kinda stuck right now so thanks for all the input you can bring J

Typically this error signifies network, DNS, or WINS issue. Are you using FQDN when you point out you domain name?

Yes !

1355 means the specified domain either does not exist or could not be contacted. I have seen this before when I missed a period in my FQDN.

I double checked the FQDN and it is fine. I actually selected it from the Browse menu. Also, I have read at some places that you might need to include a "." at the end so our domain FQDN is something like : something.company.lan I tried something.company.lan. but I have a red exclamation mark saying the domain name is not valid.

One item to try is grab the unattend.xml before it runs mini-setup. That way you can see if it is being updated correctly with the information you want. I do the below to grab unattend. It assumes command-support is enabled in your boot image. 1. After the image is applied, I press F8 for the command prompt 2. I map a drive so I can copy the unattend (Personal Preference here - I find it easier to view the .xml file from my computer rather than on the machine building) 3. I copy the unattend.xml from <<driveletter>>:\windows\panther\unattend to my mapped drive 4. Once copied, I can open it up to see what was passed to it. I can also test other settings by editing it directly and replacing the one on the build machine. This helped me one time when the join account I was passing was not formatted correctly and prevented the machine from joining the domain.

I actually figured it out ... we have 2 domains so I asked a question before the TS to select the domain. I put that in a variable that I created and called OSDDomainName ... ...the problem is that OSDDomainName is also a system variable used by SCCM and the Task Sequences...so that was the conflict... If I didn't use the variable to join one domain, it worked. As soon as I started using the variable again, it failed... I just renamed the OSDDomainName variable I used to something else and it started working again....!

I actually figured it out ... we have 2 domains so I asked a question before the TS to select the domain. I put that in a variable that I created and called OSDDomainName ... ...the problem is that OSDDomainName is also a system variable used by SCCM and the Task Sequences...so that was the conflict... If I didn't use the variable to join one domain, it worked. As soon as I started using the variable again, it failed... I just renamed the OSDDomainName variable I used to something else and it started working again....!