Domain Join issue During OSD

Question

Hi everyone,

Hope everyone is doing great and being safe!

Need your expertise with an issue I am facing during domain join during OSD where clients are failing to join to the domain during OSD.

Upon checking the netsetup log we found the below error:

NetpValidateName: checking to see if 'XYZ.global.corp' is valid as type 3 name
10/07/2020 16:09:48:459 NetpValidateName: 'XYZ.global.corp' is not a valid NetBIOS domain name: 0x7b
10/07/2020 16:09:48:459 NetpCheckDomainNameIsValid for XYZ.global.corp returned 0x54b, last error is 0x0
10/07/2020 16:09:48:459 NetpCheckDomainNameIsValid [ Exists ] for 'XYZ.global.corp' returned 0x54b
10/07/2020 16:09:48:459 NetpJoinDomainOnDs: Domain name is invalid, NetpValidateName returned: 0x54b
10/07/2020 16:09:48:459 NetpJoinDomainOnDs: Function exits with status of: 0x54b

10/07/2020 16:09:48:459 NetpJoinDomainOnDs: NetpResetIDNEncoding

A surprise to our beliefs when we use the same Account and password and try to join the domain manually it was successful and it worked. Other logs such as Setuperr are not created and we have the above error only documented multiple times as a final error too.

If someone faced this issue kindly reply so your's experience and expertise could prove to be helpful for me to fix this issue.

Regards,
Shashi Dubey

Answer 1

The above is something that is happening during Windows setup. As noted, it's difficult at best to determine why the domain name is not found when the join is attempted during Windows which occurs during the Setup Windows and ConfigMgr task but network related connectivity issue is a typical culprit.

As for locating a DP and MP without joining the domain, yes, ConfigMgr doesn't require systems to be domain joined. You cannot move or disable the Setup Windows and ConfigMgr task though as other items in TS depend on Windows setup being completed successfully. You could change the Apply Network Settings task to not specify a domain and then add a Domain Join task to the end of the TS. I don't suggest doing this though as it is simply addressing a symptom and not the issue.

Answer 2

This is unrelated to any username or password. This is most likely DNS or network related. My guess is that the network port isn't passing traffic at the time the domain join is attempt by Windows setup. Given that this is happening during Windows setup, it'll be quite difficult to troubleshoot and you may have to actually review the network traffic (or lack thereof) to determine a root cause here.

Answer 3

Hi Jason,

Thanks a bunch for your reply and time !!

So just want to be sure from the above error code everything seems to be fine from the SCCM perspective and the issue is related to the DNS or port communication that should be investigated from the networking perspective?

Just small assistance on this cause I am not sure of the reason for this whenever we try to add the computer to the domain manually it would always give us the success only this is happening during OSD in the task sequence.

Also, if we disable this step or move it in the last part of the task sequence would still my client be able to connect to MP and DP for the content location and policy if they happen to not join to the domain?

Regards,
Shashi Dubey

Answer 4

Hi Jason,

Your pointers are extremely valuable and a guide for me to move ahead with the troubleshooting. Like you guided would involve network to look at the issue related to domain join or DC connectivity.

Meanwhile, as you instructed would change "Apply Network Settings" to not join any computer to domain but keep it as a workgroup and would try to give it a try at the later stage at the end of the task sequence.

until we find the root cause our we could go for the domain join manually and this way our operation would be working too until the root cause is identified and fixed.

My sincere thanks for your guidance and expertise.

Hope to have your assistance going ahead in other issues too.

Stay safe and take care.

Regards,
Shashi Dubey