SOLVED SCCM Windows 10 standalone media NetJoinDomain failed error code is [1355]

[Gopi Krishna]

Hi,

I am trying to create a stand-alone media for windows 10 using SCCM 2012 integrated with MDT.

The media does help in the machine joining to domain. when i checked the log file in C:\Windows\Panther\UnattendGC

Setuperr.log file says:

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



Any help will be appreciated.

Thank you,

 

[Gopi Krishna]

Hello Prajwal Sir,

I am badly in need of a solution for this. Kindly help.

 

[Prajwal Desai]

1355 means DC is not reachable. Could be due to issues in communicating with DC. Did you check %windir%\debug\netsetup.log ?.

 

[Gopi Krishna]

I have uploaded the netsetup.log file. Kindly verify.

 

[Gopi Krishna]

the machine is getting an IP address and based on that IP address, the machine name is assigned.

But still it is not joining to the domain, it is directly taking me to the administrator login screen after the completion of installation.

 

[ferdous anwar]

HI Prejwal. I am having the same issue on dell latitude 5570 model laptop. it worked before under the following settings in bios
Bios version 1.7.3 and tpm 2.0
boot mode UEFI
legacy rom enabled
secure boot disabled
tpm on and activated.

A mate of mine managed to image his 5570 but that laptop had TPM 1.2 and he imaged it using legacy.

SCCM does the task sequence as normal and everything and at the end of it, i get the administrator login. and also the bit locker does not get enabled.

Laptop imaged perfectly and joined to domain about 2 months ago. Then my colleague had an issue and so I re-imaged my laptop to test and since then unable to join to domain. as per the error logs, I had the 1355 error too and seems like the windows wasnt able to communicate to the DC.

Also weirdly, we have optiplex 7010 desktop PCs in our nhs trust and some of them are facing the same issue. but other devices of the same model and same bios and same tpm version joins to domain and everything fine. i cant get my head around it.

 

[Gopi Krishna]

HI Prejwal. I am having the same issue on dell latitude 5570 model laptop. it worked before under the following settings in bios
Bios version 1.7.3 and tpm 2.0
boot mode UEFI
legacy rom enabled
secure boot disabled
tpm on and activated.

A mate of mine managed to image his 5570 but that laptop had TPM 1.2 and he imaged it using legacy.

SCCM does the task sequence as normal and everything and at the end of it, i get the administrator login. and also the bit locker does not get enabled.

Laptop imaged perfectly and joined to domain about 2 months ago. Then my colleague had an issue and so I re-imaged my laptop to test and since then unable to join to domain. as per the error logs, I had the 1355 error too and seems like the windows wasnt able to communicate to the DC.

Also weirdly, we have optiplex 7010 desktop PCs in our nhs trust and some of them are facing the same issue. but other devices of the same model and same bios and same tpm version joins to domain and everything fine. i cant get my head around it.

Hi,

I am having the same issue, Is there any solution for this?

Thank you

 

[ferdous anwar]

Hi,

I am having the same issue, Is there any solution for this?

Thank you

The simple solution is to join it to domain manually. Also the next thing is it make sure it is placed in the correct container in AD as other Win10 devices. That way it will pick up the policies and settings. I didnt know about this until i tried it and it worked perfectly. Run the gpupdate after you move container.

 

[venkateshcme_81]

Dear Team,

is the issue resolved
if so kindly share the resolution pzl...


regards
Venky