Unable to join deployed PC to domain

[cwu_doug]

Hi,

After deploying a Win10 machine, I had configured Active Directory within Fog management:

Domain: domainName.local
Join after Deploy: ticked
OU: Left blank
Username: domainName\AdminUsername
Password: AdminPassword
Password legacy: Left blank
Name change: ticked

I get the following message:

HostnameChanger Logon failure: unknown username or bad password, code = 1326

I checked other forums and I tried without domain in username still same issue. I used Add-Computer CMDlet and joins the PC manually with no issues.

There is no NetDom command in Windows 10, so not sure if this may be an issue?

Otherwise can anyone see any issues?

Thanks

[Sebastian Roth]

@cwu_doug See my post here: https://forums.fogproject.org/post/131725

[cwu_doug]

@sebastian-roth Thanks, I did use domain\username and also username and still same issue.

Using Fog 1.5.9
Fog client 0.12.0

When I use the Fog debugger, the FogCycle.txt returns the ADUser field as “Domain.local\\username”

Should that be correct? I am using just username in the field on the FOG GUI.

[Sebastian Roth]

@cwu_doug Is this a fully AD or some kind of small business server?

[cwu_doug]

@sebastian-roth We have AD on Win Server 2016, however FOG is running on Ubuntu on XenServer.

Is that what you was asking?

[Sebastian Roth]

@cwu_doug said in Unable to join deployed PC to domain:

We have AD on Win Server 2016

Ok, this sounds like a full AD - not small business stuff.

When I use the Fog debugger, the FogCycle.txt returns the ADUser field as “Domain.local\username”

Yes the FOG server actually prepends the domain to the username: https://github.com/FOGProject/fogproject/blob/master/packages/web/lib/client/hostnamechanger.class.php#L65

Well, I can tell you the domain join is working for many people and the error code 1326 is pretty clear. Must be an authentication issue.

[ayy_nelson]

What is the domain functional level of your DC?

I remember having difficulty with 2008 domain level, and I ended up having to join the domain in powershell instead of the FOG. Notice that domain does not have the .local part of it. That reallllly tripped me up for a while. Alternatively, I learned that you can do username@domain.local… at least when setting the autologin registry setting. I have not tested that in your use case, but it is something new to try

$domain = “domain”
$password = “notpassword” | ConvertTo-SecureString -asPlainText -Force
$username = “$domain\domainadmin”
$credential = New-Object System.Management.Automation.PSCredential($username,$password)
Add-Computer -DomainName $domain -Credential $credential -OUPath “OU=FOGBuilt,OU=Computers,OU=main,DC=domain,DC=LOCAL”

[cwu_doug]

@sebastian-roth OK I see, it actually returns two backslashes “\” between the domain and username. Using FogDebugger

So was thinking was it not parsing through to the client correctly

[cwu_doug]

@ayy_nelson Ah the DFL is Windows Server 2008 R2.

Would you think this would be the sole reason FOG is incompatible with this type of version?

I am looking into running it via a script, but would love to get the domain join on FOG working, if it’s possible!

Thanks again!

[Sebastian Roth]

@ayy_nelson @cwu_doug Thanks a lot for your feedback on this. I didn’t know 2008 DFL is an issue. Will keep that in mind.