I am also having issues with Windows 10 and sysprep, but not because of the internet access. Windows by default restricts the built in administrator from using edge for security reasons (I assume), so you may have internet access, but not a browser to use. I get around this by saving another browser installer on a network share and browsing to that.

@Wayne-Workman Alright, I will have to test it out. Thanks!

@Wayne-Workman when you create the image, do you use the built in audit mode or create a local account?

@Wayne-Workman you didn’t sysprep? What type of image did you set in the configuration? Also, Windows doesn’t freak out when imaged to other models??

@Avaryan yes and those accounts will show before the fog service joins the computer to the domain

thanks for the help, host joined domain successfully. Now however I have encountered this issue with every domain account when trying to log into that machine. Anybody seen this before? I’ve googled around for it, but apparently doesn’t happen much in a domain.

^ this may be the issue…

I am attempting to get the fog service to auto join the computer to my domain on windows 10. After imaging it will reboot a few times and then remain on windows 10 multi user login, not domain login. Upon checking the error log (shown below) I believe it might have to do with the account specified in the web interface for domain joining? Any help on this would be greatly appreciated.

@Scott-Adams thank you, I am aware, but I prefer the third party browsers (as I’m sure we all do) and install them as part of my image.

I am running fog 1.3 RC8, to prepare for an image I install the fog service and then sysprep from audit mode. However, I constantly run into an error where windows 10 will not boot after these steps. It will start the windows loading screen and then display the error shown below. I am running Windows 10 Enterprise (build 1607)

I am also having issues with Windows 10 and sysprep, but not because of the internet access. Windows by default restricts the built in administrator from using edge for security reasons (I assume), so you may have internet access, but not a browser to use. I get around this by saving another browser installer on a network share and browsing to that.