Computers not joining our Domain during Sysprep

[kyle.heath]

I’m also using this command to run sysprep.

cd c:\windows\system32\sysprep
sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml

[Tom Elliott]

Is your Windows 10 image an OEM type or Volume License type?

[kyle.heath]

@Tom-Elliott It’s a Volume License . Windows 10 EDU we use a KMS key.

[kyle.heath]

Been messing with the setupcomplete and nothing I change fixes the issue?

[Tom Elliott]

@kyle.heath Where is your setupcomplete.cmd file located on the post-sysprepped system?

[kyle.heath]

@Tom-Elliott I stick it in the C:\Windows\Setup\Scripts folder

[Wayne Workman]

@kyle.heath as Joe said, please post the entire C:\fog.log We can’t help much without knowing what’s in it.

[kyle.heath]

@Wayne-Workman I did. There was very little in the FOG log.

That’s all that was in it.

[kyle.heath]

Also…not sure if this matters but I am trying to “capture” my image from my VM. I created a windows 10 VM and set it up the way I wanted it. I fully registered it…and I chose join domain as 1 of the options it gives you when your full register a client. I put the unattend.xml in the sysprep folder and the setupcomplete in the scripts folder.

[Wayne Workman]

@kyle.heath And you’re looking at c:\fog.log ? If that’s literally it, reinstall the fog client. You should have more in the log just from when you installed it and rebooted before capture.

[kyle.heath]

@Wayne-Workman I reinstalled FOG and now there is no file at all. I’ll post a pic. Since I reinstalled FOG should I try to recapture now?

[Wayne Workman]

@kyle.heath No. One of the steps you should always do before capture is verify the FOG Client is functioning properly. The way you would do this is look into the fog log for errors. You should see a normal log before you start preparing the system for capture.

Check inside of Program Files for a folder called fog, one of them should have it. Look for a fog.log in there.

Also what version of Windows? And is this a fresh installation of windows or an upgrade or an old image you updated?

[kyle.heath]

@Wayne-Workman Alright the only .log file in the FOG folder is one called zazzles. Here is what’s inside.

[Wayne Workman]

@kyle.heath Please if you are able, copy/paste the logs. This makes the errors you post search-able so others can find them. Plus I can’t see the entire error in that photo.

[kyle.heath]

@Wayne-Workman Here is the full log. I can’t copy and paste because it’s from a VM.

[Wayne Workman]

@kyle.heath What distribution and version is your FOG Server running on?

[kyle.heath]

@Wayne-Workman

and we are using Ubuntu 14.04.2

[Wayne Workman]

@kyle.heath See if you have firewall or apparmor on the server. If you do, disable those at least temporarily. Also try to web-browser from the VM to the fog server and see if that works.

[kyle.heath]

@Wayne-Workman Yeah I can log into my fog management console using google chrome on my VM.

[kyle.heath]

@kyle.heath I may try to revert my VM to an earlier state and see if that helps.