OSD task sequence computer doesn't join domain - error NetJoinDomain failed error code is [1355]

I am using sccm 2012R2 and trying to deploy a task sequence to Ultrabook UEFI with usb Ethernet adaptor

I have inject network drivers in boot image and in sccm.

Task sequence runs fine till Setup Windows and Configuration. After this step computer reboots and boots in windows with local administrator account. Doesn't join to domain

I have tried ping domain and domain controller during Apply network Settings, I can ping fine and get an ip address as well.

setuperr.log file shows following error:

[Djoin.exe] Unattented Join: NetJoinDomain failed error code is [1355]

I can image other computer using x86 bootimage fine.

It is x64 boot image with UEFI Task sequence which is causing issues for me.

I have tested domain join AD account and able to do domain join same machine manually.

Need advise, not getting anywhere, already spend few days to figure out.

RJ

March 13th, 2015 11:38am

Hi,

Have a look at Windows\debug\Netsetup.log and see if you find any errors there.

Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 11:41am

Actually I have tried checking Netsetup.log and it confuses me as logs are fairly old

Computer name and image is wrong. I am not sure where is this coming from.

I have reimaged this pc more than 20 times but Netsetup.log are similar every time

Here are logs

06/10/2014 15:39:23:844 NetpDoDomainJoin
06/10/2014 15:39:23:844 NetpMachineValidToJoin: 'TEST-TC-7X64'
06/10/2014 15:39:23:844  OS Version: 6.1
06/10/2014 15:39:23:844  Build number: 7601 (7601.win7sp1_gdr.140303-2144)
06/10/2014 15:39:23:844  ServicePack: Service Pack 1
06/10/2014 15:39:23:844  SKU: Windows 7 Enterprise
06/10/2014 15:39:23:844 NetpGetLsaPrimaryDomain: status: 0x0
06/10/2014 15:39:23:844 NetpMachineValidToJoin: status: 0x0
06/10/2014 15:39:23:844 NetpJoinWorkgroup: joining computer 'TEST-TC-7X64' to workgroup 'WORKGROUP'
06/10/2014 15:39:23:844 NetpValidateName: checking to see if 'WORKGROUP' is valid as type 2 name
06/10/2014 15:39:24:031 [000006d4] NetpGetLsaPrimaryDomain: status: 0x0
06/10/2014 15:39:26:902 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as MACHINE]  returned 0x0
06/10/2014 15:39:26:902 NetpValidateName: name 'WORKGROUP' is valid for type 2
06/10/2014 15:39:27:089 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
06/10/2014 15:39:27:276 NetpJoinWorkgroup: status:  0x0
06/10/2014 15:39:27:276 NetpDoDomainJoin: status: 0x0

06/11/2014 08:39:39:593 NetpValidateName: checking to see if 'BASE2014-6' is valid as type 1 name
06/11/2014 08:39:42:713 NetpCheckNetBiosNameNotInUse for 'BASE2014-6' [MACHINE] returned 0x0
06/11/2014 08:39:42:713 NetpValidateName: name 'BASE2014-6' is valid for type 1
06/11/2014 08:39:42:729 -----------------------------------------------------------------
06/11/2014 08:39:42:729 NetpValidateName: checking to see if 'Base2014-6' is valid as type 5 name
06/11/2014 08:39:42:729 NetpValidateName: name 'Base2014-6' is valid for type 5

I have reviewed AD and sccm console and no computer exist with 'TEST-TC-7X64'

March 13th, 2015 12:11pm

Is this the whole NetSetup.log?  If not, please provide the whole log.  Are you trying to join the domain with an unattend.xml?
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 12:29pm

I am not using unattent.xml, just using Apply Network Settings step and configured Domain and Domain join account and verified with password.

I have tried to run domain join from command line during PE but it doesn't work either.

March 13th, 2015 12:45pm

Ok - I know this will sound trivial, but try using the Join Domain or Workgroup step to join the domain.  I've run into the unexplained before using the Apply Network Settings step to join the domain.  You can still use the Apply Network Settings step to apply any network settings on the NIC, if necessary, just don't join the domain in that step.

Give that shot.

Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 12:53pm

Actually I tried using Join Domain or Workgroup step instead Apply Network Settings but it doesn't work either. Task Sequence failed running this step.
March 13th, 2015 2:23pm

Could you provide the entire NetSetup.log via OneDrive, Dropbox, etc?  Could you also take a screenshot of your TS?  1355 translates to "The specified domain does not exist or cannot be contacted".

Also give this a read... http://www.unidesk.com/support/kb/debugging-domain-join-problems-windows-7

 
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2015 4:08pm

I can email you logs but not sure how to upload here..
March 13th, 2015 4:37pm

1355 = The specified domain either does not exist or could not be contacted.

Plus the log above shows a date of 2014 so it's not really up to date, is it?

