Computers not joining our Domain during Sysprep

[Wayne Workman]

@kyle.heath Please use the code wrapping tool when posting logs. It looks like this in the editing area: </>
Later in the log, the health of the FOG Client looks fine, but I see this line:

1/10/2017 10:30 AM HostnameChanger Logon failure: unknown username or bad password, code = 1326

That is a pretty clear error, bad username or password. Doublecheck your active directory settings for this particular host, also doublecheck your domain defaults in FOG Configuration -> FOG Settings -> AD Defaults

[kyle.heath]

@Wayne-Workman Alright I thought I had tried this already but I’ll double check. I’ll change it and try to capture the image again.

[kyle.heath]

@Wayne-Workman I double checked them and updated them…it still isn’t joining the domain. Any other suggestions?

[Wayne Workman]

@kyle.heath it has to be a user or pass or domain name issue. There has to be a typo or something. Unapply and reapply the domain settings to the problem system.

[kyle.heath]

@Wayne-Workman Maybe I need to do something on the actual FOG server? Is there a way to update the info on that to make sure it works correctly. I just restarted the server and logged in fine though.

[kyle.heath]

@Wayne-Workman Ok I think there is something wrong with my FOG server and the database…I need to get both of them on the same page. I was having issues so I reverted to an old snapshot I had of FOG. Whats the best way to get both the database and FOG working correctly together.

[Wayne Workman]

@kyle.heath is the database not on the same box that runs the web interface? Typically they are the same box for small setups. What makes you think they aren’t working right?

The Below stuff I said about typos and reapplying settings - I was talking about doing those things in the fog web interface. web interface -> host management -> search for host and then click it -> active directory and web interface -> fog configuration -> fog settings -> active directory defaults

[kyle.heath]

@Wayne-Workman Because I added a Windows10x64 image and it’s not showing up in the images area on the FOG server.

[Wayne Workman]

@kyle.heath the files don’t exist for an image in /images/<image path> until capture completes.

[kyle.heath]

@Wayne-Workman Ahh ok so I reverted my FOG server back and I was going to do a fresh update. It says I’m on

I’m trying to use git to update but it won’t work…anyway I can use SVN? I can’t find a SVN guide. When I use git it fails when trying to gather the repository.

[kyle.heath]

@Wayne-Workman Another question…should my setupcomplete be a batch file or a windows command script? Does that matter? It looks like I’ve been using a batch file.

[Joe Schmitt]

@kyle.heath you need to fix this error:

1/10/2017 10:30 AM HostnameChanger Logon failure: unknown username or bad password, code = 1326

before anything else. You don’t need to keep on re-capturing or deploying either. Just set up a computer with the client, monitor the fog.log file until you fix your credentials.

[kyle.heath]

@Joe-Schmitt Will the fog.log file change as I change the credentials. If so can I just change them on my VM or do I need to use a normal computer.

[Wayne Workman]

@kyle.heath You change them in the places I described below, in the fog web interface. Yes the log will reflect changes live - every time it checks in it will update the log.

[kyle.heath]

So it looks like I found the issue…for some reason my setupcomplete was changed to a batch file…it needed to be a windows command script file…not sure how that happened, but after changing it…it joined the domain.

[Wayne Workman]

@kyle.heath That makes zero sense.

[Joe Schmitt]

@Wayne-Workman setupcompletes are .cmd he probably had .bat

[kyle.heath]

@Joe-Schmitt Yep I had bat for some reason…No idea how because I used to have.cmd