Hi, I'm experiencing something weird. my MDT 2010 U1 TS doesn't join HP Compaq 6200 & ProBook 6460b to the domain when I deploy Win 7 x64. It works for x86. I'm using drivers packages and my WinPE have all drivers (same version x86 and x64). I didn't enter my domain informations in the CS.ini, I only use the "Apply Network Settings step for the domain. It's configured correctly with the SCCM account to use to join the domain. My computers account are created manually in a OU before do the OSD (not a container). I did F8 during the TS and the computer have an IP and I'm able to ping it all the time during Here is the log in advertisement status in SCCM: Severity Type Site code Date / Time System Component Message ID Description Information Milestone CTX 07/06/2012 9:30:05 AM COMPVALERIE Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Apply Network Settings) in the group (PostInstall) with exit code 0 Action output: ==============================[ OSDNetSettings.exe ]=========================== Command line: "osdnetsettings.exe" configure Setting %SystemRoot% to "D:\Windows" Loading existing answer file "D:\Windows\panther\unattend\unattend.xml" Configuring global network settings Join type: 0 Joining domain: sa.domain.com Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "amd64" DNS domain: DNS domain search order: IP filter sec enabled: false No adapters found in environment. Performing global configuration only. Writing configuration information to D:\Windows\panther\unattend\unattend.xml Successfully saved configuration information to D:\Windows\panther\unattend\unattend.xml Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings finished: 0x00000000. For some others computers able to join the domain, I have the same results in the advertisment status log file. Here is some log from the BDD.log: Loaded D:\Windows\panther\unattend\unattend.xml zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) Merge specified, but D:\_SMSTaskSequence\WDPackage\Control\\Unattend.xml wasn't found, unable to merge zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) Property UPGRADE is now = false zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) Property ComputerName is now = COMPVALERIE zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) No value found for FullName zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) No value found for OrgName zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) No value found for ProductKey zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) No value found for JoinDomain zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) No value found for MachineObjectOU zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) No value found for JoinWorkgroup zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) No value found for DomainAdmin zticonfigure 07/06/2012 9:30:06 AM 0 (0x0000) Here is the netsetup.log file: 06/01/2012 09:53:29:714 ----------------------------------------------------------------- 06/01/2012 09:53:29:714 NetpDoDomainJoin 06/01/2012 09:53:29:714 NetpMachineValidToJoin: 'COMPVALERIE' 06/01/2012 09:53:29:714 OS Version: 6.1 06/01/2012 09:53:29:714 Build number: 7601 (7601.win7sp1_gdr.110622-1506) 06/01/2012 09:53:29:714 ServicePack: Service Pack 1 06/01/2012 09:53:29:807 SKU: Windows 7 Enterprise 06/01/2012 09:53:29:807 NetpGetLsaPrimaryDomain: status: 0x0 06/01/2012 09:53:29:807 NetpMachineValidToJoin: status: 0x0 06/01/2012 09:53:29:807 NetpJoinWorkgroup: joining computer 'COMPVALERIE' to workgroup 'WORKGROUP' 06/01/2012 09:53:29:807 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name 06/01/2012 09:53:29:838 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE] returned 0x0 06/01/2012 09:53:29:838 NetpValidateName: name 'WORKGROUP' is valid for type 2 06/01/2012 09:53:29:979 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0 06/01/2012 09:53:30:057 NetpJoinWorkgroup: status: 0x0 06/01/2012 09:53:30:057 NetpDoDomainJoin: status: 0x0 Now the thing weird is the smsts.log file: Found network adapter "Bluetooth Device (Personal Area Network)" with IP Address 0.0.0.0. TSMBootstrap 07/06/2012 9:45:23 AM 2292 (0x08F4) Found network adapter "Intel(R) Centrino(R) Advanced-N 6205" with IP Address 0.0.0.0. TSMBootstrap 07/06/2012 9:45:23 AM 2292 (0x08F4) Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 0.0.0.0. TSMBootstrap 07/06/2012 9:45:23 AM 2292 (0x08F4) During the TS a I did F8 and it get a IP address and I'm able to ping the servers but why in the log I don't see an IP ? What do I need to fix this ? And Why the netsetup.log file see WORKGROUP instead of the domain ?

Hi, This definitely looks like a driver issue to me, you may see an IP if you hit F8 in WinPE but if the driver package does not contain the correct x64 drivers the OS will not get connectivity and join the domain when it restarts into the setup phase. As its working for your x86 builds this adds weight to my theory too I think. If you double check you have the correct x64 drivers in your driver package I think you should have some success, its common for hardware vendors to release separate drivers for both x86 and x64. Also check the log files in C:\Windows\Panther\UnattendGC any errors during the windows setup phase are logged in here too.