Free Windows Admin Tool Kit Click here and download it now
March 14th, 2015 12:03pm

You can't join a domain during the WinPE phase of an OSD, only during  the Setup Windows and ConfigMgr step will the computer join the domain: That's a Windows setup process.

March 14th, 2015 12:38pm

Is your Domain: defined correctly: from leaf to root ex: this.may.hurt.you

Is your Account: defined correctly: netbios domain name\accountname

Is the Apply Network Settings step followed by a Run Command Line  step to execute ZTIConfigure.wsf? ZTIConfigure.wsf cofigures the Unattend.xml file with the required property values that are applicable to the OS you're deploying. Information from the Apply Network Settings step are injected into Unattend.xml. This is performed automatically by the task sequence engine, so you're not required to create an Unattend.xml.

Free Windows Admin Tool Kit Click here and download it now
March 14th, 2015 12:56pm

What issue(s) are you having with UEFI via task sequence?

Have you created a GPT partition with the 3 (minimum) partitions required:

EFS (EFI) - 512MB - FAT32

MSR (MSR) - 128MB - Unpartitioned

Windows (Primary) - Remaining Disk Space

March 14th, 2015 1:10pm

Thanks everyone for taking time to reply, I really appreciate.

Torsten-

For some reason I only see logs from 2014 in NetSetup.log, I have already image computer about 20 times, not sure where its getting logs from and computer name in logs is not same my computer name.

Darrick-

We only have Apply network settings step and don't have ZTIConfigure.wsf or unattend.xml step running in Task Sequence.

Could you provide more details how would ZTIconfigure.wsf can be configured.

I haven't tried this so far. Images are working on all other computer Windows 7 32 bit and 64 bit.

Apply network settings contains domain and domain join account information and been verified

And

Yes I do have GPT partitions EFI, MSR and Windows (Primary) as per required.

Partitioning works and Operating system getting installed.

Apply network settings step runs. I can ping domain and sccm servers during this step.

Setup windows and configuration steps initialize and starts downloading client. Then computer reboot and setup client proceed. I have checked using F8 during this step computer not joined to domain. On next reboot computer prompt with Administrator login screen. No domain access.

I am stuck for a while with Lenovo Ultrabook now, can't get it to join to domain.

RJ

Free Windows Admin Tool Kit Click here and download it now
March 14th, 2015 5:43pm

Yes, the Setup Windows and ConfigMgr step does a hand-off to Windows setup at which point it attempts to join your machine to the domain and downloads/configures the client.

I thought the Configure step was added via the template, but if it's not, after the Apply Network Settings and Apply Windows Settings steps, create a Run Command Line  step and name it Configure

Make the following changes:

Also, check the MDT documentation. It tells you what the Configure step (ZTIConfigure.wsf) does.dism /image:c:\mount /get-scratchspace

March 14th, 2015 6:31pm

Wouldn't adding Configure command - cscript.exe %SystemRoot%\ZTIConfigure.wsf in Task sequence require some pre-requisites or MDT configuration package. 
Free Windows Admin Tool Kit Click here and download it now
March 14th, 2015 7:46pm

Yes.

Do you have an MDT integrated ConfigMgr environment?

If not, you must in order to use the MDT Toolkit features in ConfigMgr.

If you don't want to integrate MDT into ConfigMgr, you'll need to use the Join Domain or Workgroup step to provide domain information and to join computers to the d

March 14th, 2015 7:57pm

Actually I have already tried Join Domain or Workgroup step using required domain information and domain join AD account which failed to join domain.

All other computers joins to domain fine using other task sequences, its only UEFI task sequence failed to join computer to Domain.

Free Windows Admin Tool Kit Click here and download it now
March 14th, 2015 8:19pm

Ultrabook I am using have SSD if this could be part of problem.

I also see errors in Panther\UnattendGC\setupact.log 

[DJOIN.EXE] Unattend Join: DebugJoinOnlyOnThisError =[Null]

[DJOIN.EXE] Unattend Join:DsGetDcName failed: 0x54b, last error 0x0, will retry in 5 seconds

[DJOIN.EXE] Unattend Join:DsGetDcName failed: 0x54b, last error 0x0, will retry in 5 seconds

About 20 times

Exit, returning 0x0


March 16th, 2015 2:32pm

0x54b is the same as 1355 ... can you nslookup the netbios domain name and fqdn domain name then?
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2015 3:44pm

I can nslook after task sequence fails and login with local administrator account.

I do see an ip address and domain and able to ping fully qualified domain name but not netbois name during TS network settings step.

I also reviewed smsts.log again and found error

join type:0

DNS domain search order:

IP filter sec enabled: false

No adapters found in environment. Performing global configuration only.

but I still get ip and all dns settings using F8. Just to clarify I am using usb ethernet adaptor.

And also able to join domain with same adaptor plugged in.

