Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 17, 2014 2:49 PM
Hello,
I am having a strange issue with one model of laptop. It is a Lenovo Yoga that uses USB 3.0 -> Ethernet dongle to PXE. In other words there is not a "true" NIC on the laptop. I do get to PXE and I do get to choose my task sequence. I have made sure I have an IP Address before, during and after the "Apply Network Settings" step. I have checked the unattended.xml to make sure my account is correct. Below are the logs from UnattendedGC and Debug (Setuperr.log, Setupact.log, NetSetup.log)
Setuperr.log
2014-04-16 13:08:56, Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]
2014-04-16 13:08:56, Error [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b
Setupact.log
2014-04-16 13:01:56, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds... (a lot more after this)
2014-04-16 13:08:56, Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]
2014-04-16 13:08:56, Error [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b
NetSetup.Log
03/13/2012 08:12:20:156 NetpDoDomainJoin
03/13/2012 08:12:20:156 NetpMachineValidToJoin: 'MININT-9L412CG'
03/13/2012 08:12:20:156 OS Version: 6.1
03/13/2012 08:12:20:156 Build number: 7601 (7601.win7sp1_rtm.101119-1850)
03/13/2012 08:12:20:156 ServicePack: Service Pack 1
03/13/2012 08:12:20:203 SKU: Windows 7 Enterprise
03/13/2012 08:12:20:203 NetpGetLsaPrimaryDomain: status: 0x0
03/13/2012 08:12:20:203 NetpMachineValidToJoin: status: 0x0
03/13/2012 08:12:20:203 NetpJoinWorkgroup: joining computer 'MININT-9L412CG' to workgroup 'Windows7'
03/13/2012 08:12:20:203 NetpValidateName: checking to see if 'Windows7' is valid as type 2 name
03/13/2012 08:12:20:234 NetpCheckNetBiosNameNotInUse for 'Windows7' [ Workgroup as MACHINE] returned 0x0
03/13/2012 08:12:20:234 NetpValidateName: name 'Windows7' is valid for type 2
03/13/2012 08:12:20:234 NetpSetLsaPrimaryDomain: for 'Windows7' status: 0x0
03/13/2012 08:12:20:250 NetpJoinWorkgroup: status: 0x0
03/13/2012 08:12:20:250 NetpDoDomainJoin: status: 0x0
I know NetJoinDomain failed error code is [1355] is a communications error, but I am not sure how it is since I don't lose network along the way. I also understand this could indicate a DNS/WINS issue but we have other models loading fine.
The odd thing to me is that the deployment installs the applications in the Task Sequence, so my NIC doesn't appear to be the problem. I have not changed the order in the Task Sequence from the default order of steps so Network Settings is still before Drivers are applied.
All replies (13)
Friday, April 18, 2014 4:43 PM âś…Answered | 1 vote
This resolves my problem for Windows 7 and SCCM 2012 SP1 CU3
Create a program and the string is cscript.exe filename.vbs
Joins the domain after the PC reboots.
Thursday, April 17, 2014 3:03 PM
The Apply Network Settings step is only manipulating the unattend.xml file with the settings specified; it's not actually joining the machine to the domain at that point, so having an IP address at that phase has no direct bearing on the domain join. The actual domain join occurs when Windows Setup runs ("Setup Windows and Configuration Manager" task), and the most common cause for not joining the domain is missing or invalid network driver.
The Apply Driver Package task is likewise simply putting the files in place for Windows Setup to utilize during PnP detection when Windows Setup runs, so if the NIC driver for the USB3>Ethernet dongle driver is not being loaded properly the domain join will fail.
Thursday, April 17, 2014 3:21 PM
So my problem with this is the "Setup Windows and Configuration Manager" step completes and all following software installs happen. I would have a network connection in order for this to happen. When the task sequence completes I have a working agent and able to deploy to it and it is reporting.
Thursday, April 17, 2014 3:40 PM
OK, I wanted to clarify regarding the Task Sequence steps and order in relation to the actual domain join.
The NetSetup.log you posted only shows the original items from your image build and capture; more recent and relevant information will be further down in the log.
Based on your OP I'm assuming this exact Task Sequence is being used to image other machines and join them to the same domain and same OU location without any issues?
Thursday, April 17, 2014 3:54 PM
I use this task sequence to test new builds so that I can distribute to the local server only and test the installs. New builds in this case means driver packs. As far as this working, I did have it working with another model a week ago that I added the drivers. I am applying only drivers needed for the hardware by using a WMI Query and using a specific driver pack.
I can distribute the drivers out to the other sites so that I don't affect other techs working in other areas and test the install based off the normal task sequence that is run. It will take me a while to give results.
Thursday, April 17, 2014 7:04 PM
Retried with my default task sequence and the NetSetup.log is not changing. The NIC must be initializing too slow, because like I said the agent and applications are installing.
Friday, April 18, 2014 4:31 PM
Can confirm we have the exact same issue on our Win7x64 builds with the Yoga and the USB ethernet dongle. However, we do not see this issue on the Win8x64 builds.
There is only the initial release of the USB ethernet adapter, so no updated driver and no BIOS update to the Yoga. Since it is Win7 specific though, it sounds like its either driver or OS related.
We haven't opened a call with Lenovo yet but it is a relief to know other users are having the issues. Interestingly enough, when we first got the Yoga back in December, we didnt see these issues.
Daniel Ratliff | http://www.PotentEngineer.com
Friday, April 18, 2014 4:35 PM
I did try an older driver, it caused me more problems. I am testing a VB Script now to do the domain join. If it works I will post the weblink to it. It isn't the most secure way to do this because it does hold the username/pass in plain text though.
If you have R2 or MDT you can use powershell to do it too.
$domain = "domain"
$user = "domain\username"
$password = "password" | ConvertTo-SecureString -asPlainText -Force
$credential = New-Object System.Management.Automation.PSCredential($user,$password)
Add-Computer -DomainName $domain -Credential $credential
Works when run from the OS, so I imagine it would work if you can successfully execute it during OSD.
Edit: I also have communications open with a couple Lenovo Field techs and in-house techs about this. If I get anything useful from them I will let you know. This is the other driver I tried.
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21129
Friday, April 18, 2014 5:59 PM
Daniel,
How do you handle using the same usb/Ethernet adapter on multiple machines? Like do you delete the SCCM record when the machine is done being loaded and let it rejoin using its Wireless MAC? Is there a way to avoid using the MAC as an identifier? Like use the UID instead as a permanent solution.
Thanks
Friday, April 18, 2014 6:55 PM
That has been discussed a few times before and there is not a way I have seen to force it to use the UUID as opposed to the MAC address.
We dont have too many issues as long as we are fine with the hardware inventory updating the device record one the machine completes its hardware inventory.
I would be lying if I said we have never had to delete the record out of the console though, but its definitely far from a widespread issue for us. As we roll more slate/tablet devices in the future though I know that issue will grow.
Daniel Ratliff | http://www.PotentEngineer.com
Thursday, June 5, 2014 5:26 PM | 2 votes
Just found a little easier workaround for our environment. Special thanks to Michael Niehaus and the mdtosd email list over at myITForum.com for the suggestions.
There is actually a Join Domain task sequence step that I put shortly after my 'Setup Windows and ConfigMgr' step to try joining the domain again. I am using a WMI query to filter it to only run when its not already on the domain.
select Domain from win32_computersystem where Domain != 'domain.com'
I just tested on the Yoga and it worked great!!
Daniel Ratliff | http://www.PotentEngineer.com
Thursday, June 5, 2014 5:28 PM
Good deal. So far the solution I have works, unless there is an AD object of the same name.
Tuesday, October 9, 2018 6:57 PM
Adding a "Join Domain" step after "Setup Windows and ConfigMgr" worked for me, only the query you posted was evaluating as false for me, since the win32_computersystem Domain also returns the workgroup name. So I ended up using this:
select * from win32_computersystem where PartOfDomain = 'False'