Hi, Thank, I didn't think to look in C:\Windows\Panther\UnattendGC. I can see error in setupact.log and setuperr.log about unable to join domain. I will check the x64 driver in the package. But how to explain that at the end of the deployment on the computer I don't see any devices missing drivers.

Same problems with updated x64 drivers in the drivers packages

this is the error in setuperr.log [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355] [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b

Any others suggestions ?

Error 1355 = The specified domain either does not exist or could not be contacted. So it's either DNS/WINS or something local on the machine with the drivers or ip. Did you open a commandbox (F8) to test the connectivity?My Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude

I only have DNS, no WINS. And the same TS work on another computer. And yes I have a IP address when I press F8. The same driver I use in the WinPE is used in the driver package.

When you say it works on another computer, does that computer have identical hardware? Specifically, does it have an identicial NIC? If not, then that's not a valid comparison. When are you checking if you have an IP address? Before or after the Setup Windows and ConfigMgr task? Before is meaningless because that's in PE. What kind of tasks are you usin to deploy drivers in the TS?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

no sorry, not the same hardware. I check the IP before and after "Setup Windows and ConfigMgr" task. During the Setup Windows and ConfigMgr task even when I do Shift+F10 i don't get a pop up. Here is the logs files: http://sdrv.ms/LA7DCc I use the Apply Drivers package to deploy drivers. I use a MDT Task sequence.

Looking at the bdd.log I would assume that you simply haven't configured the appropriate settings for a domain join. Check the log at the ZTIConfigure component and you will see, that it doesn't have any values available to update the unattend.xml. How did you configure this information? In the Apply Network Settings step or via cs.ini? If in cs.ini, can you please supply the cs.ini for verification? Regards Maik

Hi, I this is normal in the bdd.log when using the Task Sequence MDT join domain function rather than the cs.ini file. I'm convinced it's driver related, may I suggest as a test removing the x86 NIC drivers for the model you are testing with and just leaving the x64 drivers for a test. I normally split the x86 and x64 driver packages and add a custom variable with the architecture in and set a condition to only apply the relevant x86 or x64 driver package. When the TS has finished can you ping the domain/join the domain manually OK?

@Maik, it is the correct settings for the join domain. As it works on other model. It is configured in the Apply network settings step.. @Basty_ss. My drivers packages are separated. I didn't mix the x64 with x86 drivers.

@jason I do have an ip at the Setup Windows and ConfigMgr task

Guys I have more news. I did a test at my secondary site on the same hardware. the exact same model and it works. the computer is added to the domain. I don't understand why this 2 models don't get added to the domain at my primary site. Other models work fine... Any ideas ?

The error message is pretty clear though. Just because you have an IP, doesn't mean the client can properly locate a DC and resolve its IP address. These are all DNS dependant. How are you verifying that you have an IP after (and at) the Setup Windows and ConfigMgr task? Did you also verify name resolution? This makes sense that it works in one location and not another because different network configurations are in play at each. Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Jason, I understand what you're saying. It was my first guess when i checked the log. But as I said before it works for other models for the same TS. Only these 2 models don't join the domain (HP Compaq 6200 & ProBook 6460b). I changed the drivers but same results. I tried another test. I added the task "Join domain or Workgroup" just after the Setup Windows and ConfigMgr task and it worked. they joined the domain. I still don't understand.

The Join Domain or Workgroup task is different than joining the domain during Windows Setup though, its post OS install. There are many different reasons why the network layer may not be responding correctly including bad network cables, bad switch, STP Portfast, DHCP misconfiguration, etc. etc. It's very difficult to troubleshoot at this stage in Windows Setup also. Pressing shift-F10 during setup to get a command prompt is the best way to do this.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Ok, I'll check that

I'm not able to get a command prompt by pressing shift-F10 during setup. I'm trying when I see "Setup is applying system settings"...

I have exactly the same problem here: - SCCM 2012 - the same "OS install" Task sequence works on VMWARE machine, but not on a Probook 6560b. We tried to use lots of driver version for the "Intel 82579V" network card. At the moment, we use : Intel(R) 82579LM Gigabit Network Connection v11.16.96.0, witch is also for our "82579V" card compatible. I also suppoese that this is a driver isue, but i getting crazy and can't find a solution. Did anybody solved this problem?? Many thanks in advance.

Did noone got the same problem? I am still searching for a resolution.

I finally solved the problem. I don't know what was wrong. I created a new task sequence, new driver (Intel(R) 82579LM Gigabit Network Connection v11.15.16.0), new driver package with only this network card driver into it. Then it worked.