March 16th, 2015 5:15pm

Sounds like the adapter doesn't initialize quickly enough after the machine has rebooted and needs some time to get up...

Change the Apply Network Settings -step to join your machine to workgroup. Then put a little pause after the Setup Windows & ConfigMgr step, for example add "Run a commandline" -step with command "ping localhost -n 10" and after that, add "Join domain" -step to actually join the machine to your domain.

Free Windows Admin Tool Kit Click here and download it now
March 17th, 2015 12:19am

Sounds like the adapter doesn't initialize quickly enough after the machine has rebooted and needs some time to get up...

Change the Apply Network Settings -step to join your machine to workgroup. Then put a little pause after the Setup Windows & ConfigMgr step, for example add "Run a commandline" -step with command "ping localhost -n 10" and after that, add "Join domain" -step to actually join the machine to your domain.

  • Marked as answer by RJ09 15 hours 35 minutes ago
March 17th, 2015 4:19am

Sounds like the adapter doesn't initialize quickly enough after the machine has rebooted and needs some time to get up...

Change the Apply Network Settings -step to join your machine to workgroup. Then put a little pause after the Setup Windows & ConfigMgr step, for example add "Run a commandline" -step with command "ping localhost -n 10" and after that, add "Join domain" -step to actually join the machine to your domain.

  • Marked as answer by RJ09 Monday, March 23, 2015 4:07 PM
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2015 4:19am

I have tried adding delay after  Setup Windows & Configure manage step.

Problem is TS starts downloading and installing sccm client package and reboots

Continues with client install and reboots again, brings up Windows login screen.

Task sequence doesn't even go to delay command line step. Just fails.

March 17th, 2015 10:42am

Any chance that the client installation fails? Examine ccmsetup.log.
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2015 10:57am

TS did write that he using a USB network adapter. 

Have you made sure that it is installed when SCCM tries to contact the domain?

March 17th, 2015 11:47am

Yes, I can ping site server during network settings and setup Windows and Configuration step.
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2015 11:58am

I am going with Narcoticoo's suggestion above. The USB NIC doesnt initialize in time for the TS to kick off after booting into Windows.

We have this issue on the Lenovo Yoga and USB Ethernet adapter on Win7x64.

https://social.technet.microsoft.com/Forums/en-US/260cb3a4-65ee-4adb-b04a-b11d14fd8fff/not-joining-domain-during-osd?forum=configmanagerosd

Can you try the steps there to work around it?

March 17th, 2015 12:07pm

I have looked at it before Daniel, but using script with domain user and password would be a security issue.
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2015 12:25pm

Dont use the script, use an additional 'Join domain' step, like I did. You use the same credential box as the 'Apply Network Settings' step. The problem I see is that if you still get a failure on the Setup Windows and ConfigMgr step, you will still have to fix that failure.
March 17th, 2015 12:28pm

I have tried Join domain step as well but same results, Thanks Daniel
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2015 9:10am

I have tried Join domain step as well but same results, Tha
March 19th, 2015 12:45am

Yes Narcotico, I tried all different options with Apply Network Setting but no luck!!
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2015 9:22am

Well that's weird... Could you post a screenshot of your task sequence?

I would assume that if the network is working correctly, the "Join Domain" -step would work just fine, unless you misspelled the credentials used there. "Apply Network Settings" -step simply passes the values for unattended.xml that get's processed during "Setup Windows & ConfigMgr" -step.

Does this same sequence work correctly on different model?

March 20th, 2015 12:06am

Thanks everyone,

Domain join appears to be working now after following Narcoticoo's advise. It failed first attempt

I tried rebuild Task Sequence with Apply Network Setting step to join WORKGROUP and add Domain join step right next to Setup  and configure windows without adding any delay or restart.

I will do further testing and will post results.

I really appreciate your time and great thanks..

RJ

Free Windows Admin Tool Kit Click here and download it now
March 20th, 2015 10:57am

Domain join working now with usb Ethernet adaptor fine.

Thanks everyone for advises and help.

Domain join is working but none of application installing after. SMSTS.log shows following errors.

It started happening just now..

Execution engine result code: Success (0) TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
Cleaning Up. TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
Removing Authenticator TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
Cleaning up task sequence folder TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218) TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
Failed to delete directory 'C:\_SMSTaskSequence' TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,6675) TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
SetNamedSecurityInfo() failed. TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
SetObjectOwner() failed. 0x80070005. TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,6772) TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 23/03/2015 10:36:56 AM 2348 (0x092C)

I got more work to do now..

March 23rd, 2015 12:12pm

Issues with task sequence resolve after changes Application properties

Application properties>General Information.

Selected check box - Allow this application to be installed from the install Application task sequence action without being deployed.

Task Sequence works like a charm. 

Thanks

Free Windows Admin Tool Kit Click here and download it now
March 24th, 2015 12:35pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics