Computers not joining our Domain during Sysprep

[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